Check nexus logs and staging profile configuration. Staging responding 400 Bad Request may mean nexus not finding/not having profiles to match deploy attempt for example.
-- Thanks, ~t~ On 23 Mar 2015 at 18:22:43, David Hoffer ([email protected]) wrote: Yes it keeps failing...we have tried it several times. Is there something in Nexus we need to delete? -Dave On Mon, Mar 23, 2015 at 11:14 AM, Karl Heinz Marbaise <[email protected]> wrote: > Hi have you tried to release several times...with the same version ? > > cause 400 code looks like this > > Kind regards > Karl Heinz Marbaise > > On 3/23/15 6:01 PM, David Hoffer wrote: > >> We are trying to perform an internal release of the quartz project after >> we >> made a few changes. However when we perform the Maven release we get the >> following error. We aren't sure if this is a Nexus 'bug' or if there is >> something in the quartz build that would cause this. >> >> Any ideas? >> >> *[org.quartz-scheduler:quartz-parent] Failed to execute goal >> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy >> (default-deploy) >> on project quartz-parent: Failed to retrieve remote metadata >> org.quartz-scheduler:quartz-parent/maven-metadata.xml: Could not transfer >> metadata org.quartz-scheduler:quartz-parent/maven-metadata.xml from/to >> nexus >> (dav:https://maven.issinc.com/nexus/service/local/staging/deploy/maven2 >> <https://maven.issinc.com/nexus/service/local/staging/deploy/maven2>): >> Failed to transfer file: >> https://maven.issinc.com/nexus/service/local/staging/ >> deploy/maven2/org/quartz-scheduler/quartz-parent/maven-metadata.xml >> <https://maven.issinc.com/nexus/service/local/staging/ >> deploy/maven2/org/quartz-scheduler/quartz-parent/maven-metadata.xml>. >> Return code is: 400* >> >> > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
