[ https://issues.jboss.org/browse/JBIDE-10391?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-10391: ------------------------------------- Description: 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). was: We currently create a .gitingore file if there's none so far in the workspace project that shall be "OpenShift enabled". 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

[ https://issues.jboss.org/browse/JBIDE-10391?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-10391. -------------------------------------- Fix Version/s: 3.3.0.Beta1 (was: 3.3.0.Beta2) Resolution: Done committed to TRUNK (Beta1) -- 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

[ https://issues.jboss.org/browse/JBIDE-10391?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-10391 at 3/1/12 9:17 AM: ------------------------------------------------------------------ In most project I was involved (before Red Hat) in, Eclipse specific configuration files were considered as non-project files which were not committed to the source control system. Even more if there were project members that were not working with Eclipse (but intellij, netbeans etc.). The same applies if you consider that the default project, that is created when you create a new openshift application, does not have any eclipse specific files. By adding those configuration files to the gitignore we prevent them from being committed to the OpenShift git repo and keep them local (since they were created when importing the app to the local workspace). Therefore, the current behaviour is a reasonable default to me. The user may still remove those entries from gitignore manually and commit the eclipse files if he wants to. was (Author: adietish): In most project I was involved (before Red Hat), eclipse specific configuration files were considered as non-project files which were not committed to the source control system. Even more if there were project members that were not working with eclipse (but intellij, netbeans etc.). Even more if you consider that the default project, that is created when you create a new openshift application - does not have any eclipse specific files. By adding those eclipse configuration files to the gitignore we prevent them from being committed to the OpenShift git repo, we keep them local since they were created when importing the app to the local workspace. Therefore, the current behaviour is a reasonable default to me. The user may still remove those entries from gitignore manually and commit the eclipse files if he wants to. -- 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

[ https://issues.jboss.org/browse/JBIDE-10391?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-10391 at 3/1/12 9:20 AM: ------------------------------------------------------------------ Even if you'd still think that this is annoying, I consider this as enhancement and we should close this issue if it behaves in the intended way and open a new enhancememt for CR1 was (Author: adietish): Even if you'd still think that this is annoying, I consider this as enhancement and we should move this to CR1 -- 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

[ https://issues.jboss.org/browse/JBIDE-10391?page=com.atlassian.jira.plugi... ] Lucia Jelinkova resolved JBIDE-10391. ------------------------------------- Resolution: Done -- 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

[ https://issues.jboss.org/browse/JBIDE-10391?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-10391: ------------------------------------------ ok, but I still dont really agree. Please file an issue and we'll discuss with the other team members. Ant, in my opinion is a different story since it's not IDE specific. Any dev would use ant (or maven for instance), whether he uses Eclipse, IntelliJ, Netbeans or whatever. Furthermore not touching the project is exactly what we're trying to achieve: we prevent git to commit the files that are only related to the current dev and his local setup. -- 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

[ https://issues.jboss.org/browse/JBIDE-10391?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-10391: ------------------------------------------ definitely :) Let us see what the others and Max think about it. Could perfectly be that you're matching the majority. -- 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