Hi Paul, > Is there a reason some bundles can not be added as dependencies in the > project (reactor) pom?
You should not add dependencies to the parent pom (which in this case is also the reactor pom). The parent pom should be used to manage the versions of common dependencies using the dependency management section, but any dependencies you add in the parent become dependencies of every project whether they are needed or not. This isn’t an enRoute recommendation as much as general Maven recommendation. From the error message you attached: > Caused by: java.util.zip.ZipException: invalid LOC header (bad signature) > at java.util.zip.ZipFile.read(Native Method) > at java.util.zip.ZipFile.access$1400(ZipFile.java:60) > at java.util.zip.ZipFile$ZipFileInputStream.read(ZipFile.java:734) > at > java.util.zip.ZipFile$ZipFileInflaterInputStream.fill(ZipFile.java:434) > at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:158) > at aQute.lib.io.IO.copy(IO.java:227) > at aQute.bnd.osgi.ZipResource.getBuffer(ZipResource.java:66) > at aQute.bnd.osgi.ZipResource.buffer(ZipResource.java:56) > at aQute.bnd.osgi.ZipResource.openInputStream(ZipResource.java:73) > at aQute.bnd.osgi.Jar.getManifest(Jar.java:318) > at aQute.bnd.osgi.Analyzer.analyze(Analyzer.java:201) > at aQute.bnd.osgi.Builder.analyze(Builder.java:396) > at aQute.bnd.osgi.Analyzer.calcManifest(Analyzer.java:799) > ... 35 more This indicates that you have a malformed jar in your dependencies. As you’re using Maven this probably means you have a malformed jar in your local repo. This can happen if you have multiple maven instances (e.g. command line and Eclipse) writing to the repo at the same time, or if you have some sort of network fault while downloading. The fix is to delete the broken jar files from your local repo and to re-run the maven build. This will re-download the jars and everything should work again. Best Regards, Tim > On 18 Jun 2018, at 14:36, Raymond Auge via osgi-dev <osgi-dev@mail.osgi.org> > wrote: > > Regarding Vaadin, I believe that any jar which has java classes in the root > (i.e. no package) are malformed in the eyes of OSGi and bnd will complain > about them until you find a way to silence bnd (which may only be possible > using the `-fixupmessages` directive). > > Sincerely, > - Ray > > On Mon, Jun 18, 2018 at 7:32 AM, Paul F Fraser via osgi-dev > <osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org>> wrote: > On further investigation > It is not related to dependencies in the reactor. It happens in modules as > well. > jsoup seems ok > vaadin server 8.4.3 causes errors > vaadin osgi integration bundle 8.4.3 causes errors > all other vaadin bundles seem ok. > > Paul > > > On 18/06/2018 7:05 PM, Paul F Fraser via osgi-dev wrote: > jsoup does the same thing. > Is there a reason some bundles can not be added as dependencies in the > project (reactor) pom? > > Paul > > On 17/06/2018 8:36 PM, Paul F Fraser via osgi-dev wrote: > Hi, > > Building with (new) enRoute, all is well until I add a Vaadin dependency. > > Video of problem https://youtu.be/MQX8ICmUHdc <https://youtu.be/MQX8ICmUHdc> > > Part of error report .... > > The default package '.' is not permitted by the Import-Package syntax. > This can be caused by compile errors in Eclipse because Eclipse creates > valid class files regardless of compile errors. > The following package(s) import from the default package > [net.qnenet.qVaadinOSGi] > (biz.aQute.bnd:bnd-maven-plugin:4.0.0:bnd-process:default:process-classes) > > more details in attachment. > > Any ideas as to cause of problem? > > Paul Fraser > > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org> > https://mail.osgi.org/mailman/listinfo/osgi-dev > <https://mail.osgi.org/mailman/listinfo/osgi-dev> > > > -- > Raymond Augé <http://www.liferay.com/web/raymond.auge/profile> (@rotty3000) > Senior Software Architect Liferay, Inc. <http://www.liferay.com/> (@Liferay) > Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org/> (@OSGiAlliance) > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org > https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
