You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mikhail Olifirenko (JIRA)" <ji...@codehaus.org> on 2010/01/09 17:24:55 UTC

[jira] Commented: (MEAR-119) Maven-ear-plugin seems not to expand/filter properties in classifiers

    [ http://jira.codehaus.org/browse/MEAR-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206014#action_206014 ] 

Mikhail Olifirenko commented on MEAR-119:
-----------------------------------------

You are right, Stephane. It is not issue of maven-ear-plugin.
The issue concerns properties with the same names in unrelated poms (those are not in parent-child relationship). Such properties are not considered as the same or at least proccesed separately. Sorry for wrong troubleshooting. 

> Maven-ear-plugin seems not to expand/filter properties in classifiers
> ---------------------------------------------------------------------
>
>                 Key: MEAR-119
>                 URL: http://jira.codehaus.org/browse/MEAR-119
>             Project: Maven 2.x Ear Plugin
>          Issue Type: Bug
>    Affects Versions: 2.4
>            Reporter: Mikhail Olifirenko
>
> The probable issue deals with using of classified transitive dependencies, where classifiers are specified by profiles.
> There are 3 modules: ear-application, ejb1 and ejb2 is used by ejb1 module. Ear application ear-application includes EJB modules ejb1 and ejb2. ejb1 depends on ejb2.
> Let's ear-application pom.xml contains:
> ...
>          <plugin>
>             <groupId>org.apache.maven.plugins</groupId>
>             <artifactId>maven-ear-plugin</artifactId>
>             <version>2.4</version>
>             <configuration>
>                <classifier>${var}</classifier>
>                <version>5</version>
>                <modules>
>                   <ejbModule>
>                      <groupId>com.softcomputer</groupId>
>                      <artifactId>ejb1</artifactId>
>                      <classifier>${var}</classifier>
>                   </ejbModule>
>                   <ejbModule>
>                      <groupId>com.softcomputer</groupId>
>                      <artifactId>ejb2</artifactId>
>                      <classifier>${var}</classifier>
>                   </ejbModule>
> ...
> Pom.xml of ejb1 contains:
> ...
>    <artifactId>ejb1</artifactId>
>    <groupId>com.softcomputer</groupId>
>    <name>First EJB module</name>
>    <packaging>ejb</packaging>
>    <dependencies>
>       <dependency>
>          <groupId>com.softcomputer</groupId>
>          <artifactId>ejb2</artifactId>
>          <type>ejb</type>
>          <classifier>${var}</classifier>
>       </dependency>
> ...
> Attempt to build specified enterprise application leads to:
> ...
> INFO] Failed to resolve artifact.
> Missing:
> ----------
> 1) com.softcomputer:ejb2:ejb:${var}:1.0.0-05-01
> ...
>   Path to dependency: 
>    1) com.softcomputer:ear-application:ear:1.0.0-07-05
>    2) com.softcomputer:ejb1:ejb:expandedVar:1.0.0-05-01
>    3) com.softcomputer:ejb2:ejb:${var}:1.0.0-05-01
> ...
> Where ${var} should be expanded with expandedVar value.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira