Hello,

I'm currently in the process of migrating from m1 to m2 and ran across an
issue in generating my Eclipse configuration.  In m1, I used a postGoal
script to generate extra Eclipse files besides the normal .project and
.classpath.  Specifically, I was generating a .checkstyle file and a
.mymetadata file for the Eclipse Checkstyle plugin and the MyEclipse suite
of plugins respectively.

To accomplish this in m2, I started to write my own mojo but found 2 major
disadvantages:
 1) A lot of the code in maven-eclipse-plugin would need to be rewritten or
at least referenced.
 2) Running "mvn eclipse:eclipse" would only generate the normal set of
eclipse files, not my set.  I'd have to train all developers to type "mvn
eclipse:eclipse myplugin:eclipse" or something to that effect.

Does anyone have any recommendations on how to go about this?  Looking at
the source to maven-eclipse-plugin, it would seem that if the plugin allowed
additional AbstractEclipseResourceWriters to be registered via plugin
configuration, both of my problems above would be solved.  This might lead
to other problems though.

Thanks,
Michael

Reply via email to