This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | updates.xml not created for single/standalone nbm | ||
---|---|---|---|
Product: | apisupport | Reporter: | err <err> |
Component: | Harness | Assignee: | Jesse Glick <jglick> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | 7.0 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 179047 |
Description
err
2011-05-03 22:04:25 UTC
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 ./org/netbeans/nbbuild/package.html:<dt><a href="MakeUpdateDesc.html"> <code><makeupdatedesc></code></a></dt> 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"> <makeupdatedesc desc="${build.dir}/updates.xml" distbase="." automaticgrouping="false" uselicenseurl="true"> <fileset dir="${build.dir}"> <include name="*.nbm"/> </fileset> </makeupdatedesc> </target> Integrated into 'main-golden', will be available in build *201105111436* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/b9ce30f4250a User: Jesse Glick <jglick@netbeans.org> Log: Nonexistent target. See bug #198295 comment #7. |