[
https://issues.apache.org/jira/browse/GERONIMO-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618439#action_12618439
]
David Jencks commented on GERONIMO-4221:
----------------------------------------
In either case there are issues to be solved with the geronimo-plugin.xml. An
app client geronimo-plugin.xml should contain info for assembling an app client
assembly sufficient to run the app client plugin itself.
I think the classifier approach will be more likely to provide a manageable
solution to this. I'm thinking of more c-m-p configuration with separate
"instance" sections for each app client/classifier. Possibly the
<useMavenDependencies> element should be moved or duplicated inside <instance>
> car file for daytrader module is not generated correctly via c-m-p
> -------------------------------------------------------------------
>
> Key: GERONIMO-4221
> URL: https://issues.apache.org/jira/browse/GERONIMO-4221
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: car-maven-plugin
> Affects Versions: 2.1.2, 2.1.3, 2.2
> Reporter: Lin Sun
> Assignee: Lin Sun
>
> The daytrader tomcat car file isn't generated correctly when building it
> using maven c-m-p plugin. It only generates the necessary files for the
> org.apache.geronimo.daytrader/daytrader-tomcat/2.0-SNAPSHOT/car module, but
> not the files for the two app clients that daytrader has - daytrader-wsclient
> & daytrader-streamer-client. After building the plugin using maven, the
> target/repository directory looks right to me that contains all 3 modules.
> The user impact: after installation of the daytrader tomcat plugin, the
> server doesn't recognize the moduleid for either the daytrader-wsclient or
> daytrader-streamer-client.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
