[jbosstools-issues] [JBoss JIRA] (JBIDE-10391) an existing .gitignore should get merged

[Lucia Jelinkova (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-10391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672788#comment-12672788 ] 

Lucia Jelinkova commented on JBIDE-10391:
-----------------------------------------

Yes, it is a good practise not to commit these files, but I've worked on project that has been built by ant with all needed libraries committed in the repository in a lib folder. In that case it made sense to have the .classpath committed into the repository too. 

In my opinion it is different situation to let Openshift create your project with default settings, but when I have my own project I do not want external tools to change my files and settings :-)

I do agree this issue can be closed and I'll prepare a new one. 
                
> an existing .gitignore should get merged
> ----------------------------------------
>
>                 Key: JBIDE-10391
>                 URL: https://issues.jboss.org/browse/JBIDE-10391
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: openshift
>    Affects Versions: 3.3.0.M4
>            Reporter: Andre Dietisheim
>            Assignee: Lucia Jelinkova
>             Fix For: 3.3.0.Beta1
>
>
> In the usecase, where we push an existing workspace project to OpenShift, we create a .gitingore file if there's none so far. If the project already has a .gitingore file, we just leave it alone.
> We should enhance this and just add the missing entries (merge the existing content).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira