[
https://issues.apache.org/jira/browse/MINSTALL-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821208#comment-16821208
]
Tibor Digana commented on MINSTALL-54:
--------------------------------------
[~gsimpson]
If you often see this issue and you have multithreaded build system, it means
you have the problem of design because you have a common local repo. In my
experiences this has nevere happened because every run of job in Jenkins was
designed in Groovy Jenkinsfile in the way that local repositories were isolated
in each run. Therefore no shared artifacts across builds and jobs, which is the
best practice. I don't think the file locking is the way still because shared
artifacts of jobs and builds override artifacts of your current job by foreign
job and the build shows you fake result.
> [INFO] Error installing artifact's metadata
> -------------------------------------------
>
> Key: MINSTALL-54
> URL: https://issues.apache.org/jira/browse/MINSTALL-54
> Project: Maven Install Plugin
> Issue Type: Bug
> Components: install:install
> Affects Versions: 2.2
> Environment: Windows XP
> Reporter: Geoff Simpson
> Priority: Major
> Attachments: minstall-54-error-install-artifact.patch
>
>
> {noformat}
> [INFO] 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
> {noformat}
> 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
> {code:xml}
> </versioning>
> </metadata>
> </metadata>
> {code}
> {{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 was sent by Atlassian JIRA
(v7.6.3#76005)
