You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@polygene.apache.org by "Niclas Hedhman (JIRA)" <ji...@apache.org> on 2015/12/12 03:20:46 UTC

[jira] [Created] (ZEST-131) OSGi doesn't work anymore

Niclas Hedhman created ZEST-131:
-----------------------------------

             Summary: OSGi doesn't work anymore
                 Key: ZEST-131
                 URL: https://issues.apache.org/jira/browse/ZEST-131
             Project: Zest
          Issue Type: Bug
    Affects Versions: 2.1, 2.0
            Reporter: Niclas Hedhman
             Fix For: 3.0


StackOverflow http://stackoverflow.com/questions/28153579/qi4j-on-osgi-fails-to-bootstrap brings up that the OSGi support in Zest is now broken.

It should be fixed for 3.0, or earlier.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [jira] [Created] (ZEST-131) OSGi doesn't work anymore

Posted by Niclas Hedhman <ni...@hedhman.org>.

Pax Exam2 at OPS4J...

Not Apache but Apache Karaf uses it, I think...

On Mon, Dec 14, 2015 at 2:01 PM, Kent Sølvsten <ke...@gmail.com>
wrote:

> One thought ....
>
> I suspect this is broken due to a lack of tests.
>
> This made me think .... is there any standard way of handling more
> complex test environments in apache-land?
>
> Such as using docker/vagrant to manage a container, where we launch an
> application server, deploy a test application inside it and create some
> tests for it?
>
> The OSGI case may be simpler, but i guess we even here need to create
> some sort of deployment-unit deployed into some OSGi container.
>
> /Kent
>
>
> Den 12-12-2015 kl. 03:20 skrev Niclas Hedhman (JIRA):
> >                  Key: ZEST-131
>
>


-- 
Niclas Hedhman, Software Developer
http://zest.apache.org - New Energy for Java

Re: [jira] [Created] (ZEST-131) OSGi doesn't work anymore

Posted by Kent Sølvsten <ke...@gmail.com>.

One thought ....

I suspect this is broken due to a lack of tests.

This made me think .... is there any standard way of handling more
complex test environments in apache-land?

Such as using docker/vagrant to manage a container, where we launch an
application server, deploy a test application inside it and create some
tests for it?

The OSGI case may be simpler, but i guess we even here need to create
some sort of deployment-unit deployed into some OSGi container.

/Kent


Den 12-12-2015 kl. 03:20 skrev Niclas Hedhman (JIRA):
>                  Key: ZEST-131