[
https://jira.codehaus.org/browse/ARCHETYPE-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed ARCHETYPE-280.
------------------------------------
Resolution: Won't Fix
Please refer to
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.
> Forgets to rewrite package in POM.xml
> -------------------------------------
>
> Key: ARCHETYPE-280
> URL: https://jira.codehaus.org/browse/ARCHETYPE-280
> Project: Maven Archetype
> Issue Type: Bug
> Affects Versions: 2.0-alpha-4
> Reporter: Markus KARG
> Priority: Critical
>
> I am using archetype:create-from-project to produce an archetype. It is a
> smart feature that at time of creation, the package of the resulting java
> package gets rewritten! But this feature is buggy. There are plugins that
> need to have the package named in the POM.xml (like the maven-jar-plugin to
> know the main class, or the maven-exec-plugin for the same reason). The
> POM.xml actually gets rewritten for the artifactId, groupId and version, but
> the configuration of (at least) those two (not uncommon) plugins is not
> rewritten. As a result, the created project will not work. :-(
> I want to propose that the config of (at least) these two plugin gets
> rewritten to reflect the actually configured package.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
