When using WebSphere Developer Tools for Eclipse, projects with names such as "WebSphere Application Server Liberty Profile" are added to the workspace. They contain a section of usrmy Liberty installation, so they contain things like ESA extensions, files server.xml, common JAR files, etc.
It seems that it would be nice if this project was stored in SCM so that my team would have exactly the same Liberty server.xml, extensions, and common dependencies. Is that a good idea?
If this is a good idea, my further questions are:
- Is Liberty installation required to refer to what will be a new copy of the folder
usrinside the workspace, and not inside the Liberty installation directory? - What should be added to my SCM ignore file for this project or should everything be checked?
If this is not a good idea, my next question is:
- how should we share this type of configuration within the team to avoid customization? The goal is to be able to get the source code from SCM and immediately get it in Eclipse, building X without red errors.
source
share