I added it to fix a problem w/ dependency on a newer version of the
jdt plugins (a patched version).
why oh why do you keep adding dependencies without verifying they are correct ?
Stop fixing issues this way :)
I think this might have been introduced by new Central plugins
committed last week.
If we can depend on the vanilla JDT from Indigo SR1 instead of the patched version, I can
remove the patch feature from the TP.
It should never have made it in - no way would we start depending on a patched JDT without
a discussion/approval on it.
Tycho guys pointed me at https://bugs.eclipse.org/bugs/show_bug.cgi?id=350133
indicates that p2 mechanisms will pick these up because the JDT version
of the patched version is newer.
Another point for making sure our target files are using *specific* versions and why just
using pure repositories.
On 11/28/2011 08:01 AM, Max Rydahl Andersen wrote:
> I'm getting weird dependency errors on the mvn build currently because of
org.eclipse.objectteams.otdt.core.patch.feature.jar being present.
> Why is that in there ? And where does it come from ? nothing we use depend on object
teams weird JDT patch afaik ?
> jbosstools-dev mailing list
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio