[
https://jira.codehaus.org/browse/MRRESOURCES-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=288066#comment-288066
]
Scott Carey commented on MRRESOURCES-53:
----------------------------------------
My question is why does the configuration above try and download the test-jar
artifact? The configuration is to download
org.apache:apache-jar-resource-bundle:1.4, not the project's test-jar artifact.
Has the comment from last february by Benjamin Bentmann been addressed?
{quote}
The issue is not in the maven-jar-plugin. The maven-remote-resources-plugin
explicitly resolves the test classpath of the project
(ProcessRemoteResourcesMojo.java:697) which naturally fails when the test
classes haven't even compiled.
{quote}
> use of remote resources plugin breaks ability to use test-jar artifacts
> -----------------------------------------------------------------------
>
> Key: MRRESOURCES-53
> URL: https://jira.codehaus.org/browse/MRRESOURCES-53
> Project: Maven 2.x Remote Resources Plugin
> Issue Type: Bug
> Affects Versions: 1.1
> Reporter: Scott Carey
> Priority: Critical
> Attachments: project.zip
>
>
> I have a dead simple project configuration that breaks if I inherit from
> org.apache:apache . If I disable the remote resources plugin portion, it
> works.
> The plugin is trying to resolve a test-jar artifact during the compile phase,
> but such an artifact does not exist until the test-compile phase.
> To reproduce: unpack the project provided. run 'mvn clean compile'. that
> will fail. test-compile will work. If you install, then compile will work
> because it will find the test-jar in the local repo. You must not have any
> related snapshot artifacts in the local repo related to this project to
> reproduce.
> If you break the inheritance to the apache parent, it will work. Or, you can
> override the usage of the remote resources plugin and disable it to get the
> project to function.
> It seems to work if I assign the plugin to operate in a late phase -- such as
> prepare-package. Perhaps all that is required is that the plugin operate in
> as late a phase as it can by default?
> If it must operate in compile however, it cannot look for dependencies that
> are not generated until test-compile such as test-jar types.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
