This issue was originally reported by Daniel Mutch in 15/Jul/07 at codehaus.org - see more details at
http://jira.codehaus.org/browse/MEVENIDE-542
Environment: Windows 2000

===========
Description:
===========
Adding the following profile to a pom.xml seems to render the project invalid
<profiles>
<profile>
<id>default-tools.jar</id>
<activation>
<property>
<name>java.vendor</name>
<value>Sun Microsystems Inc.</value>
</property>
</activation>
<dependencies>
<dependency>
<groupId>com.sun</groupId>
<artifactId>tools</artifactId>
<version>1.4.2</version>
<scope>system</scope>
<systemPath>${JAVA_1_4_HOME}/lib/tools.jar</systemPath>
</dependency>
</dependencies>
</profile>
</profiles>
It appears to be the dependencies. Commenting them out solves the problem.

----------------------------------------------
Comment by Daniel Mutch [ 02/Sep/07 07:32 PM ]
----------------------------------------------
By making ${JAVA_1_4_HOME} a system variable the POM loads fine. If however it is defined in a parent project instead
you get invalid project issue.

----------------------------------------------
Comment by Milos Kleint [ 18/Apr/08 07:23 AM ]
----------------------------------------------
the correct way of referencing environment variables is to use the ${env.JAVA_1_4_HOME} pattern.
However while that seems to work for build of the project, the loading of the project fails in this case. I suppose
that's an issue within maven itself. The env.JAVA_1_4_HOME property cannot only be found in the <system> element. When
defined in profile's activation for example, it seems to resolve fine.

----------------------------------------------
Comment by Milos Kleint [ 23/May/08 06:05 AM ]
----------------------------------------------
most probably a maven embedder issue ->3.2