Hmm.
I took the url from NetBeans Distribution from NeBeans 12.0
It says: https://netbeans.apache.org/nb/updates/12.0/updates.xml.gz
When I download that using wget, I do not see the absolute distribution
URL-s:
<!DOCTYPE module_updates PUBLIC "-//NetBeans//DTD Autoupdate Catalog
2.8//EN" "http://www.netbeans.org/dtds/autoupdate-catalog-2_8.dtd";>
<module_updates timestamp="07/22/23/29/05/2020">
<module codenamebase="org.netbeans.modules.cloud.amazon"
distribution="enterprise/org-netbeans-modules-cloud-amazon.nbm"
downloadsize="78166" homepage="http://www.netbeans.org/";
license="D70E3D18" moduleauthor="" needsrestart="false"
releasedate="2020/05/29" targetcluster="enterprise">
Maybe we are serving something other that we are supposed to?
On 7/24/20 8:59 AM, Neil C Smith wrote:
Hi,
Following comments on the 12.0-u1 release thread. I have some
concerns about having the full set of NBMs for 12.0 and 12.0-u1 in the
update release vote. If pushed to release like this will it this not
cause all of the already existing, non-updated NBMs to be re-mirrored
and archived?
For 11.2-u1 we only had binaries for the updated modules, and the
updates.xml on dist / mirrors only lists the updated modules - mainly
for adding as extra UC for testing.
See / compare
https://archive.apache.org/dist/netbeans/netbeans/11.2-u1/nbms/
https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.0-u1/nbms/
The additional modules are spliced into the updates xml on the VM
only. The updates xml is only ever served to the IDE from the VM for
trust reasons.
The new modules spliced in to the updates xml on the VM use absolute
links rather than relative eg.
<module autoload="true"
codenamebase="org.netbeans.modules.apisupport.harness"
distribution="https://www.apache.org/dyn/closer.lua?action=download&filename=netbeans/netbeans/11.2-u1/nbms/harness/org-netbeans-modules-apisupport-harness.nbm";
...
See https://netbeans.apache.org/nb/updates/11.2/updates.xml.gz
All existing modules retain their relative links so the existing
redirect continues to work. A related but useful change to be made
would be for all the links in this file to be absolute - the chain of
redirects for every module causes issues at times.
The downside is that now 11.2 is archived that link is broken. It's
meant to be possible to tell closer.lua to serve from the archives as
well, but that doesn't seem to actually work when I tested it.
Archived releases really need the links changing.
So, do we keep with this approach, or do we push all NBMs for every
update, or something else? What happens with 12.0-u2 .. u3 .. etc. -
do we keep each location with just the sources and updated NBMs in
place until we're ready to archive the whole release?
Automating the XML splicing process would also be useful if we keep
doing these, and might make managing the various absolute links
easier. Perhaps locally initially, but maybe longer term linked to
the build job similarly to Javadocs?
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
