Community
Participate
Working Groups
What about babel translations, JWT's are not listed in http://download.eclipse.org/technology/babel/babel_language_packs/R0.9.1/indigo/indigo.php ?? Should anything be done at yearly release level ?
See also https://bugs.eclipse.org/bugs/show_bug.cgi?id=257578 & others
added jwt update site (still 1.1.0 build) to http://babel.eclipse.org/babel/map_files.php
As we discussed during the meeting, I checked my instance of Eclipse.
So, I was saying (hmf): As we discussed during the meeting, I checked my instance of Eclipse. Everything is currently in English, including JWT, simply because one need to install a Babel plugin relating to JWT in order to translate it; this is perfectly normal. The next step would probably be to find a way to get our hands on the old translations and add them for the next release? The most recent translation I could find were intended to JWT 0.0, when it was still part of the Technology project. (see http://download.eclipse.org/technology/babel/babel_language_packs/R0.9.1/galileo/galileo.php)
So, to be clear, the process of adding a project to Babel is described here: http://wiki.eclipse.org/Babel/FAQ#Committers_FAQ I just checked the status of JWT 1.2 regarding Babel, and it seems the 1.2.0 update site was registered too (by Christian, I guess?): http://babel.eclipse.org/babel/map_files.php . So now, every *.properties files should be detected by Babel and added to the translation UI: http://babel.eclipse.org/babel/translate.php . But they are not. JWT does not even appear in the UI, as well as all other SOA subprojects (soa.swordfish 0.10.0, for instance, does not appear in the UI even though it defines some map files with valid links). I went through the babel-dev mailing list archives and found this: http://dev.eclipse.org/mhonarc/lists/babel-dev/msg00869.html, which basically tells us that the versions appearing in Babel are those defined in Bugzilla, and that it's updated several times a day. I don't know when the 1.2.0 update site was added to Babel, so I'll check this tomorrow. If JWT still doesn't show up in the translation UI, our problem might be related to the version definition in Bugzilla... ?
I posted a message on the babel-dev mailing list (http://dev.eclipse.org/mhonarc/lists/babel-dev/msg00963.html), and it appears their server is experiencing some troubles. They're working on it, so wait and see :)
Updated the release process to include some Babel-related actions: http://wiki.eclipse.org/JWT_DeveloperFAQ#Releasing_JWT_and_the_corresponding_plugins_.28e.g._the_Workflow_Editor.29
This bug is not dead and forgotten (yet ;)). Denis Roy had answered to my message to the mailing list, saying he would investigate (http://dev.eclipse.org/mhonarc/lists/babel-dev/msg00964.html). I'm trying to get some information about the current status of this investigation (http://dev.eclipse.org/mhonarc/lists/babel-dev/msg00971.html).
Well. It seems the problem may stem from JWT after all; according to Kit Lo, Babel doesn't support compressed pack.gz jars, but only plain jars at the moment (http://dev.eclipse.org/mhonarc/lists/babel-dev/msg00972.html). It seems the easiest, quickest fix would be to store plain jars along with compressed ones on the update site, still according to Kit Lo. Christian, what's your opinion? * Would it be easy? * Would it make the compressed jars completely useless? I.e., would p2 still download only the compressed jars?
It's probably possible in one way or another, I guess we have to configure the build process accordingly. Before the next release we should decide if we want to move to another method such as Maven Tycho anyway.
Ok then, we'll see that when dealing with Tycho. Is there any bug report about that? I could not find one.
According to Marc, there was no bug report about moving to another build method, so I created bug 383409, which blocks this one.
