lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Rowe (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-3825) Please push maven snapshots to repositories.apache.org again
Date Sat, 03 Mar 2012 14:57:57 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13221603#comment-13221603
] 

Steven Rowe commented on LUCENE-3825:
-------------------------------------

In order to enable deploying to the Apache snapshot repository from Jenkins, I had to modify
the {{m2-deploy}} macros to (implicitly) pull authentication from {{<server>}} configuration
in {{~/.m2/settings.xml}} (alternatively, Maven Ant Tasks will look for {{~/.ant/settings.xml}})
- note that this replaces the *explicit* username/password strategy committed under SOLR-2634:

{noformat}
Index: lucene/common-build.xml
===================================================================
--- lucene/common-build.xml     (revision 1296611)
+++ lucene/common-build.xml     (working copy)
@@ -354,9 +354,7 @@
       <artifact:pom id="maven.project" file="@{pom.xml}"/>
       <artifact:deploy file="@{jar.file}">
         <artifact-attachments/>
-       <remoteRepository url="${m2.repository.url}">
-          <authentication username="${m2.repository.username}" privateKey="${m2.repository.private.key}"
password="${m2.repository.password}"/>
-        </remoteRepository>
+       <remoteRepository id="${m2.repository.id}" url="${m2.repository.url}"/>
         <pom refid="maven.project"/>
       </artifact:deploy>
     </sequential>
@@ -374,9 +372,7 @@
       <artifact:install-provider artifactId="wagon-ssh" version="1.0-beta-7"/>
       <artifact:pom id="maven.project" file="${maven.build.dir}/pom.xml" />
       <artifact:deploy file="@{jar.file}">
-        <remoteRepository url="${m2.repository.url}">
-          <authentication username="${m2.repository.username}" privateKey="${m2.repository.private.key}"
password="${m2.repository.password}"/>
-        </remoteRepository>
+        <remoteRepository id="${m2.repository.id}" url="${m2.repository.url}"/>
         <pom refid="maven.project"/>
       </artifact:deploy>
     </sequential>
{noformat}

Committing shortly.
                
> Please push maven snapshots to repositories.apache.org again
> ------------------------------------------------------------
>
>                 Key: LUCENE-3825
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3825
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: general/build
>    Affects Versions: 4.0
>            Reporter: Benson Margulies
>         Attachments: LUCENE-3825-add-scm-to-poms-trunk.patch
>
>
> Once upon a time, snapshots of the lucene trunk went into the snapshot repo at repositories.apache.org.
No longer. Instead, they just sit at:
> https://builds.apache.org//job/Lucene-Solr-Maven-trunk/lastSuccessfulBuild/artifact/maven_artifacts/
> Unfortunately, Jenkins makes a rather mediocre maven repo. the maven-wagon-plugin can't
copy it and Nexus can't proxy it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message