[
https://issues.jboss.org/browse/JBIDE-10293?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-10293.
---------------------------------
Resolution: Done
I've committed the newest set of jars from the recent beta1b build. These jars have
been tested against the following app servers, but are presumed to work against more:
jboss 7.0.2
jboss 7.1.0.beta1b
jboss 7.1.0.cr1
It works for all usecases that i've tested. I am assuming it also works against 7.0.0
and 7.0.1.
I have ensured that both app-server's server adapters in eclipse now use the same
service, the 7.1 service, which holds these jars. This means the as7.management plugin is
now functionally useless. It is never used. It can / may be removed, if all my tests are
correct. I am not removing it yet, as I feel full automated testing should be done before
taking that step.
But for now, all 7.x adapters are using the same service and client jars in the
background, and it appears to work fantastically.
AS7.1 Beta1b support
--------------------
Key: JBIDE-10293
URL:
https://issues.jboss.org/browse/JBIDE-10293
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Reporter: Max Rydahl Andersen
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.0.M5
as71b1b is being done and to support that we need to:
* Update the client jars
* Remove the code that messes with SASL providers in global state since now it is being
scanned/handled via classpath/meta-inf/services instead
* Fix our login code which has problems recognizing authentication actually have happened
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira