BeanGen: New Feature? Ability to change generated location, not just package

GoogleCodeExporter commented 9 years ago

Is this Maven 1 or Maven 2?
Maven 2
What steps will reproduce the problem?
1. set
<generatorDestinationPackage>global/js/com.comp.proj.GwtStuff</generatorDestinat
ionPackage>
2. mvn clean package

What is the expected output? What do you see instead?
I expected to see the generated output in the folder
target/proj/global/js/.  Instead it was still under target/proj/.  No
configuration error was thrown.

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

Please provide any additional information below.
This works in a stand alone compile script, just not in maven.

Original issue reported on code.google.com by Kawasaki...@gmail.com on 8 Apr 2008 at 9:15

GoogleCodeExporter commented 9 years ago

Original comment by charlie....@gmail.com on 17 Apr 2008 at 4:37

Added labels: Type-Enhancement
Removed labels: Type-Defect

GoogleCodeExporter commented 9 years ago

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

Changed title: BeanGen: New Feature? Ability to change generated location, not just package

GoogleCodeExporter commented 9 years ago

BeanGen no longer maintained/supported (and less important now that GWT
supports Java 5).  We can re-open these if we get a maintainer, but for now
closing as won't fix.

Original comment by charlie....@gmail.com on 10 Nov 2008 at 1:50

Changed state: WontFix

saiddfhi / gwt-maven

BeanGen: New Feature? Ability to change generated location, not just package #100