Another guess of mine was that the two given root folders
may be unrecognizable to Cygwin. If you check PATH, Cygwin prefixes all entries derived from Window's Path with
/cygdrive/c/Program Files (x86)/[...]:/cygdrive/c/Program Files/TortoiseSVN/bin:/cygdrive/c/Program Files (x86)/Git/cmd:/cygdrive/c/Users/ak/Development/JBossForge/forge-distribution-1.0.5.Final
But "env | grep forge" tells me it's the case with PATH only. FORGE_HOME is set as on Windows enviroment vars:
And forge does absolutely start! (Just crashing on that missing module.) So that prefix
/cygdrive/c/ might not be a candidate.
While writing I just noticed that the term defining the two root folders
does not look healthy. Colon as path separator and drive indicator should cause trouble here. Is there a way to tell Forge to replace that drive indicator with Cygwin's
One issue is clearly that Cygwin cannot read something like C:\....
It has to be replaced by /cygdrive/c/....
And I guess this problem cascades to Forge.
As an outsider I really don't know how this could be solved. Maybe a special Cygwin-version (or Cygwin-patch) could do that is generally re-prefixing folder terms?
I am stuck with Windows. So are quite a bunch of developers, I think.
Using CMD is a pain Cygwin could ease. So I'm willing to make my contribution in this thread. This would make Forge more attractive to Win-users.
Apart from Cygwin another option would be a "shell inclusion" into Eclipse. Is there already a plan for doing that?
PS: As a newbie to Forge joining the dev-list would be oversized, but I keep it in mind.