maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Barrie Treloar (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MECLIPSE-414) Not beeing @aggregator, eclipse plugin does not require executedProject
Date Fri, 28 Nov 2008 05:56:19 GMT

    [ http://jira.codehaus.org/browse/MECLIPSE-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155709#action_155709
] 

Barrie Treloar commented on MECLIPSE-414:
-----------------------------------------

EclipsePluginIT.testProject11 now fails
as it is missing:

  <classpathentry kind="src" path="target/generated-sources/modello" including="**/*.java"/>

Not sure why moving from executedProject to project should remove generated sources from the
project list.
There is a similar comment in  MECLIPSE-415 about this test.

> Not beeing @aggregator, eclipse plugin does not require executedProject
> -----------------------------------------------------------------------
>
>                 Key: MECLIPSE-414
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-414
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Bug
>    Affects Versions: 2.5
>            Reporter: nicolas de loof
>            Assignee: Barrie Treloar
>             Fix For: 2.6
>
>
> The eclispe plugin uses both ${executedProject} and ${project}. 
> Not beeing an aggregator plugin, ${project} is allways tghe currently executed project,
and the projectDirectory is project.getBasedir().
> Having two attributes for same target makes the plugin harder to understand

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message