Does anyone know how to properly set up Eclipse classpath variables for a team that uses different JBoss versions, so that the .classpath file can be shared over source control?
More specifically, some team members use the Eclipse JBoss Tools Plugin and some do not.
So, the .classpath files have the following conflict:
<classpathentry kind="con" path="org.eclipse.jst.server.core.container/org.jboss.ide.eclipse.as.core.server.runtime.runtimeTarget/JBoss 5.1 Runtime"/>
<classpathentry kind="con" path="org.eclipse.jst.server.core.container/org.eclipse.jst.server.generic.runtimeTarget/JBoss v5.0"/>
Does anyone know how to fix this without just asking everyone to install JBoss Tools?
For such cases, e.g. I use different JBoss versions for the same project, I set a variable.
All entries for libraries can use the variable as base.
See 'build path' -> 'Add Variable'
and in this dialog you can extend the variable for each library.
To switch you only have to set the variable. Unfortunatly this will only possible for similar structure of JBoss.
I tried that but I cannot find the correct JBoss path in my file structure anywhere.
My eclipse is installed in C:\eclipse
I cannot find:
org.eclipse.jst.server.core.container/org.jboss.ide.eclipse.as.core.server.runtime.runtimeTarget/JBoss 5.1 Runtime
Is there some kind of trick to finding these?
You are trying to compile against a server runtime that needs a server installation associated with it.
Life will be complicated if you try and stick to this strategy. You are better off arranging things so that everyone is building against the same JEE APIs. Jars for these are available in many places including the Maven central repository.