You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Stephane Nicoll (JIRA)" <ji...@codehaus.org> on 2007/04/16 14:37:46 UTC
[jira] Commented: (MASSEMBLY-197) 2.2-beta-1 regression, project
artifact no longer included in
[ http://jira.codehaus.org/browse/MASSEMBLY-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93009 ]
Stephane Nicoll commented on MASSEMBLY-197:
-------------------------------------------
+1, not sure that the project artifact should be included by default however. We need to define a clear way to define it (with an option to defined optional classified build(s))
> 2.2-beta-1 regression, project artifact no longer included in <dependencySet>
> -----------------------------------------------------------------------------
>
> Key: MASSEMBLY-197
> URL: http://jira.codehaus.org/browse/MASSEMBLY-197
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Reporter: Max Bowsher
> Priority: Blocker
>
> In 2.1, <dependencySet> included the project artifact itself - i.e., all the jars actually needed to execute the project.
> In 2.2-beta-1, <dependencySet> is omitting the project artifact, so that assemblies that functioned correctly when built with 2.1, fail to execute when built with 2.2-beta-1.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira