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-14837 convert seam to use stacks for downloadRuntimes #90

Closed
wants to merge 2 commits into from

Conversation

robstryker
Copy link
Member

No description provided.

@@ -35,7 +35,6 @@ Require-Bundle: org.eclipse.ui;bundle-version="3.7.0",
org.eclipse.jst.j2ee.core;bundle-version="1.2.100",
org.eclipse.jst.common.frameworks;bundle-version="1.1.500",
org.jboss.tools.jst.web.kb;visibility:=reexport,
org.jboss.tools.jsf,
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a debatable and un-required change, but, it saved me from having to import more plugins, and, javaee still built fine locally after doing this, so IMO it was an unnecessary dependency.

But I'd be willing to revert this line if asked.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is no hard dependency on JBT JSF plugins in the code but Seam tools depends on Eclipse JSF Tools and it's important that JBT JSF is installed too. It extends Eclipse JSF Tools and fix some problems. I would not remove this dependency for JBT 4.0. Maybe latter we can return to this issue.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok I'll fix the patch.

It would seem that you guys should be using feature requirements then instead of plugin dependencies.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The seam feature does require o.j.t.jsf.feature. And maybe it's enough but I would not to remove this dependency for 4.0 anyway. Just not to break something when we so close to the final release.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

makes perfect sense.

@alexeykazakov
Copy link
Contributor

I squashed the PRs and pushed them to master.

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