<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
m2eclipse-wtp is currently built on the internal hudson :
<a class="moz-txt-link-freetext" href="https://hudson.qa.jboss.com/hudson/job/m2eclipse-wtp-e36/">https://hudson.qa.jboss.com/hudson/job/m2eclipse-wtp-e36/</a><br>
All is left is publishing the generated site and update the TP. I'm
sure Nick will be thrilled to fix it as soon as he can :-)<br>
<br>
In the mean time, for those who can't get past the Red Hat VPN,
looks like this update site <a
href="https://repository.sonatype.org/content/sites/forge-sites/m2eclipse-wtp/0.13.0/N/0.13.0.201105110807/"
target="_blank">https://repository.sonatype.<wbr>org/content/sites/forge-sites/<wbr>m2eclipse-wtp/0.13.0/N/0.13.0.<wbr>201105110807/</a>
should work with the latest m2e-core builds.<br>
<br>
regards,<br>
<br>
Fred Bricon<br>
<br>
On 27/05/2011 12:09, Snjezana Peco wrote:
<blockquote cite="mid:4DDF784D.5000007@redhat.com" type="cite">
<pre wrap="">Max Rydahl Andersen wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi,
AS 7 Final is planned to be done end of June, and so is Eclipse Indigo (3.7) meaning
getting a 3.3.0.M2 out in the planned timeframe - we had set 3.3.0.M2 currently planned to be released on 22nd
(same day as AS 7 and Eclipse 3.7 is going out)
Currently Jira has 148 issues open for this release - and almost none on the future releases.
I'm sure you don't all expect to do all 148 issues for M2 and then do nothing for M3, Beta1, Beta2 and CR1.
Could you *please* go over your assigned and component issues and state which ones you are going
to do for M2 and which you are moving of to later ?
That would make it possible to actually see what needs to be done for the release much easier for everyone.
When you do this please remember that 3.3.0.M2 has the primary goals of:
* Running on Eclipse 3.7 final release (i.e. the maven/m2e is currently broken)
</pre>
</blockquote>
<pre wrap="">
Maven/m2e problem can be easily fixed.
It is enough to create locally a m2eclipse-wtp update site compatible
with m2e-core placed in the JBT 3.7 TP and include that update site to
the JBT 3.7 TP.
Snjeza</pre>
</blockquote>
<blockquote cite="mid:4DDF784D.5000007@redhat.com" type="cite">
<blockquote type="cite">
<pre wrap="">* Work with AS 7 (start/stop/debug/run/deploy)
* Not suck
Thus if you are about to do major rework of some components and don't feel you can have it ready in
a not-suck state please do your work in a branch and merge it back to trunk *after* M2.
And those issues that does that are perfect candidates to have their jira fix version updated to M3.
Thank you!
/max
<a class="moz-txt-link-freetext" href="http://about.me/maxandersen">http://about.me/maxandersen</a>
_______________________________________________
jbosstools-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a>
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
jbosstools-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>