Thanks Uwe!

Does this fall back on maven, and thus consume authentication info from
settings.xml?

-Gus

On Tue, Oct 20, 2015 at 6:35 PM, Uwe Schindler <[email protected]> wrote:

> The target “ant generate-maven-artifacts” uploads the artifacts to the
> local ~/.m2 repository, just like “mvn install”. To upload them somewhere
> else you can pass a repository name from your maven settings.xml using -D
> properties, e.g.:
>
>
>
> -Dm2.repository.id=apache.snapshots.https
>
> -Dm2.repository.url=
> https://repository.apache.org/content/repositories/snapshots
>
>
>
> If you pass these properties it will look like:
>
>
>
> *-dist-maven*:
>
> [artifact:install-provider] Installing provider: 
> org.apache.maven.wagon:wagon-ssh:jar:1.0-beta-7:runtime
>
> [artifact:install] [INFO] Installing 
> /x1/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven-trunk/lucene/build/poms/pom.xml
>  to 
> /x1/jenkins/.m2/repository/org/apache/lucene/lucene-solr-grandparent/6.0.0-SNAPSHOT/lucene-solr-grandparent-6.0.0-SNAPSHOT.pom
>
> [artifact:deploy] Deploying to 
> https://repository.apache.org/content/repositories/snapshots
>
> [artifact:deploy] [INFO] Retrieving previous build number from 
> apache.snapshots.https
>
> [artifact:deploy] Uploading: 
> org/apache/lucene/lucene-solr-grandparent/6.0.0-SNAPSHOT/lucene-solr-grandparent-6.0.0-20151020.030757-354.pom
>  to repository apache.snapshots.https at 
> https://repository.apache.org/content/repositories/snapshots
>
> [artifact:deploy] Transferring 380K from apache.snapshots.https
>
> [artifact:deploy] Uploaded 380K
>
> [artifact:deploy] [INFO] Retrieving previous metadata from 
> apache.snapshots.https
>
> [artifact:deploy] [INFO] Uploading repository metadata for: 'artifact 
> org.apache.lucene:lucene-solr-grandparent'
>
> [artifact:deploy] [INFO] Retrieving previous metadata from 
> apache.snapshots.https
>
> [artifact:deploy] [INFO] Uploading repository metadata for: 'snapshot 
> org.apache.lucene:lucene-solr-grandparent:6.0.0-SNAPSHOT'
>
> [artifact:install-provider] Installing provider: 
> org.apache.maven.wagon:wagon-ssh:jar:1.0-beta-7:runtime
>
> [artifact:install] [INFO] Installing 
> /x1/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven-trunk/lucene/build/poms/lucene/pom.xml
>  to 
> /x1/jenkins/.m2/repository/org/apache/lucene/lucene-parent/6.0.0-SNAPSHOT/lucene-parent-6.0.0-SNAPSHOT.pom
>
> [artifact:deploy] Deploying to 
> https://repository.apache.org/content/repositories/snapshots
>
> [artifact:deploy] [INFO] Retrieving previous build number from 
> apache.snapshots.https
>
> [artifact:deploy] Uploading: 
> org/apache/lucene/lucene-parent/6.0.0-SNAPSHOT/lucene-parent-6.0.0-20151020.030757-354.pom
>  to repository apache.snapshots.https at 
> https://repository.apache.org/content/repositories/snapshots
>
> [artifact:deploy] Transferring 5K from apache.snapshots.https
>
> [artifact:deploy] Uploaded 5K
>
> [artifact:deploy] [INFO] Retrieving previous metadata from 
> apache.snapshots.https
>
> [artifact:deploy] [INFO] Uploading repository metadata for: 'artifact 
> org.apache.lucene:lucene-parent'
>
> [artifact:deploy] [INFO] Retrieving previous metadata from 
> apache.snapshots.https
>
> [artifact:deploy] [INFO] Uploading repository metadata for: 'snapshot 
> org.apache.lucene:lucene-parent:6.0.0-SNAPSHOT'
>
>
>
>
>
> Uwe
>
>
>
> -----
>
> Uwe Schindler
>
> H.-H.-Meier-Allee 63, D-28213 Bremen
>
> http://www.thetaphi.de
>
> eMail: [email protected]
>
>
>
> *From:* Gus Heck [mailto:[email protected]]
> *Sent:* Tuesday, October 20, 2015 11:52 PM
> *To:* dev
> *Subject:* Repository Publishing
>
>
>
> 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
>



-- 
http://www.the111shift.com

Reply via email to