Broken OSGI dependencies in Vaadin 7.2

Vaadin 6 / 7 / 8
1

The vaadin-shared package requires a wrong version of com.google.gwt.thirdparty.streamhtmlparser.
I fixed that issue and added a fix on github: https://github.com/vaadin/vaadin/pull/12

Could some please pull this request in order to use vaadin 7.2 in osgi?

Thanks

2

Hi Norman,

does this fix solve this problem i’m having when creating a vaadin 7.2 project in eclipse?

Some projects fail to be resolved
Impossible to resolve dependencies of com.example#v7proj;working@GENEIROS
unresolved dependency: org.eclipse.jetty.orbit#org.objectweb.asm;working@GENEIROS: not found
unresolved dependency: org.eclipse.jetty.orbit#javax.annotation;working@GENEIROS: not found
unresolved dependency: org.eclipse.jetty.orbit#javax.mail.glassfish;working@GENEIROS: not found
unresolved dependency: org.eclipse.jetty.orbit#javax.transaction;working@GENEIROS: not found

3

In this specific case i would say no …
In my case the vaadin-data package had an unresolved dependency called vaadin-shared
vaadin-shared had an unresolved dependency com.google.gwt.thirdparty.streamhtmlparser

So i fixed vaadin shared, which fixed vaadin-data.
I don’t know whats the problem in your case

4

ok,

thank you anyway…

cheers

5

Hi,

Too bad we don’t ATM accept simple pull requests. To contribute code directly, you’ll need to accept contributor agreement and post your fix to your review tool. Check out
this page
.

Is this related to
#13796
?

cheers,
matti

6

It seems not related … Ok filling out the agreement can take some time until i can contribute …
Can someone else make these changes? I realy would like to use vaadin 7.2.

7

Hi,

We can handle that pretty quickly if you can scan the signed agreement.

I can poll our R&D department about this thread, but I think it would be better if you could fill a new issue and link to your solution into
dev.vaadin.com
.

cheers,
matti

8

Hi,

there are a couple of OSGi related issues in 7.2 that we are working on. We are also working on getting an automated test setup so we would not break OSGi compatibility in the future.

9

I already create a ticket (http://dev.vaadin.com/ticket/13852) i can fix it as soon as as my contribute agreement is accepted

10

Here we are again. Same package, different dependency …

Ticket: http://dev.vaadin.com/ticket/14771
Patch: https://dev.vaadin.com/review/#/c/4985/

I hope it will be merged as soon as possible