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.

Bug 74866 - 5.0u2 harness with nb50 platform generates invalid nbm files
Summary: 5.0u2 harness with nb50 platform generates invalid nbm files
Status: VERIFIED FIXED
Alias: None
Product: apisupport
Classification: Unclassified
Component: Harness (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Jesse Glick
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-11 19:02 UTC by pzajac
Modified: 2007-01-10 13:34 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
info generated by harness u1 (826 bytes, text/xml)
2006-04-13 12:20 UTC, pzajac
Details
info generated by harness u2 (686 bytes, text/xml)
2006-04-13 12:21 UTC, pzajac
Details

Note You need to log in before you can comment on or make changes to this bug.
Description pzajac 2006-04-11 19:02:19 UTC
[200604101800]
I tried to build nbm files for NetBeans 50 platform with default IDE harness.
Installation these nbms in NetBeans 50 fails. After switching harness  to
version from platform the nbm were built correctly.
Comment 1 Jesse Glick 2006-04-12 16:45:29 UTC
Seems to be working fine for me. What problem did you see exactly?
Comment 2 pzajac 2006-04-13 12:17:40 UTC
I cannot try it with fresh userdir (Issue #74993). I compares the nbm files
generated using harness u1 and u2. I found differences in PUBLIC ID of info.xml.
I will attach them.  
Comment 3 pzajac 2006-04-13 12:20:28 UTC
Created attachment 29838 [details]
info generated by harness u1
Comment 4 pzajac 2006-04-13 12:21:09 UTC
Created attachment 29839 [details]
info generated by harness u2
Comment 5 Jesse Glick 2006-04-13 18:33:31 UTC
You mean the DTD changed from 2.3 to 2.4. True, though when I tried it the NBM
was nonetheless installable in 5.0.

I guess we can use the 2.4 DTD only if 'targetcluster' is defined, for better
compatibility. I cannot verify that the fix works because I cannot reproduce the
problem. What specifically happens when you try to use the NBM in 5.0?

Idea: perhaps the installation in 5.0 fails only if you do not have working
internet access from the IDE. org.netbeans.updater.XMLUtil.createAUResolver
returns a local copy of the 2.4 DTD only in dev builds, but the fallback is
always to load the remote system ID. Perhaps AU does not otherwise verify that
it can interpret the version of the Info.xml it is loading, which would be a
lower-priority bug for AU if you want to file it.

The question remains what to do when we have an implicitly defined targetcluster
attr, e.g. because the module is part of an app suite. We can't set the
targetcluster attr if the module is destined for 5.0, but we need to set it if
destined for 6.0. Maybe I can have <makenbm> or some other part of the build
script check the version of AU in the target platform. Same consideration
applies to the catalog DTD used for creating an update center. Tricky.
Comment 6 Jan Lahoda 2006-04-13 18:46:24 UTC
I was probably experiencing this problem too. I think you are correct with the
internet connection: if I tried with internet connect&correct proxy, everything
was OK. If I had no internet connection or incorrect proxy setting, the update
failed.
Comment 7 Jesse Glick 2006-04-13 19:53:01 UTC
OK. Well I have a patch which seems to work. The 2.4 DTD will be used (for
Info.xml as well as catalog files) if the targetcluster attr is needed, else the
2.3 DTD will be used; and the targetcluster attr is defined for named app suites
only if the updater.jar in the target platform in fact seems to know about the
2.4 DTD.
Comment 8 Jesse Glick 2006-04-13 21:09:58 UTC
Checking in ant/build.xml;
/shared/data/ccvs/repository/ant/build.xml,v  <--  build.xml
new revision: 1.114; previous revision: 1.113
done
Checking in ant/docs/build.xml;
/shared/data/ccvs/repository/ant/docs/build.xml,v  <--  build.xml
new revision: 1.22; previous revision: 1.21
done
Checking in apisupport/harness/release/suite.xml;
/shared/data/ccvs/repository/apisupport/harness/release/suite.xml,v  <--  suite.xml
new revision: 1.32; previous revision: 1.31
done
Checking in core/javahelp/build.xml;
/shared/data/ccvs/repository/core/javahelp/build.xml,v  <--  build.xml
new revision: 1.39; previous revision: 1.38
done
Checking in httpserver/servletapi/build.xml;
/shared/data/ccvs/repository/httpserver/servletapi/build.xml,v  <--  build.xml
new revision: 1.14; previous revision: 1.13
done
Checking in j2eeserver/j2eeapis/build.xml;
/shared/data/ccvs/repository/j2eeserver/j2eeapis/build.xml,v  <--  build.xml
new revision: 1.14; previous revision: 1.13
done
Checking in java/javacore/build.xml;
/shared/data/ccvs/repository/java/javacore/build.xml,v  <--  build.xml
new revision: 1.20; previous revision: 1.19
done
Checking in junit/build.xml;
/shared/data/ccvs/repository/junit/build.xml,v  <--  build.xml
new revision: 1.64; previous revision: 1.63
done
Checking in libs/commons_logging/build.xml;
/shared/data/ccvs/repository/libs/commons_logging/build.xml,v  <--  build.xml
new revision: 1.11; previous revision: 1.10
done
Checking in libs/xerces/build.xml;
/shared/data/ccvs/repository/libs/xerces/build.xml,v  <--  build.xml
new revision: 1.22; previous revision: 1.21
done
Checking in libs/xmlbeans/build.xml;
/shared/data/ccvs/repository/libs/xmlbeans/build.xml,v  <--  build.xml
new revision: 1.6; previous revision: 1.5
done
Checking in mdr/jmi/build.xml;
/shared/data/ccvs/repository/mdr/jmi/build.xml,v  <--  build.xml
new revision: 1.9; previous revision: 1.8
done
Checking in mdr/mof/build.xml;
/shared/data/ccvs/repository/mdr/mof/build.xml,v  <--  build.xml
new revision: 1.10; previous revision: 1.9
done
Checking in nbbuild/antsrc/org/netbeans/nbbuild/MakeNBM.java;
/shared/data/ccvs/repository/nbbuild/antsrc/org/netbeans/nbbuild/MakeNBM.java,v
 <--  MakeNBM.java
new revision: 1.70; previous revision: 1.69
done
Checking in nbbuild/antsrc/org/netbeans/nbbuild/MakeUpdateDesc.java;
/shared/data/ccvs/repository/nbbuild/antsrc/org/netbeans/nbbuild/MakeUpdateDesc.java,v
 <--  MakeUpdateDesc.java
new revision: 1.28; previous revision: 1.27
done
Checking in nbbuild/templates/common.xml;
/shared/data/ccvs/repository/nbbuild/templates/common.xml,v  <--  common.xml
new revision: 1.42; previous revision: 1.41
done
Checking in nbbuild/templates/projectized.xml;
/shared/data/ccvs/repository/nbbuild/templates/projectized.xml,v  <-- 
projectized.xml
new revision: 1.76; previous revision: 1.75
done
Checking in serverplugins/jmxri/build.xml;
/shared/data/ccvs/repository/serverplugins/jmxri/build.xml,v  <--  build.xml
new revision: 1.5; previous revision: 1.4
done
Checking in tasklist/usertasks/build.xml;
/shared/data/ccvs/repository/tasklist/usertasks/build.xml,v  <--  build.xml
new revision: 1.40; previous revision: 1.39
done
Checking in web/jstl11/build.xml;
/shared/data/ccvs/repository/web/jstl11/build.xml,v  <--  build.xml
new revision: 1.18; previous revision: 1.17
done
Checking in web/servletapi24/build.xml;
/shared/data/ccvs/repository/web/servletapi24/build.xml,v  <--  build.xml
new revision: 1.18; previous revision: 1.17
done
Checking in websvc/jaxrpc16_xml/build.xml;
/shared/data/ccvs/repository/websvc/jaxrpc16_xml/build.xml,v  <--  build.xml
new revision: 1.6; previous revision: 1.5
done
Checking in xml/catalog/build.xml;
/shared/data/ccvs/repository/xml/catalog/build.xml,v  <--  build.xml
new revision: 1.73; previous revision: 1.72
done
Checking in xml/css/build.xml;
/shared/data/ccvs/repository/xml/css/build.xml,v  <--  build.xml
new revision: 1.71; previous revision: 1.70
done
Comment 9 pzajac 2007-01-10 13:34:08 UTC
verified