Community
Participate
Working Groups
When using the WTP plugin recently, I get a lot of system errors that the path to files in the plugin is too long - basically if I want to use the WTP plugin, my Eclipse has to be rooted at something like c:\eclipse. This results in a lack of flexibility in using the plugin; for example, our build will try to reference the plugin for compiling, and fail because the path is too long: D:/projects/Main_projectBranch/win32_x86/release/bin/External/java/eclipse/Platform/3.2/eclipse/plugins/org.eclipse.jst.enterprise_ui.feature.source_1.5.0.v200605151622-pEBq_gIyo0MQnRh/src/org.eclipse.jst.j2ee.ejb.annotation.model_1.0.0.v200605041230/schema.... Is there a purpose to all the seemingly random letters and such added to the version? Is it possible to shorten the path down for the files installed by the plugin to avoid these errors?
There is a purpose to them (they are part of the qualification field, based on "contained" plugins ... however, I'm not sure you need _source_ on your compile path? Just executable code? If its for JavaDoc, then ... not sure what you can do. There are several of limitations of using Windows to do builds ... path problems being one of them. A possible solution that sometimes helps, if you are using ANT, is to use elements that just specify the general location of where to get jars for classpath, so you don't have to list them all out in a string.
