Same thing on Hudson as well. Just run mvn deploy as a goal (or you can also mark the deploy checkbox on job configuration page to let Hudson deploy all sub-modules after successful build - there's a minor difference). This is shared Hudson server at apache? I'd assume it's already configured with credentials to publish snapshots, so you just need to use the correct repository id so Maven picks up the right credentials from settings. If you can see other builds on Hudson, take a look at them for example.
Kalle On Wed, Jul 29, 2009 at 12:08 PM, Les Hazlewood<[email protected]> wrote: > Very cool - thanks for the tips guys. What about the Hudson continuous > integration builds? I mean, isn't that the one that is supposed to be > publishing the snapshots? Any ideas on how we'd tell Hudson to do > this? > > I won't be able to mess with this much until tonight or possibly > tomorrow so if anyone wants to jump in, please feel free to modify the > poms as necessary and then post the patch to this list or a jira > issue. Or tell us what we should do :) > > Thanks! > > Les > > On Wed, Jul 29, 2009 at 2:56 PM, Brian Topping<[email protected]> wrote: >> Les, >> >> Kalle is correct, when I previously deployed the snapshots, I used the 'mvn >> deploy' command line. >> >> Be sure you have your settings.xml set up with the following (I posted this >> on 7/7/09): >> >>> <settings> >>> ... >>> <servers> >>> <server> >>> <id>apache-maven-snapshots</id> >>> <username>CHANGEME</username> >>> </server> >>> </servers> >>> >>> </settings> >> >> You'll also need to confirm that you can SSH to people.apache.org and you >> are logged in without a password (i.e. that your DSA key is set up >> properly). >> >> Please let me know if I missed anything, I'm happy to help you debug your >> system. (If IM is easier, ping me off-list and I can give you a gtalk >> address.) >> >> I could just publish the binaries, but I want to make sure you are fully set >> up. >> >> Cheers, Brian >> >> On Jul 29, 2009, at 2:44 PM, Kalle Korhonen wrote: >> >>> Les, >>> >>> this should be of help: >>> http://maven.apache.org/plugins/maven-deploy-plugin/usage.html. For >>> Nexus, the repository url (in the pom) should be something like: >>> dav:http://nexus.apache.org/. We use Nexus and publish snapshots to it >>> all the time and it works great! >>> >>> Kalle >>> >>> >>> On Mon, Jul 27, 2009 at 3:15 PM, Les Hazlewood<[email protected]> >>> wrote: >>>> >>>> Yay! >>>> >>>> Thanks Craig :) I'll try to run RAT and see how that goes too for good >>>> measure. >>>> >>>> Now I gotta go dig up that email that mentioned how to publish snapshots >>>> :) >>>> >>>> Are we all in agreement that we'll publish them to the newer Nexus >>>> repo? Any objections? >>>> >>>> - Les >>>> >>>> On Mon, Jul 27, 2009 at 6:04 PM, Craig L Russell<[email protected]> >>>> wrote: >>>>> >>>>> <mentor hat="on"> >>>>> You can start publishing snapshots. There is a discussion underway in >>>>> legal >>>>> regarding requirements for incubating projects but I believe that shiro >>>>> is >>>>> in compliance. >>>>> </mentor> >>>>> >>>>> Craig >>>>> >>>>> On Jul 27, 2009, at 2:49 PM, Les Hazlewood wrote: >>>>> >>>>>> Hi Mentors, >>>>>> >>>>>> Per last week's email with the dev emails stating the conversion to >>>>>> the ASF license was agreed upon, as well as having all of our CLAs on >>>>>> file - is there anything else required before we can start publishing >>>>>> snapshots? >>>>>> >>>>>> I'd really like to start this asap to help people with continuous >>>>>> integration. >>>>>> >>>>>> Thanks, >>>>>> >>>>>> Les >>>>> >>>>> Craig L Russell >>>>> Architect, Sun Java Enterprise System http://db.apache.org/jdo >>>>> 408 276-5638 mailto:[email protected] >>>>> P.S. A good JDO? O, Gasp! >>>>> >>>>> >>>> >>> >> >> >
