maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Casey (JIRA)" <j...@codehaus.org>
Subject [jira] Reopened: (MASSEMBLY-416) outputDirectory default value in fileSet seems changed; now seems to use directory name of fileSet sourcedir
Date Tue, 09 Jun 2009 15:29:42 GMT

     [ http://jira.codehaus.org/browse/MASSEMBLY-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

John Casey reopened MASSEMBLY-416:
----------------------------------


The problem is a missing <useProjectArtifact>false</useProjectArtifact> line in
jar-with-dependencies.xml. I'm not sure why this wasn't happening in my tests, or maybe something
is different between our versions of the 'jar' tool and the way it reports duplicate entries...I
don't know.

I'm fixing the descriptor now, and will re-close this issue for 2.2-beta-5.

In the meantime, you can copy the contents of jar-with-dependencies.xml[1].  Be sure <useProjectArtifact>false</useProjectArtifact>
is in the dependencySet before you use it.

You can use it in either a custom assembly descriptor jar[2] (it would go in src/main/resources/assemblies
of your custom jar project), or from a location within your current project's structure, using
the <descriptors> configuration.


1. http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-assembly-plugin/src/main/resources/assemblies/
2. http://maven.apache.org/plugins/maven-assembly-plugin/examples/sharing-descriptors.html


> outputDirectory default value in fileSet seems changed; now seems to use directory name
of fileSet sourcedir
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: MASSEMBLY-416
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-416
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2-beta-3
>            Reporter: John Casey
>            Assignee: John Casey
>            Priority: Blocker
>             Fix For: 2.2-beta-4
>
>         Attachments: massembly-416-1.0-SNAPSHOT-jar-with-dependencies.jar, massembly-416-2.jar,
massembly-416-jar-listing.txt, massembly-416.zip
>
>
> From Grzegorz Slowikowski on the dev@maven mailing list ([VOTE] maven-assembly-plugin
2.2-beta-4 thread):
> {noformat}
> Hi
> With this configuration:
>    <pluginRepositories>
>        <pluginRepository>
>            <id>maven-staging-031</id>
>            <name>maven-staging-031</name>
>            <url>https://repository.apache.org/content/repositories/maven-staging-031</url>
>        </pluginRepository>
>    </pluginRepositories>
>    <build>
>        <plugins>
>            <plugin>
>                <groupId>org.apache.maven.plugins</groupId>
>                <artifactId>maven-assembly-plugin</artifactId>
>                <version>2.2-beta-4</version>
>                <configuration>
>                    <descriptorRefs>
>                        <descriptorRef>jar-with-dependencies</descriptorRef>
>                    </descriptorRefs>
>                </configuration>
>                <executions>
>                    <execution>
>                        <id>make-assembly</id>
>                        <phase>package</phase>
>                        <goals>
>                            <goal>single</goal>
>                        </goals>
>                    </execution>
>                </executions>
>            </plugin>
>        </plugins>
>    </build>
> I have "target" folder/package inside jar-with-dependencies archive which contains copies
of my project classes (they are in the normal
> package structure within this archive too).
> ...
> {noformat}

-- 
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

        

Mime
View raw message