Hi,
actually, this is the manual for Lucene Committers to deploy our own artifacts. IMHO, It is a bit too complicated for a “normal user”, because we (Apache Lucene Committers) first build the artifacts to a separate directory, then the release vote goes on, and then we use the “stage” ant task to upload them to the server. During the vote the artifacts are already signed and hashed, so they cannot be regenerated for deploying to Maven. So we have split this. If you are just interested in creating and deploying maven artifacts in one single step to some Maven repo where you have username and password, it is just easy: - Create settings.xml - Call “ant generate-maven-artifacts” (like you did before, this time just with passing the maven server coordinates on command line -Dm2.repository.id=XXX -Dm2.repository.url=XXX; see my other mail for info; this will take all passwords from settings.xml) - If you don’t want to stage a snapshot version, pass a “real” version: -Dversion=”6.0.0-yourspecialvariant” as version number By the way, Jenkins is doing that every night (you can get maven snapshot artifacts from the official Apache Snapshot repo, if you like). Uwe ----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen <http://www.thetaphi.de/> http://www.thetaphi.de eMail: [email protected] From: Gus Heck [mailto:[email protected]] Sent: Wednesday, October 21, 2015 1:12 AM To: dev Subject: Re: Repository Publishing Ah "The Fine Manual" :) Thx :) On Tue, Oct 20, 2015 at 7:06 PM, Steve Rowe <[email protected]> wrote: Hi Gus, Check out the section “C. How to deploy Maven artifacts to a repository” in dev-tools/maven/README.maven in the Lucene/Solr source. I recommend reading the rest of that file too, especially the part about specifying custom artifact versions, in item 3 under section “D. How to use Maven to build Lucene/Solr” (which also applies to the generate-maven-artifacts target). The process used to publish Lucene/Solr artifacts to ASF Nexus (from which they are periodically sync’d to Maven Central) is documented here: <http://wiki.apache.org/lucene-java/PublishMavenArtifacts>. This process uses another Ant target (stage-maven-artifacts), which can “attach” GPG signatures and SHA1/MD5 checksums to each artifact. If you also need those (instead of just the poms and binary/javadoc/source jars produced by generate-maven-artifacts), check out that wiki page. Steve > On Oct 20, 2015, at 5:52 PM, Gus Heck <[email protected]> wrote: > > Does the lucene-solr build contain a target that I could use to publish > artifacts to a local repository after supplying a url and credentials? I see > the target generate-maven-artifacts, but I don't see anything I can > immediately identify as an analog to the deployment features of maven/gradle. > > I've got a project that wants to use features in 6.0 but obviously trunk of > any project is somewhat riskier than a release version. We want to push what > we are using into our repository to ensure that we don't consume changes from > trunk until we are ready. I can upload it manually of course but it would be > nice if I could be sure that I was uploading a full set of everything > normally published for each version without missing anything. > > -Gus --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] -- http://www.the111shift.com
