[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cross-project-issues-dev] Eclipse Mylyn wants to participate in SimRel 2023-06
|
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
_______________________________________________
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