[dash-dev] Maven repositories at Eclipse

[Alex Blewitt]

I have set up the Maven Eclipse repositories as follows:

* build {central,sonatype,codehaus} - for executing builds against e.g. pluginDependency (mirror)
* build-snapshots {codehaus-snapshots) - for David's FindBugs dependency for those that need it (mirror)
* integration {integration-juno} - for I builds (-SNAPSHOT)
* milestone {milestone-juno} - for M builds (release)
* nightly {nightly-juno} - for N builds (-SNAPSHOT)
* release {release-helios,release-ganymede} - for releases (release)
* orbit - for orbit approved dependencies
* testing - for our testing purposes

I have put these repositories under /home/nexus/repositories with the nightly/milestone/integration as parent directories. This should allow us to roll forward with new releases as they come up, whilst aggregating under the repository URL for the group.

I have put {integration,milestone,nightly,release} as the defined set for the public repositories. I'm unsure what to do for orbit. If we include it in the public repositories, then it may prevent others from consuming from there and central. On the other hand, there may be some things in orbit which aren't available elsewhere that we need to address. I suspect we can fix this subsequently.

Lastly, this will be a little ugly as a URL:

http://maven.eclipse.org/nexus/content/groups/public

We may want to set up a rewrite rule so that (e.g.)

http://maven.eclipse.org/maven2/ -> http://maven.eclipse.org/nexus/content/groups/public

which would then let us use http://maven.eclipse.org/maven2 as the pubic facing URL for access to the outside world.

Alex

[Aaron Digulla]

Post by Alex Blewitt
I have put these repositories under /home/nexus/repositories with the
nightly/milestone/integration as parent directories. This should allow
us to roll forward with new releases as they come up, whilst
aggregating under the repository URL for the group.

Very good. I like it.

Post by Alex Blewitt
I have put {integration,milestone,nightly,release} as the defined set
for the public repositories. I'm unsure what to do for orbit. If we
include it in the public repositories, then it may prevent others from
consuming from there and central. On the other hand, there may be some
things in orbit which aren't available elsewhere that we need to
address. I suspect we can fix this subsequently.

How about another virtual repo which includes public and orbit? That
way, we can have both.

Post by Alex Blewitt
http://maven.eclipse.org/nexus/content/groups/public
We may want to set up a rewrite rule so that (e.g.)
http://maven.eclipse.org/maven2/
-> http://maven.eclipse.org/nexus/content/groups/public
which would then let us use http://maven.eclipse.org/maven2 as the
pubic facing URL for access to the outside world.

Agreed. But I'd map http://maven.eclipse.org/maven2/ to
http://maven.eclipse.org/nexus/content/groups/
<http://maven.eclipse.org/nexus/content/groups/public> (i.e. one level
above) so that all public groups appear under that URL.

Regards,

[Alex Blewitt]

Am 20.03.2011 15:13, schrieb Alex Blewitt

Post by Alex Blewitt
I have put {integration,milestone,nightly,release} as the defined set for the public repositories. I'm unsure what to do for orbit. If we include it in the public repositories, then it may prevent others from consuming from there and central. On the other hand, there may be some things in orbit which aren't available elsewhere that we need to address. I suspect we can fix this subsequently.

How about another virtual repo which includes public and orbit? That way, we can have both.

Makes some sense - what to call it though?

Post by Alex Blewitt
http://maven.eclipse.org/nexus/content/groups/public
We may want to set up a rewrite rule

Agreed. But I'd map http://maven.eclipse.org/maven2/ to http://maven.eclipse.org/nexus/content/groups/ (i.e. one level above) so that all public groups appear under that URL.

/maven2/ is typically not a set of repos but rather a single (albeit virtual) repo. There's no reason we couldn't set up short names for others if desired e.g. /milestone -> /nexus/content/groups/milestone - but I wouldn't want to expose the set of them, not the least of which is that groups URL contains more than just Eclipse content.

Alex

[Alex Blewitt]

Post by Aaron Digulla

Post by Alex Blewitt
I have put these repositories under /home/nexus/repositories with the nightly/milestone/integration as parent directories. This should allow us to roll forward with new releases as they come up, whilst aggregating under the repository URL for the group.

Very good. I like it.

I forgot indigo; I've created nightly, integration and milestone repositories for these and added them to the appropriate groups, and updated the wiki appropriately.

Alex

[Aaron Digulla]

Post by Alex Blewitt
I forgot indigo; I've created nightly, integration and milestone
repositories for these and added them to the appropriate groups, and
updated the wiki appropriately.

Can you please try to import them (or part of them) and let me know
your thoughts on my tools?

Regards,