Just before giving up on the new enRoute system I decided to go back to the start and follow the
quickstart tutorial exactly as outlined in the documents.
I had tried to be too clever and use the bare project...wrong.
Using the full project artifact solved all of the problems. I deleted my .m2
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
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,
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
Hi,
Building with (new) enRoute, all is well until I add a Vaadin dependency.
Video of problem 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
