[
http://jira.codehaus.org/browse/MASSEMBLY-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey closed MASSEMBLY-197.
--------------------------------
Resolution: Fixed
I've added two new flags to the dependencySet: useProjectArtifact and
useProjectAttachments. By default, they are true and false, respectively.
Enabling these flags makes them subject to filtering on includes/excludes, with
the default action to include them (again, only when they are enabled...).
I'm running a deploy build with integration tests, then I'll commit these
changes. Shouldn't take longer than 10 mins.
> 2.2-beta-1 regression, project artifact no longer included in
> -------------------------------------------------------------
>
> 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
> Assignee: John Casey
> Priority: Blocker
> Fix For: 2.2-beta-2
>
>
> 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
