Generator-Mojo: URI Error In Opaque Part

[GoogleCodeExporter]

When running a multi-module build with one module using generator-mojo with 
custom Groovy 
templates on Windows XP and Vista generator-mojo gives a URI parse exception 
unless build is 
done in each sub-module separately.  After digging into the code it seemed like 
something cross-
platform was going on so I ran the template paths through 
File.toURI().toString().  Seems to have 
fixed the problem in our environments.  Modified GeneratorMojo.java attached.

Cheers,

-- Tim

Original issue reported on code.google.com by tful...@dslextreme.com on 18 Nov 2008 at 2:27

Attachments:

• GeneratorMojo.java

[GoogleCodeExporter]

Hey,

Can you give me a sample of that?

I think I have another idea, but I wanna a real sample to check.

VELO

Original comment by velo...@gmail.com on 19 Nov 2008 at 3:57

• Changed state: Accepted

[GoogleCodeExporter]

Hello,

Thanks for getting back to me on this.  Love the work done so far on the 
flex-mojos project.  You guys rock!

Anyway, here's a test project.  Couple of things to note: we're using an 
internal repo with some custom 
dependencies for the BlazeDS artifacts.  You might have to mod the flex/pom.xml 
dependencies to point to  
BlazeDS artifacts in your repo.  Also, a top level build does not fail on Win32 
machines since nothing is 
actually depending on the generated AS objects.  Doing a build in the top level 
gen-mojo will show the error, 
tho.  It would  be nice to have an error while generating fail the build right 
there, but that's another issue :)

Thanks again, VELO.

- Tim

Original comment by tful...@dslextreme.com on 25 Nov 2008 at 3:11

Attachments:

• gen-mojo.zip

[GoogleCodeExporter]

Has there been any progress on this issue?  We are currently using our 
customized snapshot version with the fix 
above for development and have to change to a release version for releases.  It 
would be nice to be able to keep 
up with the your updates as well.

-- Tim

Original comment by tful...@dslextreme.com on 6 Jan 2009 at 10:34

[GoogleCodeExporter]

Fixed, check revision 949, sorry for the delay

Original comment by velo...@gmail.com on 7 Jan 2009 at 12:25

• Changed state: Fixed

[GoogleCodeExporter]

Issue 149 has been merged into this issue.

Original comment by velo...@gmail.com on 10 Jan 2009 at 1:47