1:51 p.m.
Hi all,
I've heard several complaints and seen several confusing issues caused
by the incompatibility between Tycho 0.18.0 and Maven 3.1. We're still
using Tycho 0.18.0 on jbosstools-4.1.x branch which makes it only
compatible with Maven 3.0.
Tycho 0.18.1 was released some time ago to fix that, and the master
branch is already using it. So I'm suggesting to move also the 4.1.x
branch to Tycho 0.18.1. Cf https://issues.jboss.org/browse/JBIDE-15585
and https://github.com/jbosstools/jbosstools-build/pull/112 . Does
anyone have any objection about merging that pull request?
Cheers,
--
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>
3:27 p.m.
Tycho 0.18.1 to be able to compile with 3.1 is fine by me.
But main mvn version is still mvn 3.0 for the branch.
/max
On Mon, Sep 30, 2013 at 01:51:12PM +0200, Mickael Istria wrote:
Hi all,
I've heard several complaints and seen several confusing issues caused
by the incompatibility between Tycho 0.18.0 and Maven 3.1. We're still
using Tycho 0.18.0 on jbosstools-4.1.x branch which makes it only
compatible with Maven 3.0.
Tycho 0.18.1 was released some time ago to fix that, and the master
branch is already using it. So I'm suggesting to move also the 4.1.x
branch to Tycho 0.18.1. Cf https://issues.jboss.org/browse/JBIDE-15585
and https://github.com/jbosstools/jbosstools-build/pull/112 . Does
anyone have any objection about merging that pull request?
Cheers,
--
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
4:55 p.m.
Since forge will need this for JBT 4.1.1.Beta1, and there's no real
danger IMHO in moving all the JBT projects from 0.18.0 to 0.18.1, I
would +1 this PR.
Max, why do you prefer to keep this change local to Forge only?
N
On 09/30/2013 09:27 AM, Max Rydahl Andersen wrote:
Tycho 0.18.1 to be able to compile with 3.1 is fine by me.
But main mvn version is still mvn 3.0 for the branch.
/max
On Mon, Sep 30, 2013 at 01:51:12PM +0200, Mickael Istria wrote:
> Hi all,
>
> I've heard several complaints and seen several confusing issues caused
> by the incompatibility between Tycho 0.18.0 and Maven 3.1. We're still
> using Tycho 0.18.0 on jbosstools-4.1.x branch which makes it only
> compatible with Maven 3.0.
> Tycho 0.18.1 was released some time ago to fix that, and the master
> branch is already using it. So I'm suggesting to move also the 4.1.x
> branch to Tycho 0.18.1. Cf https://issues.jboss.org/browse/JBIDE-15585
> and https://github.com/jbosstools/jbosstools-build/pull/112 . Does
> anyone have any objection about merging that pull request?
>
> Cheers,
> --
> 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
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
5 p.m.
On 09/30/2013 04:55 PM, Nick Boldt wrote:
Since forge will need this for JBT 4.1.1.Beta1, and there's no
real
danger IMHO in moving all the JBT projects from 0.18.0 to 0.18.1, I
would +1 this PR.
Ok, thanks, I'm merging it then.
Moreover, the migration from Tycho 0.18.0 to 0.18.1 on master some weeks
ago happened vithout any issue.
Max, why do you prefer to keep this change local to Forge only?
What I understood is that it's OK to move the whole branch to Tycho
0.18.1, however, let's keep Maven 3.0 and use Maven 3.1 for Forge when
we need it.
--
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>
5:14 p.m.
+1, I see no need to update any of the jobs (other than Forge, which
already does) to use 3.1 until they specifically require it.
We could update them all to 3.0.5, however (many are still on 3.0.4).
N
On 09/30/2013 11:00 AM, Mickael Istria wrote:
On 09/30/2013 04:55 PM, Nick Boldt wrote:
> Since forge will need this for JBT 4.1.1.Beta1, and there's no real
> danger IMHO in moving all the JBT projects from 0.18.0 to 0.18.1, I
> would +1 this PR.
Ok, thanks, I'm merging it then.
Moreover, the migration from Tycho 0.18.0 to 0.18.1 on master some weeks
ago happened vithout any issue.
> Max, why do you prefer to keep this change local to Forge only?
What I understood is that it's OK to move the whole branch to Tycho
0.18.1, however, let's keep Maven 3.0 and use Maven 3.1 for Forge when
we need it.
--
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>
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
5:55 p.m.
On Mon, Sep 30, 2013 at 11:14:53AM -0400, Nick Boldt wrote:
+1, I see no need to update any of the jobs (other than Forge, which
already does) to use 3.1 until they specifically require it.
This is why I wanted to limit it in forge for the branch at least.
For master it might make sense to use 3.1 - but I really would like to grok what changed
between maven 3.0 and 3.1 since historically we get bitten somehow on each maven upgrade.
We could update them all to 3.0.5, however (many are still on 3.0.4).
If majority is on 3.0.5 then yeah lets use the same across the builds.
/max
N
On 09/30/2013 11:00 AM, Mickael Istria wrote:
>On 09/30/2013 04:55 PM, Nick Boldt wrote:
>>Since forge will need this for JBT 4.1.1.Beta1, and there's no real
>>danger IMHO in moving all the JBT projects from 0.18.0 to 0.18.1, I
>>would +1 this PR.
>Ok, thanks, I'm merging it then.
>Moreover, the migration from Tycho 0.18.0 to 0.18.1 on master some weeks
>ago happened vithout any issue.
>
>>Max, why do you prefer to keep this change local to Forge only?
>What I understood is that it's OK to move the whole branch to Tycho
>0.18.1, however, let's keep Maven 3.0 and use Maven 3.1 for Forge when
>we need it.
>--
>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>
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
3882
days inactive
3882
days old
jbosstools-dev@lists.jboss.org
5 comments
3 participants
participants (3)
-
Max Rydahl Andersen -
Mickael Istria -
Nick Boldt