Hi,
Depending on snapshots is not a good idea, because snapshots are
volatile by definition. You'd rather depend on a stabler repository that
doesn't risk to change that often.
However, I don't know what can be considered as a stable URL for
Nebula... Apparently, there's nothing like that yet.
What I'd advise is the following structure:
* http://download.eclipse.org/technology/
** snapshots/ (where the latest CI build would be published, for testing
purpose)
** releases/ (home of releases)
*** 1.0.0/ (named releases)
*** 1.0.1/
*** 1.1.0/
*** ....
*** latest/ (would be either a copy of the latest release repo, or some
composite files pointing to the latest release repo).
Then consumers could reference a static site
http://download.eclipse.org/technology/nebula/release/1.0.1 in their
build. Content wouldn't change so they wouldn't be broken. However, with
such URLs, customers have to monitor project activity and manually
update the .target/products/pom files to get a new version.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
_______________________________________________
nebula-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/nebula-dev
