What is legacy component intended for?

Max Rydahl Andersen wrote: > Hi, > > I was trying to setup a clean tools environment today and stumbled on that we have duplicate .project's in trunk. Why is that ? > > example org.jboss.ide.eclipse.jdt.test.core exists both in legacy and in core..which one is the relevant one ? > > Alot of the others in legacy also seem duplicated...why. > > This prevents me (and other users) to simply to do an import of trunk in eclipse in more or less a single click. > > -max > > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev >

Legacy was intended to be things that were deprecated and no longer under active development, and would eventually be removed. Both modules should be the same as each other right now but I will double check. If they are both the same and there are no differences, I'll remove one ASAP. If there are differences, I'll try to discover which one is the right one and remove the other.

- Rob Max Rydahl Andersen wrote: > On Thu, 10 Jan 2008 02:57:02 +0100, Denis Golovin <dgolovin(a)exadel.com&gt; wrote: > > >> What is legacy component intended for? >> > > Something rob/marshall created a while back - I thought it was only temporary while cleaning up but seems to have stuck around. > > I think it needs to be removed but need to hear from Rob/Marshall the status. > > /max > > >> Max Rydahl Andersen wrote: >> >>> Hi, >>> >>> I was trying to setup a clean tools environment today and stumbled on that we have duplicate .project's in trunk. Why is that ? >>> >>> example org.jboss.ide.eclipse.jdt.test.core exists both in legacy and in core..which one is the relevant one ? >>> >>> Alot of the others in legacy also seem duplicated...why. >>> >>> This prevents me (and other users) to simply to do an import of trunk in eclipse in more or less a single click. >>> >>> -max >>> >>> >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>> >>> >> > > > >

They're not updated, but they're still public in case an adopter wants to check them out and use them.

The real issue here is the duplication of a plugin. Which will be fixed.

Max Rydahl Andersen wrote: > On Fri, 11 Jan 2008 19:18:05 +0100, Rob Stryker <rob.stryker(a)redhat.com&gt; wrote: > > >> Legacy was intended to be things that were deprecated and no longer >> under active development, and would eventually be removed. Both modules >> should be the same as each other right now but I will double check. If >> they are both the same and there are no differences, I'll remove one >> ASAP. If there are differences, I'll try to discover which one is the >> right one and remove the other. >> > > thanks. > > Why not just delete the legacy modules from trunk/svn ? > > /max > > >> - Rob >> >> >> >> Max Rydahl Andersen wrote: >> >>> On Thu, 10 Jan 2008 02:57:02 +0100, Denis Golovin <dgolovin(a)exadel.com&gt; wrote: >>> >>> >>> >>>> What is legacy component intended for? >>>> >>>> >>> Something rob/marshall created a while back - I thought it was only temporary while cleaning up but seems to have stuck around. >>> >>> I think it needs to be removed but need to hear from Rob/Marshall the status. >>> >>> /max >>> >>> >>> >>>> Max Rydahl Andersen wrote: >>>> >>>> >>>>> Hi, >>>>> >>>>> I was trying to setup a clean tools environment today and stumbled on that we have duplicate .project's in trunk. Why is that ? >>>>> >>>>> example org.jboss.ide.eclipse.jdt.test.core exists both in legacy and in core..which one is the relevant one ? >>>>> >>>>> Alot of the others in legacy also seem duplicated...why. >>>>> >>>>> This prevents me (and other users) to simply to do an import of trunk in eclipse in more or less a single click. >>>>> >>>>> -max >>>>> >>>>> >>>>> _______________________________________________ >>>>> jbosstools-dev mailing list >>>>> jbosstools-dev(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>>>> >>>>> >>>>> >>> >>> >>> >> > > > >