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 248415 - asm-all-5.0 should not be on application classpath
Summary: asm-all-5.0 should not be on application classpath
Status: RESOLVED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Module System (show other bugs)
Version: 8.1
Hardware: PC Linux
: P1 normal (vote)
Assignee: Jaroslav Tulach
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-05 09:02 UTC by Jaroslav Tulach
Modified: 2014-11-14 03:57 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jaroslav Tulach 2014-11-05 09:02:05 UTC 
Due to attempts to keep binary backward compatiblity when issue 247200 was integrated, Sváťa had to use asm.jar in o.n.bootstrap. As such the asm-all-5.0.jar ended up on application classpath.

This is slightly dangerous as various asm versions are known to not keep backward compatiblity and we already had some problems when bringing the new version to JDeveloper.

I am creating this issue to track investigation of moving asm.jar outside of app classpath (I am almost sure I can move it to dynamic app classpath - e.g. next to core.startup module), possibly turn it into regular module.
Comment 1 Jaroslav Tulach 2014-11-08 07:12:50 UTC 
ergonomics#83b767a28885
Comment 2 Quality Engineering 2014-11-14 03:57:24 UTC 
Integrated into 'main-silver', will be available in build *201411140002* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)

Changeset: http://hg.netbeans.org/main-silver/rev/83b767a28885
User: Jaroslav Tulach <jtulach@netbeans.org>
Log: #248415: asm.jar no longer needs to be on application classpath