[JBoss JIRA] (JBIDE-10312) Define a minimal target platform as opposed to the recommend one we have now for builds
3:33 a.m.
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: Critical
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:10 a.m.
[
https://issues.jboss.org/browse/JBIDE-10312?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-10312:
------------------------------------
So when you say "minimal" you don't mean minimal size / fewest IUs, but
*oldest compatible version level*?
eg., we COULD be building against Indigo SR0 instead of SR1 or SR2, but we tend to build
against the latest/greatest available in order to stay current w/ the latest upstream
releases and be able to feedback to upstream / get fixes in upstream.
Would simply building against an older version of the TP be sufficient? For example...
http://download.jboss.org/jbosstools/updates/target-platform_3.3.indigo/e...
http://www.qa.jboss.com/binaries/RHDS/updates/jbds-target-platform_3.3.in...
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: Critical
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:44 p.m.
[
https://issues.jboss.org/browse/JBIDE-10312?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-10312:
---------------------------------------------
yes, oldest compatible version level - using older TP would not be sufficient since it
does not contain all dependencies.
note, building is not required, just installing + run tests.
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: Critical
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:12 a.m.
[
https://issues.jboss.org/browse/JBIDE-10312?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen updated JBIDE-10312:
----------------------------------------
Fix Version/s: 3.3.0.CR1
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: Critical
Fix For: 3.3.0.CR1
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:13 p.m.
[
https://issues.jboss.org/browse/JBIDE-10312?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-10312:
-------------------------------
Fix Version/s: 3.3.0.CR1
(was: 3.3.0.Beta3)
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: Critical
Fix For: 3.3.0.CR1
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:05 p.m.
[
https://issues.jboss.org/browse/JBIDE-10312?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-10312:
-------------------------------
Priority: Minor (was: Critical)
Moving severity down. This may slip into the Juno cycle.
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: 3.3.0.CR1
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:44 a.m.
[
https://issues.jboss.org/browse/JBIDE-10312?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-10312:
-------------------------------
Fix Version/s: 3.4.x
(was: 3.3.0.CR1)
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: 3.4.x
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:20 p.m.
[
https://issues.jboss.org/browse/JBIDE-10312?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-10312:
-------------------------------
Fix Version/s: 4.0.0.Alpha2
(was: 4.0.0.Alpha1)
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.Alpha2
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
12:44 a.m.
[
https://issues.jboss.org/browse/JBIDE-10312?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-10312:
-------------------------------
Fix Version/s: 4.0.0.Beta1
(was: 4.0.0.Alpha2)
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
10:40 a.m.
[
https://issues.jboss.org/browse/JBIDE-10312?page=com.atlassian.jira.plugi...
]
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
10:40 a.m.
[
https://issues.jboss.org/browse/JBIDE-10312?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-10312:
-------------------------------
Priority: Blocker (was: Minor)
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: 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
10:42 a.m.
[
https://issues.jboss.org/browse/JBIDE-10312?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-10312 at 10/3/12 11:41 AM:
--------------------------------------------------------------
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".
Goal: avoid problems like we had w/ 3.7.x:
https://www.jboss.org/tools/download/installation/update_3_3#installon370371
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)
was (Author: nickboldt):
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
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
10:42 a.m.
[
https://issues.jboss.org/browse/JBIDE-10312?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-10312:
-------------------------------
Affects Version/s: 4.0.0.Alpha2
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
10:44 a.m.
[
https://issues.jboss.org/browse/JBIDE-10312?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-10312 at 10/3/12 11:42 AM:
--------------------------------------------------------------
-Moving severity down. This may slip into the Juno cycle.- Slipped into Juno. Moving
severity back up.
was (Author: nickboldt):
Moving severity down. This may slip into the Juno cycle.
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
10:46 a.m.
[
https://issues.jboss.org/browse/JBIDE-10312?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-10312:
----------------------------------------
What about a multiple-minimal.target.
We keep using latest for all builds, CI and so on (to line-up with JBDS), and we use this
minimal.target just to check stuff builds/tests correctly with older version.
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
2:53 p.m.
[
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
3:53 p.m.
[
https://issues.jboss.org/browse/JBIDE-10312?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-10312:
------------------------------------
I've simplified the publish.sh script so it uses the target platform folder name as
the flag -- thus jbosstools-JunoSR1 or jbdevstudio-JunoSR0b.
Updated jobs now spinning:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_stabl...
>=1
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio-6.0_stable...
>=1
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_trunk...
>=33
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio-6.0_trunk....
>=15
Next... once the stable_branch TPs are built, we can link to them from trunk builds
(parent pom, associate.properties)
We could further simplify the jobs if we had a pom in each target-platforms/*/ folder
which ran a build of multiple, local, unified, and jenkins subfolders.
WDYT?
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
2:58 a.m.
[
https://issues.jboss.org/browse/JBIDE-10312?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-10312:
----------------------------------------
We need to update parent pom accordingly since artifactId for targets have changed.
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
5:08 a.m.
[
https://issues.jboss.org/browse/JBIDE-10312?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-10312:
----------------------------------------
Also, current target-platforms folder is not "standalone": some pom.xml still
reference old GAVs and then don't consume the expected file.
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
5:12 a.m.
[
https://issues.jboss.org/browse/JBIDE-10312?page=com.atlassian.jira.plugi...
]
Mickael Istria edited comment on JBIDE-10312 at 10/4/12 6:10 AM:
-----------------------------------------------------------------
Also, current target-platforms folder is not "standalone": some pom.xml still
reference old GAVs and then don't consume the expected file.
We should try to have fun by putting target-version in groupIds so we don't have to
keep this complex naming and can more easily set up links between platform types.
was (Author: mickael_istria):
Also, current target-platforms folder is not "standalone": some pom.xml
still reference old GAVs and then don't consume the expected file.
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
8:04 a.m.
[
https://issues.jboss.org/browse/JBIDE-10312?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-10312:
----------------------------------------
I updated target-platform pom to have GAV changing on groups only (groups contain for
instance jbosstools-JunoSR1), and artifactId always being on of
multiple/unified/jenkins/local. This make things much more homogeneous.
I also updated parent pom to use this new convention. I introduced a property to change
target-platform, currently it's set to jbosstools-JunoSR1.
I'm wondering whether we should not use 2 properties to select a TP (one for the
group, the other for the kind), and keep only a single target profile, activated by
default.
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
9:16 a.m.
[
https://issues.jboss.org/browse/JBIDE-10312?page=com.atlassian.jira.plugi...
]
Mickael Istria edited comment on JBIDE-10312 at 10/4/12 10:14 AM:
------------------------------------------------------------------
I updated target-platform pom to have GAV changing on groups only (groups contain for
instance jbosstools-JunoSR1), and artifactId always being on of
multiple/unified/jenkins/local. This make things much more homogeneous.
I also updated parent pom to use this new convention. I introduced a property to change
target-platform, currently it's set to jbosstools-JunoSR1.
I'm wondering whether we should not use 2 properties to select a TP (one for the
group, the other for the kind), and keep only a single target profile, activated by
default. Eg
{code:xml}
<properties>
....
<targetPlatformGroup>jbosstools-JunoSR1</targetPlatformGroup>
<targetPlatformKind>unified</targetPlatformKind>
</properties>
...
<build>
<plugins>
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>target-platform-configuration</artifactId>
<version>${tychoVersion}</version>
<configuration>
<target>
<artifact>
<groupId>org.jboss.tools.target-platforms.${targetPlatformGroup}</groupId>
<artifactId>${targetPlatformKind}</artifactId>
<version>${JBT_VERSION}.${BUILD_ALIAS}-SNAPSHOT</version>
<classifier>${targetPlatformKind}</classifier>
</artifact>
</target>
</configuration>
</plugin>
</plugins>
</build>
{code}
was (Author: mickael_istria):
I updated target-platform pom to have GAV changing on groups only (groups contain for
instance jbosstools-JunoSR1), and artifactId always being on of
multiple/unified/jenkins/local. This make things much more homogeneous.
I also updated parent pom to use this new convention. I introduced a property to change
target-platform, currently it's set to jbosstools-JunoSR1.
I'm wondering whether we should not use 2 properties to select a TP (one for the
group, the other for the kind), and keep only a single target profile, activated by
default.
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
1:46 p.m.
[
https://issues.jboss.org/browse/JBIDE-10312?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-10312:
------------------------------------
Sounds good, but we should set the default to be the latest minimum (SR0b, SR0c) rather
than the latest maximum (SR1, SR1a, ...).
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
1:46 p.m.
[
https://issues.jboss.org/browse/JBIDE-10312?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-10312:
-------------------------------
Assignee: Mickael Istria (was: Nick Boldt)
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: Mickael Istria
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
9:26 a.m.
[
https://issues.jboss.org/browse/JBIDE-10312?page=com.atlassian.jira.plugi...
]
Mickael Istria closed JBIDE-10312.
----------------------------------
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: Mickael Istria
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
9:26 a.m.
[
https://issues.jboss.org/browse/JBIDE-10312?page=com.atlassian.jira.plugi...
]
Mickael Istria resolved JBIDE-10312.
------------------------------------
Resolution: Done
This was implemented and has be used for almost a week without trouble.
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: Mickael Istria
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
4279
days inactive
4599
days old
jbosstools-issues@lists.jboss.org
25 comments
6 participants
participants (6)
-
Max Rydahl Andersen (Commented) (JIRA) -
Max Rydahl Andersen (Created) (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Mickael Istria (JIRA)
-
Nick Boldt (Commented) (JIRA)
-
Nick Boldt (JIRA)