Replies: 2 comments 2 replies
-
I don't have concerns over such a change. Only question is do you plan to work on it soon? I think it's time to set a date for Tycho 3.0 and work towards it. Smth like end of September is what is currently on my mind. |
Beta Was this translation helpful? Give feedback.
1 reply
-
@mickaelistria any concerns? Do we know about any other users of |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
As the name suggest
sisu-equinox
is dedicated to equinox, but in fact many of its API is not really specific to equinox, one might even argue that as launching and behavior of OSGi Frameworks is well defined it should be possible to completely abstract that Equinox is used.I therefore like to suggest to rename
sisu-equinox
tosisu-osgi
and as part of this move all generic api to one module (currently it is split oversisu-equinox-api
/sisu-equinox-embedder
/sisu-equinox-launching
.Also
sisu-equinox-launching
currently is tied totycho-embedder-api
byorg.eclipse.tycho.ArtifactDescriptor
andorg.eclipse.tycho.ArtifactKey
this seems not suitable and should be replaced with a sisu interface (that Tycho maybe implements/extends). When we have do the API split we can easily have asisu-equinox-launching
that contains the equinox specific parts.This will make the reuse of this components in other context much more the 3.x release seems a good opportunity for this, any ideas / concerns?
Beta Was this translation helpful? Give feedback.
All reactions