[ 
http://jira.codehaus.org/browse/MINVOKER-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=264544#action_264544
 ] 

John Sipher commented on MINVOKER-104:
--------------------------------------

I understand the point about the recommended practice, but...

The proposed fix - adding maven-metadata-local.xml.lock - seems pretty simple. 
Why not go ahead and fix it and save people like me the trouble of researching 
the problem and figuring out a workaround? 

I think there are probably a lot of Maven users like me that just want to use 
the tool without making a career out of understanding all the ins and outs. 
That's possible because great tools like Maven "will run with sensible 
defaults" (see http://maven.apache.org/run-maven/index.html#Quick_Start for 
quote). In this case Maven doesn't run (at least not reliably) with the default 
behavior, and I'm using up a good chunk of my Sunday trying to figure out a 
workaround that won't break something else.

> Error installing artifact's metadata
> ------------------------------------
>
>                 Key: MINVOKER-104
>                 URL: http://jira.codehaus.org/browse/MINVOKER-104
>             Project: Maven 2.x Invoker Plugin
>          Issue Type: Bug
>            Reporter: Geoff Simpson
>            Priority: Critical
>         Attachments: minstall-54-error-install-artifact.patch
>
>
> Error installing artifact's metadata: Error installing metadata: Error 
> updating group repository metadata
> end tag not allowed in epilog but got / (position: END_TAG seen ...\n
> Looks like there might be an issue with updates to maven-metadata-local.xml 
> during the mvn install task. we have a build server that is multi threaded. 
> we often see this in the
> </versioning>
> </metadata>
> </metadata>
> maven-metadata-local.xml.
> maybe a solution is to add maven-metadata-local.xml.lock to ensure two 
> threads don't update the file at the same time

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