[jbosstools-dev] About m2e-wtp releases

Fred Bricon fbricon at redhat.com
Mon Jul 25 05:24:50 EDT 2011


Hi,

I spoke with Igor this morning on IRC. He said he was out from work for 
the last couple of weeks and has " a few things to do before [he]'ll get 
a chance to look at the update site". Meaning anything could happen 
between today and the end of the week.
He knows he's the bottleneck when it comes to m2e-wtp releases and still 
expects us to do the releases ourselves, as we discussed when 0.13.0 got 
out.

I think it's really time for us to host m2e-wtp. It could be "simple" 
... or not :
1 - We need to ask Sonatype to let us change the "provider" name (maybe 
other mentions) of the plugins to Red Hat|JBoss by Red Hat| JBoss a Red 
Hat division. Current namespace used throughout the plugin is 
org.maven.ide.*, it doesn't need to change.

Provided we agree on that, then :
2 - Since we have a Nexus pro instance at JBoss, we could deploy 
unzipped update sites there (similar to previous flow at Sonatype). But 
I think we need to have a single update site for m2e-wtp releases, as we 
do for the nightlies. As soon as we provide the single update site URL 
to Igor, we won't need Sonatype, at all, for subsequent releases. Not 
having that single URL means asking Igor to point to the new version URL 
in their m2e marketplace, every time m2e-wtp is released.

But then it gets trickier :
3 - do we keep the current github repo 
(https://github.com/sonatype/m2eclipse-wtp) or should we fork it 
elsewhere (on a jboss, jbosstools or m2e-wtp account)
4 - m2e-wtp JIRA is hosted / maintained by Sonatype. It would seem 
logical to migrate the issues off of their system. If so, where to and how?
5 - But then, some time in the future, who knows, m2e-wtp might be 
managed under the Eclipse umbrella. Not sure we'd want to go through 
*another* migration process.

So, in my opinion, doing just #1 and #2 would allow us (and the project) 
to keep being productive. We need to decide first if/when we want to go 
the eclipse route, before settling on #3/#4/#5.

If we can setup #2, I (or Max) 'll send a mail to Sonatype asking 
permission to change the provider name and ask their opinion on the 
other questions.

WDYT?

Regards,

Fred Bricon



More information about the jbosstools-dev mailing list