[jira] Commented: (MDEP-192) generated classpath should match what maven produces
[
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:
>
> org.apache.maven.plugins
> maven-dependency-plugin
>
>
> classpathUnix
> generate-sources
>
> build-classpath
>
>
> :
> ${project.artifactId}
>
> ${project.build.directory}/${project.artifactId}-unix.classpath
>
>
>
>
--
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
[
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:
>
> org.apache.maven.plugins
> maven-dependency-plugin
>
>
> classpathUnix
> generate-sources
>
> build-classpath
>
>
> :
> ${project.artifactId}
>
> ${project.build.directory}/${project.artifactId}-unix.classpath
>
>
>
>
--
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
[
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:
>
> org.apache.maven.plugins
> maven-dependency-plugin
>
>
> classpathUnix
> generate-sources
>
> build-classpath
>
>
> :
> ${project.artifactId}
>
> ${project.build.directory}/${project.artifactId}-unix.classpath
>
>
>
>
--
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
[
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:
>
> org.apache.maven.plugins
> maven-dependency-plugin
>
>
> classpathUnix
> generate-sources
>
> build-classpath
>
>
> :
> ${project.artifactId}
>
> ${project.build.directory}/${project.artifactId}-unix.classpath
>
>
>
>
--
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
[
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:
>
> org.apache.maven.plugins
> maven-dependency-plugin
>
>
> classpathUnix
> generate-sources
>
> build-classpath
>
>
> :
> ${project.artifactId}
>
> ${project.build.directory}/${project.artifactId}-unix.classpath
>
>
>
>
--
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
