Issue 5 in constants-to-enum-eclipse-plugin: Split implementation and tests

0 views
Skip to first unread message

codesite...@google.com

unread,
Aug 28, 2009, 6:24:28 AM8/28/09
to convert_constant...@googlegroups.com

Comment #2 on issue 5 by b.muskalla: Split implementation and tests
http://code.google.com/p/constants-to-enum-eclipse-plugin/issues/detail?id=5

While I generally prefer the approach to split core and UI, we should think
about this
twice. Keeping in mind to integrate ourselves into JDT, this change doesn't
make much
sense as the whole refactoring story of JDT lives in UI.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

codesite...@google.com

unread,
Aug 28, 2009, 6:45:37 AM8/28/09
to convert_constant...@googlegroups.com
Updates:
Status: Fixed

Comment #3 on issue 5 by b.muskalla: Split implementation and tests
http://code.google.com/p/constants-to-enum-eclipse-plugin/issues/detail?id=5

Introduced a new bundle called edu.ohio_state.khatchad.refactoring.tests.
Tests and resources are moved to the new bundle.
Tests now have a direct dependency to the JDT test infrastructure, thus you
need the
JDT refactoring tests plugins in your workspace.

I attached a team project set you can use the import the test bundles into
your
workspace. Used the 3_5 branch of JDT as we can't build against HEAD at the
moment.

Attachments:
tests.psf 533 bytes

codesite...@google.com

unread,
Aug 28, 2009, 9:21:07 AM8/28/09
to convert_constant...@googlegroups.com

Comment #4 on issue 5 by raffi.t.khatchadourian: Split implementation and
tests
http://code.google.com/p/constants-to-enum-eclipse-plugin/issues/detail?id=5

Great, thanks! Yes, I agree that splitting UI and core doesn't make much
sense if we are planning to integrate into
the JDT.

Reply all
Reply to author
Forward
0 new messages