On 04/04/2013 06:39 AM, Max Rydahl Andersen wrote:
rob - where is the jira outlining this ?
There currently is no jira, but I will make one.
i.e. why do a rename on the tests plugin risking breakage - is that
really worth it ?
I am not renaming any test plugin. Currently there are two core test
plugins, the one from 5 years ago, and the one made this past year with
parametized junit tests to automatically expand on creation of new
server adapters etc.
All of the tests were slowly ported over, most of them when we created
the eap6.1 server adapter. Rather than add yet another test method to
old outdated classes, I'd simply port the test class into the new
plugin, make it parametized, make sure it auto-tests new server types,
and then I'd de-activate the old test.
We're now at the point where the old test plugin has 0 tests.
Technically one is still active, but thats just so the test plugin
doesnt fail with "no tests found". Also I obviously can't remove the
utility methods which others (like esb etc) may use.
There's no RUSH for me to remove the test plugin, but there's also
absolutely no reason for the plugin to remain around either. It
currently sits there and does nothing, so it'd be nice to remove it if
nobody is using it. if people are using it, they're likely also using
outdated ways of testing things (deployment etc) or outdated apis.
So... I'm not renaming any plugin.
On Wed, Apr 03, 2013 at 03:52:13AM +0800, Rob Stryker wrote:
> Just a reminder:
> I've been continuing work on migrating any test plugins which depend on
> org.jboss.ide.eclipse.as.test to use methods and classes in
> org.jboss.tools.as.test.core instead.
> I've grepped my local codebase, but I haven't seen any plugins with a
> dependency on this test plugin. So if you're an owner of a module which
> you know requires any code from org.jboss.ide.eclipse.as.test, please
> respond and let me know so we can investigate the impact of eventually
> removing this project from the build.
> So far I've only seen esb matching any strings im searching for, and it
> seems they already depend on the new one:
> So anyone else who has a dependency, please let me know.
> - Rob Stryker.
> jbosstools-dev mailing list