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

Discussion:

Martin Lippert

2018-09-05 11:22:56 UTC

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.document”.

Any idea what is going wrong here?

Cheers,
-Martin

Gunnar Wagenknecht

2018-09-05 12:20:25 UTC

Permalink

Post by Martin Lippert
org.apache.lucene.queryparser_7.1.0.v20180828-2118

This looks like https://bugs.eclipse.org/538546 <https://bugs.eclipse.org/538546>

What other bundles are not resolving?

-Gunnar

Roland Grunberg

2018-09-05 16:48:31 UTC

Permalink

Post by Martin Lippert
org.apache.lucene.queryparser_7.1.0.v20180828-2118

--
Roland Grunberg

Nick Boldt

2018-09-10 14:37:23 UTC

Permalink

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 builds
to the simrel, but it'll be contributed soon too.

Post by Roland Grunberg

Post by Martin Lippert
org.apache.lucene.queryparser_7.1.0.v20180828-2118

--
Nick Boldt

Principal Software Engineer, RHCSA

Productization Lead :: JBoss Tools & Dev Studio

IM: @nickboldt / @nboldt / http://nick.divbyzero.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
@ @redhatnews <https://twitter.com/redhatnews> Red Hat
<https://www.facebook.com/RedHatInc>
<https://www.facebook.com/RedHatInc>

âThe Only Thing That Is Constant Is Changeâ - Heraclitus

Nick Boldt

2018-09-10 15:45:38 UTC

Permalink

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] https://ci.eclipse.org/simrel/job/simrel.runaggregator.pipeline/

Nick

Post by Nick Boldt
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 builds
to the simrel, but it'll be contributed soon too.

Post by Roland Grunberg

Post by Martin Lippert
org.apache.lucene.queryparser_7.1.0.v20180828-2118

Ed Willink

2018-09-10 15:59:25 UTC

Permalink

Hi Nick

If you contribute determinstically such as:

Â <repositories
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 such as:

Â <repositories
location="http://download.eclipse.org/modeling/mdt/ocl/updates/milestones"
description="OCL">

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 broken until you fix the mess.

IMHO generic contributions should be strongly deprecated.

Â Â Â Regards

Â Â Â Â Â Â Ed Willink

Post by Nick Boldt
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] https://ci.eclipse.org/simrel/job/simrel.runaggregator.pipeline/
Nick
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 builds to the simrel, but it'll be contributed soon too.
On Wed, Sep 5, 2018 at 12:48 PM Roland Grunberg

On Sep 5, 2018, at 13:22, Martin Lippert
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 believe for DTP).
AFAICT only, org.eclipse.datatools.sqltools.result is
requiring it so
once they rebuild, it should no longer cause issues.
Cheers,
--
Roland Grunberg
_______________________________________________
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
--
Nick Boldt
Principal Software Engineer, RHCSA
Productization Lead :: JBoss Tools & Dev Studio
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
@ @redhatnews <https://twitter.com/redhatnews> Â Â Â Red Hat
<https://www.facebook.com/RedHatInc>
<https://www.facebook.com/RedHatInc>
âThe Only Thing That Is Constant Is Changeâ - Heraclitus
--
Nick Boldt
Principal Software Engineer, RHCSA
Productization Lead :: JBoss Tools & Dev Studio
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
@ @redhatnews <https://twitter.com/redhatnews> Â Â Â Red Hat
<https://www.facebook.com/RedHatInc>
<https://www.facebook.com/RedHatInc>
âThe Only Thing That Is Constant Is Changeâ - Heraclitus
_______________________________________________
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

Nick Boldt

2018-09-10 16:08:24 UTC

Permalink

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
deterministic.

Anyway I guess your point is that the job trigger SHOULD be git, not manual
via the JIPP's web UI. Therefore I'll just push no-op changes when I need
to trigger a rebuild.

Thanks!

Nick

