Sven,
The plugin version numbers will not cause any problem. The update site info looks good. I added additional plugin exclude patterns to exclude language properties files like "*_de.properties" and "*_de_DE.properties". I also ran the syncup script to pull in any existing translations. Take a look at this file for example:
http://babel.eclipse.org/babel/translate.php?project=soa.stardust&version=1.0&file=org.eclipse.stardust.reporting.oda.jdbc.ui/org/eclipse/stardust/reporting/oda/jdbc/ui/nls/JdbcPluginResources.properties
Regards,
Kit Lo
Eclipse Babel Project Lead
IBM Eclipse SDK (IES) Globalization Technical Lead
IBM Rational solution for Collaborative Lifecycle Management (CLM) Globalization Technical Lead
---05/16/2013 03:52:31 AM---Hi Denis, IMO this was our fault. We haven't set any version numbers in Bugzilla. Now we have caught
From: <Sven.Rottstock@xxxxxxxxxxx>
To: <babel-dev@xxxxxxxxxxx>,
Date: 05/16/2013 03:52 AM
Subject: Re: [babel-dev] "Release Version" dowpdown box shows always "unspecified"
Sent by: babel-dev-bounces@xxxxxxxxxxx
Hi Denis,
IMO this was our fault. We haven’t set any version numbers in Bugzilla. Now we have caught up this and I can see the version in Babel, too. Nevertheless I have another question: in Bugzilla we have the version 1.0 but the bundle version of our plugins are set to 1.0.0.<timestamp>. Is this a problem?
Regards,
Sven
Von: babel-dev-bounces@xxxxxxxxxxx [mailto:babel-dev-bounces@xxxxxxxxxxx] Im Auftrag von Denis Roy
Gesendet: Mittwoch, 15. Mai 2013 15:52
An: babel-dev@xxxxxxxxxxx
Betreff: Re: [babel-dev] "Release Version" dowpdown box shows always "unspecified"
Sven,
This is likely a sync issue between Bugzilla and Babel.
I'm planning on spending some time fixing up a bunch of Babel issues tomorrow; I'll look at this then and get back to you.
Denis
On 05/15/2013 03:54 AM, Sven.Rottstock@xxxxxxxxxxx wrote:
Hi,
yesterday I’ve changed the URL of the update site in the http://babel.eclipse.org/babel/map_files.php form because the release version dropdown box for the project soa.stardust shows only the “unspecified” entry. So I have assumed that the Babel job cannot handle Composite Repositories. Therefore I’ve provided an URL which points directly to an update site (where the features and plugins folders exists). But unfortunately the release version still shows “unspecified”. Have I missed something that needs to be done to include the Stardust project into the Babel project?
Regards,
Sven
_______________________________________________
babel-dev mailing list
babel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/babel-dev
|