[
https://issues.jboss.org/browse/JBIDE-11738?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11738:
---------------------------------------------
From Fred in mail:
I've been working on a - local -
prototype, a maven configurator, that manages an Endorsed Libraries classpath library :
- It parses <compilerArgument> for -Djava.endorsed.dirs=([^ \\t]+) and falls back on
the <compilerArguments><endorseddirs> value.
- It lists all the jars and zips found under the endorsed dirs and adds them to the
Endorsed Libraries classpath library.
- Endorsed Libraries is put first on the project's classpath. For now the endorsed
dirs need to have been created/populated before the project's configuration.
Still needs to :
- check/support relative paths for endorsed dirs
- serialize the Endorsed Lib on disk to survive workspace restarts
- maybe trigger dependency:copy, as Max suggested, if the endorsed dirs don't exist
already (but I'm not super fan of that solution)
- fix some other stuff I'll discover later.
Solve/workaround the issue of needing endorsed libraries on Java 6
------------------------------------------------------------------
Key: JBIDE-11738
URL:
https://issues.jboss.org/browse/JBIDE-11738
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers, maven
Reporter: Max Rydahl Andersen
Assignee: Fred Bricon
Priority: Critical
Fix For: 3.3.0.CR1
JAX-WS has non-backwards compatible API changes requiring you to put specific jars on to
endorsed libraries.
Could we write a configurator that reacts to common ways of working around it in
eclipse.
m2e issue:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=363237
Related to JBIDE-11348
--
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