Its not just a jar, so it actually can not be needed for compilation:

[504][valkyrie: trunk]$ jar -tf /home/svn/repository.jboss.org/maven2/jboss/jbossts/jbossts-tools/4.6.1.GA/jbossts-tools-4.6.1.GA.sar
META-INF/
META-INF/MANIFEST.MF
META-INF/jboss-beans.xml
embedded-tools.jar
toolsframework.xml
tools/
tools/plugins/
tools/plugins/osbv-defaults.jar
tools/tsmx-objectstorebrowser.jar
tsmx-tools.jar

Its only being included in the build distribution as an example:

[612][valkyrie: bin]$ find .. -name 'jbossts-tools*'
../docs/examples/transactions/jbossts-tools.sar

so we need to clean up the dependency on this to only be relevant to the packaging phase or something. Can that be done Paul?

Max Rydahl Andersen wrote:

Question: Are those .sar *really* treatable as .jar's ?

If yes, then I would consider pushing on JDT to not care about the postfix (assuming that javac works with .sar?)

If no and these are purely for JBoss AS understanding, then why are these .sar's even in the classpath ?

/max

_______________________________________________
jboss-development mailing list
jboss-development@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development