Accepting.

I'm one of the owners of translatedfiles module,
and since my module has nothing to do with the code - it's 
only the l10n of the IDE,
I want my module distributed via AutoUpdate.

I already made a build.xml file, which can create nbm,
so this is your task now to help me distribute it to the 
public.

I prepared testing Update centre on URL
http://www.netbeans.org/updates/alpha/dev_alpha_daily.xml

Add this URL into your IDE by menu "Tool | Options..." and then select
"IDE Configuration | System | Autoupdate Type". Click right button and
select "New | NetBeans Update Center".
Name the new Update Center i.e. "NetBeans Alpha Update Centre - DAILY
(test)" and click on "Finish" button. Select the newly added Update
Centre and paste the URL above to Server URL property in the
properties tab. Now click on "Close" button and from menu select
"Tools | Update Center...". Make sure you newly added Update Centre is
the only one with checked checkbox in left column. Check your "Proxy
Configuration" and then click on "Next" button.

Due bugs in build.xml files a few modules are not downloadable
(xml/jaxp/xalan/schem2beans). I will fix their build.xml files in a
few days.

Please be patient and take it as it is in test-mode.

Well, when we see the core.nmb and openide.nbm 's?

Rudolf, thats for the initiative, if it's not too 
difficult, please post here the progress of this issue

Something went wrong
Below the contents of 
http://www.netbeans.org/updates/alpha/dev_alpha_daily.xml

AU says "unable to connect..."

<?xml version='1.0'?>

<!DOCTYPE module_updates [
    <!ENTITY include0 SYSTEM "dev_alpha_release.ent">
    <!ENTITY include1 SYSTEM "dev_alpha_daily.ent">
]>

<module_updates timestamp="00/00/01/05/06/2002">
    &include0;
    &include1;
</module_updates>

Maxym,
it seem to be related to issue 24351. I will fix the catalog
generating routine.

Rudolf, please include translatedfiles into the build,
I tested, nbm and jars tasks work.

Now, after 3.4 branch, we can go on. Ruda, will you change the
infrastructure to upload files to real Alpha Center?

Btw. I have build the ide with "ant -Dmodules=autoupdate" and tried to
update some modules and it seems that for example Java Source Support
could not be located...

Set target milestone to TBD

Rudolf, I see the French L10N, but no Russian L10N on the 
NetBeans DAILY (test) Autoupdate center.

Large excuse, everybody, it is there, but since I do have 
one, and didn't update Specification Version ;), it 
doesn't show up.

But none of Localizations seems to be found:

GET 
http://www.netbeans.org/nbms/alpha/dev/russian_l10n.nbm 

HTTP/1.1 404 Not Found
Date: Tue, 30 Jul 2002 08:46:54 GMT
Server: Apache/1.3.26 (Unix) ApacheJServ/1.1.2
HelmLoginID: guest

Maxym, I'll regenerate the catalog with proper URLs.

Done. Regenerated catalog seems to be fixed.

Verified, thanks.

Ruda, could you please modify the build process for our current dev
version to upload the NBMs to standard alpha update center?

Dev Alpha Update Centre was modified to include also catalog from Dev
Daily Alpha Update Centre. URLs was not modified.

That's a little weird because now the Alpha server has e.g.
web/taglibed in both 1.6.1 and 1.7 versions! How is a user supposed to
distinguish them?

Either remove the 1.6.1 version or fix autoupdate client to show just
the newest if more than one version of module is available.

If I understand correctly Alpha AU for 3.4 shows releases for 3.4 and
also trunk releases created automatically now by incrementing spec no.
I am not convinced that it is OK that version created for branch and
trunk are merged here. 

I don't think that autoupdate client should "to show just
the newest if more than one version of module is available".
User can see specification number in AU wizard.

Maybe there should be rather new special Update Center for daily build
nbm's.

Re. showing only the newest NBM when there are older ones too: IMHO
the AU client should show only the newest, *but* it should be smarter
than it is about dependencies. If the newer NBM requires a version of
openide (for example) that you don't have and can't get, only the
older NBM that you can actually use should be shown.

Re. new update center for daily NBMs: perhaps. Remember though that
the "daily NBMs" are not really daily, because they are only published
when the spec version is incremented: a conscious decision by the
module maintainer, similar to asking to have a new alpha version
published. So I don't think keeping them on the alpha server is wrong.

To Radim: if I understand correctly, the problem is only on the Dev
Alpha server. Here you have explicitly published the r34 version of
the NBM, which is the problem I think. The "daily alpha" dev version
is enough.

Rudolf, several questions:
1. How often is Daily built done?
2. If my module cannot be built for some reason, where can 
I, as a module owner, see the error message?

I'm asking this because I've updated russian_l10n module's 
spec to 0.1.2 on 2002/07/30 18:02:05 and on the Alpha & 
DevAlpha I can see only 0.1.1.

Maxym,

ad1) daily build (including NBM build) is run every business day -
Monday to Friday

ad2) actually the build log is not being published, but could be

We had two major changes in build system, one progressive (build
failure skipping) and one which I feel regressive/troublemaking (Ant
1.4.1).

Behavior of daily alpha update should dramatically improve after
recent change in build system which allows Ant to skip unbuildable
modules. Also recent important change in script which changes Update
Centre catalog will improve the reliability. Actually I'm doing last
changes to improve it's stability so it should become really daily
build and NBM package should be available with every build.

If there will be no more issues regarding this issue, I plan to
resolve this issue as FIXED by Friday Sep 6.

Fixed