Re: [cross-project-issues-dev] Eclipse Mylyn wants to participate in Sim

[Ed Merks <ed.merks@xxxxxxxxx>]

Let's discuss on the issue so we don't flood the group's inbox. 

Then we can note there that

1. Generated OSGi artifacts are not part of the process, and if they are to be part of the process, then we need a process for them.
   
2. The m2e-generated package imports don't have version ranges, which appears to be what is suggested to be bad metadata; that appears to be a problem that cannot be solved.  The generated exported package metadata appears to be very rich though, so that's great!
   

On 01.05.2023 10:01, Christoph Läubrich wrote:

> There
>       already IS a central place, called maven-central, the rest is just
>       a matter of bad meta-data use that is:
>       
>       
>       - require-bundle for no good reason
>       
>       - no proper version ranges on imports
>       
>       - no use-clauses and versions on exports
>       
>       
>       
>       Am 01.05.23 um 09:42 schrieb Alexander Fedorov:
>       
> > Hello Ed,
> >         
> >         
> >         I am also not happy to see a black hole that appeared on the
> >         site of the Orbit project.
> >         
> >         
> >         I tried my best to understand what is the right way to consume
> >         required 3rd party libraries and the answer was "In the end, I
> >         think the process is very clear.*Everyone use the latest
> >         version*."
> >         (https://github.com/merks/simrel-maven/issues/3#issuecomment-1497228678)
> >         
> >         And this is exactly what was done.
> >         
> >         
> >         Please publish the recommended process of managing 3rd party
> >         libraries and we will follow it.
> >         
> >         And I also don't see how it could be achieved without
> >         introducing another central location instead of Orbit.
> >         
> >         
> >         Regards,
> >         
> >         AF
> >         
> >         
> >         5/1/2023 10:01 AM, Ed Merks пишет:
> >         
> > >           
> > >           While I'm happy to see Mylyn back, I'm not happy to see it
> > >           depending on direct-from-maven dependencies that are
> > >           generated. It also appears that the direct-from-maven
> > >           artifacts are not being signed.  I've opened up this to track
> > >           the issues:
> > >           
> > >           
> > >           https://github.com/eclipse-mylyn/org.eclipse.mylyn/issues/103
> > >           
> > >           
> > >           Note that TM4E is also generating direct-from-maven
> > >           dependencies.
> > >           
> > >           
> > >           As I mentioned in the above issue, I think generated
> > >           dependencies is a new can of worms and we've not even been
> > >           managing the existing bucket of worms.   We really don't need
> > >           a 4th version of  org.apache.lucene.core on the train,  even
> > >           if it's called org.apache.lucene.lucene-core instead.
> > >           
> > >           
> > >            I see no good solution for managing this other than managing
> > >           it from one central location that ensures exactly one p2
> > >           artifact is produced per maven artifact:
> > >           
> > >           
> > >           https://github.com/eclipse/orbit/issues/8
> > >           
> > >           https://github.com/merks/simrel-maven/issues/4
> > >           
> > >           
> > >           
> > >           On 01.05.2023 03:29, Jonah Graham wrote:
> > >           
> > > > Welcome back Mylyn!
> > > >             
> > > >             
> > > >             As planning council chair I see no problem with Mylyn
> > > >             rejoining for M2, but I'll bring it up with the full
> > > >             Planning Council at our next meeting for good measure and if
> > > >             there is any concern I'll let you know. In the meantime I
> > > >             look forward to seeing your updated contribution. Please
> > > >             reach out if you have any questions or concerns with
> > > >             reenabling the contribution.
> > > >             
> > > >             
> > > >             Well done on rebooting Mylyn.
> > > >             
> > > >             
> > > >             Jonah
> > > >             
> > > >             
> > > >             
> > > >             On Sun, Apr 30, 2023, 3:57 p.m. Alexander Fedorov
> > > >             <alexander.fedorov@xxxxxxxxxx> wrote:
> > > >             
> > > >             
> > > >                 Hello,
> > > >             
> > > >             
> > > >                 As Eclipse Mylyn Project Lead,  in accordance with
> > > >             Simultaneous
> > > >             
> > > >                 Release
> > > >             
> > > >                 Requirements [1], I hereby announce the intent of
> > > >             Eclipse Mylyn to
> > > >             
> > > >                 participate in SimRel 2023-06
> > > >             
> > > >                 I hope the fact of re-joining will serve as an excuse
> > > >             for a slightly
> > > >             
> > > >                 later notification (which should have happened before
> > > >             M1).
> > > >             
> > > >             
> > > >                 The plan is to start from contribution of 3.26.0 [2] to
> > > >             SimRel
> > > >             
> > > >                 2023-06
> > > >             
> > > >                 M2 and then to provide another service release for
> > > >             2023-06 RC2 with
> > > >             
> > > >                 addressed feedback.
> > > >             
> > > >                 There is a 3.26.0 RC1 build available for early testing
> > > >             [3], please
> > > >             
> > > >                 submit your feedback to Mylyn GitHub repository [4].
> > > >             
> > > >             
> > > >                 [1]
> > > >             
> > > >                
> > > > https://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements#How_to_announce_your_participation
> > > >                 [2]
> > > >             https://projects.eclipse.org/projects/tools.mylyn/releases/3.26.0
> > > >             
> > > >                 [3] https://download.eclipse.org/mylyn/stage/
> > > >             
> > > >                 [4]
> > > >             https://github.com/eclipse-mylyn/org.eclipse.mylyn/issues
> > > >             
> > > >             
> > > >                 Regards,
> > > >             
> > > >                 AF
> > > >             
> > > >                 _______________________________________________
> > > >             
> > > >                 cross-project-issues-dev mailing list
> > > >             
> > > >                 cross-project-issues-dev@xxxxxxxxxxx
> > > >             
> > > >                 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@xxxxxxxxxxx
> > > >             
> > > >             To unsubscribe from this list,
> > > >             visithttps://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
> > > >             
> > > >           
> > >           
> > >           _______________________________________________
> > >           
> > >           cross-project-issues-dev mailing list
> > >           
> > >           cross-project-issues-dev@xxxxxxxxxxx
> > >           
> > >           To unsubscribe from this list,
> > >           visithttps://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
> > >           
> > >         
> >         
> >         
> >         _______________________________________________
> >         
> >         cross-project-issues-dev mailing list
> >         
> >         cross-project-issues-dev@xxxxxxxxxxx
> >         
> >         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@xxxxxxxxxxx
>       
>       To unsubscribe from this list, visit
>       https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>       
>