Using archetypes to deeply nest java files

[Scott Ryan <sc...@theryansplace.com>]

I am trying to build out an archetype in support of an appfuse plugin that I
am building for Maven 2.0.  I have the following structure

src/main/java/service/packagename.../service/Manager.java
src/main/java/service/packagename.../service/impl/ManagerImpl.java

I set up my archetype-resources as so:
/src/main/java/service/Manager.java with $package in the package name
/src/main/java/service/impl/ManagerImpl.java with $package in the package
name.

When I ran the archetype with package name com.examplepackage the result
was:

/src/main/java/service/com/examplepackage/Manager.java
/src/main/java/service/impl/com/examplepackage/ManagerImpl.java

both had the package name com.examplepackage

I also tried to use $package.service and $package.service.impl in the base
java files and no substitution took place at all.

I would also like to update any dependencies within the files with the
proper package name for example if the Impl relies on the base then I would
like the following to work:

FILE 1:

Manager.java
package $package.service;

FILE 2:

ManagerImpl.java
package $package.service.impl

import $package.service.Manager;

________________

and have the files placed in the proper location.

Is this possible?  If not does it make sense to place this code in my plugin
and just move and package the files during a setup step?

Thanks for all you help and I hope to publish the appfuse plugin soon.

Scott Ryan
Chief Technology Officer
Soaring Eagle L.L.C.
scott@theryansplace.com
www.soaringeagleco.com
(303) 263-3044



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: Using archetypes to deeply nest java files

[Brett Porter <br...@apache.org>]

It sounds like a bug. Would you like to file it against the archetype
project?

http://jira.codehaus.org/browse/ARCHETYPE

Thanks,
Brett

Scott Ryan wrote:
> I am trying to build out an archetype in support of an appfuse plugin that I
> am building for Maven 2.0.  I have the following structure
> 
> src/main/java/service/packagename.../service/Manager.java
> src/main/java/service/packagename.../service/impl/ManagerImpl.java
> 
> I set up my archetype-resources as so:
> /src/main/java/service/Manager.java with $package in the package name
> /src/main/java/service/impl/ManagerImpl.java with $package in the package
> name.
> 
> When I ran the archetype with package name com.examplepackage the result
> was:
> 
> /src/main/java/service/com/examplepackage/Manager.java
> /src/main/java/service/impl/com/examplepackage/ManagerImpl.java
> 
> both had the package name com.examplepackage
> 
> I also tried to use $package.service and $package.service.impl in the base
> java files and no substitution took place at all.
> 
> I would also like to update any dependencies within the files with the
> proper package name for example if the Impl relies on the base then I would
> like the following to work:
> 
> FILE 1:
> 
> Manager.java
> package $package.service;
> 
> FILE 2:
> 
> ManagerImpl.java
> package $package.service.impl
> 
> import $package.service.Manager;
> 
> ________________
> 
> and have the files placed in the proper location.
> 
> Is this possible?  If not does it make sense to place this code in my plugin
> and just move and package the files during a setup step?
> 
> Thanks for all you help and I hope to publish the appfuse plugin soon.
> 
> Scott Ryan
> Chief Technology Officer
> Soaring Eagle L.L.C.
> scott@theryansplace.com
> www.soaringeagleco.com
> (303) 263-3044
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org