Community
Participate
Working Groups
I tend to use descriptive class names and on large projects I wind up nesting packages quite deep. This problem arose for me when I used nested classes (82-character package path, 53-character class name, 59-character inner class name) but a simple test using a ridiculously long package path and a simple class showed the problem too. When I 'Export...' my plug-in with 'Deployable plug-ins and fragments', the JAR file excludes .class files with very long paths. Personnally, I can live with this (now I know to avoid it) but the problem happens without any warning so it's likely to cause problems for people who don't know about the issue. Jeff
Unfortunately there is nothing much we can do about that, since no errors are warnings are being raised. The only recommendation is to run automated build from a short path. I will make sure there is a readme for that issue.
It seems strange that there isn't an error or warning somewhere down the line that could be bubbled up to users. It's good to make the issue know though because it's certain to bite people from time to time. Thanks :-)
The entry has been provided to Mike and Jim.
