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

JBIDE-14299 convert astools to use new runtimes extension point and use stacks #73

Merged
merged 1 commit into from
May 10, 2013

Conversation

robstryker
Copy link
Member

The attached PR (at this moment) is not fully complete. It requires the changes to base (new core component) to be approved. Also, it currently directly links to a custom stacks file in my own jdf topic branch simply as a convenience to let me code the thing up.

But, it works. Nicely 👯

…point and use stacks

updated to reflect progress monitors

JBIDE-14299_use_stacks more work to conform to stacks

Depend on common.core until o.j.t.core is committed

 JBIDE-14299 final cleanup
@robstryker robstryker merged commit d9363b4 into jbosstools:master May 10, 2013
@robstryker
Copy link
Member Author

I've merged the code in without any API changes. The API changs and deprecations will be reserved for cleanup jiras.

@dgolovin
Copy link
Member

How do you know if it works without even single test for this new plugin?

@robstryker
Copy link
Member Author

I knew you'd ask that ;)

Tests are coming, speciically to verify that the id's of the downloadruntimes haven't changed (because central depends on them). I suppose I should have made it part of this commit.

I tested both locally (runtime workbench) and by building locally and verifying all pieces were built, and installing from the local update site. I believe that's sufficient, but, tests are coming.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants