lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Rowe (Commented) (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3825) Please push maven snapshots to again
Date Wed, 07 Mar 2012 11:48:57 GMT


Steven Rowe commented on LUCENE-3825:

bq. Perhaps the last step is to now modify README.maven to point to
instead of Jenkins?

Done - see [r1296722|]
and [r1296723|].

bq. As an aside, do you know why SSL is mandatory to access nexus? [...] If you don't know
the answer, who/how should I inquire further?

Sorry, I don't know the answer to either question.  I would start asking either on #asfinfra
or, and they should be able to point you to the right person.
> Please push maven snapshots to again
> ------------------------------------------------------------
>                 Key: LUCENE-3825
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: general/build
>    Affects Versions: 4.0
>            Reporter: Benson Margulies
>            Assignee: Steven Rowe
>             Fix For: 3.6, 4.0
>         Attachments: LUCENE-3825-add-scm-to-poms-trunk.patch
> Once upon a time, snapshots of the lucene trunk went into the snapshot repo at
No longer. Instead, they just sit at:
> 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:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message