[
https://issues.jboss.org/browse/JBIDE-10312?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-10312:
------------------------------------
+1 to a *minimal* target, since that's sorta what the title of this JIRA is asking
for. :)
I've implemented it this way:
* minimal / stable *
http://svn.jboss.org/repos/jbosstools/trunk/build/target-platforms/jbosst...
http://svn.jboss.org/repos/jbosstools/trunk/build/target-platforms/jbdevs...
* latest / trunk *
http://svn.jboss.org/repos/jbosstools/trunk/build/target-platforms/jbosst...
http://svn.jboss.org/repos/jbosstools/trunk/build/target-platforms/jbdevs...
Thus we can build the stuff we release from Jenkins using the stable TP & devs can use
it locally.
And in trunk, we can build stuff we *don't* release (nightlies) using the latest TP
& devs can - when necessary - use it to verify issues.
I've also added profiles to the root pom:
http://svn.jboss.org/repos/jbosstools/trunk/build/target-platforms/pom.xml so it's
easier to run a build of both multiple and local in one operation.
Now all we need to do is clone the trunk jobs into stable_branch so that I can publish the
new SR0b target platform (it's SR0 + updated GWT) and then link to that from trunk
parent pom / associate.properties
Define a minimal target platform as opposed to the recommend one we
have now for builds
---------------------------------------------------------------------------------------
Key: JBIDE-10312
URL:
https://issues.jboss.org/browse/JBIDE-10312
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Build/Releng
Affects Versions: 4.0.0.Alpha2
Reporter: Max Rydahl Andersen
Assignee: Nick Boldt
Priority: Blocker
Fix For: 4.0.0.Beta1
Seeing JBIDE-10311 made me realize that we actually could catch these by having a
*minimal* target platform to either build or test against.
The problem here is that a plugin got a plugin dependency based on the target platform -
but the target platform have the latest 3.7.1 version meaning those users running 3.7.0
would have problems installing it.
If we had a minimal target platform (.target) we could actually install/verify these
issues against it.
Not necessarily every night - but like once a week run the build or install the
updatesite against the minimal target platform would
reveal these dependency issues.
WDYT?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira