[JBoss JIRA] (JBIDE-26180) TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26180?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-26180:
--------------------------------
Description:
In order to start Eclipse 4.9-based builds, we need an updated target platform.
For sprint 152 / AM1: simrel M1
For sprint 153 / AM2: simrel M2
For sprint 154 / AM3: simrel M3
For sprint 155 / GA: simrel RC2/GA
Coming in the next update, some orbit changes:
* batik, icu4j, platform, felix gogo, httpclient (due 27 Aug)
Also:
* reddeer 2.3
* m2e http://download.eclipse.org/technology/m2e/milestones/1.9/1.9.1.20180823-...
was:
In order to start Eclipse 4.9-based builds, we need an updated target platform.
For sprint 152 / AM1: simrel M1
For sprint 153 / AM2: simrel M2
For sprint 154 / AM3: simrel M3
For sprint 155 / GA: simrel RC2/GA
Coming in the next update, some orbit changes:
* batik, icu4j, platform, felix gogo, httpclient (due 27 Aug)
Also:
* reddeer 2.3
* m2e http://download.eclipse.org/technology/m2e/milestones/1.9/1.9.1.20180822-...
> TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)
> ----------------------------------------------------------------
>
> Key: JBIDE-26180
> URL: https://issues.jboss.org/browse/JBIDE-26180
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, upstream
> Affects Versions: 4.9.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.9.0.AM3, 4.9.0.Final, 4.9.x
>
> Attachments: am1-vs-am2.p2diff.txt
>
>
> In order to start Eclipse 4.9-based builds, we need an updated target platform.
> For sprint 152 / AM1: simrel M1
> For sprint 153 / AM2: simrel M2
> For sprint 154 / AM3: simrel M3
> For sprint 155 / GA: simrel RC2/GA
> Coming in the next update, some orbit changes:
> * batik, icu4j, platform, felix gogo, httpclient (due 27 Aug)
> Also:
> * reddeer 2.3
> * m2e http://download.eclipse.org/technology/m2e/milestones/1.9/1.9.1.20180823-...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 10 months
[JBoss JIRA] (ERT-657) Remove older bundle versions in Orbit when newer ones exist
by Roland Grunberg (JIRA)
[ https://issues.jboss.org/browse/ERT-657?page=com.atlassian.jira.plugin.sy... ]
Roland Grunberg closed ERT-657.
-------------------------------
Fix Version/s: 2018-09 RC1
Resolution: Done
Various felix, and icu4j bundles will be removed from the active build since they're no longer needed. This will be visible in RC1.
> Remove older bundle versions in Orbit when newer ones exist
> -----------------------------------------------------------
>
> Key: ERT-657
> URL: https://issues.jboss.org/browse/ERT-657
> Project: Eclipse Release Train
> Issue Type: Task
> Reporter: Roland Grunberg
> Assignee: Roland Grunberg
> Fix For: 2018-09 RC1
>
>
> In Orbit, we should push to remove older bundle versions where a newer one can be used. Things like ICU4J, and the Apache Felix stack should be fine, but by declaring our intent to remove others we can also encourage people to migrate for 2018-12 (deadlines for 2018-09 M3 are fast approaching and removals into RC1 shouldn't happen).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 10 months
[JBoss JIRA] (ERT-656) Cannot run JUnit test method having parameter
by Roland Grunberg (JIRA)
[ https://issues.jboss.org/browse/ERT-656?page=com.atlassian.jira.plugin.sy... ]
Roland Grunberg commented on ERT-656:
-------------------------------------
This issue has run into some complications around supporting some additional features.
> Cannot run JUnit test method having parameter
> ---------------------------------------------
>
> Key: ERT-656
> URL: https://issues.jboss.org/browse/ERT-656
> Project: Eclipse Release Train
> Issue Type: Task
> Affects Versions: Oxygen.1 (4.7), Photon (4.8), 2018-09 M2
> Reporter: Roland Grunberg
> Assignee: Roland Grunberg
>
> Since Oxygen.0, some changes introduced for JUnit 5 support, regressed the ability to run individual test methods that happen to take a parameter (eg. testFoo(TestContext) ). The filter matching against the method itself was broken.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 10 months