Re: [cross-project-issues-dev] massive amount of unresolved bundles in 2018-09 M3 (JEE package)

Hi, The simrel.runaggregator.pipeline job checks for SCM changes every 10 minutes. Regards, Fred On 10.09.2018 17:45, Nick Boldt wrote: > DTP and TM are rebuilt. Simrel rebuilding [0]. > > [0] https://ci.eclipse.org/simrel/job/simrel.runaggregator.pipeline/95/ > > What's the best way to trigg

Re: [cross-project-issues-dev] massive amount of unresolved bundles in 2018-09 M3 (JEE package)

Hi, On Mon, Sep 10, 2018 at 5:59 PM, Ed Willink wrote: > you have your problem, nobody can be sure what you contributed when and > some lucky SimRel users may get to see a contribution change mid-build. > Worse, if you mess up so that your aggregate repo is bad, the SimRel > aggregation is broke

Re: [cross-project-issues-dev] massive amount of unresolved bundles in 2018-09 M3 (JEE package)

Agree in principle, but in practice since DTP and TM move so slowly (and have so few changes), I feel it's safe enough to use a snapshot URL for the pre-Final build, then switch to a non-SNAPSHOT one for the Final build. Saves me having to rebuild/rename/copy snapshots just to make them more deter

Re: [cross-project-issues-dev] massive amount of unresolved bundles in 2018-09 M3 (JEE package)

Hi Nick If you contribute determinstically such as:   location="http://download.eclipse.org/modeling/mdt/ocl/updates/milestones/6.5.0/S201809100900"; description="OCL"> you have to do a real *.aggrcon edit for each updated contribution so no trigger problem. If you contribute generically s

Re: [cross-project-issues-dev] massive amount of unresolved bundles in 2018-09 M3 (JEE package)

DTP and TM are rebuilt. Simrel rebuilding [0]. [0] https://ci.eclipse.org/simrel/job/simrel.runaggregator.pipeline/95/ What's the best way to trigger a respin of the simrel staging site [1]? Push an empty commit to the repo? Could authorized/logged in users be given the job build permission? [1]

Re: [cross-project-issues-dev] massive amount of unresolved bundles in 2018-09 M3 (JEE package)

I've just triggered rebuilds of TM 4.5.0-SNAPSHOT, DTP 1.14.101-SNAPSHOT, and WTP 3.11. DTP and TM will be automatically contributed to the simrel staging site via its SNAPSHOT URLs when simrel staging site does its next rebuild. WTP has a more arcane (read: slow, manual) process for contributing

Re: [cross-project-issues-dev] massive amount of unresolved bundles in 2018-09 M3 (JEE package)

On Wed, 2018-09-05 at 14:20 +0200, Gunnar Wagenknecht wrote: > > On Sep 5, 2018, at 13:22, Martin Lippert wrote: > > > > org.apache.lucene.queryparser_7.1.0.v20180828-2118 This should be resolved in the upcoming Orbit RC2 contribution. Nick requested lucene-queryparser 7.1 not long ago (I believ

Re: [cross-project-issues-dev] massive amount of unresolved bundles in 2018-09 M3 (JEE package)

> On Sep 5, 2018, at 13:22, Martin Lippert wrote: > > org.apache.lucene.queryparser_7.1.0.v20180828-2118 This looks like https://bugs.eclipse.org/538546 What other bundles are not resolving? -Gunnar___ cross-projec

[cross-project-issues-dev] massive amount of unresolved bundles in 2018-09 M3 (JEE package)

Hey! When I download 2018-09-M3 JEE package for macOS and run it, I get massive amounts of bundles being installed, but not resolved. Most of these things seem to go back to: org.apache.lucene.queryparser_7.1.0.v20180828-2118 having issues to resolve a package import for “org.apache.lucene.docu