Hi all
I have a small issue. I'm building some Eclipse plugins but the PDE environment build fails so I'm now writing a maven to fix the problem. To acheive the build, I need to reference some external directories in the classpath when I compile. Is there a way to do this using jelly code in a maven.xml?
I manage to make this work by making a small change in the java plugin to support this, added a property that becomes a path element so we can add paths to the cp of the java compiler but if its not already in there.. it must be for a reason.
But, by checking the jelly/java code of the plugin and from maven, it occured to me that this could be resolved by defining a new type of dependency, a path dependency. Does this make sense? If not, what would be the more maven-friendly way to go in those cases? Of course the classes could be packaged in a jar (they are in fact later on but inside another jar...) but since the jar holding the code is not the deliverable, it seems way overkill to jar it, deploy it so that it could be refered as a dependency.
In some other projects, I've combine the target/classes directory to overcome but in this perticular case, I cannot use this approach.
Any suggestions / comments?
Eric.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
