[jbosstools-dev] Feedback on new TP naming ?

[Rob Cernich]

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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>