Post by Ed Willink
Hi Nick
<repositories location=
"http://download.eclipse.org/modeling/mdt/ocl/updates/milestones/6.5.0/S201809100900"
<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.
<repositories location=
"http://download.eclipse.org/modeling/mdt/ocl/updates/milestones"
<http://download.eclipse.org/modeling/mdt/ocl/updates/milestones>
description="OCL">
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 broken until you fix the mess.
IMHO generic contributions should be strongly deprecated.
Regards
Ed Willink
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] https://ci.eclipse.org/simrel/job/simrel.runaggregator.pipeline/
Nick

Post by Nick Boldt
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
builds to the simrel, but it'll be contributed soon too.

Post by Roland Grunberg

Post by Martin Lippert
org.apache.lucene.queryparser_7.1.0.v20180828-2118

--
Nick Boldt
Principal Software Engineer, RHCSA
Productization Lead :: JBoss Tools & Dev Studio
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
@ @redhatnews <https://twitter.com/redhatnews> Red Hat
<https://www.facebook.com/RedHatInc>
<https://www.facebook.com/RedHatInc>
âThe Only Thing That Is Constant Is Changeâ - Heraclitus
_______________________________________________
To change your delivery options, retrieve your password, or unsubscribe from this list, visithttps://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
<#m_-6459543008617502765_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
_______________________________________________
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Mickael Istria

2018-09-10 16:11:35 UTC

Permalink

Hi,

Post by Ed Willink
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 broken until you fix the mess.
IMHO generic contributions should be strongly deprecated.

Documentation makes it clear:
https://wiki.eclipse.org/Simrel/Contributing_to_Simrel_Aggregation_Build#Format
However, pragmatically, plugins that do a lot of builds and want them to be
continuously integrated don't have a real choice here, unless they're fine
to update their aggrcon several times a day... Referencing mutable repos or
content is pragmatically more productive, and that's probably the cause of
several bad practices.

While generic contributions are pragmatically used by many projects during
the "dev" stream, they should indeed be banished while we enter the RC
phase.
But as long a we do not automate a failing build for this bad practice,
no-one will really spend more care on applying this rule.

What we need to develop is a set of concrete and automatable rules that for
a given .aggrcon file can say whether it's valid or not.
Then, we can plug it in the builder so an invalid aggrcon fails the build
if we're in RC.

Frederic Gurr

2018-09-10 16:11:45 UTC

Permalink

Hi,

The simrel.runaggregator.pipeline job checks for SCM changes every 10
minutes.

Regards,

Fred

Post by Nick Boldt
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] https://ci.eclipse.org/simrel/job/simrel.runaggregator.pipeline/
Nick
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
builds to the simrel, but it'll be contributed soon too.

Post by Martin Lippert
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 believe for DTP).
AFAICT only, org.eclipse.datatools.sqltools.result is requiring it so
once they rebuild, it should no longer cause issues.
Cheers,
--
Roland Grunberg
_______________________________________________
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
--
Nick Boldt
Principal Software Engineer, RHCSA
Productization Lead :: JBoss Tools & Dev Studio
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
@ @redhatnews <https://twitter.com/redhatnews> Red Hat
<https://www.facebook.com/RedHatInc>
<https://www.facebook.com/RedHatInc>
“The Only Thing That Is Constant Is Change” - Heraclitus
--
Nick Boldt
Principal Software Engineer, RHCSA
Productization Lead :: JBoss Tools & Dev Studio
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
@ @redhatnews <https://twitter.com/redhatnews> Red Hat
<https://www.facebook.com/RedHatInc>
<https://www.facebook.com/RedHatInc>
“The Only Thing That Is Constant Is Change” - Heraclitus
_______________________________________________
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

--
Frederic Gurr
Release Engineer | Eclipse Foundation Europe GmbH

Annastr. 44, D-64673 Zwingenberg
Handelsregister: Darmstadt HRB 92821
Managing Directors: Ralph Mueller, Mike Milinkovich, Chris Laroque