maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Nicolici (JIRA)" <>
Subject [jira] Commented: (MECLIPSE-469) CLONE -mark contents of "target" directory as derived
Date Thu, 02 Jul 2009 14:49:22 GMT


Vladimir Nicolici commented on MECLIPSE-469:

I was very surprised to find this bug marked as "won't fix". I can't even vote for it.

If there isn't an easy solution, you should at least notify the Eclipse user that he/she should
set the flag himself/herself, to avoid problems with searches and commits. It took me some
time before I discovered how to set the derived flag from the UI.

For an explanation on how to set this flag with the API, look here:

I also think the flag should set in the project, not in the workspace, but the Eclipse guys
seem to have a different philosophy regarding the nature of the derived flag.

> CLONE -mark contents of "target" directory as derived
> -----------------------------------------------------
>                 Key: MECLIPSE-469
>                 URL:
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2
>            Reporter: Andreas Schildbach
> Eclipse has the notion of "derived resources", which are normally excluded from many
dialogs like the "Open Resource" dialog (Ctrl-Shift-R). Without this marker, all those dialogs
would be cluttered with unrelevant files (which can't be edited anyway because they will be
overwritten on the next build).
> Unfortunately, unlike Eclipse itself, "mvn eclipse:eclipse" does not mark generated files
as derived. A good candidate would be the entire contents of the "target" directory.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message