Matthew Pryor wrote:
<side-note>
I suppose I could go down the path of trying to treat the
Eclipse specific stuff as real dependencies and create artifacts for them
and write a custom artifact handler that could read them from the Eclipse
plugins folder, but I think that would be a lot of code and not be that much
better than simply adding the jar files to the classpath before calling the
AbstractCompilerMojo - private API issues aside
</side-note>
I think that your approach is valid. Its only disadvantage is that a
"normal" (ie non eclipse plugin) maven project cannot use an eclipse
plugin as a dependency, but it's a very marginal use case. One could
extract the needed code to an utilty library project and depend on that.
If it saves you coding/testing effort, I would say go for it.
It's nice to hear that you are working on Maven 2 plugin for building
eclipse specific artifacts. I think this funcitonality is missing from
Maven 1 ecosystem.
I always felt that maven-eclipse-plugin should be a Maven plugin for
building Eclipse plugins, features etc. and integrating Maven into
Eclipse IDE should be done by writing a proper eclipse plugin (MavenIDE
way), and not tinkering with Eclipse config files from a maven plugin.
Too much to do, to little time....
Rafal
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
