Hi

agreed, I noticed that. 

Is it possible for the project to configure to run the plugin
in a later phase, if the project knows it will generate 
sources at a later phase. If so, how?

Regards
Mark Donszelmann
 

> -----Original Message-----
> From: John Casey [mailto:[EMAIL PROTECTED] 
> Sent: Thursday, December 01, 2005 7:31 AM
> To: Maven Developers List
> Subject: Re: [m2] Does the eclipse plugin support ...
> 
> I guess the basic problem with #2 below is where to 
> stop...any mojo binding in any phase could add to the compile 
> sourceroots or test compile sourceroots...and the later we 
> push this into the lifecycle, the greater the chances that 
> we'll have the condition where you cannot generate the 
> bindings for your project in Eclipse because the project 
> won't build...but it's hard to fix the project, because you 
> have to build the Eclipse project up by hand! :)
> 
> That said, probably pushing it to the process-sources or 
> process-resources (forgetting which runs last right now, or 
> if they are both before compile) would be a reasonable step.
> 
> Donszelmann, Mark wrote:
> > Hi
> > 
> > I have 2 questions regarding the eclipse plugin 
> (2.0-beta-3-SNAPSHOT from svn):
> > 
> > 1. Does the eclipse plugin support source file excludes.
> > My pom contains:
> > 
> >       <plugin>
> >         <artifactId>maven-compiler-plugin</artifactId>
> >         <configuration>
> >           <excludes>
> >             <exclude>**/*Factory.java</exclude>
> >           </excludes>
> >         </configuration>
> >       </plugin>
> > 
> > for which I would expect in the .classpath:
> > 
> >   <classpathentry excluding="**/*Factory.java" 
> > output=".deployables/..." kind="src" path="src/main/java"/>
> > 
> > but I get:
> > 
> >   <classpathentry kind="src" path="src/main/java"/>
> > 
> > should I file a JIRA issue?
> > 
> > 
> > 2. As far as I understand, the eclipse:eclipse "goal" runs 
> as part of the generate-sources "phase".
> > I guess it thereby pick up paths created by other plugins 
> as additions to the compileSourceRoot. 
> > One of my plugins filters sources and does this as part of the 
> > process-sources phase. It adds a path to compileSourceRoot 
> which is ignored by the eclipse plugin.
> > 
> > Should one not run the eclipse goal as part of the 
> process-resources 
> > phase (just before compile), when all paths are in order?
> > 
> > If so, shall I file a JIRA issue?
> > 
> > Regards
> > Mark Donszelmann
> > 
> > 
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED] For 
> > additional commands, e-mail: [EMAIL PROTECTED]
> > 
> > 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED] For 
> additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to