Just remember Staging Repository support is only available in Nexus if
you get the Nexus Pro version, which Sonatype has offered to you guys in
the past at no charge, but was turned down.
If hosting a Nexus Pro instance still goes against eclipse foundation
software usage guidelines, then the only alternative I see is doing a
partnership with oss.sonatype.org. If you want more control over the
repos and tieing everything into your Eclipse security infrastructure
then you need to hose a Nexus Pro instance.
I'll let you guys figure out the best way forward.
Remember also there are some qualitity assurance items that need to
happen as well to get items into Maven Central. Currently
oss.sonatype.org provides all those checks ahead of time.
Dave
On 01/31/2013 10:16 AM, Thanh Ha wrote:
I had a look at oss.sonatype.org's nexus instance and from what I
gather it provides each project with 4 repository services.
project-snapshots (hosted)
project-releases (hosted)
project-with-staging (group)
project repositories (group)
I think if we setup maven.eclipse.org with a similar model we can
achieve the releases with the "project-releases" service and
nightly/weekly builds with the "project-snapshots" service.
I'm new to Nexus so it's not clear to me what the difference between
the 2 groups are I hope someone who's used oss.sonatype.org might be
able to explain. If I had to guess "project repositories" is a group
containing the releases repo and project-with-staging contains both
snapshots and releases? I'm guessing these groups are alternative URLs
to the hosted repos?
As for an entry into maven central I think initially we won't be able
to provide this service as the focus will be on getting projects using
maven.eclipse.org but it's something we can look as the service ramps up.
Thanh
On 31/01/13 09:20 AM, Martin Taal wrote:
As a replacement of sonatype, I would need 2 things:
- a place to publish nightly/weekly builds
- an entry in maven central (with a 2 step procedure, that's fine)
I don't need the sonatype ui, so publishing/releasing through maven
commandline would be fine with me.
I think eclipse could offer a location for nightly builds (to be
consumed by maven) and entry point into maven central. Eclipse.org
does not need to offer an eternal durable maven repo. I would just
use maven central for that.
gr. Martin
With Regards, Martin Taal
Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Cell: +31 (0)6 288 48 943
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail:mt...@springsite.com -mt...@elver.org
Web:www.springsite.com -www.elver.org
On 01/31/2013 02:59 PM, Jesse McConnell wrote:
Martin,
And you would not want to use something @ eclipse that didn't have
the staging functionality that exists on oss.sonatype.org
<http://oss.sonatype.org> correct?
cheers,
jesse
--
jesse mcconnell
jesse.mcconn...@gmail.com <mailto:jesse.mcconn...@gmail.com>
On Thu, Jan 31, 2013 at 7:37 AM, Martin Taal <mt...@elver.org
<mailto:mt...@elver.org>> wrote:
I agree with Jesse...
Maybe it is best to take maven.eclipse.org down, but don't do
anything else unless someone takes responsibility and there is
funding to do so.
I currently publish EMF Texo/Teneo and EMF jars through
sonatypeto get them on maven.central. It works fine, but I find
it strange that eclipse projects have to use a 3rd party to get
their code on maven central. I would expect eclipse.org
<http://eclipse.org>to provide a service similar to sonatype...
Just my 2 cents...
gr. Martin
With Regards, Martin Taal
Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Cell:+31 (0)6 288 48 943 <tel:%2B31%20%280%296%20288%2048%20943>
Tel:+31 (0)84 420 2397 <tel:%2B31%20%280%2984%20420%202397>
Fax:+31 (0)84 225 9307 <tel:%2B31%20%280%2984%20225%209307>
Mail:mt...@springsite.com <mailto:mt...@springsite.com> -mt...@elver.org
<mailto:mt...@elver.org>
Web:www.springsite.com <http://www.springsite.com> -www.elver.org
<http://www.elver.org>
On 01/31/2013 02:32 PM, Jesse McConnell wrote:
I really don't understand the point of resetting it if there is
not a clear understanding of what roll it will serve within the
organization moving forward and a recommended path for how
projects will interact with it.
If it is only going to be a proxy for maven central, then that
is fine and you should go for it, but if you're planning on
having projects actually deploy to it and/or build out the
story for syncing to maven central then all of that should be
ironed out ahead of time and wired up accordingly.
Maven repositories are meant to be durable and exist forever,
unlike orbit repositories that are transitory and exist for
small windows of time. If you screw something up with Orbit
then no biggy, it will eventually just disappear and problem
solved. With a maven repository once it is released it is
locked away for time eternal, which is why I am such a strong
proponent of having staging repositories so upon release you
can give things a pre-flight check before releasing it and
locking it down.
Once you set this up and take ownership of it you are making a
contract with anyone that uses it that you will support the
stuff in there from that point on. None of this disappearing
repository stuff where you check out an old tag and some
repository you built against is now missing and perhaps
replaced with a different version of some dependency.
cheers,
jesse
--
jesse mcconnell
jesse.mcconn...@gmail.com <mailto:jesse.mcconn...@gmail.com>
On Thu, Jan 31, 2013 at 7:20 AM, Thanh Ha <thanh...@eclipse.org
<mailto:thanh...@eclipse.org>> wrote:
Hi Everyone,
Per Bug 394792 I'm looking at moving maven.eclipse.org
<http://maven.eclipse.org> to become a managed service at
Eclipse. I plan on tackling this issue soon and was
wondering if taking this server down would affect any projects?
Some things we'd like to do is update the Nexus server
version as well as restart the service from a fresh
configuration, essentially start over.
Thanks,
Thanh
_______________________________________________
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 <mailto:dash-dev@eclipse.org>
https://dev.eclipse.org/mailman/listinfo/dash-dev
_______________________________________________
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
_______________________________________________
dash-dev mailing list
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
