new "configuration" phase ? (was: xdoclet plugin makes eclipse:eclipse fail)

[nicolas de loof <ni...@gmail.com>]

I solved this by setting xdoclet to run under process-resources phase and
not generate-resource, as the eclispe:eclispe goal is attached to it.

Is there some plan to add native support in maven for environment
configuration, without any requirement for a build phase ?
Why should the eclispe plugin handle generation (or copy from a POM CDATA)
of the ".checkstyle" ? Cannot the checkstyle plugin generate it from maven
configuration ?

What about a "configure" phase for configuring the developer environment ?
Every maven plugin could handle the target environment if it also has
support as a IDE plugin.

example :

<profille>
   <id>eclipse</id>
   <plugins>
      <plugin>
          <artifactId>maven-eclipse-plugin</artifactId>
          <execution>
             <phase>configure</phase>
             <goal>eclipse<goal>
          </execution>
      </plugin>
      <plugin>
          <artifactId>maven-checkstyle-plugin</artifactId>
          <execution>
             <phase>configure</phase>
             <goal>eclipse<goal>
          </execution>
      </plugin>
   </plugins>
<profille>





2007/1/26, nicolas de loof <ni...@gmail.com>:
>
> Hello,
>
> I'm using the xdoclet plugin in maven2 for jspdoclets.
> My webapp depends on another module (persistence).
>
> When the xdoclet plugin is commented, maven eclipse:eclipse works fine.
> When the xdoclet plugin used, maven eclipse:eclipse requires the
> persistence.jar to be in repository.
>
> A new  developer on the project has to build the persitence artifact
> before beeing able to configure eclipse. As there may be bugs in the current
> CVS, he cannot get the project in eclipse and solve any issue !
>
> Is this a known limitation ?
>