<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix"><br>
The new TP includes the updated Sapphire v.
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
9.0.0.201505051659.<br>
Sapphire was updated in M7 and this version is not compatible with
Sapphire
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
v.9.0.0.201408261741 which was included in Mars TP before (M1-M6)<br>
<br>
Batch and Arquillian tools require Sapphire. It's not a big deal
for us to migrate Batch and Arquillian to new Sapphire API.<br>
But the problem is that the new Sapphire (M7) has <b>RequiredExecutionEnvironment:
JavaSE-1.8</b><br>
<br>
If we can't require Java 8 for Batch and Arquillian then we have
to switch to Sapphire 8.2 from 9.0 in our TP.<br>
Sapphire 8.2 supports Mars but Mars update site includes Sapphire
9.0. only.<br>
<br>
How are we going to deal with that?<br>
<br>
<br>
On 05/07/2015 09:26 AM, Nick Boldt wrote:<br>
</div>
<blockquote cite="mid:554B924B.6090505@redhat.com" type="cite">
<pre wrap="">Here is a proposal for a change to the JBoss Tools and Red Hat JBoss
Developer Studio 4.50.0.Beta1-SNAPSHOT target platforms.
<a class="moz-txt-link-freetext" href="https://github.com/jbosstools/jbosstools-target-platforms/pull/142/">https://github.com/jbosstools/jbosstools-target-platforms/pull/142/</a>
It consists in the following change(s):
* JBIDE-19776: Create and use Mars M7 target-platform
p2diff reports:
<a class="moz-txt-link-freetext" href="https://issues.jboss.org/secure/attachment/12389427/jbosstools.p2diff.txt">https://issues.jboss.org/secure/attachment/12389427/jbosstools.p2diff.txt</a>
<a class="moz-txt-link-freetext" href="https://issues.jboss.org/secure/attachment/12389428/jbdevstudio.p2diff.txt">https://issues.jboss.org/secure/attachment/12389428/jbdevstudio.p2diff.txt</a>
Please review the above PR(s), as it will be applied as soon as possible.
You can use the following to build & test the target-platform locally
against your component(s).
Build target-platform:
cd jbosstools-target-platforms/jbosstools/multiple
git checkout
<a class="moz-txt-link-freetext" href="https://github.com/jbosstools/jbosstools-target-platforms/pull/142/">https://github.com/jbosstools/jbosstools-target-platforms/pull/142/</a>
mvn clean install
Or, without hub:
cd jbosstools-target-platforms/jbosstools/multiple
git fetch origin pull/142/head && git checkout FETCH_HEAD
mvn clean install
Try with just built target-platform:
$ cd /path/to/your/component
$ mvn clean verify -Dtpc.version=4.50.0.Beta1-SNAPSHOT -Pmultiple.target
--
If you want to perform a scripted install of the entire target platform
into your local Eclipse or JBDS instance, you can now do so with this
script:
<a class="moz-txt-link-freetext" href="https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/installFromTarget.sh">https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/installFromTarget.sh</a>
Usage is documented in the above script, and in this README:
<a class="moz-txt-link-freetext" href="https://github.com/jbosstools/jbosstools-target-platforms/tree/master#updating-versions-of-ius-in-target-files">https://github.com/jbosstools/jbosstools-target-platforms/tree/master#updating-versions-of-ius-in-target-files</a>
--
</pre>
</blockquote>
<br>
</body>
</html>