Re: [m2e-wtp-dev] m2e-wtp RC1 and the mavenarchiver issue

[Fred Bricon <fbricon@xxxxxxxxx>]

Awesome Sharon from the IP team already cleared the CQ so this became a non-issue \o/

I'll release m2e-wtp 0.16.0 RC1 along with mavenarchiver 0.15.0.201207090125 tomorrow around noon (Paris time)

Regards,

Fred Bricon

On Tue, Aug 21, 2012 at 7:29 PM, Chuck Bridgham <cbridgha@xxxxxxxxxx> wrote:

Also vote for #1 - the right thing to do...


Thanks - Chuck

Senior Architect, RAD Java EE Tools, WTP PMC Lead
IBM Software Lab - Research Triangle Park, NC



From:        Fred Bricon <fbricon@xxxxxxxxx>
To:        M2E-WTP Developers mailing list <m2e-wtp-dev@xxxxxxxxxxx>
Cc:        Wayne Beaton <emo@xxxxxxxxxxx>
Date:        08/21/2012 12:56 PM

Subject:        [m2e-wtp-dev] m2e-wtp RC1 and the mavenarchiver issue

Sent by:        m2e-wtp-dev-bounces@xxxxxxxxxxx

---

Hi,

I was fairly confident in releasing m2e-wtp 0.16.0 RC1 tomorrow until a user reported an incompatibility between mavenarchiver 0.15.0.201109290002, 
(which is added to m2e-wtp's update site) and m2e 1.2, which is about to be released : mavenarchiver declares an m2e dependency with a range of  [1.0.0, 1.2.0)

I didn't see the problem earlier because my local environment already uses mavenarchiver 0.15.0.201207090125 and m2e 1.2, while the CI builds compile m2e-wtp against m2e 1.1.
So it's really my bad.

I created CQ 6501 so we can publish the proper mavenarchiver version but, even though it's priority was bumped to P2, I don't know when it's gonna be approved (for the record, it's the same code between the 2 versions, only difference is the m2e requirements changed to [1.0.0, 2.0.0)) and it will probably not be ready for tomorrow (I'd love to be proved wrong).

We initially wanted to release on Aug 22nd to be on par with the Juno SR1/Kepler release train but since m2e-wtp is not actually part of the release train, I hope it's not a big deal if we slip a few days behind.

So, here are the options :
1 - we hold the RC1 release till we get approval to publish mavenarchiver 0.15.0.201207090125
2 - we release RC1 tomorrow with mavenarchiver 0.15.0.201207090125 before we get approval (cause I'm a rebel you know :-)) and remove it if we get caught by Wayne or it's not approved eventually.
3 - we release RC1 tomorrow and keep the old mavenarchiver 0.15.0.201109290002 in the update site. This will cause a lot of installation issues for users upgrading m2e to 1.2. They will need to add  http://repository.tesla.io:8081/nexus/content/sites/m2e.extras/m2eclipse-mavenarchiver/0.15.0/N/0.15.0.201207090125/ to their available update sites before actually installing m2e-wtp.

I'm 50-50 on #1 and #3. What do you think?

I was also planning on doing a dev call this week but I'm still waiting to get a new conf #.

Regards,

Fred Bricon.

--

"Have you tried turning it off and on again" - The IT Crowd

_______________________________________________
m2e-wtp-dev mailing list
m2e-wtp-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev


_______________________________________________
m2e-wtp-dev mailing list
m2e-wtp-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev

--
"Have you tried turning it off and on again" - The IT Crowd