[
http://issues.apache.org/jira/browse/GERONIMO-2225?page=comments#action_12423320
]
Anita Kulshreshtha commented on GERONIMO-2225:
----------------------------------------------
When the deployer is invoked (please see PackageBuilder.invokeDeployer(..)
using a filename it creates a zipped artifact (.car) in target/repository. If
it is invoked with null it leaves the generated artifacts unpacked at
target/repository/o/a/g/artifactId.
The daytrader config generates 3 artifacts. These are installed using the
attached artifact feature of Maven 2. The <multipleArtifact> is used for
daytrader. The deployer gives error if target/repository/o/a/g/artifactId
exists. Hence geronimo-plugin.xml must be filtered after the deployer has
finished its work.
I have been using geronimo_groupId (see etc.patch and configs.patch) in
the plans when there was an incompatibility issue. We should create
geronimo-plugin.xml files for M2 in src/conf2.
> The M2 build no longer inserts META-INF/geronimo-plugin.xml into the CARs
> -------------------------------------------------------------------------
>
> Key: GERONIMO-2225
> URL: http://issues.apache.org/jira/browse/GERONIMO-2225
> Project: Geronimo
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: buildsystem
> Affects Versions: 1.2
> Reporter: Jason Dillon
> Assigned To: Jason Dillon
> Priority: Blocker
> Fix For: 1.2
>
>
> The M2 build no longer inserts META-INF/geronimo-plugin.xml into the CARs
> that have src/conf/geronimo-plugin.xml. There was handling for this in the
> M1 build (e.g. for the welcome app and other examples).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
