[
http://jira.codehaus.org/browse/MNG-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed MNG-3191.
-----------------------------
Assignee: Brett Porter
Resolution: Won't Fix
I don't think this is a good idea according to Maven best practices. You should
use a profile instead
> Filtering not applied to dependency POMs
> ----------------------------------------
>
> Key: MNG-3191
> URL: http://jira.codehaus.org/browse/MNG-3191
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 2.0.7
> Reporter: Eric Miles
> Assignee: Brett Porter
>
> I have a dependency in my project from a 3rd party, and it's deployed POM has
> a dependency that is determined via filtering. IE:
> <dependency>
> <groupId>${repository.database.driver.groupId}</groupId>
> <artifactId>${repository.database.driver.artifactId}</artifactId>
> <version>${repository.database.driver.version}</version>
> </dependency>
> When I attempt to reference this dependency in the dependency section of my
> project, I receive the following error while attempting to package:
> [DEBUG] Retrieving parent-POM: com.jaspersoft.jasperserver:server::2.0.0
> for project:
> com.jaspersoft.jasperserver:jasperserver-export-tool-package:jar:2.0.0
> from the repository.
> [WARNING] POM for
> 'com.jaspersoft.jasperserver:jasperserver-export-tool-package:pom:2.0.0:compile'
> is invalid. It will be ignored for artifact resolution. Reason: Failed to
> validate POM for project
> com.jaspersoft.jasperserver:jasperserver-export-tool-package at Artifact
> [com.jaspersoft.jasperserver:jasperserver-export-tool-package:pom:2.0.0:compile]
> [DEBUG] Reason: Failed to validate POM for project
> com.jaspersoft.jasperserver:jasperserver-export-tool-package at Artifact
> [com.jaspersoft.jasperserver:jasperserver-export-tool-package:pom:2.0.0:compile]
> [DEBUG]
> Validation Errors:
> [DEBUG] 'dependencies.dependency.artifactId' with value
> '${repository.database.driver.artifactId}' does not match a valid id
> pattern.
> [DEBUG] 'dependencies.dependency.groupId' with value
> '${repository.database.driver.groupId}' does not match a valid id
> pattern.
> [DEBUG]
> Even if I setup my settings to contain the 3 expression values, they are NOT
> applied to the dependency. If I check the effective POM for my project,
> those settings are seen so I know I have set it up appropriately.
--
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
