Pilipno men on cam Hudson error updating group repository metadata

If I'm a developer I may need to build both locally at roughly the same time.

hudson error updating group repository metadata-33

I have to run a job every 30seconds on Nexus to refresh it or I can never get the LATEST artifact.

In fact I implemented a job for continuous integration on Hudson to deploy the LATEST successfully built artifact.

Here is a snippet of the output from the failing job:[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 'cd315359376ec31bb4e3213a368618ecc7beca1e'; remote = '8de5987a48151f2d923dda8dd28797d07c15d4d6' - RETRYING[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 'cd315359376ec31bb4e3213a368618ecc7beca1e'; remote = '8de5987a48151f2d923dda8dd28797d07c15d4d6' - IGNORING.........[INFO] ------------------------------------------------------------------------[ERROR] BUILD ERROR[INFO] ------------------------------------------------------------------------[INFO] Error installing artifact's metadata: Error installing metadata: Error updating group repository metadatain epilog non whitespace content is not allowed but got 4 (position: END_TAG seen ...\for that project on the server hosting Archiva, and confirmed the xml is malformed (per the line number in the error).

If I look at the maven repo on the build machine (different server) for that project, I can see that is valid.

Default Lifecycle Executor.execute Task Segments(Default Lifecycle Executor.java:348) at org.apache.maven.lifecycle.

We are using maven, and being that we have to support multiple versions of our product we sometimes have a 1.x and 2.x build structure going on.

You need to configure in Jenkins using a local maven repository to avoid such situations.

Using a local repository only works if you're dealing with CI.

There's a warning that the hash values don't match, and then it appears to ignore that fact.

I checked settings.xml, nothing for checksum policy for snapshots repo.

When both 1.x and 2.x are built in parallel, sometimes we see Error installing artifact's metadata: Error installing metadata: Error updating group repository metadata From what I can tell, the in the local user's repo (for the artifact, not the version of the artifact) is being written to at the same time by another maven process.