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
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
