Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
11.0
Description
Our NB-platform based app does the following in the platform.properties file
cluster.path=\ ${nbplatform.active.dir}/extide:\ ${nbplatform.active.dir}/harness:\ ${nbplatform.active.dir}/ide:\ ${nbplatform.active.dir}/java # .... disabled.modules=\ org.apache.commons.lang,\ # ....
Whena I build a distribution, (ant build-zip), the file java/maven/lib/commons-lang-2.6.jar is excluded, because:
- it is a OSGi bundle
- it's Bundle-Symbolic-Name matches the excluded module's codename
Despite the file is in a different directory, where NB modules shouldn't be placed, it's recognized as a module and excluded from the distribution.
The bug causes maven embedder to fail during startup, since it can't link to **its libraries.
Attachments
Issue Links
- links to