[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
B.J. Reed updated GERONIMODEVTOOLS-344:
---------------------------------------
Attachment: GERONIMODEVTOOLS-344.patch
I was unable to figure out exactly where the clash was occurring, so I went the
second route....removing the need for xstream and xpp3 from
ModuleArtifactMapper. I have added an inner class that does simple parsing and
writing for the moduleserver.info file. I'm sure we could use JAXB or some
other solution to be more elegant, but I figure for the small amount of data
that we are dealing with in that file, we can just roll our own. Also needed
to change a few pom's and a manifest.mf since we no longer need the xstream and
xpp3 jars so it will make the whole GEP smaller.
Ted, please give this a try and see if it helps.
> Cannot utilize the xpp3-1.1.3.4.O jar in GEP
> ---------------------------------------------
>
> Key: GERONIMODEVTOOLS-344
> URL:
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-344
> Project: Geronimo-Devtools
> Issue Type: Bug
> Affects Versions: 2.1.0
> Reporter: Tim McConnell
> Assignee: B.J. Reed
> Fix For: 2.1.1
>
> Attachments: GERONIMODEVTOOLS-344.patch
>
>
> During the release of the GEP 2.1.0 we encountered problems with the
> xpp3-1.1.3.4.O.jar file when trying to create a new dynamic web problem
> (i.e., unhandled event condition). Need to investigate and understand why so
> that we can use the same version of this artifact that the server is using.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
