Why aren't the compile time dependencies, code generators etc in a separate plugin similar to the way the antlr plugin is? That way the project doesn't need to list those jars as dependencies.
You could always add a property to the dependency (like the war and ear plugins do) and use that in your collection process.
:)
First things first. I can't control all the build environments my users will have. With the ability to distinguish the dependency types, I can have my users mark them accordingly and all is well. I am working on my first Maven plugin, so I haven't gotten around to everything else.
Ok. So how do I add a property to the dependency? Is it as simple as just adding my own tag like this?:
<dependecy> <groupId>guiapp-extension</groupId> <artifactId>browser</artifactId> <version>SNAPSHOT</version> <type>runtime</type> </dependency>
and then accessing the information like this?:
${pom.dependency.type}
If so, how do I pull items from the repository and stuff them in my own lib directory--filtering out the items I don't want?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
