[
https://issues.apache.org/jira/browse/NPANDAY-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed NPANDAY-395.
--------------------------------
Resolution: Duplicate
Assignee: Brett Porter
this is a duplicate of NPANDAY-98. The main cause is due to the RDF store in
use that duplicates Maven functionality, but does it imperfectly. It is planned
to be removed.
> Support referencing of maven properties in pom.xml
> --------------------------------------------------
>
> Key: NPANDAY-395
> URL: https://issues.apache.org/jira/browse/NPANDAY-395
> Project: NPanday
> Issue Type: Improvement
> Components: Maven Plugins
> Affects Versions: 1.3.1-incubating
> Environment: Windows XP, Maven 2.2.1, java 1.6
> Reporter: Khai Do
> Assignee: Brett Porter
> Labels: properties
> Attachments: pom.xml
>
>
> I have a .NET multi module project. I'm using the npanday plugin to build
> the project and it seems to be working ok. However I can't reference maven
> properties from within my pom.xml file like I can with java projects. I've
> tried the following variants: ${version}, ${pom.version}, and
> ${project.version}. None of them seem to work. It seems to reference the
> file in the /target folder correctly however it doesn't actually copy the
> library to the /target folder from the local or host repositories before the
> compile phase. Therefore it fails saying that it can't find the file.
> Attached is something similar to my pom.xml
> Dashboard.Client depends on Dashboard.Common, both are set to the same
> version '1.0-SNAPSHOT '. I want to reference groupId and version info in
> Dashboard.Client pom.xml with the ${project.groupId} and ${project.version}
> properties.
> Releases are difficult without being able to reference maven properties in
> the pom.xml
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
