You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Nikola Petrov (JIRA)" <ji...@codehaus.org> on 2010/04/28 23:37:13 UTC
[jira] Updated: (MDEP-192) generated classpath should match what
maven produces
[ http://jira.codehaus.org/browse/MDEP-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nikola Petrov updated MDEP-192:
-------------------------------
Attachment: build-classpath.patch
A patch that fixes the problem
> generated classpath should match what maven produces
> ----------------------------------------------------
>
> Key: MDEP-192
> URL: http://jira.codehaus.org/browse/MDEP-192
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: build-classpath
> Affects Versions: 2.0, 2.1
> Environment: all
> Reporter: deckrider
> Assignee: Brian Fox
> Attachments: build-classpath.patch
>
>
> The generated classpath should be what maven produces, but appears to be in some other order when the following configuration is used for both version 2.0 and today's (Dec 12, 2008) latest trunk:
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-dependency-plugin</artifactId>
> <executions>
> <execution>
> <id>classpathUnix</id>
> <phase>generate-sources</phase>
> <goals>
> <goal>build-classpath</goal>
> </goals>
> <configuration>
> <pathSeparator>:</pathSeparator>
> <prefix>${project.artifactId}</prefix>
> <outputFile>${project.build.directory}/${project.artifactId}-unix.classpath</outputFile>
> </configuration>
> </execution>
> </executions>
> </plugin>
--
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