You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Arnaud Heritier (JIRA)" <ji...@codehaus.org> on 2008/07/21 23:56:26 UTC
[jira] Created: (MECLIPSE-469) CLONE -mark contents of "target"
directory as derived
CLONE -mark contents of "target" directory as derived
-----------------------------------------------------
Key: MECLIPSE-469
URL: http://jira.codehaus.org/browse/MECLIPSE-469
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Affects Versions: 2.2
Reporter: Andreas Schildbach
Fix For: 2.2
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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MECLIPSE-469) CLONE -mark contents of "target"
directory as derived
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier closed MECLIPSE-469.
------------------------------------
Resolution: Won't Fix
I didn't find how to fix it. If someone know how to do. After searching a little bit, fhis setting isn't stored in project configuration files. It seems to be somewhere in the workspace and it can be set only from eclipse APIs. It's to difficult to add. You can have a look at m2eclipse and q4e which handles it.
> CLONE -mark contents of "target" directory as derived
> -----------------------------------------------------
>
> Key: MECLIPSE-469
> URL: http://jira.codehaus.org/browse/MECLIPSE-469
> 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MECLIPSE-469) CLONE -mark contents of
"target" directory as derived
Posted by "Morten Hattesen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=173150#action_173150 ]
Morten Hattesen edited comment on MECLIPSE-469 at 4/16/09 7:45 AM:
-------------------------------------------------------------------
Another consequence of not having the target folder marked as derived, is that you eaily risk committing the target folder to a repository (cvs/svn). If the target folder is marked as "derived", cvs and svn plugins will ignore the resource, and not offer to add/commit the resource.
If you create a new project using [New/Project.../New Maven project] then run a maven build, and/or [Maven/Update Project Configuration], and then [Team/Add to version control/Commit...] then the target folder will be committed to the repository (possibly along with classes/resources) - not a desirable situation!
The only workaround currently, is to remember to mark the target folder "Team/Add to svn:ignore" (using SubClipse), before committing.
was (Author: mortenhattesen):
Another consequence of not having the target folder marked as derived, is that you eaily risk committing the target folder to a repository (cvs/svn). If the target folder is marked as "derived", cvs and svn plugins will ignore the resource, and not offer to add/commit the resource.
If you create a new project using [New/Project.../New Maven project] then run a maven build, and/or [Maven/Update Project Configuration], and then [Team/Add to version control/Commit...] then the target folder will be committed to the repository (possibly along with classes/resources) - not a desirable situation!
> CLONE -mark contents of "target" directory as derived
> -----------------------------------------------------
>
> Key: MECLIPSE-469
> URL: http://jira.codehaus.org/browse/MECLIPSE-469
> 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MECLIPSE-469) CLONE -mark contents of "target"
directory as derived
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MECLIPSE-469:
-------------------------------------
Fix Version/s: (was: 2.2)
> CLONE -mark contents of "target" directory as derived
> -----------------------------------------------------
>
> Key: MECLIPSE-469
> URL: http://jira.codehaus.org/browse/MECLIPSE-469
> 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-469) CLONE -mark contents of "target"
directory as derived
Posted by "Morten Hattesen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=173150#action_173150 ]
Morten Hattesen commented on MECLIPSE-469:
------------------------------------------
Another consequence of not having the target folder marked as derived, is that you eaily risk committing the target folder to a repository (cvs/svn). If the target folder is marked as "derived", cvs and svn plugins will ignore the resource, and not offer to add/commit the resource.
If you create a new project using [New/Project.../New Maven project] then run a maven build, and/or [Maven/Update Project Configuration], and then [Team/Add to version control/Commit...] then the target folder will be committed to the repository (possibly along with classes/resources) - not a desirable situation!
> CLONE -mark contents of "target" directory as derived
> -----------------------------------------------------
>
> Key: MECLIPSE-469
> URL: http://jira.codehaus.org/browse/MECLIPSE-469
> 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MECLIPSE-469) CLONE -mark contents of
"target" directory as derived
Posted by "Morten Hattesen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=173150#action_173150 ]
Morten Hattesen edited comment on MECLIPSE-469 at 4/16/09 7:46 AM:
-------------------------------------------------------------------
Another consequence of not having the target folder marked as derived, is that you eaily risk committing the target folder to a repository (cvs/svn). If the target folder is marked as "derived", cvs and svn plugins will ignore the resource, and not offer to add/commit the resource.
If you create a new project using [New/Project.../New Maven project] then run a maven build, and/or [Maven/Update Project Configuration], and then [Team/Add to version control/Commit...] then the target folder will be committed to the repository (possibly along with classes/resources) - not a desirable situation!
The only workaround currently, is to remember to tell the SCM to ignore the target folder (SubClipse: mark the target folder "Team/Add to svn:ignore"), before committing.
was (Author: mortenhattesen):
Another consequence of not having the target folder marked as derived, is that you eaily risk committing the target folder to a repository (cvs/svn). If the target folder is marked as "derived", cvs and svn plugins will ignore the resource, and not offer to add/commit the resource.
If you create a new project using [New/Project.../New Maven project] then run a maven build, and/or [Maven/Update Project Configuration], and then [Team/Add to version control/Commit...] then the target folder will be committed to the repository (possibly along with classes/resources) - not a desirable situation!
The only workaround currently, is to remember to mark the target folder "Team/Add to svn:ignore" (using SubClipse), before committing.
> CLONE -mark contents of "target" directory as derived
> -----------------------------------------------------
>
> Key: MECLIPSE-469
> URL: http://jira.codehaus.org/browse/MECLIPSE-469
> 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-469) CLONE -mark contents of "target"
directory as derived
Posted by "Vladimir Nicolici (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=182284#action_182284 ]
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:
http://www.pushing-pixels.org/?p=847
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: http://jira.codehaus.org/browse/MECLIPSE-469
> 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-469) CLONE -mark contents of "target"
directory as derived
Posted by "Nicholas Tung (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=226039#action_226039 ]
Nicholas Tung commented on MECLIPSE-469:
----------------------------------------
please reoopen. many maven targets, like assemble, produce source and class files which are visible by the "open resource" dialog (ctrl+shift+r). The clutter is undesirable, and unfortunately, Eclipse doesn't save derived flags with the project.
> CLONE -mark contents of "target" directory as derived
> -----------------------------------------------------
>
> Key: MECLIPSE-469
> URL: http://jira.codehaus.org/browse/MECLIPSE-469
> 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira