Guys - please remember Alpha1 is *not* meant to be without test errors.
That is *normal* when we upgrade Eclipse release train.
What alpha1 is for is to fix compilation errors and get issues found
related to the upgrade - and any issue that can't be easily fixed gets
a jira marked as critical for Alpha2 to look into.
/max
On Thu, Dec 05, 2013 at 10:03:38AM +0100, Mickael Istria wrote:
Here are some errors that IMO, requires to postpone the codefreeze:
* jsf tests has a compilation errors
* jbosstools-forge has compilation errors
* jbosstools-vpe has compilation errors (related to the one in jsf)
And some things that needs to be investigated:
* jbosstools-base has test failures and timeout
* jbosstools-central has test failures and timeout
* jbosstools-hibernate has test timeout
As a reminder, all this can be observed by looking at the jenkins
status and reading the notifications sent by jenkins.
Also, all those jobs are now built using the 4.40.0.Alpha1-SNAPSHOT
which is based on Luna M3. So if you're done with JBT 4.1.1, you
should make sure you're using this new target-platform while
developing.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <
http://www.jboss.org/tools>
My blog <
http://mickaelistria.wordpress.com> - My Tweets
<
http://twitter.com/mickaelistria>
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev