Please use the Apache issue tracking system for new NetBeans issues (https://issues.apache.org/jira/projects/NETBEANS0/issues) !!
Bug 198295 - updates.xml not created for single/standalone nbm
updates.xml not created for single/standalone nbm
Status: RESOLVED INVALID
Product: apisupport
Classification: Unclassified
Component: Harness
7.0
PC Windows XP
: P3 (vote)
: TBD
Assigned To: Jesse Glick
issues@apisupport
:
Depends on:
Blocks: 179047
  Show dependency treegraph
 
Reported: 2011-05-03 22:04 UTC by err
Modified: 2011-05-11 19:41 UTC (History)
0 users

See Also:
Issue Type: DEFECT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description err 2011-05-03 22:04:25 UTC
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
Comment 1 err 2011-05-04 13:32:10 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.
Comment 2 err 2011-05-04 14:30:17 UTC
BTW, requires two modules in a module suite to get uipdates.xml created.
Comment 3 Jesse Glick 2011-05-05 21:40:40 UTC
(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.
Comment 4 err 2011-05-06 03:52:47 UTC
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.
Comment 5 Jesse Glick 2011-05-06 11:42:12 UTC
(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.
Comment 6 err 2011-05-06 14:01:43 UTC
> > 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.
Comment 7 err 2011-05-06 17:23:53 UTC
A srcgrep turned up 
    ./org/netbeans/nbbuild/package.html:<dt><a href="MakeUpdateDesc.html">
    <code>&lt;makeupdatedesc&gt;</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)
Comment 8 Jesse Glick 2011-05-09 15:10:16 UTC
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.
Comment 9 err 2011-05-09 16:30:40 UTC
> 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>
Comment 10 Quality Engineering 2011-05-11 19:41:54 UTC
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.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo