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

John Casey reopened MRRESOURCES-37:
-----------------------------------


Okay, I reproduced the problem with 1.1-SNAPSHOT...but ONLY under very special 
circumstances:

1. remove testing/**
2. remove ~/.m2/repository/com/acme/**
3. open testing.zip
4. cd testing
5. mvn -f pom-firstTime.xml install
6. mvn install

It seems that no matter whether I use the default configuration or supply a 
concrete version (1.0 or 1.1-SNAPSHOT), step 6 fails. If I start with the 
vanilla project zipfile, run up through step 5 with that, try step 6 and get an 
error, then update pom.xml to use the 1.1-SNAPSHOT version and re-run step 6, 
it works and continues to work until start over with step 1 again.

Very strange. I'm going to see what I can find out, now that I have a way to 
reproduce/reset this build if needed.

> embedded error with maven-remote-resources-plugin; maven build order?
> ---------------------------------------------------------------------
>
>                 Key: MRRESOURCES-37
>                 URL: http://jira.codehaus.org/browse/MRRESOURCES-37
>             Project: Maven 2.x Remote Resources Plugin
>          Issue Type: Bug
>    Affects Versions: 1.0
>         Environment: [INFO] [enforcer:display-info {execution: default}]
> [INFO] Maven Version: 2.0.10
> [INFO] JDK Version: 1.5.0_16 normalized as: 1.5.0-16
> [INFO] OS Info: Arch: i386 Family: unix Name: linux Version: 2.6.28.8
>            Reporter: jieryn
>            Assignee: John Casey
>             Fix For: 1.1
>
>         Attachments: MNG-4094.zip, testing.zip
>
>
> I am attaching a sample project which exhibits the error. Please run   mvn -f 
> pom-firstTime.xml  to prime your .m2/repository so that the real pom.xml's 
> <build> finds the artifacts properly. Now, run mvn (default goal install is 
> coded) and notice the Embedded error. I scan the previously created JARs in 
> my .m2/repository and the maven-remote-resources-plugin files are definitely 
> in the JAR.....
> I am at a loss, not convinced this is a bug, but need better minds to examine 
> this. Thank you!

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

        

Reply via email to