[
https://issues.apache.org/jira/browse/GERONIMO-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618403#action_12618403
]
David Jencks commented on GERONIMO-4221:
----------------------------------------
I've thought about this for a long time and see 2 possible ways forward:
1. run the c-m-p 3 times and have it produce the 3 car files indenpendently.
This is really wasteful since the c-m-p already does build all the needed car
files, it just doesn't move 2 of them into the local maven repo.
2. use maven classifiers for the app clients rather than having completely
separate artifact names.
(2) seems like it would probably involve more changes to geronimo internals but
it also fits much better with maven so I think we should look into just how
hard it would be to implement.
> 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.
