Community
Participate
Working Groups
I've registered the Object Teams plug-ins to babel by specifying our p2 update site. Our plug-ins are correctly picked up but inside the translation fragments all property files are stored in the fragment's root directory. Thus all files that are search in any subdirectories will not be found. Note, that I was happy about the option to specify a p2 update site rather than a map file, because Object Teams sits in an SVN repository for which map-files don't seem to be standardized, meaning: I would be surprised if announcing our map file to babel would actually work.
Hi Stephan, as long as the Babel plugin fragments specify the correct Fragment-Host in the plugin manifest files, I think Eclipse will be able to load the plugin fragments properly. Can you provide a picture of what you expect to see?
Created attachment 195234 [details] current (wrong) structure (In reply to comment #1) > Hi Stephan, as long as the Babel plugin fragments specify the correct > Fragment-Host in the plugin manifest files, I think Eclipse will be able to > load the plugin fragments properly. Loading the fragment isn't the problem, finding the property files inside the fragment is. > Can you provide a picture of what you expect to see? The screenshot attached to this comment shows what I currently see for one of our plugins.
Created attachment 195235 [details] original structure This is how property files sit in our directory structure. The same structure must be re-created in the translation fragment, I believe.
Created attachment 195237 [details] property files in our binary plugin Here's a better picture, taken from the actual content of a plug-in jar file. Just ignore any other files except for *.properties. (The previous picture showed a bogus toplevel directory and "src", both not relevant when building the jars).
I see the problem now. We do create the directory structure for plugins from map files. There must be a bug on the update site side. I will take a look.
Most plugin source files in CVS are organized in source folders like "src", "src_ant", and "Ant Editor". For example: "org.eclipse.ant.ui/Ant Editor/org/eclipse/ant/internal/ui/dtd/AntDTDMessages.properties" Babel NL pack generator has a regular expression to mask out the optional source folder name in the file path. In some situations, the regular expression couldn't match the pattern and removed the folder structure in the jar instead. I added logics to test for patterns like this. Please verify the new language packs at: http://build.eclipse.org/technology/babel/babel_language_packs/N20110613-0400/indigo.php
I tried the packs for Object Teams and they look good now. Thanks!
Verified, closing.
