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.
Ant 1.8.3 is to be released soon.
Awaiting fix of a regression affecting many NB build scripts: https://issues.apache.org/bugzilla/show_bug.cgi?id=52621
If we do another 7.1 patch, this would be a reasonable thing to offer, assuming no regressions are found.
Jesse, any dates when it will be released ?
Second release candidate was published yesterday; vote due to close this week.
core-main #c95f12381c0d
Integrated into 'main-golden', will be available in build *201203010400* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/c95f12381c0d User: Jesse Glick <jglick@netbeans.org> Log: #208147: Ant 1.8.3 upgrade.
Jesse, going through candidates for Patch2 and thinking of skipping this from Patch2. The main reason is : with the change of ant version we will need to retest many areas, and I doubt we do not have time for that. So, if the main reason for upgrade is to deliver fix for NB build scripts, this will not really help end users and in that case it's safer to skip it for Patch 2. Or is there any other issue/bug this upgrade is fixing ? Thanks for explanation.
I do not know of any fixes in 1.8.3 needed for NB-generated build scripts; it was rather a general update release. The most important change from my perspective was a workaround for an incompatible security change in JDK 7's JAXP which prevented certain usages of <junitreport> and <xslt> from being run from the IDE. No NB-generated script uses these tasks that I know of, but lots of hand-written scripts (e.g. in freeform projects) do. Whether such fixes justify the extra work of retesting is of course a judgment call. BTW compare bug #205620 which was accepted for 7.1.1 under similar circumstances. Is there a general policy?
(In reply to comment #8) > BTW compare bug #205620 which was accepted for 7.1.1 under similar > circumstances. Is there a general policy? No general policy. The Maven upgrade was approved for 7.1.1 (which was the release we planned in advance to have more time for, this is not the case for 7.1.2 ... this one was intended to be "only JDK7u4 related fixes" release). But if you think the risk of upgrade is almost 0, I am one for upgrade ... just do not expect to test it deeply in 7.1.2, so we'll run sanity test of 'not touched' project types only.
Product Version: NetBeans IDE Dev (Build 201203300938) Java: 1.6.0_31; Java HotSpot(TM) Client VM 20.6-b01 System: Linux version 3.0.0-17-generic-pae running on i386; UTF-8; en_US (nb) Some basic sanity test were executed.No problem was found. Verified in trunk.
(In reply to comment #10) > Product Version: NetBeans IDE Dev (Build 201203300938) > Java: 1.6.0_31; Java HotSpot(TM) Client VM 20.6-b01 > System: Linux version 3.0.0-17-generic-pae running on i386; UTF-8; en_US (nb) > > Some basic sanity test were executed.No problem was found. > Verified in trunk. Ok, Jesse please proceed with integration into releases/release71_fixes . Thanks in advance.
releases #a019a0b2bb87
Integrated into 'releases', will be available in build *201204030956* or newer. Wait for official and publicly available build. Changeset: http://hg.netbeans.org/releases/rev/a019a0b2bb87 User: Jesse Glick <jglick@netbeans.org> Log: #208147: Ant 1.8.3 upgrade.