[
https://issues.apache.org/jira/browse/GERONIMO-4239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633030#action_12633030
]
David Jencks commented on GERONIMO-4239:
----------------------------------------
Previous changes left us with a nasty class cast exception when trying to use
the offline deployer. This took a while to unravel sensibly but I think rev
697438 is an OK solution.
-- moved our ModuleConfigurer class into the jsr88 classloader plugin. This
was the class causing the problem and can be used prettty much anywhere jsr88
is used so this seems reasonable.
-- moved the DConfigBean support into geronimo-service-builder. I'm not
thrilled with this but all our plans include the environment element so
anything using DConfigBeans will be depending on g-service-builder anyway.
These classes don't really fit into the jsr88 classloader since they use
xmlbeans.
This caused a lot of ripples through the build but the results seem perhaps
slightly cleaner that when I started.
> car-maven-plugin dependencies configuration should enhance maven dependencies
> -----------------------------------------------------------------------------
>
> Key: GERONIMO-4239
> URL: https://issues.apache.org/jira/browse/GERONIMO-4239
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: car-maven-plugin
> Affects Versions: 2.2
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 2.2
>
>
> When useMavenDependencies is true, we should take any info in the c-m-p
> plugin configuration dependencies section and use it to enhance the maven
> dependencies with <import> and <start> information. This should let us
> _always_ have useMavenDependencies on and result in much shorter plugin
> configurations.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
