[jbosstools-dev] [cross-project-issues-dev] TM withdrawal from Mars

Max Rydahl Andersen manderse at redhat.com
Mon Nov 24 03:16:11 EST 2014


If it is not available in Mars we can't really depend on it without we start bundling it and then we own the maintaence of It risking others will bundle other versions and we'll be incompatible. It is bad enough there now are multiple terminals, but multiple ways to define and connect to remote hosts for file transferring. That would be a mess. 

why are we using their dedicated repo and not the release train as we do for other things ? To get source for Dev to or?

So sure, there are hacks for bundling this in. None of them are sustainable if the project is looking for termination. 

/max
http://about.me/maxandersen


> On 24 Nov 2014, at 09:03, Mickael Istria <mistria at redhat.com> wrote:
> 
> I'm not sure this is *so* critical. There message means that TM won't be in Mars by default, and that they don't plan new development on the project.
> 
> The removal of TM from Mars doesn't prevent us from consuming it in our TP. We actually don't even use the Mars repo to get TM currently, but already their dedicated repo.
> The fact that there won't be new development is not important as long as they welcome patches.
> 
> So the project is not "killed" in a way that it's not usable any more, it's only that not much will happen from its current contributors.
> -- 
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat
> My blog - My Tweets
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141124/4244ddcf/attachment.html 


More information about the jbosstools-dev mailing list