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 257807 - Cannot run zipped distribution build on top of platform 8.1
Summary: Cannot run zipped distribution build on top of platform 8.1
Status: NEW
Alias: None
Product: platform
Classification: Unclassified
Component: Launchers&CLI (show other bugs)
Version: 8.1
Hardware: PC All
: P4 normal with 2 votes (vote)
Assignee: Libor Fischmeistr
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-01 19:12 UTC by heithecker
Modified: 2016-12-27 13:44 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description heithecker 2016-02-01 19:12:53 UTC
When running a zipped RCP application distribution build on to of netbeans 8.1 the following error is raised: 

Exception in thread "main" java.lang.NoClassDefFoundError:  org/objectweb/asm/ClassVisitor while loading org.openide.filesystems.FileSystem 
....

The reason is obviously that "{nbinstall}/platform/core/asm-all-5.0.1.jar" is not copied into the zipped target folders. 

Please fix this.
Comment 1 Sean.mi.phillips 2016-04-18 19:35:03 UTC
The only legit work around I have found requires recompilation of your older plugins. This is a 8.1 vs older specification problem with the FileSystem, Execution and Progress APIs.  Below is what I had to do:

I have been dealing with this issue as well with the recent development of a new NetBeans Platform application. We have a lot of existing plugins written between NetBeans versions 7.2 and 8.0. Almost all of them use one of the API's that have 8.0 compatibility bridges. NetBeans 8.1 will detect this and attempt to automatically add these bridge dependencies. THIS is the problem.   
I found I had to go through all my plugins and module suites and one by one remove the "8.0 Compatibility" dependencies.  This will cause your compile to fail because it is retaining a reference to the older specification of that dependency.  Next you need to go through each plugin dependency list and remove the base API dependency.   Your code will still fail to compile but now your class files will 'red line' in the editor. Now if you click on your compilation error within the editor and select "Search for Module Dependency"... NetBeans will automatically pull in the latest 8.1 specification version.  To my knowledge the three APIs that suffer from this are the FileSystem API, Execution API, and Progress API.
Comment 2 ulim 2016-12-27 13:44:54 UTC
This workaround didn't change anything for me, but manually inserting the missing asm jar did. I followed the suggestion from this thread:
http://forums.netbeans.org/ptopic65225.html