Hi

https://bugs.eclipse.org/bugs/show_bug.cgi?id=579584 raised to re-instate antlr 3.2.0

https://bugs.eclipse.org/bugs/show_bug.cgi?id=579583 raised to re-instate lpg.runtime.java

Regards

Ed Willink

On 04/04/2022 16:35, Christian Dietrich wrote:

ok, i found some some orphans
guice 5 (on 2022-06) needs javax.inject
and org.aopalliance which are both no longer part of 2022-06
i wonder if there is tooling to find more of these inconsistencies

i removed our usage of commons.lang
and updated junit to 4.13.2

gson was broken data in local maven repo

Am 04.04.22 um 16:33 schrieb Jonah Graham:
Hi Christian / Ed / Ed / other Orbit consumers,

> @Jonah does this mean i deed to use 10 repos to get the sum of my orbit deps?

No, it means if you rely on the old CVS defined orbit bundles you now need to make that reference explicit in your target file (i.e to R20201118194144 + S20220403232146 for M1) as the Orbit project is not maintaining the old CVS defined bundles anymore.

Using the CVS defined orbit is a risk for the project (and up to the project to decide how much of a risk that is). We no longer have the sources or build machine of the CVS defined bundles and have for the last few years been patching the repo*. Because we don't have a way to build those old bundles everytime a modification needed to be made it was a lot of manual crafting of p2 repos and modifying metadata.

Here is a concrete example. Orbit's upcoming releases do not want to recommend org.apache.log4j 1.2.15 anymore (due to CVEs). That bundle version is not in S20220403232146, but its replacement is (1.2.19) and no one wants to make another derivative of R20201118194144 that has it excluded.

As for specific dependencies identified in this thread:

>org.antlr.runtime/3.2.0.v201101311130
That version is available in R20201118194144 and newer versions (3.5.2, and numerous 4.x versions) will be in the recommended 2022-06 release.

>JUnit 4.12
Also in R20201118194144 and newer versions (4.13.2 and 5.x) will be in the recommended 2022-06 release.

> com.google.gson 2.8.9
This is in the 2022-06 M1, so not sure what the issue is here.

> javax.inject
Available in R20201118194144. As of now no one has added jakarta.inject (the new name for this bundle) to Orbit's git as an EBR. The whole javax -> jakarta transition has lots of its own problems that so far are being handled piecemeal (and is part of why Mylyn stopped working and has been removed from SimRel).

> commons.lang
Available in R20201118194144. As of now no one has added it to Orbit's git as an EBR.

> should we create a bugzilla?
There is one - https://bugs.eclipse.org/bugs/show_bug.cgi?id=568936

I hope that clarifies things. Please ask follow-ups.
Jonah


* https://download.eclipse.org/tools/orbit/downloads/drops/R20160520211859/ was the last recommended build from CVS, https://download.eclipse.org/tools/orbit/downloads/drops/R20201118194144/ is the many times patched version of that.




~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com <http://www.kichwacoders.com>


On Mon, 4 Apr 2022 at 01:03, Christian Dietrich <christian.dietr...@itemis.de> wrote:

    @Jonah does this mean i deed to use 10 repos to get the sum of my
    orbit deps?

    i am getting

    Error: Failed to resolve target definition
    
/home/runner/work/xtext-reference-projects/xtext-reference-projects/integrationtests/org.eclipse.xtext.integrationtests.target/org.eclipse.xtext.integrationtests.target.target:
    Could not find "org.antlr.runtime/3.2.0.v201101311130" in the
    repositories of the current location

    is that intentional?

    Am 04.04.22 um 01:57 schrieb Jonah Graham:
    Hello folks,

    I am distributing this wider than normal because of the larger
    impact of this change. See details below in the quoted emails.

    Following the build process on the wiki[0] I'm declaring
    S20220403232146 [1,2] as our contribution for SimRel 2022-06 M1 [3].

    *Reminder: *As of 2022-06 this is no longer a composite repo.
    The final CVS defined bundles are available
    in R20201118194144[4]. If you need these old bundles I highly
    recommend you add recipes to orbit[5] or change to other options
    like the new Maven in PDE option[6]. We don't really have a way
    to rebuild these old bundles therefore having your project
    depend on them is a risk in your project.

    The following changes are new for 2022-06 M1 since  2022-03 R
    (sorry for the noisy commits on build scripts - these changes
    used to be hidden in configuration changes on Jenkins, but I
    migrated all the build scripts to git):

    4322974 Bug 569078: GMF Runtime have fixed their SimRel
    contribution (fixup)
    fe394e5 Merge "Bug 569078: GMF Runtime have fixed their SimRel
    contribution"
    467effd Bug 568936: Automatically set name/description of build
    0ea4906 Bug 568936: Fix typos/syntax error in build scripts
    43f6ea5 Bug 569078: GMF Runtime have fixed their SimRel contribution
    05613db Bug 568936: Add description to main build process
    6fe3fb2 Bug 568936: Add description to main build process
    *76a5833 Bug 568936: Add org.apache.xml.resolver recipe *<--
    highlighted because this is the /only/ bundle change for 2022-06
    M1 vs 2022-03 R
    e638e8e Bug 568936: Remove CVS bundles from mirroring and output
    bccd811 Bug 568936: Fix name of Jenkinsfile
    7569a3d Bug 568936: Fix typos/syntax error in build scripts
    09458b8 Bug 568936: The timestamp should be ms since 1970
    c3e0f5e Bug 568936: Fix typos/syntax error in build scripts
    9502f26 Bug 568936: Composite handling + always promote build
    119c3f1 Bug 568936: Fix typos/syntax error in build scripts
    74eb7d7 Bug 568936: Fix typos/syntax error in build scripts
    556e608 Bug 568936: Fix typos/syntax error in build scripts
    1fb1ece Bug 568936: Fix typos/syntax error in build scripts
    19fce78 Bug 568936: Fix typos/syntax error in build scripts
    ed3f604 Bug 568936: Remove CVS sourced bundles from Orbit
    e355dbf Bug 568936: Move Jenkinsfile and used scripts into
    source control
    105e5c4 Bug 569078: Make a limited version of bundles from Orbit
    for SimRel (fixup)
    b544c64 Bug 569078: Make a limited version of bundles from Orbit
    for SimRel
    37f3210 Build against Eclipse 4.23
    8d3e517 Update reference repository to 2022-03 R release

    As for the comparing repos - Roland has provided me details
    which I added to the Wiki[0] - but it is non trivial for me to
    run at the moment. Please let me know if you are able to help
    out by providing that info.

    [0]
    
