On 01/23/2013 06:10 PM, Jesse McConnell wrote:
[snip]
Unless you get Denis and the webmasters to bring maven.eclipse.org
<http://maven.eclipse.org> under the 5 9's support it is not a good
thing to do to your users IMO. Builds are critical.
For what it's worth, doing just that is on Thanh's list of things to do.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=394792
If memory serves me correctly, I believe he plans on tackling our
Maven/repo story in February.
Denis
Anyway, on a Vert.x thread about them coming to eclipse Wayne said
that there were big plans for maven.eclipse.org
<http://maven.eclipse.org> and it could turn into a safe place to put
your artifacts....as of right now though I would shy away until it has
a clear mandate that is widely communicated (ie wayne's comments on
that vert.x thread were news to me :)
cheers,
jesse
--
jesse mcconnell
jesse.mcconn...@gmail.com <mailto:jesse.mcconn...@gmail.com>
On Wed, Jan 23, 2013 at 4:32 PM, Jesse McConnell
<jesse.mcconn...@gmail.com <mailto:jesse.mcconn...@gmail.com>> wrote:
IMO
deploy it to central through oss.sonatype.org
<http://oss.sonatype.org>
maven.eclipse.org <http://maven.eclipse.org> has no clear mandate
at this point, no path to having artifacts sent to maven central,
and when you go into maven central you have to work out the orbit
dependency issues yourself which is important. (which also
currently have no path to maven central either)
cheers,
jesse
--
jesse mcconnell
jesse.mcconn...@gmail.com <mailto:jesse.mcconn...@gmail.com>
On Wed, Jan 23, 2013 at 4:18 PM, Kissner, Juergen
<juergen.kiss...@sap.com <mailto:juergen.kiss...@sap.com>> wrote:
Hi,
on behalf of the Eclipse Gemini project[1], I would like to
collect some information concerning the maven.eclipse.org
<http://maven.eclipse.org> repository. The subject has been
brought up in a post in our forum[2]. Obviously, it would be
nice for users of Eclipse Maven artifacts to access them
through a central repository.
The Gemini sub projects offer their Maven artifacts in a
common repository as described in [3]. This is true for
released versions. However, each sub projects has its own
private Maven repository for milestones. The Maven artifacts
of most projects still require some manual steps.
For the Gemini project and its users the maven.eclipse.org
<http://maven.eclipse.org> looks like an attractive option.
We have discussed the subject, but had still several question,
as you can see in our meeting minutes[4].
I have discovered the wiki page [5], and have been looking at
the dash mailing list. From the wiki, the repository and [6],
I have the impression that the repository is still work in
progress.
What is your recommendation?
Would it be possible to
1)replicate our Gemini repository [6] to maven.eclipse.org
<http://maven.eclipse.org>
2)access the replicated repository using the repository url
like <url>http://maven.eclipse.org/release</url>
3)browsed our artifacts with Nexus?
Clearly, it would be essential for our users to access a
repository that will not vanish in the near future. Would
there be any decision at some stage which somehow guarantees
the survival of the repository for some time?
How should we proceed, if we think that the repository would
be a good choice?
Thanks a lot,
Juergen
[1] http://eclipse.org/gemini/
[2] http://dev.eclipse.org/mhonarc/lists/dash-dev/msg01332.html
[3] http://wiki.eclipse.org/Gemini/mvn
[4] http://wiki.eclipse.org/Gemini/Meetings/Minutes_Jan_15_2013
[5] http://wiki.eclipse.org/Maven
[6] http://download.eclipse.org/gemini/mvn/
_______________________________________________
dash-dev mailing list
dash-dev@eclipse.org <mailto:dash-dev@eclipse.org>
https://dev.eclipse.org/mailman/listinfo/dash-dev
_______________________________________________
dash-dev mailing list
dash-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/dash-dev
