On 7 Oct 2016, at 2:43, Alexey Kazakov wrote:
I'm not sure we can do anything about that beyond documenting it
as a
known issue.
We could contribute the fix to make it updatable.
If I understand the issue correctly he would just need to provide p2
metadata similar to what we have
done when org.sonatype moved to org.eclipse and org.jboss.tools.m2e.*
moved to org.eclipse.
Very few actually knows how to do that.
/max
Yes, updates might be tricky no matter how you installed and updating
Subeclipse. Via pure p2 or Central. But we don't install Subeclipse by
default, so, doesn't look like a critical issue ;)
Thanks.
On 10/06/2016 02:18 AM, Mickael Istria wrote:
> On 10/06/2016 11:11 AM, Max Rydahl Andersen wrote:
>> Hey,
>> Not sure if others noticed this but subclipse moved and upgrades
>> might be tricky.
>> Something that might affect our central update experience.
> Maybe in a good way ;) Having 2 competing SVN plugins is a bad thing,
> maybe Subclipse will loose enough users by the way to make us able to
> drop it.
> --
> Mickael Istria
> Eclipse developer for Red Hat Developers
> <
http://developers.redhat.com>
> My blog <
http://mickaelistria.wordpress.com> - My Tweets
> <
http://twitter.com/mickaelistria>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
/max
http://about.me/maxandersen