You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "deckrider (JIRA)" <ji...@codehaus.org> on 2008/12/12 22:18:19 UTC
[jira] Created: (MDEP-192) generated classpath should match what
maven produces
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
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
[jira] Issue Comment Edited: (MDEP-192) generated classpath should
match what maven produces
Posted by "Nikola Petrov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=219312#action_219312 ]
Nikola Petrov edited comment on MDEP-192 at 4/28/10 4:36 PM:
-------------------------------------------------------------
It happened to be far easier than i thought. I would be glad if you can apply this patch as fast as you can, because we are having the same problem when trying to auto generate some classpath files.
was (Author: nikolavp):
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
[jira] Commented: (MDEP-192) generated classpath should match what
maven produces
Posted by "deckrider (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157882#action_157882 ]
deckrider commented on MDEP-192:
--------------------------------
By the way, from http://maven.apache.org/release-notes.html I would expect the order to be changeable based on pom order:
MNG-1412 / MNG-3111 introduced deterministic ordering of dependencies on the classpath. In the past, natural set ordering was used and this lead to odd results. The ordering is now preserved from your pom, with dependencies added by inheritence added last. In builds that had conflicting or duplicate dependencies, this may introduce a change to the output. In short, if you have weird issues with 2.0.9, take a look at the dependencies to see if you have conflicts somewhere.
> 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
>
> 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
[jira] Closed: (MDEP-192) generated classpath should match what
maven produces
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox closed MDEP-192.
--------------------------
Resolution: Fixed
Fix Version/s: 2.2
> 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
> Fix For: 2.2
>
> 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
[jira] Commented: (MDEP-192) generated classpath should match what
maven produces
Posted by "Nikola Petrov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=222009#action_222009 ]
Nikola Petrov commented on MDEP-192:
------------------------------------
Can someone please commit this before the next release. This bug is getting old and is breaking too many stuff. The dependency:list goal has the same 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
[jira] Updated: (MDEP-192) generated classpath should match what
maven produces
Posted by "Nikola Petrov (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (MDEP-192) generated classpath should match what
maven produces
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MDEP-192:
------------------------------
Patch Submitted: [Yes]
> 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
[jira] Commented: (MDEP-192) generated classpath should match what
maven produces
Posted by "Nikola Petrov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=219229#action_219229 ]
Nikola Petrov commented on MDEP-192:
------------------------------------
I have a patch that fixes the problem but it cannot pass the tests, because it uses MavenSession and for some odd reason the class is not injected when testing it with junit. As soon as i figure out how to do that i will post the code here.
> 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
>
> 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
[jira] Issue Comment Edited: (MDEP-192) generated classpath should
match what maven produces
Posted by "Nikola Petrov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=222009#action_222009 ]
Nikola Petrov edited comment on MDEP-192 at 5/21/10 1:46 AM:
-------------------------------------------------------------
Can someone please commit this before the next release. This bug is getting old and is breaking many things. The dependency:list goal has the same problem.
was (Author: nikolavp):
Can someone please commit this before the next release. This bug is getting old and is breaking too many stuff. The dependency:list goal has the same 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