https://wiki.eclipse.org/Orbit/Promotion,_Release,_and_Retention_Policies#Milestone_Release_Process
    [1]
    
https://download.eclipse.org/tools/orbit/downloads/drops/S20220403232146/repository/
 <--
    this release
    [2] https://download.eclipse.org/tools/orbit/downloads/2022-06/
    [3] https://wiki.eclipse.org/Category:SimRel-2022-06
    [4]
    https://download.eclipse.org/tools/orbit/downloads/drops/R20201118194144/
    <-- old CVS repo!
    [5]
    https://wiki.eclipse.org/Orbit/Adding_Bundles_To_Orbit_In_5_Minutes
    [6] I'm not sure what the best link for this is - but Eclipse
    Platform does it here
    
https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/blob/7aa6ff4ba08601f8e5152a95d29b248e490f5fe8/eclipse.platform.releng.prereqs.sdk/eclipse-sdk-prereqs.target#L239

    Thanks,
    Jonah

    ~~~
    Jonah Graham
    Kichwa Coders
    www.kichwacoders.com <http://www.kichwacoders.com>


    On Tue, 22 Feb 2022 at 22:32, Jonah Graham
    <jo...@kichwacoders.com> wrote:

        Hello folks,

        Starting with 2022-06 M1 the Orbit repo will no longer be a
        composite repo combining the old CVS build with the latest
        git based build.

        The 2022-03 recommended build will be the last to contain
        these old CVS bundles.

        Please comment on the bug if this causes you any concerns,
        or would like to voice your support.

        Thanks,
        Jonah

        ~~~
        Jonah Graham
        Kichwa Coders
        www.kichwacoders.com <http://www.kichwacoders.com>


        ---------- Forwarded message ---------
        From: <bugzilla-dae...@eclipse.org>
        Date: Tue, 22 Feb 2022 at 22:29
        Subject: [Bug 568936] Remove remaining CVS defined bundles
        from Orbit recommended builds starting in 2022-06
        To: <jo...@kichwacoders.com>


        https://bugs.eclipse.org/bugs/show_bug.cgi?id=568936
        Product/Component: Orbit / bundles


        Jonah Graham <jo...@kichwacoders.com> changed:

                   What    |Removed      |Added
        
----------------------------------------------------------------------------
                    Summary|Move remaining CVS defined  |Remove
        remaining CVS
                           |bundles to git       |defined bundles
        from Orbit
                           |       |recommended builds starting
                           |       |in 2022-06
           Target Milestone|---      |2022-06

        --- Comment #7 from Jonah Graham <jo...@kichwacoders.com> ---
        After discussing with various stakeholders, including at the
        Planning
        Council[1] the current plan is to instead of migrating all
        these bundles is to
        just deprecate the CVS versions.

        Projects consuming the CVS versions of the bundles can point
        to the last
        release containing them (will be 2022-03 recommended build*)
        and/or update the
        git repo to include them, or better yet consume directly
        from Maven Central.

        Therefore the plan is from 2022-06 M1 the CVS component of
        this Orbit repo will
        be dropped.


        [1] https://wiki.eclipse.org/Planning_Council/2022-02-02
        * please recall that "R" builds in Orbit means recommend,
        not release.

-- You are receiving this mail because:
        You are the assignee for the bug.
        You reported the bug.
        You are on the CC list for the bug.


    _______________________________________________
    cross-project-issues-dev mailing list
    cross-project-issues-dev@eclipse.org
    To unsubscribe from this list, 
visithttps://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

    Vorstand/Board: Jens Wagener (Vors./chairman), Dr. Stephan
    Eberle, Abdelghani El-Kacimi, Wolfgang Neuhaus, Franz-Josef
    Schuermann
    Aufsichtsrat/Supervisory Board: Michael Neuhaus (Vors./chairman),
    Harald Goertz, Eric Swehla
    Sitz der Gesellschaft/Registered Office: Am Brambusch 15-24,
    44536 Lünen (Germany)
    Registergericht/Registry Court: Amtsgericht Dortmund | HRB 20621
    _______________________________________________
    cross-project-issues-dev mailing list
    cross-project-issues-dev@eclipse.org
    To unsubscribe from this list, visit
    https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev


_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, 
visithttps://www.eclipse.org/mailman/listinfo/cross-project-issues-dev


Vorstand/Board: Jens Wagener (Vors./chairman), Dr. Stephan Eberle, Abdelghani El-Kacimi, Wolfgang Neuhaus, Franz-Josef Schuermann Aufsichtsrat/Supervisory Board: Michael Neuhaus (Vors./chairman), Harald Goertz, Eric Swehla Sitz der Gesellschaft/Registered Office: Am Brambusch 15-24, 44536 Lünen (Germany)
Registergericht/Registry Court: Amtsgericht Dortmund | HRB 20621

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, 
visithttps://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to