FYI: New JBT/JBDS Target Platforms for Kepler M4, Juno R and Juno SR0 (M5 and SR2 coming next month)
1:02 p.m.
On 01/23/2013 01:49 AM, Nick Boldt wrote:
After much refactoring, renaming, reorganizing, and (hopefully soon)
publishing to a github repo, we have 3 new target platforms for use with
builds.
These have as yet NOT been coupled up into the parent poms for the
40x/60x and 41x/70x streams so that you can have some time to try them
out. How do you use them? Via a standard maven build, but passing in
this additional flag:
> mvn clean install ... -DTARGET_PLATFORM_VERSION=4.20.5.Final-SNAPSHOT
Changes to the previous target platforms (other than refactoring [5] and
migration to a new github repo [6]) include the removal of source and
sdk features [7], so these are slimmer and trimmer than their
predecessors, previously referred to as JunoSR0c and JunoSR1a.
The new TPs, rather than being named for an Eclipse release train, will
now be named for the version of Eclipse included therein.
Thus:
* JunoSR0c (the 4th iteration) would be called 4.20.4.Final-SNAPSHOT
* JunoSR1a (the 2nd iteration) would be called 4.21.2.Final-SNAPSHOT
Therefore the new target platforms are:
* 4.20.5.Final-SNAPSHOT
* 4.21.3.Final-SNAPSHOT
* 4.30.0.Alpha1-SNAPSHOT
These are available here for JBT [1] and JBDS [2]:
[1] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/
[2]
http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbdevstudiotarget/
They are also mirrored for use with Jenkins - see settings.xml [3] for
details.
[3]
https://svn.jboss.org/repos/devstudio/trunk/hudson-jobs/settings/hudson-s...
All the TPs are being built with a single job [9], which next month will
grow to include target platforms for Juno SR2 (4.22.0.Final-SNAPSHOT)
and Kepler M5 (4.30.1.Alpha1-SNAPSHOT).
[9]
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Targ...
Publishing to the JBoss Nexus snapshots repo is now done to this path
[4], under which you'll now see jbdevstudio-multiple,
jbdevstudio-unified, jbosstools-multiple, & jbosstools-unified. We are
still making a distinction between multiple.target, which includes
multiple URLs, and unified.target, which points to the single unified
URL to which the TP is published ([1] or [2] above).
[4]
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
If you have any questions or comments, please post them here [5], [6],
[7], [8], or reply to this thread.
[5] https://issues.jboss.org/browse/JBIDE-13232 (refactor/rename/reorg)
[6] https://issues.jboss.org/browse/JBIDE-13386 (create new github repo)
[7] https://issues.jboss.org/browse/JBIDE-13329 (remove sources)
[8] https://issues.jboss.org/browse/JBIDE-13408 (remove SNAPSHOT suffix)
-------- Original Message --------
Subject: Re: New JBT/JBDS Target Platforms for Kepler M4, Juno R and
Juno SR0 (M5 and SR2 coming next month)
Date: Wed, 23 Jan 2013 14:01:27 -0500
From: Nick Boldt <nboldt(a)redhat.com>
Due to the GAV refactoring you may run into a problem using the new TPs
in their current form w/o patching [1] & rebuilding the parent pom.
"Failed to resolve target definition
/home/nboldt/.m2/repository/org/jboss/tools/target-platforms/jbdevstudio/unified/4.30.0.Alpha1-SNAPSHOT/unified-4.30.0.Alpha1-SNAPSHOT-unified.target"
"Failed to load metadata repository from location
http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbdevstudiotarget/4...
[1]
https://issues.jboss.org/secure/attachment/12360088/12360088_JBIDE13232.p...
---
HOWEVER, you can use @mistria's version of the bits (older GAV & URLs,
same content) w/o hacking the parent pom like this:
mvn clean install ... -DTARGET_PLATFORM_VERSION=4.2.0.c-SNAPSHOT -U
mvn clean install ... -DTARGET_PLATFORM_VERSION=4.2.1.a-SNAPSHOT -U
mvn clean install ... -DTARGET_PLATFORM_VERSION=4.3.0.M4-SNAPSHOT -U
Soon, I'll be switching the parent pom in 40x and master branches to use
the new GAV path /org/jboss/tools/targetplatforms/jbdevstudio-unified/
instead of /org/jboss/tools/target-platforms/jbdevstudio/unified/, which
will make the old TPs unusable.
Stay tuned!
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
6:27 a.m.
New subject: Feedback on new TP naming ?
Nicks email from earlier talked alot about how things are built - and I think it might
have been missed so i'm outlining it here:
Would be great to hear if anyone spot any issue with applying this naming to our target
platforms in general, i.e. for layered builds like integration-stack.
> These have as yet NOT been coupled up into the parent poms for
the
> 40x/60x and 41x/70x streams so that you can have some time to try them
> out. How do you use them? Via a standard maven build, but passing in
> this additional flag:
>
>> mvn clean install ... -DTARGET_PLATFORM_VERSION=4.20.5.Final-SNAPSHOT
>
> Changes to the previous target platforms (other than refactoring [5] and
> migration to a new github repo [6]) include the removal of source and
> sdk features [7], so these are slimmer and trimmer than their
> predecessors, previously referred to as JunoSR0c and JunoSR1a.
>
> The new TPs, rather than being named for an Eclipse release train, will
> now be named for the version of Eclipse included therein.
>
> Thus:
>
> * JunoSR0c (the 4th iteration) would be called 4.20.4.Final-SNAPSHOT
> * JunoSR1a (the 2nd iteration) would be called 4.21.2.Final-SNAPSHOT
>
> Therefore the new target platforms are:
>
> * 4.20.5.Final-SNAPSHOT
> * 4.21.3.Final-SNAPSHOT
> * 4.30.0.Alpha1-SNAPSHOT
More precisely its:
jbosstoolstarget-4.20.5.Final (the -SNAPSHOT is just temporary for now)
Which in general consist of:
<"thing being
targeted">target-<eclipsemajor>-<eclipsemajor+minor>.<revision>.<quality>
So for jbdevstudio targeting Kepler its jbdevstudiotarget-4.30.0.Alpha1.
If integration-stack made one and had 3 changes/release it would be something like this
when it goes final:
jbosstools-integration-stacktarget-4.30.3.Final
We could also just version them completely independent of eclipse version number but it
seems useful to be able to actually see what release its core dependencies are based on.
Input/thoughts ?
I would like to avoid renaming these things constantly so please speak up now if you see a
problem :)
/max
8:57 a.m.
New subject: Feedback on new TP naming ?
Hey Max,
I commented on the JIRA. For the integration stack, we'll be versioning our TP along
with the stack version. At this time, we're not planning on having multiple versions
based on Eclipse, but will be more closely aligned with JBT versions. For example:
org.jboss.tools.integration-stack:target-platform-4.0.0-base.target
org.jboss.tools.integration-stack:target-platform-4.0.0-test.target
(Currently, we only provide a base which includes test dependencies.)
Similarly for core:
org.jboss.tools:target-platform-4.1.0-junosr1.target
org.jboss.tools:target-platform-4.1.0-kepler.target
etc.
That was gist of my proposal, but you can look at the JIRA for the complete history. I
don't think that fit very well with the way you release.
Rob
----- Original Message -----
Nicks email from earlier talked alot about how things are built -
and
I think it might have been missed so i'm outlining it here:
Would be great to hear if anyone spot any issue with applying this
naming to our target platforms in general, i.e. for layered builds
like integration-stack.
>> These have as yet NOT been coupled up into the parent poms for the
>> 40x/60x and 41x/70x streams so that you can have some time to try
>> them
>> out. How do you use them? Via a standard maven build, but passing
>> in
>> this additional flag:
>>
>>> mvn clean install ...
>>> -DTARGET_PLATFORM_VERSION=4.20.5.Final-SNAPSHOT
>>
>> Changes to the previous target platforms (other than refactoring
>> [5] and
>> migration to a new github repo [6]) include the removal of source
>> and
>> sdk features [7], so these are slimmer and trimmer than their
>> predecessors, previously referred to as JunoSR0c and JunoSR1a.
>>
>> The new TPs, rather than being named for an Eclipse release train,
>> will
>> now be named for the version of Eclipse included therein.
>>
>> Thus:
>>
>> * JunoSR0c (the 4th iteration) would be called
>> 4.20.4.Final-SNAPSHOT
>> * JunoSR1a (the 2nd iteration) would be called
>> 4.21.2.Final-SNAPSHOT
>>
>> Therefore the new target platforms are:
>>
>> * 4.20.5.Final-SNAPSHOT
>> * 4.21.3.Final-SNAPSHOT
>> * 4.30.0.Alpha1-SNAPSHOT
More precisely its:
jbosstoolstarget-4.20.5.Final (the -SNAPSHOT is just temporary for
now)
Which in general consist of:
<"thing being
targeted">target-<eclipsemajor>-<eclipsemajor+minor>.<revision>.<quality>
So for jbdevstudio targeting Kepler its
jbdevstudiotarget-4.30.0.Alpha1.
If integration-stack made one and had 3 changes/release it would be
something like this when it goes final:
jbosstools-integration-stacktarget-4.30.3.Final
We could also just version them completely independent of eclipse
version number but it seems useful to be able to actually see what
release its core dependencies are based on.
Input/thoughts ?
I would like to avoid renaming these things constantly so please
speak up now if you see a problem :)
/max
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
4123
days inactive
4125
days old
jbosstools-dev@lists.jboss.org
2 comments
3 participants
participants (3)
-
Max Rydahl Andersen -
Nick Boldt -
Rob Cernich