[
https://issues.jboss.org/browse/JBIDE-9140?page=com.atlassian.jira.plugin...
]
Denis Golovin commented on JBIDE-9140:
--------------------------------------
"it indicates to the runtime that your plug-in should run even if an optional plug-in
dependency is missing or not resolved" (c). It works only if there is no direct
references to classes from optional bundle (i.e Java Reflection is used), thus it is not
required for compilation.
That is how PDA build used to work (i'm not sure it is work the same way in 3.7). It
just didn't include optional dependency in build classpath in generated ant build.
This behavior also lets avoid Class Definition Not found exceptions.
For example, if you have orq.bundle2.Class1 imported in class1 that belongs to org.bindle1
and org.bundle1 is marked as optional dependency, compilation now passes without errors,
but what is going to happen after orq.bundle2 is installed without accessible org.bundle1?
P2 lets org.bundle2 to be installed and class not found exception is thrown on attempt to
load org.bundle2.Class1.
move to tycho 0.13 for JBT and JBDS builds
------------------------------------------
Key: JBIDE-9140
URL:
https://issues.jboss.org/browse/JBIDE-9140
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M3
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.x
Attachments: JBIDE-9140.patch
After M2, move to latest Tycho 0.13 including refactoring plugin names in parent pom and
elsewhere (eg., test plugin poms that override settings)
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira