Hi Matt,

Sorry for the late reply

Yes, please create the jiras

Raphaël

2009/4/29 mraible <m...@raibledesigns.com>

>
> I've been using archetype:create-from-project to create archetypes and have
> noticed some issues:
>
> 1. The generated archetype has a version of 1.0-SNAPSHOT. I want the
> archetype's version to be the same as my project.
>
> 2. When I have an empty property (e.g. <jdbc.password></jdbc.password>),
> it's removed from the resulting pom.xml.
>
> 3. When generating a multi-module archetype, the package names in my
> hibernate.cfg.xml are replaced with ${package}. This doesn't happen when
> generating a single-module archetype.
>
> 4. Package expansion doesn't happen for files in a package hierarchy under
> src/main/resources.
>
> 5. I'm unable to set a description for the generated archetype.
>
> 6. Replacing of package names with ${package} seems to work different b/w
> multi-module and single-module projects. In a multi-module project,
> "org.appfuse.webapp" gets replaced with "${package}.webapp". In a
> single-module project, "org.appfuse.webapp" gets replaced with
> "${package}".
>
> 7. TLD files are not scanned for packages to replace.
>
> 8. The web.xml file is not scanned for packages to replace.
>
> I've been able to workaround most of these issues by using Ant to
> manipulate
> the project after it's generated (before installing). Should I enter these
> as issues in JIRA?
>
> Thanks,
>
> Matt
> --
> View this message in context:
> http://www.nabble.com/Issues-with-archetype%3Acreate-from-project-tp23286970p23286970.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Reply via email to