11:22 a.m.
Changes (compared to 4.40.0.Beta1)
=======
In the category "Fix dependencies" (after the cleanup of previous release)
* JBIDE-16910: Fix some dependencies for Atlassian (Mylyn)
* JBIDE-16960: Removed GWT
* JBIDE-17019: Add m2eclipse-egit
* JBDS-3003: Add TestNG (JBDS only)
* JBIDE-17160: Add Tern.java
* JBIDE-17254: Move to Luna M7
* JBIDE-17266: Remove Birt (hopefully temporary)
Usage
=====
Target platform 4.40.0.Beta2 is what JBoss Tools 4.2.0.Beta2 will use.
All Jenkins jobs for branch and parent pom 4.2.0.Beta2-SNAPSHOT have
been updated to use target platform 4.40.0.Beta2.
The following p2 repositories *will be modified* to point to this new
target platform once JBoss Tools 4.2.0.Beta2 is released:
*
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/
*
http://download.jboss.org/jbosstools/targetplatforms/jbdevstudiotarget/luna/
*
http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/luna/
Download
========
Update site:
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4...
Update site zip:
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4...
.zip
Git tag:
https://github.com/jbosstools/jbosstools-target-platforms/tree/4.40.0.Beta2
Testing/Development
===================
If your root pom correctly specifies the latest parent pom version as
4.2.0.Beta2-SNAPSHOT, you need only this:
$ mvn clean verify
If you're using a different parent pom, use this:
$ mvn clean verify -Dtpc.version=4.40.0.Beta2
For advanced usage and help (using in IDE, building a mirror locally,
using a zip), see
https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ...
What's next?
============
jbosstools-target-platforms project branch 4.40.x has been prepared for
potential upgrades, and its version is now 4.40.0.Beta3-SNAPSHOT. We can
at least expect for Beta3:
* Move to Luna release/R/SR0
* Re-introduction of a compatible version of Birt
* Shall you need anything else, please follow those instructions to
request a change ASAP:
https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ...
All Jenkins jobs for *master* have been updated to use target platform
4.40.0.Beta3-SNAPSHOT.
--
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:11 p.m.
Seems we released this a bit too hastily. A 4.40.0.Beta3 is in progress
now, which will fix these issues:
* updated BIRT, compatible w/ M7: JBIDE-17266
* updated m2e.java & m2e.apt: JBIDE-16757, JBIDE-17306
* updated tern.java: JBIDE-17317
On 05/20/2014 12:22 PM, Mickael Istria wrote:
Changes (compared to 4.40.0.Beta1)
=======
In the category "Fix dependencies" (after the cleanup of previous release)
* JBIDE-16910: Fix some dependencies for Atlassian (Mylyn)
* JBIDE-16960: Removed GWT
* JBIDE-17019: Add m2eclipse-egit
* JBDS-3003: Add TestNG (JBDS only)
* JBIDE-17160: Add Tern.java
* JBIDE-17254: Move to Luna M7
* JBIDE-17266: Remove Birt (hopefully temporary)
Usage
=====
Target platform 4.40.0.Beta2 is what JBoss Tools 4.2.0.Beta2 will use.
All Jenkins jobs for branch and parent pom 4.2.0.Beta2-SNAPSHOT have
been updated to use target platform 4.40.0.Beta2.
The following p2 repositories *will be modified* to point to this new
target platform once JBoss Tools 4.2.0.Beta2 is released:
*
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/
*
http://download.jboss.org/jbosstools/targetplatforms/jbdevstudiotarget/luna/
*
http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/luna/
Download
========
Update site:
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4...
Update site zip:
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4...
.zip
Git tag:
https://github.com/jbosstools/jbosstools-target-platforms/tree/4.40.0.Beta2
Testing/Development
===================
If your root pom correctly specifies the latest parent pom version as
4.2.0.Beta2-SNAPSHOT, you need only this:
$ mvn clean verify
If you're using a different parent pom, use this:
$ mvn clean verify -Dtpc.version=4.40.0.Beta2
For advanced usage and help (using in IDE, building a mirror locally,
using a zip), see
https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ...
What's next?
============
jbosstools-target-platforms project branch 4.40.x has been prepared for
potential upgrades, and its version is now 4.40.0.Beta3-SNAPSHOT. We can
at least expect for Beta3:
* Move to Luna release/R/SR0
* Re-introduction of a compatible version of Birt
* Shall you need anything else, please follow those instructions to
request a change ASAP:
https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ...
All Jenkins jobs for *master* have been updated to use target platform
4.40.0.Beta3-SNAPSHOT.
--
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
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
7:50 p.m.
New subject: parent pom broken?
Got this error when trying to build jst (master):
[ERROR] Internal error: java.lang.RuntimeException: No solution found
because the problem is unsatisfiable.: [Unable to satisfy dependency
from org.jboss.tools.jst.jsdt 3.6.0.qualifier to bundle
com.googlecode.json-simple 1.1.1.; No solution found because the problem
is unsatisfiable.] -> [Help 1]
org.apache.maven.InternalErrorException: Internal error:
java.lang.RuntimeException: No solution found because the problem is
unsatisfiable.: [Unable to satisfy dependency from
org.jboss.tools.jst.jsdt 3.6.0.qualifier to bundle
com.googlecode.json-simple 1.1.1.; No solution found because the problem
is unsatisfiable.]
7:52 p.m.
New subject: parent pom broken?
This is because
https://github.com/jbosstools/jbosstools-build/commit/bba1cad1f3c6a30c1d3....
Parent pom in master has version beta2, but references tp beta3.
Denis
On 05/21/2014 05:50 PM, Alexey Kazakov wrote:
Got this error when trying to build jst (master):
[ERROR] Internal error: java.lang.RuntimeException: No solution found
because the problem is unsatisfiable.: [Unable to satisfy dependency
from org.jboss.tools.jst.jsdt 3.6.0.qualifier to bundle
com.googlecode.json-simple 1.1.1.; No solution found because the problem
is unsatisfiable.] -> [Help 1]
org.apache.maven.InternalErrorException: Internal error:
java.lang.RuntimeException: No solution found because the problem is
unsatisfiable.: [Unable to satisfy dependency from
org.jboss.tools.jst.jsdt 3.6.0.qualifier to bundle
com.googlecode.json-simple 1.1.1.; No solution found because the problem
is unsatisfiable.]
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
2:15 a.m.
So today is a bad day for target-platforms: some changes were requested
and applied after TP was released. We'll investigate whether those
changes were actually necessary and if they are worth a TP respin.
But please, do anticipate required TP change! We cannot afford to change
TP on the day of a code freeze, that's a risky operation that slows us
down our reduce our ability to ship on time and increase the risk of
respins for QA.
The date of target-platform releases are on the JBDS-Tech calendar. Make
sure your requests get it on time.
Although many supposed urgent changes were applied to
4.40.0.Beta2-SNAPSHOT (and may issues created/revealed as a side
effect), all that just shows that urgent changes in TP are not good at all.
So my plan/with is still to use 4.40.0.Beta2 if possible. Depending on
the criticity of the issues those changes try to fix, we can think about
building a 4.40.0.Beta3 TP for JBoss Tools 4.2.0.Beta2. But that clearly
is a bad thing because it would make the code-freeze more complex
(master currently testing against Beta3-SNAPSHOT whereas it will be
branched and built against Beta2 or maybe Beta3, we don't know yet....))
On 05/22/2014 12:11 AM, Nick Boldt wrote:
Seems we released this a bit too hastily. A 4.40.0.Beta3 is in
progress now, which will fix these issues:
* updated BIRT, compatible w/ M7: JBIDE-17266
This needs to be discussed. Maybe it
could be in a respin? Or just
dropped out of Beta2 and get back in Beta3
* updated m2e.java & m2e.apt: JBIDE-16757, JBIDE-17306
This
is far from being a blocker for Beta2.
* updated tern.java: JBIDE-17317
@Victor:
Is this really necessary? What blocker for beta2 was this change
supposed to fix? Couldn't you keep on depending on previous version of
tern.java for 4.2.0.Beta2 ?
How come you didn't request it earlier (before TP 4.40.0.Beta2 was released)
--
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>
3638
days inactive
3640
days old
jbosstools-dev@lists.jboss.org
4 comments
4 participants
participants (4)
-
Alexey Kazakov -
Denis Golovin -
Mickael Istria -
Nick Boldt