Question about bundling ?

Hi

I'm upgrading the GenStar repository with latest version of goomph plugin 1.7.0, and i see something strange.

I have a specific way to bundle my sources after compilation, i use this bnd to create a manifest :

```

// configure the OSGi bundle
jar.manifest.attributes(
//'-exportcontents': 'core.*, gospl.*, spin.*, spll.*, gaml.*, genstar.*',
'-removeheaders': 'Bnd-LastModified,Bundle-Name,Created-By,Tool,Private-Package,Require-Capability',
'Conditional-Package': '!org.w3c.*, !org.xml.*, !javax.*, !org.jfree.*, !org.graphstream.*, !msi.*, *',
'Import-Package': '!*',
'Require-Bundle': 'msi.gama.core',
'Export-Package': 'gama.genstar.plugin',
'Bundle-Version': '1.0.0.${tstamp;yyyyMMddHHmm}',
'Bundle-SymbolicName': project.name +";singleton:=true",
'Bundle-RequiredExecutionEnvironment': 'JavaSE-1.8',
'Require-Capability': 'osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=1.8))"',
'Bundle-Vendor': 'Gama team',
'Bundle-License': "http://www.apache.org/licenses/LICENSE-2.0"
)

osgiBndManifest {
copyTo 'META-INF/MANIFEST.MF'
}
```

Normally this code generate a big Jar with all java classes statically linked when i run `gradle build` ( effect of conditional Package option), but this is not the case.

Any idea ? Some bugs ?

Inizia riproducendo la build di GenStar con goomph 1.7.0, la configurazione del manifest bnd mostrata e `gradle build`; esamina il task `osgiBndManifest` e il JAR e manifest generati. Il lavoro è completato quando si determina perché `Conditional-Package` non include le classi previste e si documenta o corregge il comportamento con un risultato di build verificabile.

Scritto dal modello di indicizzazione a partire dal testo della issue.