You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Geoff Simpson (JIRA)" <ji...@codehaus.org> on 2010/06/29 07:50:32 UTC
[jira] Created: (MINVOKER-104) Error installing artifact's metadata
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
[jira] Commented: (MINVOKER-104) Error installing artifact's
metadata
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MINVOKER-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=226618#action_226618 ]
Benjamin Bentmann commented on MINVOKER-104:
--------------------------------------------
The recommended practice for the Invoker is to use a private local repository somewhere inside the project's output directory where concurrency concerns should not apply. Hence, I am tempted to close this as won't fix.
> 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
[jira] Commented: (MINVOKER-104) Error installing artifact's
metadata
Posted by "Geoff Simpson (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MINVOKER-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=226615#action_226615 ]
Geoff Simpson commented on MINVOKER-104:
----------------------------------------
note that there is a duplicate report here http://jira.codehaus.org/browse/MINSTALL-54 but as the fix is inside this project i've raised a second bug report here.
> 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
[jira] Commented: (MINVOKER-104) Error installing artifact's
metadata
Posted by "John Sipher (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] (MINVOKER-104) Error installing artifact's metadata
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MINVOKER-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MINVOKER-104.
-----------------------------------
Resolution: Won't Fix
Assignee: Robert Scholte
I agree with Benjamin.
Also, when comparing the overhead/costs of IO, synchronized methods (which only works within the same JVM), sleeps and timeouts with the chance that this situation occurs, IMHO it's not worth it.
> Error installing artifact's metadata
> ------------------------------------
>
> Key: MINVOKER-104
> URL: https://jira.codehaus.org/browse/MINVOKER-104
> Project: Maven 2.x Invoker Plugin
> Issue Type: Bug
> Reporter: Geoff Simpson
> Assignee: Robert Scholte
> 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, 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