Maven 2.1.0 pax:eclipse creates ${project.basedir} directory
-------------------------------------------------------------
Key: PAXCONSTRUCT-111
URL: http://issues.ops4j.org/browse/PAXCONSTRUCT-111
Project: Pax Construct
Issue Type: Bug
Components: maven-pax-plugin
Affects Versions: 1.4
Environment: Windows Vista sp1, java full version "1.5.0_18-b02"
Reporter: Gordon Dickens
Assignee: Stuart McCulloch
There appears to be an incompatibility between maven 2.1 and Pax Plugin 1.4.
When would build mvn clean pax:eclipse it would generate a directory
${project.basedir} and put target files there.
The Maven 2.1 documentation alludes to this
http://maven.apache.org/guides/introduction/introduction-to-the-pom.html
"Project Model Variables
Any field of the model that is a single value element can be referenced as a
variable. For example, ${project.groupId}, ${project.version},
${project.build.sourceDirectory} and so on. Refer to the POM reference to see a
full list of properties.
These variables are all referenced by the prefix "project.". You may also see
references with pom. as the prefix, or the prefix omitted entirely - these
forms are now deprecated and should not be used."
I reverted to Maven 2.0.10 and it built without creating the erroneous
directory.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
