-
1. Re: Sharing Eclipse classpath with the team using different JBoss versions
wdfink Apr 26, 2012 5:00 AM (in response to onlywei)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.
-
2. Re: Sharing Eclipse classpath with the team using different JBoss versions
onlywei Apr 26, 2012 10:43 AM (in response to wdfink)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.eclipse.jst.server.generic.runtimeTarget/JBoss v5.0
nor
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?
-
3. Re: Sharing Eclipse classpath with the team using different JBoss versions
wdfink Apr 26, 2012 2:45 PM (in response to onlywei)I don't know what classes that are.
I use my local JBoss installation, e.g. /JBoss/5.1.1/, to set the variable.
Suppose that this are some classes of a plugin ?!
-
4. Re: Sharing Eclipse classpath with the team using different JBoss versions
sfcoy Apr 27, 2012 9:59 AM (in response to onlywei)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.
In particular, it is nearly impossible to have a repeatable build process with an IDE. Many people use Apache Maven for this in conjunction with the m2eclipse plugin.