[
https://issues.apache.org/jira/browse/MINSTALL-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16652346#comment-16652346
]
Dan Armbrust commented on MINSTALL-54:
--------------------------------------
Whenever someone mentions maven, and I curse under my breath, this bug report
is now the most recent example of everything that is wrong with this project.
We have a dumb bug, identified 8 years ago.
A patch is provided years and years ago.
And the maintainers can't even be bothered to apply it.
Now that I have switched over to using pipeline builds with jenkins - when i do
a release, it ends up building both master and development branches at the same
time.
Guess what happens when a build server tries to do two builds at the same
time... good lord.
What the heck is the point of having a local cache, if you can't use it in
parallel? This should be part of the basic requirements.....
The point of the cache is to save me from GB and GB of downloads. If I have to
use a per-build cache, or reconfigure jenkins to have a per-instance cache, I'm
wasting disk, bandwidth, slowing down all my builds, and making it impossible
to build dependent code without having an artifact server running, since I
can't rely on a mvn install from one instance making the latests snapshot code
available to another instance.
What is it going to take to get this fixed?
Does someone need to remote in to a maintainers computer, and type the
keystrokes for them to do the merge?
Of course, at this point, since they ignored a patch that was supplied to them,
I'm sure it will no longer apply cleanly.
> [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)
