[
https://issues.apache.org/jira/browse/XALANJ-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17762207#comment-17762207
]
Joseph Kessselman commented on XALANJ-2370:
-------------------------------------------
Looking at maven builds now.
Maven has a plugin that can be configured to leave out packages which will be
supplied by the usage environment. I believe the same plug-in can be set up to
automatically rename packages that get bundled into the jarfile, or to generate
a specialized classloader so our code only loads trusted versions of packages
that shipped in its jarfile while other code can search other classpaths for
the version(s) they need. I'm still deciding what makes sense in that regard.
I'm also trying to bring our dependencies up to a recent Maven version, when
possible.
Not necessarily a complete solution to Thomas' concern, but if I can get this
working it'll at least be a step in the right direction.
> java_cup - duplicate classes in classpath
> -----------------------------------------
>
> Key: XALANJ-2370
> URL: https://issues.apache.org/jira/browse/XALANJ-2370
> Project: XalanJ2
> Issue Type: Bug
> Components: Xalan, XSLTC
> Affects Versions: 2.7.1
> Reporter: Thomas Spiegl
> Priority: Blocker
>
> xalan.jar contains java cup classes http://www2.cs.tum.edu/projects/cup/
> without changing the namespace (package name). This leads to duplicate class
> problems, if someone is using a different cup version in his project.
> Just stumbled on this issue as my generated parser did not compile, because
> my IDE loaded xalan's cup classes first.
> I can work around this issue by refactoring cup classes by myself. But this
> should only be a temporary solution.
> To be done: refactor cup package names when delivering with xalan.jar
> Thanks!
> Thomas
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
