Oh! yes, after updating plug-in code to use 2.0.1-SNAPSHOT artifacts
geronimo-web-2.5-builder, I am now getting the errors initially reported in
that JIRA.
Any particular reason why those changes (as well as GERONIMODEVTOOLS-180)
haven't yet been committed into trunk?
Now testing upgrade to
Hi again Shiva, the changes to trunk for the geronimo-web-2.5 artifact is part
of the set of changes required for using the new 2.0.1 Geronimo server, and
since they had not been working well until last night, I have not committed them
to trunk. I'm doing a clean M2 repo build of the plugin now
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521019
]
Kan Ogawa commented on GERONIMODEVTOOLS-184:
Perhaps, XmlBeans library ( included in
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521078
]
Ted Kirby commented on GERONIMODEVTOOLS-184:
Thanks, Kan, that looks like the problem. The
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521125
]
Shiva Kumar H R commented on GERONIMODEVTOOLS-184:
--
Instead of
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521137
]
Shiva Kumar H R commented on GERONIMODEVTOOLS-184:
--
Changing xmlbeans version to 2.3.0
Hi Shiva, are you using the new 2.0.1 artifacts to build the plugin ?? And if
so, did you change the pom.xml to use the geronimo-web-2.5-builder artifact
instead of the geronimo-web-builder artifact ??
Shiva Kumar H R (JIRA) wrote:
[
