Reposting here.
However Jukka responded with
"
Instead of using the "Deploy artifacts to Maven repository" option in
Hudson with an "mvn install" build, you can configure the build to do
a normal "mvn deploy" which is guaranteed to correctly pick up any
extra artifacts attached to the build lifecycle.
BR,
Jukka Zitting
"
Which I did.
AFAICT the artifacts are appearing in the Nexus repo manager, and
should flow through to the hosted location shortly (not knowing a
great deal about the workflow)
Ian
Begin forwarded message:
From: Nigel Daley <ni...@apache.org>
Date: 3 November 2009 09:55:34 PST
To: Ian Boston <i...@tfd.co.uk>
Cc: Apache Infrastructure <infrastruct...@apache.org>
Subject: Re: Hudson Guidance needed
Ian, please subscribe and move this to bui...@apache.org.
Nige
On Nov 3, 2009, at 8:34 AM, Ian Boston wrote:
Hi,
Sling currently has a problem on one of its Hudson builds[1] that
should be deploying artifacts to the snapshot repository[2], but
isnt. There are several artifacts, and its the *-app.jar and *-
webapp.jar artifacts that are not getting into snapshots. *.jar and
*-sources.jar are getting in fine.
Is there anyway to make Hudson deploy artifacts with classifiers ?
I have a login, and could fix (If only I knew how)
Thanks
Ian
[1]
http://hudson.zones.apache.org/hudson/job/sling-trunk-1.5/org.apache.sling$org.apache.sling.launchpad.base/
[2]
http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad.base/2.0.5-SNAPSHOT/
