I'm putting together an update center, starting with modules from a module-suite. I want to add a standalone module to this UC; I discovered that there is no updates.xml generated for the lone module when I create NBMs.
BTW, I decided to throw together a python script to combine updates.xml that I want to include in the UC. Is there a better approach? (of course this assumes there is updates.xml files to work with)
Product Version: NetBeans IDE 7.0 (Build 201104080000)
Java: 1.6.0_23; Java HotSpot(TM) Client VM 19.0-b09
System: Windows XP version 5.1 running on x86; Cp1252; en_US (nb)
Userdir: C:\Documents and Settings\erra\.netbeans\7.0
Took a fresh look and saw the module and manifest tags in Info/info.xml. Looks like I can use that, and set the values for the distribution and downloadsize attributes; also should add the autoload attribute.
I'll look around and see if I can find/invoke the ant targets that the module suite uses.
And for now I can set up some dummy module suites, and hope to just work with udpates.xml.
BTW, requires two modules in a module suite to get uipdates.xml created.
(In reply to comment #0)
> there is no updates.xml generated for the lone module when I create NBMs.
Not sure exactly what that means, but update site generation is a feature of suites, not of modules. If you want an update site for the module, add it to a suite.
> I decided to throw together a python script to combine updates.xml that I
> want to include in the UC. Is there a better approach?
No. Should suffice to more or less do an XML concatenation.
Needing to create a suite *and* populate it with 2 modules is a hassle for working with a single module. Long term the simplest approach might be to hack a module target to create an "updates.xml" file.
Feasible? Any tips before I start digging through harness and friends?
> > throw together a python script to combine updates.xml
> Should suffice to more or less do an XML concatenation.
Getting the license files inline into a catalog was more work than cat'ing the modules. Still pretty simple.
(In reply to comment #4)
> Needing to create a suite *and* populate it with 2 modules
Huh? One module.
> hack a module target to create an "updates.xml" file.
> Feasible? Any tips before I start digging through harness and friends?
This aspect of the build scripts should be self-explanatory.
Regarding UC concatenation, http://wiki.netbeans.org/AggregatingUC may be interesting reading; only a proposal though.
> > Needing to create a suite *and* populate it with 2 modules
> Huh? One module.
You are correct. Not sure what I was looking at.
> Regarding UC concatenation, http://wiki.netbeans.org/AggregatingUC may be
> interesting reading; only a proposal though.
FYI. There's: Bug 106350 - plugin doesn't appear in update center
which I filed some years ago about a plugin portal zip file not showing up in an update center.
A srcgrep turned up
I opened nbbuild project and used the make javadoc target and got
Target "bootstrap-javadoc" does not exist in the project "nbbuild".
BUILD FAILED (total time: 0 seconds)
Javadoc for org.netbeans.nbbuild is not published. You can browse sources, though <makeupdatedesc>'s important parameters are pretty simply; mainly just takes a fileset of *.nbm.
> Javadoc for org.netbeans.nbbuild is not published
Right. I was pointing that out.
> mainly just takes a fileset of *.nbm.
Following works great
<target name="nbm" depends="projectized-common.nbm">
Integrated into 'main-golden', will be available in build *201105111436* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Jesse Glick <firstname.lastname@example.org>
Log: Nonexistent target. See bug #198295 comment #7.