Re: [jbosstools-dev] Getting 3.3.0.M2 ready for June/AS 7 launch

>> * Running on Eclipse 3.7 final release (i.e. the maven/m2e is currently broken) >> > > 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. Do we have a jira for it outlining what Nick needs/should do ? If yes, mark it as blocker for 3.0.0.M2 If no, create one, and mark it as blocker for 3.0.0.M2 Simple :) /max > > Snjeza > >> * 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 >> http://about.me/maxandersen >> >> >> >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> >> > /max http://about.me/maxandersen _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev