[jbosstools-issues] [JBoss JIRA] (JBIDE-10312) Define a minimal target platform as opposed to the recommend one we have now for builds

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-10312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723721#comment-12723721 ] 

Nick Boldt commented on JBIDE-10312:
------------------------------------

Using [~mickael_istria]'s new https://svn.jboss.org/repos/jbosstools/trunk/build/target-platforms/ builder, we need to set up the following:

a) jenkins build used to produce the "latest" target platform, which will contain the best/newest deps available - SR0, SR0a, SR1
* assume some commandline flag like -f latest.pom.xml used to point to non-default operation

b) these bits will be published into a unique folder, eg., http://download.jboss.org/jbosstools/updates/juno/SR1/ - providing both zip and folder

c) local developer in /build/target-platforms/ folder should be able to run `mvn install` and build the "minimum" target platform, which contains the SR0 bits, *not* the latest (as in (a))

d) local developer in /build/target-platforms/ folder can OPTIONALLY repeat what Jenkins does using the same flag as the job

e) whatever is configured for JBT TP must also be done for JBDS TP

f) parent pom in trunk (and branch) must always point to SR0 bits, not "latest"

g) associate.properties in trunk (and branch) must always point to SR0 bits, not "latest"

h) automated install tests should run against ALL *final* target platforms (SR0, SR1, but not SR0a) to ensure we can install JBT on all flavours of Juno
 * install from Central
 * install from update site
 * install JBDS BYOE
 * ...?

i) JBDS installer should aggregate "latest" TP bits (SR0, SROa, SR1)
                
> 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
>            Reporter: Max Rydahl Andersen
>            Assignee: Nick Boldt
>            Priority: Minor
>             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