Hi All: I spent some time making this dependency tree and marking it up a bit.
https://bugs.eclipse.org/bugs/attachment.cgi?id=269412 What we can see here is that jeetools and ejb are hopelessly intertwined. These two repos should simply be merged. I find it difficult to come to any other conclusion. Also, it's not the least bit relevant that JEE means "Java Enterprise" and EJB means "Enterprise Java". On the left side, though, we see a small problem with webservices and it's relationship to jeetools. There are two webservices plugins that live in jeetools. They are at the top of the tree inside jeetools, so nothing in jeetools depends on them, however, they depend on 3 webservices plugins. The possible solutions here are to move the 3 deps (wst.ws.parser, wst.wsdl, command.env.core) down into jeetools, or move the other two (jst.j2ee.webservice[.ui]) up into webservices. On a plugin level, these are the changes that make sense. On a feature level, the problem is a bit messier. I believe jeetools currently considers itself the master repo for creating all features. With a clearly separated jeetools / webservices, any jeetools features that depend on ws would need to be moved up into ws directly. This likely means a lot of the larger encompassing features would also need to move up into webservices. This issue (at least the ws side) is being tracked here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=519793
_______________________________________________ wtp-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/wtp-dev
