babel-dev http://dev.eclipse.org/mhonarc/lists/babel-dev/maillist.html babel-dev en-us Sat, 18 May 2013 22:10:06 GMT Sat, 18 May 2013 22:10:06 GMT http://blogs.law.harvard.edu/tech/rss MHonArc RSS 2.0 RCFile webmaster@eclipse.org (Webmaster) webmaster@eclipse.org (Webmaster) babel-dev http://www.eclipse.org/eclipse.org-common/themes/Phoenix/images/eclipse_home_header.jpg http://dev.eclipse.org/mhonarc/lists/babel-dev/maillist.html Re: [babel-dev] "Release Version" dowpdown box shows always "unspecified" http://dev.eclipse.org/mhonarc/lists/babel-dev/msg01113.html 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 ...

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

Inactive hide details for ---05/16/2013 03:52:31 AM---Hi Denis, IMO this was our fault. We haven't set any version numbers in B---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

GIF image

]]> Sat, 18 May 2013 22:07:46 GMT http://dev.eclipse.org/mhonarc/lists/babel-dev/msg01113.html kitlo@xxxxxxx (Kit Lo) Re: [babel-dev] "Release Version" dowpdown box shows always "unspecified" http://dev.eclipse.org/mhonarc/lists/babel-dev/msg01112.html

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

 

]]> Thu, 16 May 2013 07:50:19 GMT http://dev.eclipse.org/mhonarc/lists/babel-dev/msg01112.html Sven.Rottstock@xxxxxxx (Sven.Rottstock) Re: [babel-dev] "Release Version" dowpdown box shows always "unspecified" http://dev.eclipse.org/mhonarc/lists/babel-dev/msg01111.html 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


]]> Wed, 15 May 2013 13:52:19 GMT http://dev.eclipse.org/mhonarc/lists/babel-dev/msg01111.html denis.roy@xxxxxxx (Denis Roy) [babel-dev] "Release Version" dowpdown box shows always "unspecified" http://dev.eclipse.org/mhonarc/lists/babel-dev/msg01110.html Hi, yesterday I&#8217;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 &#8220;unspecified&#8221; entry. So I have assumed that the Babel job...

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

]]> Wed, 15 May 2013 07:54:51 GMT http://dev.eclipse.org/mhonarc/lists/babel-dev/msg01110.html Sven.Rottstock@xxxxxxx (Sven.Rottstock) Re: [babel-dev] Prepare for Kepler http://dev.eclipse.org/mhonarc/lists/babel-dev/msg01109.html Thank you! :-) Andreas > Not sure if the cron job is running. I manually started the extraction > process. The new Code Recommenders 1.0.4 files are now available for > translation. Thank you! :-) Andreas -- Codetrails UG (haftungsbeschränkt) The knowledge transfer company Robert-Bosch-Str. 7, 64293 Darmstadt Mobile: +49-170-811-3791 http://www.codetrails.com/ Managing Director: Dr. Marcel Bruch Handelsregister: Darmstadt HRB 91940 ]]> Tue, 07 May 2013 07:18:03 GMT http://dev.eclipse.org/mhonarc/lists/babel-dev/msg01109.html andreas.sewe@xxxxxxx (Andreas Sewe) Re: [babel-dev] Prepare for Kepler http://dev.eclipse.org/mhonarc/lists/babel-dev/msg01108.html Not sure if the cron job is running. I manually started the extraction process. The new Code Recommenders 1.0.4 files are now available for translation. Kit Lo Eclipse Babel Project Lead IBM Eclipse SDK (IES) Globalization Technical Lead IBM Rational solu... Not sure if the cron job is running. I manually started the extraction process. The new Code Recommenders 1.0.4 files are now available for translation.

Kit Lo
Eclipse Babel Project Lead
IBM Eclipse SDK (IES) Globalization Technical Lead
IBM Rational solution for Collaborative Lifecycle Management (CLM) Globalization Technical Lead

Inactive hide details for Andreas Sewe ---05/06/2013 03:45:23 AM---Hi, we recently (May 1st) did a new release (1.0.4) of Code Andreas Sewe ---05/06/2013 03:45:23 AM---Hi, we recently (May 1st) did a new release (1.0.4) of Code Recommenders,

From: Andreas Sewe <andreas.sewe@xxxxxxxxxxxxxx>
To: Babel committers mailing list <babel-dev@xxxxxxxxxxx>,
Date: 05/06/2013 03:45 AM
Subject: Re: [babel-dev] Prepare for Kepler
Sent by: babel-dev-bounces@xxxxxxxxxxx



Hi,

we recently (May 1st) did a new release (1.0.4) of Code Recommenders,
which included some new (messages|bundle).properties files:

 org/eclipse/recommenders/completion/rcp/chain/l10n/messages.properties
 org/eclipse/recommenders/completion/rcp/subwords/l10n/messages.properties
 org/eclipse/recommenders/extdoc/rcp/l10n/messages.properties
 org/eclipse/recommenders/rcp/l10n/messages.properties

Unfortunately, these changes haven't yet been picked up by Babel [1]. I
thought there was a nightly synchronization job running. Or do I have to
do something special to make it pick up new releases?

Best wishes,

