Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Split implementation and tests #5

Closed
GoogleCodeExporter opened this issue Jun 4, 2015 · 4 comments
Closed

Split implementation and tests #5

GoogleCodeExporter opened this issue Jun 4, 2015 · 4 comments
Labels
auto-migrated Component-Logic Milestone-Release1.0 OpSys-All Priority-Medium Type-Enhancement Usability

Comments

@GoogleCodeExporter
Copy link
Contributor 

Currently everything is packed inside one bundle.
The goal would be to split the actual implementation and the test code into 
two bundles so you don't end up with dependencies to the test framework when 
just installing the refactoring.

Original issue reported on code.google.com by b.muskalla@gmail.com on 22 Aug 2009 at 10:14
@GoogleCodeExporter
Copy link
Contributor Author 

Yes that would be optimal. Also, in the past, I have split the core logic from 
the UI. That may be another option.

Original comment by raffi.t.khatchadourian on 25 Aug 2009 at 2:58

  • Changed state: Accepted
  • Added labels: Component-Logic, Milestone-Release1.0, OpSys-All, Type-Enhancement, Usability
  • Removed labels: Type-Defect

@GoogleCodeExporter
Copy link
Contributor Author 

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.

Original comment by b.muskalla@gmail.com on 28 Aug 2009 at 10:23

@GoogleCodeExporter
Copy link
Contributor Author 

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.

Original comment by b.muskalla@gmail.com on 28 Aug 2009 at 10:44

  • Changed state: Fixed

Attachments:

@GoogleCodeExporter
Copy link
Contributor Author 

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

Original comment by raffi.t.khatchadourian on 28 Aug 2009 at 1:20

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Component-Logic Milestone-Release1.0 OpSys-All Priority-Medium Type-Enhancement Usability
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter