You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Omer A Kudat (JIRA)" <ji...@codehaus.org> on 2011/01/26 19:13:57 UTC
[jira] Created: (MASSEMBLY-544) DependencySet includes filter not
working after 2.2-beta-2
DependencySet includes filter not working after 2.2-beta-2
----------------------------------------------------------
Key: MASSEMBLY-544
URL: http://jira.codehaus.org/browse/MASSEMBLY-544
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2
Environment: win32, Maven 2.2.1 and Maven 3.0.2
Reporter: Omer A Kudat
If the includes/include "subelements are present, they define a set of artifact coordinates to include." That's the definition from the assembly site. Until recently, we have been using this filter as advertised. However, yesterday we upgraded the plugin from 2.2-beta-2 to 2.2. Now, the inclusion filter has no effect, and all dependencies are included.
{code}
<?xml version="1.0"?>
<assembly xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/xsd/assembly-1.1.0-SNAPSHOT.xsd">
<id>dam</id>
<formats>
<format>tar</format>
</formats>
<includeBaseDirectory>true</includeBaseDirectory>
<baseDirectory>${project.version}</baseDirectory>
<dependencySets>
<dependencySet>
<outputFileNameMapping>${artifact.artifactId}.${artifact.extension}</outputFileNameMapping>
<outputDirectory>lib</outputDirectory>
<fileMode>0744</fileMode>
<directoryMode>0755</directoryMode>
<useTransitiveDependencies>true</useTransitiveDependencies>
<useTransitiveFiltering>true</useTransitiveFiltering>
<includes>
<include>com.mycompany*</include>
</includes>
</dependencySet>
</dependencySets>
</assembly>
{code}
--
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
[jira] Commented: (MASSEMBLY-544) DependencySet includes filter not
working in 2.2
Posted by "Andreas (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=257240#action_257240 ]
Andreas commented on MASSEMBLY-544:
-----------------------------------
I solved my problem in defining the filters with wildcards for all subsections of the artifact patterns.
> DependencySet includes filter not working in 2.2
> ------------------------------------------------
>
> Key: MASSEMBLY-544
> URL: http://jira.codehaus.org/browse/MASSEMBLY-544
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2
> Environment: win32, Maven 2.2.1 and Maven 3.0.2
> Reporter: Omer A Kudat
>
> If the includes/include "subelements are present, they define a set of artifact coordinates to include." That's the definition from the assembly site. Until recently, we have been using this filter as advertised. However, yesterday we upgraded the plugin from 2.2-beta-2 to 2.2. Now, the inclusion filter has no effect, and all dependencies are included.
> {code}
> <?xml version="1.0"?>
> <assembly xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/xsd/assembly-1.1.0-SNAPSHOT.xsd">
> <id>dam</id>
> <formats>
> <format>tar</format>
> </formats>
> <includeBaseDirectory>true</includeBaseDirectory>
> <baseDirectory>${project.version}</baseDirectory>
> <dependencySets>
> <dependencySet>
> <outputFileNameMapping>${artifact.artifactId}.${artifact.extension}</outputFileNameMapping>
> <outputDirectory>lib</outputDirectory>
> <fileMode>0744</fileMode>
> <directoryMode>0755</directoryMode>
> <useTransitiveDependencies>true</useTransitiveDependencies>
> <useTransitiveFiltering>true</useTransitiveFiltering>
> <includes>
> <include>com.mycompany*</include>
> </includes>
> </dependencySet>
> </dependencySets>
> </assembly>
> {code}
--
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
[jira] Commented: (MASSEMBLY-544) DependencySet includes filter not
working in 2.2
Posted by "Andreas (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=257176#action_257176 ]
Andreas commented on MASSEMBLY-544:
-----------------------------------
we have same issue also for exclude filter after upgrading from 2.2-beta-5 to 2.2
> DependencySet includes filter not working in 2.2
> ------------------------------------------------
>
> Key: MASSEMBLY-544
> URL: http://jira.codehaus.org/browse/MASSEMBLY-544
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2
> Environment: win32, Maven 2.2.1 and Maven 3.0.2
> Reporter: Omer A Kudat
>
> If the includes/include "subelements are present, they define a set of artifact coordinates to include." That's the definition from the assembly site. Until recently, we have been using this filter as advertised. However, yesterday we upgraded the plugin from 2.2-beta-2 to 2.2. Now, the inclusion filter has no effect, and all dependencies are included.
> {code}
> <?xml version="1.0"?>
> <assembly xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/xsd/assembly-1.1.0-SNAPSHOT.xsd">
> <id>dam</id>
> <formats>
> <format>tar</format>
> </formats>
> <includeBaseDirectory>true</includeBaseDirectory>
> <baseDirectory>${project.version}</baseDirectory>
> <dependencySets>
> <dependencySet>
> <outputFileNameMapping>${artifact.artifactId}.${artifact.extension}</outputFileNameMapping>
> <outputDirectory>lib</outputDirectory>
> <fileMode>0744</fileMode>
> <directoryMode>0755</directoryMode>
> <useTransitiveDependencies>true</useTransitiveDependencies>
> <useTransitiveFiltering>true</useTransitiveFiltering>
> <includes>
> <include>com.mycompany*</include>
> </includes>
> </dependencySet>
> </dependencySets>
> </assembly>
> {code}
--
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
[jira] Closed: (MASSEMBLY-544) DependencySet includes filter not
working in 2.2
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MASSEMBLY-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey closed MASSEMBLY-544.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.3
Assignee: John Casey
Verified to work vs. maven-assembly-plugin 2.2.1. Added integration test.
> DependencySet includes filter not working in 2.2
> ------------------------------------------------
>
> Key: MASSEMBLY-544
> URL: https://jira.codehaus.org/browse/MASSEMBLY-544
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2
> Environment: win32, Maven 2.2.1 and Maven 3.0.2
> Reporter: Omer A Kudat
> Assignee: John Casey
> Fix For: 2.3
>
>
> If the includes/include "subelements are present, they define a set of artifact coordinates to include." That's the definition from the assembly site. Until recently, we have been using this filter as advertised. However, yesterday we upgraded the plugin from 2.2-beta-2 to 2.2. Now, the inclusion filter has no effect, and all dependencies are included.
> {code}
> <?xml version="1.0"?>
> <assembly xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/xsd/assembly-1.1.0-SNAPSHOT.xsd">
> <id>dam</id>
> <formats>
> <format>tar</format>
> </formats>
> <includeBaseDirectory>true</includeBaseDirectory>
> <baseDirectory>${project.version}</baseDirectory>
> <dependencySets>
> <dependencySet>
> <outputFileNameMapping>${artifact.artifactId}.${artifact.extension}</outputFileNameMapping>
> <outputDirectory>lib</outputDirectory>
> <fileMode>0744</fileMode>
> <directoryMode>0755</directoryMode>
> <useTransitiveDependencies>true</useTransitiveDependencies>
> <useTransitiveFiltering>true</useTransitiveFiltering>
> <includes>
> <include>com.mycompany*</include>
> </includes>
> </dependencySet>
> </dependencySets>
> </assembly>
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MASSEMBLY-544) DependencySet includes filter not
working in 2.2
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated MASSEMBLY-544:
--------------------------------------
Summary: DependencySet includes filter not working in 2.2 (was: DependencySet includes filter not working after 2.2-beta-2)
> DependencySet includes filter not working in 2.2
> ------------------------------------------------
>
> Key: MASSEMBLY-544
> URL: http://jira.codehaus.org/browse/MASSEMBLY-544
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2
> Environment: win32, Maven 2.2.1 and Maven 3.0.2
> Reporter: Omer A Kudat
>
> If the includes/include "subelements are present, they define a set of artifact coordinates to include." That's the definition from the assembly site. Until recently, we have been using this filter as advertised. However, yesterday we upgraded the plugin from 2.2-beta-2 to 2.2. Now, the inclusion filter has no effect, and all dependencies are included.
> {code}
> <?xml version="1.0"?>
> <assembly xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/xsd/assembly-1.1.0-SNAPSHOT.xsd">
> <id>dam</id>
> <formats>
> <format>tar</format>
> </formats>
> <includeBaseDirectory>true</includeBaseDirectory>
> <baseDirectory>${project.version}</baseDirectory>
> <dependencySets>
> <dependencySet>
> <outputFileNameMapping>${artifact.artifactId}.${artifact.extension}</outputFileNameMapping>
> <outputDirectory>lib</outputDirectory>
> <fileMode>0744</fileMode>
> <directoryMode>0755</directoryMode>
> <useTransitiveDependencies>true</useTransitiveDependencies>
> <useTransitiveFiltering>true</useTransitiveFiltering>
> <includes>
> <include>com.mycompany*</include>
> </includes>
> </dependencySet>
> </dependencySets>
> </assembly>
> {code}
--
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