I mean that the use of IDE specific properties might be dangerous -- although it appears to be quite useful in this case --, in the long run we will end up in project descriptors, that depend on one specific IDE. I don't think that this would be the idea of Maven.
So, is it possible to modify this hack to use already build in features of Maven, to gain the same effect? And: Is there a policy about how IDE specific the project descriptor is allowed to be?
-Mo.
Am Mittwoch, 02.04.03 um 17:21 Uhr schrieb Diego Fernandez:
Hi, I want to submit a small hack to the eclipse plug-in to allow project references in the generation of the classpath. It works like this: - In the project dependencies add a property "eclipse.project" to the dependency and it will be treated as an eclipse project, for example: <dependencies> <dependency> <groupId>delfos</groupId> <artifactId>delfos-ejb</artifactId> <version>SNAPSHOT</version> <properties> <eclipse.project>true</eclipse.project> </properties> </dependency> </dependencies>
Then the plug-in generates the .classpath like this: <classpathentry kind="src" path="/delfos-ejb" />
This is very useful when you have sub-projects.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
