[JBoss JIRA] (JBIDE-12761) Target-platfom should contain depdencies in the "minimal compatible" version
8:35 a.m.
Mickael Istria created JBIDE-12761:
--------------------------------------
Summary: Target-platfom should contain depdencies in the "minimal
compatible" version
Key: JBIDE-12761
URL: https://issues.jboss.org/browse/JBIDE-12761
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 4.0.0.Beta1
Currently, TP contains the latest version of all dependencies. However, JBT can run on
lower versions of Eclipse. It happens that developer introduce a depdendency on a very
recent version when it's not necessary because they rely on our target-platform.
Instead, TP should contain the minimal versions of all dependencies that are compatible
with JBoss Tools. Then developers can rely on very old version, and when necessary,
request usage of new one and break dependencies.
Installation tests are already there to verify installation on latest versions of
Eclipse.
--
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:42 a.m.
[
https://issues.jboss.org/browse/JBIDE-12761?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-12761:
------------------------------------
If you want to use the older TP site, they're here:
http://download.jboss.org/jbosstools/updates/target-platform_4.0.juno.SR0/
http://download.jboss.org/jbosstools/updates/target-platform_4.0.juno.SR0a/
and now the newest one:
http://download.jboss.org/jbosstools/updates/target-platform_4.0.juno.SR1/
How do you propose we build/verify that everything works against the latest (SR1, SR2)
while still ALSO verifying that it builds/works against the minimum (SR0) ?
Target-platfom should contain depdencies in the "minimal
compatible" version
----------------------------------------------------------------------------
Key: JBIDE-12761
URL: https://issues.jboss.org/browse/JBIDE-12761
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 4.0.0.Beta1
Currently, TP contains the latest version of all dependencies. However, JBT can run on
lower versions of Eclipse. It happens that developer introduce a depdendency on a very
recent version when it's not necessary because they rely on our target-platform.
Instead, TP should contain the minimal versions of all dependencies that are compatible
with JBoss Tools. Then developers can rely on very old version, and when necessary,
request usage of new one and break dependencies.
Installation tests are already there to verify installation on latest versions of
Eclipse.
--
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:48 a.m.
[
https://issues.jboss.org/browse/JBIDE-12761?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-12761:
----------------------------------------
{quote}
How do you propose we build/verify that everything works against the latest (SR1, SR2)
while still ALSO verifying that it builds/works against the minimum (SR0) ?
{quote}
Currently we have:
* build and automated tests again "latest"
* installation test against "minimal" (SR0)
* manual tests against <?>
So if I understand correctly, what you suggest is what we currently have.
Having devs using the latest TP in their IDE leads to compatiblity issue (depending on
latest whereas an older version would be fine). In JBT, we don't need latest, we
should avoid using it as much as possible. That's why I think having JBT Targets
containing "minimal dependencies" would work too and prevent from such issues
where people tend to rely on too recent stuff.
Target-platfom should contain depdencies in the "minimal
compatible" version
----------------------------------------------------------------------------
Key: JBIDE-12761
URL: https://issues.jboss.org/browse/JBIDE-12761
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 4.0.0.Beta1
Currently, TP contains the latest version of all dependencies. However, JBT can run on
lower versions of Eclipse. It happens that developer introduce a depdendency on a very
recent version when it's not necessary because they rely on our target-platform.
Instead, TP should contain the minimal versions of all dependencies that are compatible
with JBoss Tools. Then developers can rely on very old version, and when necessary,
request usage of new one and break dependencies.
Installation tests are already there to verify installation on latest versions of
Eclipse.
--
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:55 a.m.
[
https://issues.jboss.org/browse/JBIDE-12761?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-12761 at 10/1/12 1:55 AM:
-------------------------------------------------------------
So I'm hearing that you want to have:
a) multiple_minimum.target (*SR0*) and multiple_latest.target (*SR1*) plus
jbds_minimum.target (*SR0*) and jbds_latest.target (*SR1*)
... AND ...
b) we tell devs to use _minimum.target and matching update sites (with *SR0 bits*), NOT
the SR1 stuff
... BUT ...
c) build JBT components / aggregates based on *SR1 bits*
d) build JBDS update sites / installers based on and including *SR1 bits*
Does that sound right?
was (Author: nickboldt):
So I'm hearing that you want to have:
a) multiple_minimum.target and multiple_latest.target (along with jbds_minimum.target and
jbds_latest.target)
... AND ...
b) we tell devs to use _minimum.target and matching update sites (with *SR0 bits*), NOT
the SR1 stuff
... BUT ...
c) build JBT components / aggregates based on *SR1 bits*
d) build JBDS update sites / installers based on and including *SR1 bits*
Does that sound right?
Target-platfom should contain depdencies in the "minimal
compatible" version
----------------------------------------------------------------------------
Key: JBIDE-12761
URL: https://issues.jboss.org/browse/JBIDE-12761
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 4.0.0.Beta1
Currently, TP contains the latest version of all dependencies. However, JBT can run on
lower versions of Eclipse. It happens that developer introduce a depdendency on a very
recent version when it's not necessary because they rely on our target-platform.
Instead, TP should contain the minimal versions of all dependencies that are compatible
with JBoss Tools. Then developers can rely on very old version, and when necessary,
request usage of new one and break dependencies.
Installation tests are already there to verify installation on latest versions of
Eclipse.
--
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:55 a.m.
[
https://issues.jboss.org/browse/JBIDE-12761?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-12761:
------------------------------------
So I'm hearing that you want to have:
a) multiple_minimum.target and multiple_latest.target (along with jbds_minimum.target and
jbds_latest.target)
... AND ...
b) we tell devs to use *_minimum.target and matching update sites (with *SR0 bits*), *NOT
the SR1 stuff*
... BUT ...
c) build JBT components / aggregates based on *SR1 bits*
d) build JBDS update sites / installers based on and including *SR1 bits*
Does that sound right?
Target-platfom should contain depdencies in the "minimal
compatible" version
----------------------------------------------------------------------------
Key: JBIDE-12761
URL: https://issues.jboss.org/browse/JBIDE-12761
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 4.0.0.Beta1
Currently, TP contains the latest version of all dependencies. However, JBT can run on
lower versions of Eclipse. It happens that developer introduce a depdendency on a very
recent version when it's not necessary because they rely on our target-platform.
Instead, TP should contain the minimal versions of all dependencies that are compatible
with JBoss Tools. Then developers can rely on very old version, and when necessary,
request usage of new one and break dependencies.
Installation tests are already there to verify installation on latest versions of
Eclipse.
--
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:55 a.m.
[
https://issues.jboss.org/browse/JBIDE-12761?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-12761 at 10/1/12 1:54 AM:
-------------------------------------------------------------
So I'm hearing that you want to have:
a) multiple_minimum.target and multiple_latest.target (along with jbds_minimum.target and
jbds_latest.target)
... AND ...
b) we tell devs to use _minimum.target and matching update sites (with *SR0 bits*), NOT
the SR1 stuff
... BUT ...
c) build JBT components / aggregates based on *SR1 bits*
d) build JBDS update sites / installers based on and including *SR1 bits*
Does that sound right?
was (Author: nickboldt):
So I'm hearing that you want to have:
a) multiple_minimum.target and multiple_latest.target (along with jbds_minimum.target and
jbds_latest.target)
... AND ...
b) we tell devs to use *_minimum.target and matching update sites (with *SR0 bits*), *NOT
the SR1 stuff*
... BUT ...
c) build JBT components / aggregates based on *SR1 bits*
d) build JBDS update sites / installers based on and including *SR1 bits*
Does that sound right?
Target-platfom should contain depdencies in the "minimal
compatible" version
----------------------------------------------------------------------------
Key: JBIDE-12761
URL: https://issues.jboss.org/browse/JBIDE-12761
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 4.0.0.Beta1
Currently, TP contains the latest version of all dependencies. However, JBT can run on
lower versions of Eclipse. It happens that developer introduce a depdendency on a very
recent version when it's not necessary because they rely on our target-platform.
Instead, TP should contain the minimal versions of all dependencies that are compatible
with JBoss Tools. Then developers can rely on very old version, and when necessary,
request usage of new one and break dependencies.
Installation tests are already there to verify installation on latest versions of
Eclipse.
--
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 a.m.
[
https://issues.jboss.org/browse/JBIDE-12761?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-12761:
----------------------------------------
Not exactly. I thought:
* Having multiple.target containing minimal deps (SR0, m2e-wtp 0.16...)
* Dev use multiple.target
* We build JBT components using multiple.target and minimal deps
* We run JBT unit tests using minimal deps
But
* We run manual tests against most common dependencies (currently I think it's still
SR0)
And
* We build and bundle JBDS using latest/preferred dependencies (SR1)
Target-platfom should contain depdencies in the "minimal
compatible" version
----------------------------------------------------------------------------
Key: JBIDE-12761
URL: https://issues.jboss.org/browse/JBIDE-12761
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 4.0.0.Beta1
Currently, TP contains the latest version of all dependencies. However, JBT can run on
lower versions of Eclipse. It happens that developer introduce a depdendency on a very
recent version when it's not necessary because they rely on our target-platform.
Instead, TP should contain the minimal versions of all dependencies that are compatible
with JBoss Tools. Then developers can rely on very old version, and when necessary,
request usage of new one and break dependencies.
Installation tests are already there to verify installation on latest versions of
Eclipse.
--
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
4:29 p.m.
[
https://issues.jboss.org/browse/JBIDE-12761?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-12761:
------------------------------------
If you do that you'll only catch dep problems in the JBDS build. I'd rather see
breakages upstream within the components themselves, than to push the "problem"
down on your the heads of you/me/Denis/Max.
Target-platfom should contain depdencies in the "minimal
compatible" version
----------------------------------------------------------------------------
Key: JBIDE-12761
URL: https://issues.jboss.org/browse/JBIDE-12761
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 4.0.0.Beta1
Currently, TP contains the latest version of all dependencies. However, JBT can run on
lower versions of Eclipse. It happens that developer introduce a depdendency on a very
recent version when it's not necessary because they rely on our target-platform.
Instead, TP should contain the minimal versions of all dependencies that are compatible
with JBoss Tools. Then developers can rely on very old version, and when necessary,
request usage of new one and break dependencies.
Installation tests are already there to verify installation on latest versions of
Eclipse.
--
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:11 p.m.
[
https://issues.jboss.org/browse/JBIDE-12761?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-12761:
---------------------------------------------
Nick - why would we only catch dep problems in JBDS build ?
from what I would see JBT would catch them earlier if devs used something wrong ?
by building JBT with lowest common denominator we are sure it should work when the
aggregator of JBDS runs and collect (not re-build) the right bits or am I missing
something ?
Mickael - you are missing that the manual/unit tests should be run against JBDS with
latest/preferred deps too.....otherwise we dont spot the bugs.
Target-platfom should contain depdencies in the "minimal
compatible" version
----------------------------------------------------------------------------
Key: JBIDE-12761
URL: https://issues.jboss.org/browse/JBIDE-12761
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 4.0.0.Beta1
Currently, TP contains the latest version of all dependencies. However, JBT can run on
lower versions of Eclipse. It happens that developer introduce a depdendency on a very
recent version when it's not necessary because they rely on our target-platform.
Instead, TP should contain the minimal versions of all dependencies that are compatible
with JBoss Tools. Then developers can rely on very old version, and when necessary,
request usage of new one and break dependencies.
Installation tests are already there to verify installation on latest versions of
Eclipse.
--
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:58 p.m.
[
https://issues.jboss.org/browse/JBIDE-12761?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-12761:
------------------------------------
I'm thinking that if we only build JBDS w/ the latest 4.2.x, we won't find these
problems [1] as readily as when EVERYONE is testing their stuff against BOTH the minimum
and the latest.
[1] https://www.jboss.org/tools/download/installation/update_3_3#installon370371
Target-platfom should contain depdencies in the "minimal
compatible" version
----------------------------------------------------------------------------
Key: JBIDE-12761
URL: https://issues.jboss.org/browse/JBIDE-12761
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 4.0.0.Beta1
Currently, TP contains the latest version of all dependencies. However, JBT can run on
lower versions of Eclipse. It happens that developer introduce a depdendency on a very
recent version when it's not necessary because they rely on our target-platform.
Instead, TP should contain the minimal versions of all dependencies that are compatible
with JBoss Tools. Then developers can rely on very old version, and when necessary,
request usage of new one and break dependencies.
Installation tests are already there to verify installation on latest versions of
Eclipse.
--
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
11:14 p.m.
[
https://issues.jboss.org/browse/JBIDE-12761?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-12761 at 10/2/12 12:13 AM:
--------------------------------------------------------------
So where today (and in the past) we've linked all the build process to the latest
version (starting with parent pom and associate.properties files to link to the latest
target platform or composite requirements mirror), in future you would rather see all
those references STAY on SR0 instead of moving up to newer versions as they're
released?
... while at the same time, jbds.target WOULD move up to the latest versions (SR0a, SR1,
etc.)?
was (Author: nickboldt):
So where today (and in the past) we've linked all the build process to the latest
version (starting with parent pom and associate.properties files to link to the latest
target platform or composite requirements mirror), in future you would rather see all
those references STAY on SR0 instead of moving up to newer versions as they're
released?
... while at the same time, jbds.target WOULD move up to the latest versions?
Target-platfom should contain depdencies in the "minimal
compatible" version
----------------------------------------------------------------------------
Key: JBIDE-12761
URL: https://issues.jboss.org/browse/JBIDE-12761
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 4.0.0.Beta1
Currently, TP contains the latest version of all dependencies. However, JBT can run on
lower versions of Eclipse. It happens that developer introduce a depdendency on a very
recent version when it's not necessary because they rely on our target-platform.
Instead, TP should contain the minimal versions of all dependencies that are compatible
with JBoss Tools. Then developers can rely on very old version, and when necessary,
request usage of new one and break dependencies.
Installation tests are already there to verify installation on latest versions of
Eclipse.
--
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
11:14 p.m.
[
https://issues.jboss.org/browse/JBIDE-12761?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-12761:
------------------------------------
So where today (and in the past) we've linked all the build process to the latest
version (starting with parent pom and associate.properties files to link to the latest
target platform or composite requirements mirror), in future you would rather see all
those references STAY on SR0 instead of moving up to newer versions as they're
released?
... while at the same time, jbds.target WOULD move up to the latest versions?
Target-platfom should contain depdencies in the "minimal
compatible" version
----------------------------------------------------------------------------
Key: JBIDE-12761
URL: https://issues.jboss.org/browse/JBIDE-12761
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 4.0.0.Beta1
Currently, TP contains the latest version of all dependencies. However, JBT can run on
lower versions of Eclipse. It happens that developer introduce a depdendency on a very
recent version when it's not necessary because they rely on our target-platform.
Instead, TP should contain the minimal versions of all dependencies that are compatible
with JBoss Tools. Then developers can rely on very old version, and when necessary,
request usage of new one and break dependencies.
Installation tests are already there to verify installation on latest versions of
Eclipse.
--
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:20 a.m.
[
https://issues.jboss.org/browse/JBIDE-12761?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-12761:
----------------------------------------
This ticket is just in order to track brainstorming.
I think as long as we keep the "installation tests" working on the oldest
platform we want to support, and keep most-recent stuff in TP, dev may sometimes introduce
too restrictive deps, but they are easy to spot with this installation tests.
That's a few-hours feedback loop, which is probably good enough for our needs (Which
also are to run unit test against latest version deps as they will be in JBDS).
Target-platfom should contain depdencies in the "minimal
compatible" version
----------------------------------------------------------------------------
Key: JBIDE-12761
URL: https://issues.jboss.org/browse/JBIDE-12761
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 4.0.0.Beta1
Currently, TP contains the latest version of all dependencies. However, JBT can run on
lower versions of Eclipse. It happens that developer introduce a depdendency on a very
recent version when it's not necessary because they rely on our target-platform.
Instead, TP should contain the minimal versions of all dependencies that are compatible
with JBoss Tools. Then developers can rely on very old version, and when necessary,
request usage of new one and break dependencies.
Installation tests are already there to verify installation on latest versions of
Eclipse.
--
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:25 p.m.
New subject: [JBoss JIRA] (JBIDE-12761) Target-platfom should contain "minimal compatible" version of dependencies
[
https://issues.jboss.org/browse/JBIDE-12761?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-12761:
-------------------------------
Summary: Target-platfom should contain "minimal compatible" version of
dependencies (was: Target-platfom should contain depdencies in the "minimal
compatible" version)
Target-platfom should contain "minimal compatible" version
of dependencies
--------------------------------------------------------------------------
Key: JBIDE-12761
URL: https://issues.jboss.org/browse/JBIDE-12761
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 4.0.0.Beta1
Currently, TP contains the latest version of all dependencies. However, JBT can run on
lower versions of Eclipse. It happens that developer introduce a depdendency on a very
recent version when it's not necessary because they rely on our target-platform.
Instead, TP should contain the minimal versions of all dependencies that are compatible
with JBoss Tools. Then developers can rely on very old version, and when necessary,
request usage of new one and break dependencies.
Installation tests are already there to verify installation on latest versions of
Eclipse.
--
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:50 p.m.
New subject: [JBoss JIRA] (JBIDE-12761) Target-platfom should contain "minimal compatible" version of dependencies
[
https://issues.jboss.org/browse/JBIDE-12761?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-12761:
------------------------------------
Per decisions made in http://ether-man.rhcloud.com/p/build.next on Oct 10, the target
platform used for building all of JBT should now be the latest minimum one (currently
SR0b) rather than the latest maximum (currently SR1):
{quote}
JBT - set up component jobs to do this:
[Mistria] create profiles for "minimum" and "maximum" targets
[Mistria] update jobs to do this:
mvn clean install -DskipTests -Pminimum.target (or equivalent) # build
publish.sh # publish
mvn verify -f tests/pom.xml -Platest.target (or equivalent) # test
{quote}
Target-platfom should contain "minimal compatible" version
of dependencies
--------------------------------------------------------------------------
Key: JBIDE-12761
URL: https://issues.jboss.org/browse/JBIDE-12761
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 4.0.0.Beta1
Currently, TP contains the latest version of all dependencies. However, JBT can run on
lower versions of Eclipse. It happens that developer introduce a depdendency on a very
recent version when it's not necessary because they rely on our target-platform.
Instead, TP should contain the minimal versions of all dependencies that are compatible
with JBoss Tools. Then developers can rely on very old version, and when necessary,
request usage of new one and break dependencies.
Installation tests are already there to verify installation on latest versions of
Eclipse.
--
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 p.m.
New subject: [JBoss JIRA] (JBIDE-12761) Target-platfom should contain "minimal compatible" version of dependencies
[
https://issues.jboss.org/browse/JBIDE-12761?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-12761 at 10/11/12 2:59 PM:
--------------------------------------------------------------
Per decisions made in http://ether-man.rhcloud.com/p/build.next on Oct 10, the target
platform used for building all of JBT should now be the latest minimum one (currently
SR0b) rather than the latest maximum (currently SR1):
{quote}
JBT - set up component jobs to do this:
* [Mistria] create profiles for "minimum" and "maximum" targets
* [Mistria] update jobs to do this:
* mvn clean install -DskipTests -Pminimum.target (or equivalent) # build
* publish.sh # publish
* mvn verify -f tests/pom.xml -Platest.target (or equivalent) # test
JBT aggregate build with latest TP mirror -
http://download.jboss.org/jbosstools/updates/juno/SR1/
* point at latest TP mirror via
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/site/asso...
* this means the installation and the backing TP site contain the same bits -- latest
Juno reqs
* [Nick] to verify this is correct in both trunk/branch & release_guide docs
Installation tests (fired downstream from JBT build)
* 0. fetch Eclipse
* 1. install JBT from update site into 4.2, 4.2.latest
* 2. install JBT Central features into 4.2, 4.2.latest
JBDS - single job for sites + installer (as we do today)
* build Product and Extras update sites w/ latest TP [trunk AND branch]
* build installers w/ latest TP [trunk AND branch]
* build composite sites using latest TP --
https://devstudio.jboss.com/updates/6.0-staging/compositeContent.xml - point to Core site
(built with latest TP) and latest TP mirror on devstudio.jboss.com
* this means the installer and the backing update site contain the same bits -- latest
Juno reqs
* [Nick] verify the above is true/working
{quote}
was (Author: nickboldt):
Per decisions made in http://ether-man.rhcloud.com/p/build.next on Oct 10, the target
platform used for building all of JBT should now be the latest minimum one (currently
SR0b) rather than the latest maximum (currently SR1):
{quote}
JBT - set up component jobs to do this:
[Mistria] create profiles for "minimum" and "maximum" targets
[Mistria] update jobs to do this:
mvn clean install -DskipTests -Pminimum.target (or equivalent) # build
publish.sh # publish
mvn verify -f tests/pom.xml -Platest.target (or equivalent) # test
{quote}
Target-platfom should contain "minimal compatible" version
of dependencies
--------------------------------------------------------------------------
Key: JBIDE-12761
URL: https://issues.jboss.org/browse/JBIDE-12761
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 4.0.0.Beta1
Currently, TP contains the latest version of all dependencies. However, JBT can run on
lower versions of Eclipse. It happens that developer introduce a depdendency on a very
recent version when it's not necessary because they rely on our target-platform.
Instead, TP should contain the minimal versions of all dependencies that are compatible
with JBoss Tools. Then developers can rely on very old version, and when necessary,
request usage of new one and break dependencies.
Installation tests are already there to verify installation on latest versions of
Eclipse.
--
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
4:33 p.m.
New subject: [JBoss JIRA] (JBIDE-12761) Target-platfom should contain "minimal compatible" version of dependencies
[
https://issues.jboss.org/browse/JBIDE-12761?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-12761 at 10/11/12 5:32 PM:
--------------------------------------------------------------
Per decisions made in http://ether-man.rhcloud.com/p/build.next on Oct 10, the target
platform used for building all of JBT should now be the latest minimum one (currently
SR0b) rather than the latest maximum (currently SR1):
{quote}
JBT - set up component jobs to do this:
* [Nick] create profiles for "minimum" (enabled by default, unified.target)
and new "maximum" target :: *DONE*
* [Nick] update jobs to do this:
* mvn clean install -DskipTests -Pminimum.target (or equivalent) # build :: *DONE*
* publish.sh # publish :: *DONE*
* mvn verify -f tests/pom.xml -P*maximum* (or equivalent) # test :: *DONE*
JBT aggregate build with latest TP mirror -
http://download.jboss.org/jbosstools/updates/juno/SR1/
* point at latest TP mirror via
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/site/asso...
* this means the installation and the backing TP site contain the same bits -- latest
Juno reqs
* [Nick] to verify this is correct in both trunk/branch & release_guide docs
Installation tests (fired downstream from JBT build)
* 0. fetch Eclipse
* 1. install JBT from update site into 4.2, 4.2.latest
* 2. install JBT Central features into 4.2, 4.2.latest
JBDS - single job for sites + installer (as we do today)
* build Product and Extras update sites w/ latest TP [trunk AND branch]
* build installers w/ latest TP [trunk AND branch]
* build composite sites using latest TP --
https://devstudio.jboss.com/updates/6.0-staging/compositeContent.xml - point to Core site
(built with latest TP) and latest TP mirror on devstudio.jboss.com
* this means the installer and the backing update site contain the same bits -- latest
Juno reqs
* [Nick] verify the above is true/working
{quote}
was (Author: nickboldt):
Per decisions made in http://ether-man.rhcloud.com/p/build.next on Oct 10, the target
platform used for building all of JBT should now be the latest minimum one (currently
SR0b) rather than the latest maximum (currently SR1):
{quote}
JBT - set up component jobs to do this:
* [Mistria] create profiles for "minimum" and "maximum" targets
* [Mistria] update jobs to do this:
* mvn clean install -DskipTests -Pminimum.target (or equivalent) # build
* publish.sh # publish
* mvn verify -f tests/pom.xml -Platest.target (or equivalent) # test
JBT aggregate build with latest TP mirror -
http://download.jboss.org/jbosstools/updates/juno/SR1/
* point at latest TP mirror via
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/site/asso...
* this means the installation and the backing TP site contain the same bits -- latest
Juno reqs
* [Nick] to verify this is correct in both trunk/branch & release_guide docs
Installation tests (fired downstream from JBT build)
* 0. fetch Eclipse
* 1. install JBT from update site into 4.2, 4.2.latest
* 2. install JBT Central features into 4.2, 4.2.latest
JBDS - single job for sites + installer (as we do today)
* build Product and Extras update sites w/ latest TP [trunk AND branch]
* build installers w/ latest TP [trunk AND branch]
* build composite sites using latest TP --
https://devstudio.jboss.com/updates/6.0-staging/compositeContent.xml - point to Core site
(built with latest TP) and latest TP mirror on devstudio.jboss.com
* this means the installer and the backing update site contain the same bits -- latest
Juno reqs
* [Nick] verify the above is true/working
{quote}
Target-platfom should contain "minimal compatible" version
of dependencies
--------------------------------------------------------------------------
Key: JBIDE-12761
URL: https://issues.jboss.org/browse/JBIDE-12761
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 4.0.0.Beta1
Currently, TP contains the latest version of all dependencies. However, JBT can run on
lower versions of Eclipse. It happens that developer introduce a depdendency on a very
recent version when it's not necessary because they rely on our target-platform.
Instead, TP should contain the minimal versions of all dependencies that are compatible
with JBoss Tools. Then developers can rely on very old version, and when necessary,
request usage of new one and break dependencies.
Installation tests are already there to verify installation on latest versions of
Eclipse.
--
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
4:35 p.m.
New subject: [JBoss JIRA] (JBIDE-12761) Target-platfom should contain "minimal compatible" version of dependencies
[
https://issues.jboss.org/browse/JBIDE-12761?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-12761 at 10/11/12 5:33 PM:
--------------------------------------------------------------
Per decisions made in http://ether-man.rhcloud.com/p/build.next on Oct 10, the target
platform used for building all of JBT should now be the latest minimum one (currently
SR0b) rather than the latest maximum (currently SR1):
{quote}
JBT - set up component jobs to do this:
* [Nick] create profiles for "minimum" (enabled by default, unified.target)
and new "maximum" target :: *DONE*
* [Nick] update jobs to do this:
** mvn clean install -DskipTests -Pminimum.target (or equivalent) # build :: *DONE*
** publish.sh # publish :: *DONE*
** mvn verify -f tests/pom.xml -P*maximum* (or equivalent) # test :: *DONE*
JBT aggregate build with latest TP mirror -
http://download.jboss.org/jbosstools/updates/juno/SR1/
* point at latest TP mirror via
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/site/asso...
* this means the installation and the backing TP site contain the same bits -- latest
Juno reqs
* [Nick] to verify this is correct in both trunk/branch & release_guide docs
Installation tests (fired downstream from JBT build)
* 0. fetch Eclipse
* 1. install JBT from update site into 4.2, 4.2.latest
* 2. install JBT Central features into 4.2, 4.2.latest
JBDS - single job for sites + installer (as we do today)
* build Product and Extras update sites w/ latest TP [trunk AND branch]
* build installers w/ latest TP [trunk AND branch]
* build composite sites using latest TP --
https://devstudio.jboss.com/updates/6.0-staging/compositeContent.xml - point to Core site
(built with latest TP) and latest TP mirror on devstudio.jboss.com
* this means the installer and the backing update site contain the same bits -- latest
Juno reqs
* [Nick] verify the above is true/working
{quote}
was (Author: nickboldt):
Per decisions made in http://ether-man.rhcloud.com/p/build.next on Oct 10, the target
platform used for building all of JBT should now be the latest minimum one (currently
SR0b) rather than the latest maximum (currently SR1):
{quote}
JBT - set up component jobs to do this:
* [Nick] create profiles for "minimum" (enabled by default, unified.target)
and new "maximum" target :: *DONE*
* [Nick] update jobs to do this:
* mvn clean install -DskipTests -Pminimum.target (or equivalent) # build :: *DONE*
* publish.sh # publish :: *DONE*
* mvn verify -f tests/pom.xml -P*maximum* (or equivalent) # test :: *DONE*
JBT aggregate build with latest TP mirror -
http://download.jboss.org/jbosstools/updates/juno/SR1/
* point at latest TP mirror via
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/site/asso...
* this means the installation and the backing TP site contain the same bits -- latest
Juno reqs
* [Nick] to verify this is correct in both trunk/branch & release_guide docs
Installation tests (fired downstream from JBT build)
* 0. fetch Eclipse
* 1. install JBT from update site into 4.2, 4.2.latest
* 2. install JBT Central features into 4.2, 4.2.latest
JBDS - single job for sites + installer (as we do today)
* build Product and Extras update sites w/ latest TP [trunk AND branch]
* build installers w/ latest TP [trunk AND branch]
* build composite sites using latest TP --
https://devstudio.jboss.com/updates/6.0-staging/compositeContent.xml - point to Core site
(built with latest TP) and latest TP mirror on devstudio.jboss.com
* this means the installer and the backing update site contain the same bits -- latest
Juno reqs
* [Nick] verify the above is true/working
{quote}
Target-platfom should contain "minimal compatible" version
of dependencies
--------------------------------------------------------------------------
Key: JBIDE-12761
URL: https://issues.jboss.org/browse/JBIDE-12761
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 4.0.0.Beta1
Currently, TP contains the latest version of all dependencies. However, JBT can run on
lower versions of Eclipse. It happens that developer introduce a depdendency on a very
recent version when it's not necessary because they rely on our target-platform.
Instead, TP should contain the minimal versions of all dependencies that are compatible
with JBoss Tools. Then developers can rely on very old version, and when necessary,
request usage of new one and break dependencies.
Installation tests are already there to verify installation on latest versions of
Eclipse.
--
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
7:42 p.m.
New subject: [JBoss JIRA] (JBIDE-12761) Target-platfom should contain "minimal compatible" version of dependencies
[
https://issues.jboss.org/browse/JBIDE-12761?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-12761 at 10/11/12 8:40 PM:
--------------------------------------------------------------
Per decisions made in http://ether-man.rhcloud.com/p/build.next on Oct 10, the target
platform used for building all of JBT should now be the latest minimum one (currently
SR0b) rather than the latest maximum (currently SR1):
{quote}
JBT - set up component jobs to do this:
* [Nick] create profiles for "minimum" (enabled by default, unified.target)
and new "maximum" target :: *DONE, trunk + stable_branch*
* [Nick] update jobs to do this: *DONE, trunk + stable_branch*
** mvn clean install -DskipTests -Pminimum.target (or equivalent) # build
** publish.sh # publish
** mvn verify -f tests/pom.xml -Pmaximum # test
JBT aggregate build with latest TP mirror -
http://download.jboss.org/jbosstools/updates/juno/SR1/ :: *DONE, trunk + stable_branch*
* point at latest TP mirror via
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/site/asso...
:: *DONE, trunk + stable_branch*
* this means the installation and the backing TP site contain the same bits -- latest
Juno reqs
* [Nick] to verify this is correct in both trunk/branch & release_guide docs ::
*DONE*
[Mickael] Installation tests (fired downstream from JBT build)
* 0. fetch Eclipse
* 1. install JBT from update site into 4.2, 4.2.latest
* 2. install JBT Central features into 4.2, 4.2.latest
JBDS - single job for sites + installer (as we do today)
* build Product and Extras update sites w/ latest TP [trunk AND branch] :: *DONE, jobs
updated*
* build installers w/ latest TP [trunk AND branch] :: *DONE*
* build composite sites using latest TP --
https://devstudio.jboss.com/updates/6.0-staging/compositeContent.xml - point to Core site
(built with latest TP) and latest TP mirror on devstudio.jboss.com
* this means the installer and the backing update site contain the same bits -- latest
Juno reqs
* [Nick] verify the above is true/working
{quote}
was (Author: nickboldt):
Per decisions made in http://ether-man.rhcloud.com/p/build.next on Oct 10, the target
platform used for building all of JBT should now be the latest minimum one (currently
SR0b) rather than the latest maximum (currently SR1):
{quote}
JBT - set up component jobs to do this:
* [Nick] create profiles for "minimum" (enabled by default, unified.target)
and new "maximum" target :: *DONE*
* [Nick] update jobs to do this:
** mvn clean install -DskipTests -Pminimum.target (or equivalent) # build :: *DONE*
** publish.sh # publish :: *DONE*
** mvn verify -f tests/pom.xml -P*maximum* (or equivalent) # test :: *DONE*
JBT aggregate build with latest TP mirror -
http://download.jboss.org/jbosstools/updates/juno/SR1/
* point at latest TP mirror via
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/site/asso...
* this means the installation and the backing TP site contain the same bits -- latest
Juno reqs
* [Nick] to verify this is correct in both trunk/branch & release_guide docs
Installation tests (fired downstream from JBT build)
* 0. fetch Eclipse
* 1. install JBT from update site into 4.2, 4.2.latest
* 2. install JBT Central features into 4.2, 4.2.latest
JBDS - single job for sites + installer (as we do today)
* build Product and Extras update sites w/ latest TP [trunk AND branch]
* build installers w/ latest TP [trunk AND branch]
* build composite sites using latest TP --
https://devstudio.jboss.com/updates/6.0-staging/compositeContent.xml - point to Core site
(built with latest TP) and latest TP mirror on devstudio.jboss.com
* this means the installer and the backing update site contain the same bits -- latest
Juno reqs
* [Nick] verify the above is true/working
{quote}
Target-platfom should contain "minimal compatible" version
of dependencies
--------------------------------------------------------------------------
Key: JBIDE-12761
URL: https://issues.jboss.org/browse/JBIDE-12761
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 4.0.0.Beta1
Currently, TP contains the latest version of all dependencies. However, JBT can run on
lower versions of Eclipse. It happens that developer introduce a depdendency on a very
recent version when it's not necessary because they rely on our target-platform.
Instead, TP should contain the minimal versions of all dependencies that are compatible
with JBoss Tools. Then developers can rely on very old version, and when necessary,
request usage of new one and break dependencies.
Installation tests are already there to verify installation on latest versions of
Eclipse.
--
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:50 a.m.
New subject: [JBoss JIRA] (JBIDE-12761) Target-platfom should contain "minimal compatible" version of dependencies
[
https://issues.jboss.org/browse/JBIDE-12761?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-12761:
-------------------------------
Assignee: Mickael Istria (was: Nick Boldt)
Target-platfom should contain "minimal compatible" version
of dependencies
--------------------------------------------------------------------------
Key: JBIDE-12761
URL: https://issues.jboss.org/browse/JBIDE-12761
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 4.0.0.Beta1
Currently, TP contains the latest version of all dependencies. However, JBT can run on
lower versions of Eclipse. It happens that developer introduce a depdendency on a very
recent version when it's not necessary because they rely on our target-platform.
Instead, TP should contain the minimal versions of all dependencies that are compatible
with JBoss Tools. Then developers can rely on very old version, and when necessary,
request usage of new one and break dependencies.
Installation tests are already there to verify installation on latest versions of
Eclipse.
--
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:50 a.m.
New subject: [JBoss JIRA] (JBIDE-12761) Target-platfom should contain "minimal compatible" version of dependencies
[
https://issues.jboss.org/browse/JBIDE-12761?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-12761:
------------------------------------
[~mickael_istria]: Next steps are for you. Bounce back to me when done.
Target-platfom should contain "minimal compatible" version
of dependencies
--------------------------------------------------------------------------
Key: JBIDE-12761
URL: https://issues.jboss.org/browse/JBIDE-12761
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 4.0.0.Beta1
Currently, TP contains the latest version of all dependencies. However, JBT can run on
lower versions of Eclipse. It happens that developer introduce a depdendency on a very
recent version when it's not necessary because they rely on our target-platform.
Instead, TP should contain the minimal versions of all dependencies that are compatible
with JBoss Tools. Then developers can rely on very old version, and when necessary,
request usage of new one and break dependencies.
Installation tests are already there to verify installation on latest versions of
Eclipse.
--
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:18 a.m.
New subject: [JBoss JIRA] (JBIDE-12761) Target-platfom should contain "minimal compatible" version of dependencies
[
https://issues.jboss.org/browse/JBIDE-12761?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-12761:
----------------------------------------
{quote}
[Mickael] Installation tests (fired downstream from JBT build)
0. fetch Eclipse
1. install JBT from update site into 4.2, 4.2.latest
2. install JBT Central features into 4.2, 4.2.latest
{quote}
This is already done by those jobs:
*
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
*
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
Target-platfom should contain "minimal compatible" version
of dependencies
--------------------------------------------------------------------------
Key: JBIDE-12761
URL: https://issues.jboss.org/browse/JBIDE-12761
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 4.0.0.Beta1
Currently, TP contains the latest version of all dependencies. However, JBT can run on
lower versions of Eclipse. It happens that developer introduce a depdendency on a very
recent version when it's not necessary because they rely on our target-platform.
Instead, TP should contain the minimal versions of all dependencies that are compatible
with JBoss Tools. Then developers can rely on very old version, and when necessary,
request usage of new one and break dependencies.
Installation tests are already there to verify installation on latest versions of
Eclipse.
--
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
11:23 p.m.
New subject: [JBoss JIRA] (JBIDE-12761) Target-platfom should contain "minimal compatible" version of dependencies
[
https://issues.jboss.org/browse/JBIDE-12761?page=com.atlassian.jira.plugi...
]
Nick Boldt closed JBIDE-12761.
------------------------------
Resolution: Done
Closing. Opened subtask JBIDE-12848 to track remaining verification step.
Target-platfom should contain "minimal compatible" version
of dependencies
--------------------------------------------------------------------------
Key: JBIDE-12761
URL: https://issues.jboss.org/browse/JBIDE-12761
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 4.0.0.Beta1
Currently, TP contains the latest version of all dependencies. However, JBT can run on
lower versions of Eclipse. It happens that developer introduce a depdendency on a very
recent version when it's not necessary because they rely on our target-platform.
Instead, TP should contain the minimal versions of all dependencies that are compatible
with JBoss Tools. Then developers can rely on very old version, and when necessary,
request usage of new one and break dependencies.
Installation tests are already there to verify installation on latest versions of
Eclipse.
--
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
4371
days inactive
4385
days old
jbosstools-issues@lists.jboss.org
22 comments
3 participants
participants (3)
-
Max Rydahl Andersen (JIRA) -
Mickael Istria (JIRA)
-
Nick Boldt (JIRA)