please add subtasks or link jiras up with details on build failure/reasons so
we can start getting a grasp of it. Thanks!
/max
On Wed, Oct 09, 2013 at 02:57:36PM -0700, Denis Golovin wrote:
I was testing new target platform and did rundom builds to see if
we're lucky
and no migration required.
jbosstools-base was fine, but jbosstools-server and jbosstools-hibernate
require migration.
Denis
On 10/09/2013 12:15 PM, Snjezana Peco wrote:
The portlet and birt components are built with the Luna target platform.
The arquilian component contains compile errors due to the change of OSGi
internals. I have created
https://issues.jboss.org/browse/JBIDE-15647.
Snjeza
On 10/9/2013 12:09 PM, Mickael Istria wrote:
Before we can make TP 4.40.0.Alpha1-SNAPSHOT the default target
platform on master branch in parent pom and CI jobs, it's important
that you tried it on your component and that you get an idea of how
much effort it is to migrate. To know that, just follow the
instructions in
https://issues.jboss.org/browse/JBIDE-15639 and report
your feedback here.
As usual, it's just a simple mvn clean verify -Ptpc.version=
4.40.0.Alpha1-SNAPSHOT on the master branch for your component.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev