[
https://issues.jboss.org/browse/JBIDE-11729?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-11729:
-------------------------------------
A significant re-org has been done. It seems now that consumers of astools have two
options:
1) They have a dependency on org.jboss.ide.eclipse.as.wtp.core for interface / compile
dependencies. If they require classes that are not there, they must make an API request to
me to move code into the API plugin.
OR, if they REQUIRE all of astools present,
2) The consumer must have a feature-level dependency on the astools feature.
Depending only on org.jboss.ide.eclipse.as.core is no longer "supported". Users
*will* get only a half-complete astools, as the as71 services will not be installed. So
it's up to consumers to consume either only the api plugin or the entire astools
feature.
I'd be willing to open this bug again if someone is finding it impossible to do as
suggested here. But other than that, it seems now that the plugins are organized properly
such that this is now in the hands of the consuming component.
problem with AS installation since declarative services are not
installed automagically
---------------------------------------------------------------------------------------
Key: JBIDE-11729
URL:
https://issues.jboss.org/browse/JBIDE-11729
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Reporter: Max Rydahl Andersen
Assignee: Rob Stryker
Priority: Blocker
Fix For: 4.0.0.Alpha2
need to investigate the root cause of JBIDE-11645 and JBIDE-10803
Is the solution just that central and jaxrs feature depends on the AS feature?
But doesn't that limit the general p2 installation/configuration?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira