saiddfhi / gwt-maven

Automatically exported from code.google.com/p/gwt-maven
0 stars 0 forks source link

Markers and Expansion should be in same directories! #127

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Is this Maven 1 or Maven 2? Maven2, building Curriki.

What steps will reproduce the problem?
1. simply invoke a build that uses the gwt maven plugin
2. be on mac for example, and reboot, this empties /tmp/
3. try build again... obtain a class-not-found GWTCompiler

What is the expected output? What do you see instead?

I would expect it to run again...

I suppose the GWT plugin considers it does not need to reexpand the GWT toolkit 
in /tmp since 
the markers are there still in target.

What version of the product are you using? On what operating system?

1.3.3

Please provide any additional information below.

 Suggestions: put the markers and expansion in same directories.

Original issue reported on code.google.com by paul.lib...@googlemail.com on 17 Jul 2008 at 3:24

GoogleCodeExporter commented 9 years ago
Branch addresses this by doing the expansion with maven dependency plugin and
eliminating the extract and setup goals (if I understand the issue correctly).  
With
the new approach you can specify the directory where expansion happens, and you 
can
tell it whether to overwrite or not (not always in target/gwtBin). 

This branch will get merged to trunk soon, and a new release will happen.  
Leaving
this open and accepted until the branch hits the trunk. 

Original comment by charlie....@gmail.com on 26 Aug 2008 at 7:07

GoogleCodeExporter commented 9 years ago
Fixed as of 2.0-beta22

Original comment by charlie....@gmail.com on 7 Sep 2008 at 10:36