[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[m2e-dev] Questions about the m2eclipse-wtp release process
|
Hi,
as I indicated in a previous mail, JBoss provides nightly builds of m2eclipse-wtp 0.13.0 at
download.jboss.org/jbosstools/builds/staging/m2eclipse-wtp-e36/all/repo/
This version is compatible with m2e 1.0.0. So we intend to release a final version at some point around the Indigo release (June 22nd).
In order to prepare the next release of m2eclipse-wtp (and subsequent ones), I can imagine several options :
1 - On release day, we ask Sonatype to point its m2eclipse-extras update site to the JBoss update site.
That means JBoss needs to provide access to versioned builds - only the latest dev build is set up so far-
2 - On release day, Sonatype builds and publishes m2eclipse-wtp on its own infrastructure, given a tagged version in github, then updates the m2eclipse-extras update site
3 - Sonatype grants JBoss deploy access to its forge-site repo, so m2eclipse-wtp builds can be pushed / released directly by JBoss on the target update site, at any time
4 - On release day, JBoss provides a zipped update site to Sonatype. Sonatype does all the necessary updates / deployments
Obviously, #1 seems the most flexible solution, however the m2eclipse-wtp project is currently owned by Sonatype. As such, it would make sense
for the release builds to be hosted on Sonatype's infra (legally speaking).
So, what's the plan? :-)
Fred Bricon
--
"Have you tried turning it off and on again" - The IT Crowd
