[ 
https://issues.apache.org/jira/browse/GERONIMO-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487625
 ] 

Peter Petersson commented on GERONIMO-2993:
-------------------------------------------

I run into this problem (having maven-metadata-local.xml files instead of 
maven-metadata.xml files) with a relatively fresh local 2.0.5 maven repository 
during work on a Geronimo Roller Plugin see GERONIMO-2994. As I had problems 
getting the plugin function finding the modules in my local repository I 
started to trace things in the PluginInstallerGBean and found that the problem 
could be fixed with a small (actually 2) modification to  the findArtifact 
method (see the included "PluginInstallerGBean.patch" in GERONIMO-2994 for 
deatils). 

For some reason (unknown to me) maven creates maven-metadata-local.xml files 
instead of maven-metadata.xml files in some cases and without modifying this 
method (findArtifact) I could not test install and work on the plugin using the 
local maven repository. 
The "patch" is pretty simple and works like this:
If findArtifact fails to look up the maven-metadata.xml file it will, instead 
of exit with null, first look up the maven-metadata-local.xml file and only if 
that also fails exit with Artifact=null.      

> Private repository causes offline builds to fail due to missing metadata
> ------------------------------------------------------------------------
>
>                 Key: GERONIMO-2993
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-2993
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: buildsystem
>    Affects Versions: 2.0-M4
>         Environment: WinXP, RHEL4 and SLED10
>            Reporter: Donald Woods
>         Assigned To: Donald Woods
>            Priority: Minor
>             Fix For: 2.0-M5
>
>
> When trying to rebuild the configs in offline mode, several will fail due to 
> Maven 2.0.5 not being able to find the metadata for the jars that we include 
> in /repository, such as MyFaces.  We need to include enough POM and metadata 
> information so the build can be run in offline mode....  This may be a 
> car-plugin bug, as I've seen other problems when you have 
> maven-metadata-local.xml files in your repo instead of maven-metadata.xml, 
> which will cause CAR builds to fail, but the corresponding modules will 
> build.....

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to