[1]
http://babel.eclipse.org/babel/translate.php?project=technology.recommenders&version=1.0.0
--
Codetrails UG (haftungsbeschränkt)
The knowledge transfer company

Robert-Bosch-Str. 7, 64293 Darmstadt
Mobile: +49-170-811-3791
http://www.codetrails.com/

Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940
_______________________________________________
babel-dev mailing list
babel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/babel-dev


GIF image

]]> Tue, 07 May 2013 01:18:23 GMT http://dev.eclipse.org/mhonarc/lists/babel-dev/msg01108.html kitlo@xxxxxxx (Kit Lo) Re: [babel-dev] Prepare for Kepler http://dev.eclipse.org/mhonarc/lists/babel-dev/msg01107.html Hi, we recently (May 1st) did a new release (1.0.4) of Code Recommenders, which included some new (messages|bundle).properties files: org/eclipse/recommenders/completion/rcp/chain/l10n/messages.properties org/eclipse/recommenders/completion/rcp/subwords/l1... Hi, we recently (May 1st) did a new release (1.0.4) of Code Recommenders, which included some new (messages|bundle).properties files: org/eclipse/recommenders/completion/rcp/chain/l10n/messages.properties org/eclipse/recommenders/completion/rcp/subwords/l10n/messages.properties org/eclipse/recommenders/extdoc/rcp/l10n/messages.properties org/eclipse/recommenders/rcp/l10n/messages.properties Unfortunately, these changes haven't yet been picked up by Babel [1]. I thought there was a nightly synchronization job running. Or do I have to do something special to make it pick up new releases? Best wishes, [1] http://babel.eclipse.org/babel/translate.php?project=technology.recommenders&version=1.0.0 -- Codetrails UG (haftungsbeschränkt) The knowledge transfer company Robert-Bosch-Str. 7, 64293 Darmstadt Mobile: +49-170-811-3791 http://www.codetrails.com/ Managing Director: Dr. Marcel Bruch Handelsregister: Darmstadt HRB 91940 ]]> Mon, 06 May 2013 07:43:14 GMT http://dev.eclipse.org/mhonarc/lists/babel-dev/msg01107.html andreas.sewe@xxxxxxx (Andreas Sewe) Re: [babel-dev] Prepare for Kepler http://dev.eclipse.org/mhonarc/lists/babel-dev/msg01106.html My apologies -- this is on my todo list. Really :) Denis
On 04/10/2013 11:10 AM, Kit Lo wrote:

transition period trying to switch to extract from the Git repository instead of the old CVS repository. We did not finish switching to the new mechanism yet. We should have the switching over finished very soon. Please stay tuned. We will provide more information in this mailing list soon.


My apologies -- this is on my todo list.  Really  :)

Denis


]]> Tue, 16 Apr 2013 20:04:49 GMT http://dev.eclipse.org/mhonarc/lists/babel-dev/msg01106.html denis.roy@xxxxxxx (Denis Roy) Re: [babel-dev] Prepare for Kepler http://dev.eclipse.org/mhonarc/lists/babel-dev/msg01105.html Kit, I've updated the allowed IP address on download.eclipse.org for Babel's new IP address. Denis
On 04/11/2013 01:32 PM, Kit Lo wrote:
Denis, I noticed that rsync reported "Unknown module 'eclipseFullMirror' rsync error" for the "download.eclipse.org" rsync_host. Could you check if the module is up and running?ector, IT

Kit,

I've updated the allowed IP address on download.eclipse.org for Babel's new IP address.

Denis


]]> Tue, 16 Apr 2013 20:03:58 GMT http://dev.eclipse.org/mhonarc/lists/babel-dev/msg01105.html denis.roy@xxxxxxx (Denis Roy) Re: [babel-dev] Prepare for Kepler http://dev.eclipse.org/mhonarc/lists/babel-dev/msg01104.html Hi, Managing the excludes is no big deal. Nevertheless, I still think includes+excludes is a natural thing to have and has rather simple semantics, which anyone is familiar with from Ant/Maven/etc.: first, apply the includes (e.g., org.eclipse.recommenders... Hi, >> There is no include patterns mechanism, right (something like >> org.eclipse.recommenders.*)? > That's correct. There is no include patterns mechanism. I thought of > adding the function, but we still need the exclude mechanism to exclude > the test plugins for some projects. Also, the user interface to define > what to exclude first, what to include next will be complicated. > Therefore, I decided to make it simple. Just provide the exclude > mechanism, which should be able to do the job. Managing the excludes is no big deal. Nevertheless, I still think includes+excludes is a natural thing to have and has rather simple semantics, which anyone is familiar with from Ant/Maven/etc.: first, apply the includes (e.g., org.eclipse.recommenders.*), then apply the excludes (e.g., build.properties). Best wishes, Andreas -- Codetrails UG (haftungsbeschränkt) The knowledge transfer company Robert-Bosch-Str. 7, 64293 Darmstadt Mobile: +49-170-811-3791 http://www.codetrails.com/ Managing Director: Dr. Marcel Bruch Handelsregister: Darmstadt HRB 91940 ]]> Sun, 14 Apr 2013 16:58:38 GMT http://dev.eclipse.org/mhonarc/lists/babel-dev/msg01104.html andreas.sewe@xxxxxxx (Andreas Sewe)