lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Rowe (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LUCENE-3825) Please push maven snapshots to repositories.apache.org again
Date Mon, 27 Feb 2012 05:58:48 GMT

     [ https://issues.apache.org/jira/browse/LUCENE-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Steven Rowe updated LUCENE-3825:
--------------------------------

    Attachment: LUCENE-3825-add-scm-to-poms-trunk.patch

According to http://www.apache.org/dev/publishing-maven-artifacts.html#prepare-poms item #3,
all POMs should have SCM sections.

I had previously thought that a single SCM section in the lucene-solr-grandparent POM would
do the trick, but upon inspection of the output from {{mvn help:effective-pom}}, I can see
that the grandparent POM's section doesn't properly interpolate {{$\{module-directory}}{{\}}}
(since the property isn't defined in that POM), and the values inherited in other POMs are
all wrong, because path steps are added with artifact names instead of directory names, in
addition to {{$\{module-directory}}{{\}}} interpolation...

Anyway, this patch fixes the SCM definition problem for trunk POMs.  I'll do the same for
branch_3x too.

I didn't included SCM sections in the few aggregation-only POMs, since these are never deployed/released.

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