[ 
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

        

Reply via email to