Re: Exposing a webapp as an OSGi service?

[Steinar Bang]

> Steinar Bang :

>> [2] - 
>> https://github.com/ops4j/org.ops4j.pax.web/blob/master/pax-web-itest/pax-web-itest-container/pax-web-itest-container-jetty/src/test/java/org/ops4j/pax/web/itest/jetty/WhiteboardServletAnnotatedIntegrationTest.java

> I'm currently in the process of transforming my eaxample webapp from war
> to jar.
>  https://github.com/steinarb/ukelonn/tree/using-vaadin/ukelonn.bundle

> Ie. making the webapp bundle a regular OSGi bundle with a regular
> internal layout, not a WAR-type layout.

> The regular bundle will register the servlet by having the activator
> listen for the WebContainer service and registering the servlet on
> that.

This turned out to be quite easy
 
https://github.com/steinarb/ukelonn/blob/scratch/using-vaadin-jar-with-webcontainer-injection/ukelonn.bundle/src/main/java/no/priv/bang/ukelonn/impl/UkelonnServiceProvider.java#L80

> Once I've got that approach up and working I will look into reversing
> the approach, ie. try to expose a service like in [2] above.

This, on the other hand has turned out to be not so easy...:-)

What I did, was:
 - Expose the shiro EventLoaderListener as an OSGi service
 - Expose the shiro filter as an OSGi service
 - Expose the servlet as an OSGi service

This worked, as far as having all of the services start and be picked up
by the pax whiteboard extender, e.g. like so:
 karaf@root()> bundle:capabilities 72
 no.priv.bang.ukelonn [72] provides:
 ---
 osgi.wiring.bundle; no.priv.bang.ukelonn 1.0.0.SNAPSHOT [UNUSED]
 osgi.wiring.host; no.priv.bang.ukelonn 1.0.0.SNAPSHOT [UNUSED]
 osgi.identity; no.priv.bang.ukelonn 1.0.0.SNAPSHOT [UNUSED]
 service; [java.util.EventListener] with properties:
service.bundleid = 72
service.id = 173
service.scope = singleton
Used by:
   org.ops4j.pax.web.pax-web-extender-whiteboard [114]
 service; [javax.servlet.Filter] with properties:
httpContext.path = /ukelonn
service.bundleid = 72
service.id = 176
service.scope = singleton
servletNames = ukelonn
urlPatterns = [/*]
Used by:
   org.ops4j.pax.web.pax-web-extender-whiteboard [114]
 service; [javax.servlet.Servlet] with properties:
alias = /
httpContext.path = /ukelonn
service.bundleid = 72
service.id = 177
service.scope = singleton
servletNames = ukelonn
Used by:
   org.ops4j.pax.web.pax-web-extender-whiteboard [114]

However, it didn't actually work.

The problem is that the EventloaderListener has to be started first, and
that it needs to receive an actual event, before the filter can be
created.  If not, I see this message in the karaf.log (as well as having
nothing actually working):
 2017-06-30T14:18:12,760 | ERROR | Thread-49| WebApplication
   | 114 - org.ops4j.pax.web.pax-web-extender-whiteboard - 6.0.3 | 
Registration skipped for [FilterWebElement{mapping=DefaultFilterMapping 
[httpContextId=null, filter=org.ops4j.pax.web.service.spi.model.FilterModel-23, 
urlPatterns=[/*], servletNames=[ukelonn], initParams={service.id=179, 
servletNames=ukelonn, urlPatterns=[Ljava.lang.String;@14304ee, 
httpContext.path=/ukelonn, objectClass=[Ljava.lang.String;@6db98b5, 
service.scope=singleton, service.bundleid=72}, asyncSupported=false]}] due to 
error during registration
 java.lang.RuntimeException: javax.servlet.ServletException: 
java.lang.IllegalStateException: No WebEnvironment found: no 
EnvironmentLoaderListener registered?

I tried putting an dependency for the EnvironmentLoaderListener OSGi
service in the filter service, but that has two problems:
 1. The EnvironmentLoaderListener is registered as an EventListener OSGi
service and that injection could potentially be satisfied by a
different EventListener
 2. Even if the EnvironmentLoaderListener is the actual EventLoader
injected (and it has been when I have been debugging this) having
the service up and running doesn't necessarily mean that a
WebEnvironment can be found, because the WebEnvironment is created
when the EnviromentLoaderListener receives a ServletContextEvent

I've been scratching my head for a while figuring out how to best
accomplish this, and haven't come up with something that works yet.

All hints and tips are appreciated.

-- 
-- 
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com

--- 
You received this message because you are subscribed to the Google Groups 
"OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ops4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: jersey-common not resolving javax.annotation even if it is already up

['Achim Nierbeck' via OPS4J]

Hi,

which version of javax.annotation-api do you have installed?
The exception clearly states it is looking for a version greater or equal
to 1.2 but lesser then 2.0.
If you have a 1.1.x version or lesser installed, that won't resolve.

regards, Achim


2017-06-28 16:13 GMT+02:00 Umesh Rajani :

> I'm running junit test for REST API in web-pax, heret I'm facing very
> strange behaviour I don't know why this dependency not getting resolved.
>
> Please have a look in exception:
>
> rg.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.swissbox.extender.BundleWatcher]
>  : Scanning bundle [javax.validation.api]
> org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.swissbox.extender.BundleWatcher]
>  : Scanning bundle [javax.annotation-api]
> org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.swissbox.extender.BundleWatcher]
>  : Scanning bundle [javax.json-api]
> org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.swissbox.extender.BundleWatcher]
>  : Scanning bundle [javax.ws.rs.jsr311-api]
> org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.swissbox.extender.BundleWatcher]
>  : Scanning bundle [org.apache.servicemix.bundles.javax-inject]
> org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.swissbox.extender.BundleWatcher]
>  : Scanning bundle [org.objectweb.asm.all.debug]
> ERROR: Bundle org.glassfish.jersey.core.jersey-common [83] Error starting 
> mvn:org.glassfish.jersey.core/jersey-common/2.25 
> (org.osgi.framework.BundleException: Unable to resolve 
> org.glassfish.jersey.core.jersey-common [83](R 83.0): missing requirement 
> [org.glassfish.jersey.core.jersey-common [83](R 83.0)] osgi.wiring.package; 
> (&(osgi.wiring.package=javax.annotation)(version>=1.2.0)(!(version>=2.0.0))) 
> Unresolved requirements: [[org.glassfish.jersey.core.jersey-common [83](R 
> 83.0)] osgi.wiring.package; 
> (&(osgi.wiring.package=javax.annotation)(version>=1.2.0)(!(version>=2.0.0)))])
> org.osgi.framework.BundleException: Unable to resolve 
> org.glassfish.jersey.core.jersey-common [83](R 83.0): missing requirement 
> [org.glassfish.jersey.core.jersey-common [83](R 83.0)] osgi.wiring.package; 
> (&(osgi.wiring.package=javax.annotation)(version>=1.2.0)(!(version>=2.0.0))) 
> Unresolved requirements: [[org.glassfish.jersey.core.jersey-common [83](R 
> 83.0)] osgi.wiring.package; 
> (&(osgi.wiring.package=javax.annotation)(version>=1.2.0)(!(version>=2.0.0)))]
> at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4111)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:2117)
> at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1371)
> at 
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
> at java.lang.Thread.run(Thread.java:745)
>
>
>
> Here we can see javax.annotation-api bundle successfully scanned and
> running in pax-exam contained even though jersey-common is not getting
> resolved it says javax.annotation not found.
>
> Does anybody faced this, then please suggest me.
>
> Thanks you,
>
> Umesh
>
> --
> --
> --
> OPS4J - http://www.ops4j.org - ops4j@googlegroups.com
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OPS4J" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ops4j+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Apache Member
Apache Karaf  Committer & PMC
OPS4J Pax Web  Committer &
Project Lead
blog 
Co-Author of Apache Karaf Cookbook 

Software Architect / Project Manager / Scrum Master

-- 
-- 
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com

--- 
You received this message because you are subscribed to the Google Groups 
"OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ops4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Version increase required; detected 6.1.0.SNAPSHOT, suggested 7.0.0

['Achim Nierbeck' via OPS4J]

Hi,

well it doesn't matter that you are working on a snapshot version.
Obviously the change you want to introduce is a major api breaking change.
Therefore this change will require a version bump to 7.0 instead of 6.1.
Take a look at semantic versioning for details about this, and also about
semantic versioning in the scope of OSGi.
I hope that will make it clearer.

First of all regarding your fix, make sure you
a) change the API in a non breaking way
b) if not possible we need to postpone it to a new major version.

thanks for willing to give back to the community, but for the sake of
compatibility we need to make sure we stick to semantic versioning.
The bnd baselining just enforces that.

regards, Achim


2017-06-30 10:36 GMT+02:00 Lukasz Lech :

> Hello,
>
>
>
> Yes, I’ve changed some interface, but I’m in snapshot version, and I
> assume, there are other API changes, compared to 6.0.x.
>
>
>
> How this check is supposed to work?
>
>
>
> I’ve added a new configuration parameter and I’ve extended
> org.ops4j.pax.web.service.spi.Configuration interface. It’s connected
> with https://ops4j1.jira.com/browse/PAXWEB-1105.
>
>
>
> What should I do?
>
>
>
> If the fix does for me what I hope it to do, I’d like to commit my changes
> to community.
>
>
>
> Best regards!
>
> Lukasz Lech
>
>
>
>
>
> *From:* 'Achim Nierbeck' via OPS4J [mailto:ops4j@googlegroups.com]
> *Sent:* Freitag, 30. Juni 2017 09:56
> *To:* ops4j@googlegroups.com
> *Subject:* Re: Version increase required; detected 6.1.0.SNAPSHOT,
> suggested 7.0.0
>
>
>
> Hi Lukasz,
>
>
>
> you obviously changed an API which isn't a compatible change.
>
> What you are seening is called bnd baselining. It checks API changes for
> compatibility.
>
>
>
> regards, Achim
>
>
>
> 2017-06-30 9:49 GMT+02:00 Lukasz Lech :
>
> Hello,
>
>
>
> I’m trying to build current pax-web version (6.1.0.SNAPSHOT) against my
> custom changes, but I get the following error:
>
>
>
> [ERROR] org.ops4j.pax.web.service.spi: Version increase required; detected
> 6.1.0.SNAPSHOT, suggested 7.0.0
>
>
>
> Do I have some error in local environment, or the pom.xml in master is
> malformed?
>
>
>
>
>
> Best Regards,
>
> Lukasz Lech
>
>
>
> --
> --
> --
> OPS4J - http://www.ops4j.org - ops4j@googlegroups.com
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OPS4J" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ops4j+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
>
>
>
>
> --
>
>
> Apache Member
>
> Apache Karaf  Committer & PMC
> OPS4J Pax Web  Committer &
> Project Lead
> blog 
>
> Co-Author of Apache Karaf Cookbook 
>
>
>
> Software Architect / Project Manager / Scrum Master
>
>
>
> --
> --
> --
> OPS4J - http://www.ops4j.org - ops4j@googlegroups.com
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OPS4J" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ops4j+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> --
> --
> OPS4J - http://www.ops4j.org - ops4j@googlegroups.com
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OPS4J" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ops4j+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Apache Member
Apache Karaf  Committer & PMC
OPS4J Pax Web  Committer &
Project Lead
blog 
Co-Author of Apache Karaf Cookbook 

Software Architect / Project Manager / Scrum Master

-- 
-- 
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com

--- 
You received this message because you are subscribed to the Google Groups 
"OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ops4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Web PAX-EXAM: Do we have any simple web pax test example

[Umesh Rajani]

Hi,

Here I'm using DS based comp. dev't, and I have one bundle 
 'vnc-mw-example-http' that registers servlet successfully but it fails for 
actual test saying context path not found.

I'm getting this exception:

org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.swissbox.extender.BundleWatcher]
 
: Scanning bundle [vnc-mw-directory-http]
org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.swissbox.extender.BundleWatcher]
 
: Scanning bundle [vnc-mw-example-http]
org.ops4j.pax.web.pax-web-runtime[org.ops4j.pax.web.service.internal.HttpServiceFactoryImpl]
 
: Binding bundle: [vnc-mw-example-http [161]] to http service
org.ops4j.pax.web.pax-web-runtime[org.ops4j.pax.web.service.internal.HttpServiceStarted]
 
: Creating http service for: vnc-mw-example-http [161]
org.ops4j.pax.web.pax-web-runtime[org.ops4j.pax.web.service.internal.HttpServiceProxy]
 
: HttpServiceProxy created for HttpService 
org.ops4j.pax.web.service.internal.HttpServiceStarted@133de94b for bundle 
vnc-mw-example-http [161]
biz.vnc.mw.api.http.ServletRegistration@41be6f4e registering 
biz.vnc.mw.api.http.JAXApplication@4c93fc50 : 1 classes, 1 singletons, 0 
properties @ '/mw-test'
org.ops4j.pax.web.pax-web-runtime[org.ops4j.pax.web.service.internal.HttpServiceProxy]
 
: Registering servlet: [/mw-test] -> 
org.glassfish.jersey.servlet.ServletContainer@7fe3ddd8
org.ops4j.pax.web.pax-web-runtime[org.ops4j.pax.web.service.internal.HttpServiceStarted]
 
: Register servlet (alias=/mw-test). Using context 
[ContextModel{id=org.ops4j.pax.web.service.spi.model.ContextModel-1,name=,httpContext=DefaultHttpContext
 
[bundle=vnc-mw-example-http [161], 
contextID=default],contextParams={},virtualHosts={},connectors={}}]
org.ops4j.pax.web.pax-web-runtime[org.ops4j.pax.web.service.internal.ServletEventDispatcher]
 
: Sending web event ServletEvent [replay=false, type=DEPLOYING, 
bundle=161-vnc-mw-example-http, timestamp=1498822301386, alias=/mw-test, 
servletName=org.ops4j.pax.web.service.spi.model.ServletModel-2, 
urlParameter=[/mw-test/*], 
servletClass=org.glassfish.jersey.servlet.ServletContainer], 
httpContext=DefaultHttpContext [bundle=vnc-mw-example-http [161], 
contextID=default]] for bundle vnc-mw-example-http
org.ops4j.pax.web.pax-web-runtime[org.ops4j.pax.web.service.internal.LogServiceHandler]
 
: org/osgi/service/web/DEPLOYING
org.ops4j.pax.web.pax-web-jetty[org.ops4j.pax.web.service.jetty.internal.JettyServerImpl]
 
: Adding servlet 
[ServletModel{id=org.ops4j.pax.web.service.spi.model.ServletModel-2,name=org.ops4j.pax.web.service.spi.model.ServletModel-2,urlPatterns=[/mw-test/*],alias=/mw-test,servlet=org.glassfish.jersey.servlet.ServletContainer@7fe3ddd8,initParams={},context=ContextModel{id=org.ops4j.pax.web.service.spi.model.ContextModel-1,name=,httpContext=DefaultHttpContext
 
[bundle=vnc-mw-example-http [161], 
contextID=default],contextParams={},virtualHosts={},connectors={}}}]
org.ops4j.pax.web.pax-web-jetty[org.ops4j.pax.web.service.jetty.internal.JettyServerWrapper]
 
: Creating new ServletContextHandler for HTTP context [DefaultHttpContext 
[bundle=vnc-mw-example-http [161], contextID=default]] and model 
[ContextModel{id=org.ops4j.pax.web.service.spi.model.ContextModel-1,name=,httpContext=DefaultHttpContext
 
[bundle=vnc-mw-example-http [161], 
contextID=default],contextParams={},virtualHosts={},connectors={}}]
org.ops4j.pax.web.pax-web-api[org.ops4j.pax.web.utils.ServletContainerInitializerScanner]
 
: will add 
org.eclipse.jetty.websocket.server.NativeWebSocketServletContainerInitializer 
to ServletContainerInitializers
org.ops4j.pax.web.pax-web-api[org.ops4j.pax.web.utils.ServletContainerInitializerScanner]
 
: added ServletContainerInitializer: 
org.eclipse.jetty.websocket.server.NativeWebSocketServletContainerInitializer
org.ops4j.pax.web.pax-web-api[org.ops4j.pax.web.utils.ServletContainerInitializerScanner]
 
: will add 
org.eclipse.jetty.websocket.jsr356.server.deploy.WebSocketServerContainerInitializer
 
to ServletContainerInitializers
org.ops4j.pax.web.pax-web-api[org.ops4j.pax.web.utils.ServletContainerInitializerScanner]
 
: added ServletContainerInitializer: 
org.eclipse.jetty.websocket.jsr356.server.deploy.WebSocketServerContainerInitializer
org.ops4j.pax.web.pax-web-jetty[org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection]
 
: Adding bean: HttpServiceContext{httpContext=null}
org.ops4j.pax.web.pax-web-jetty[org.ops4j.pax.web.service.jetty.internal.HttpServiceContext]
 
: Creating default LateInvalidatingHashSessionManager, no SessionIdManager 
currently set
org.ops4j.pax.web.pax-web-jetty[org.ops4j.pax.web.service.jetty.internal.HttpServiceContext]
 
: registering context DefaultHttpContext [bundle=vnc-mw-example-http [161], 
contextID=default], with context-name: 
org.ops4j.pax.web.pax-web-jetty[org.ops4j.pax.web.service.jetty.internal.JettyServerWrapper]
 
: configureSessionManager for context 
[HttpServiceContext{httpContext=DefaultHttpContext 
[bundle=vnc-mw-example-http [161], 

Re: PAX Wicket 4 (moving to wicket 8)

[nino martinez wael]

ok great :)

On Fri, Jun 30, 2017 at 11:47 AM, 'Christoph Läubrich' via OPS4J <
ops4j@googlegroups.com> wrote:

> The test are running fine now :-)
> I'll try to prepare a release of a 4.0.0 Version for Wicket 7 then we can
> move on to wicket 8 as a next step
>
> Am 28.06.2017 15:21, schrieb nino martinez wael:
>
>> just made a single commit..
>>
>>
> --
> --
> --
> OPS4J - http://www.ops4j.org - ops4j@googlegroups.com
>
> --- You received this message because you are subscribed to a topic in the
> Google Groups "OPS4J" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/to
> pic/ops4j/A3x7_4ktoqk/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> ops4j+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Best regards / Med venlig hilsen
Nino Martinez

-- 
-- 
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com

--- 
You received this message because you are subscribed to the Google Groups 
"OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ops4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: PAX Wicket 4 (moving to wicket 8)

['Christoph Läubrich' via OPS4J]

The test are running fine now :-)
I'll try to prepare a release of a 4.0.0 Version for Wicket 7 then we 
can move on to wicket 8 as a next step


Am 28.06.2017 15:21, schrieb nino martinez wael:

just made a single commit..



--
--
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com

--- 
You received this message because you are subscribed to the Google Groups "OPS4J" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to ops4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: Version increase required; detected 6.1.0.SNAPSHOT, suggested 7.0.0

[Lukasz Lech]

Hello,

Yes, I’ve changed some interface, but I’m in snapshot version, and I assume, 
there are other API changes, compared to 6.0.x.

How this check is supposed to work?

I’ve added a new configuration parameter and I’ve extended 
org.ops4j.pax.web.service.spi.Configuration interface. It’s connected with 
https://ops4j1.jira.com/browse/PAXWEB-1105.

What should I do?

If the fix does for me what I hope it to do, I’d like to commit my changes to 
community.

Best regards!
Lukasz Lech


From: 'Achim Nierbeck' via OPS4J [mailto:ops4j@googlegroups.com]
Sent: Freitag, 30. Juni 2017 09:56
To: ops4j@googlegroups.com
Subject: Re: Version increase required; detected 6.1.0.SNAPSHOT, suggested 7.0.0

Hi Lukasz,

you obviously changed an API which isn't a compatible change.
What you are seening is called bnd baselining. It checks API changes for 
compatibility.

regards, Achim

2017-06-30 9:49 GMT+02:00 Lukasz Lech 
>:
Hello,

I’m trying to build current pax-web version (6.1.0.SNAPSHOT) against my custom 
changes, but I get the following error:

[ERROR] org.ops4j.pax.web.service.spi: Version increase required; detected 
6.1.0.SNAPSHOT, suggested 7.0.0

Do I have some error in local environment, or the pom.xml in master is 
malformed?


Best Regards,
Lukasz Lech

--
--
--
OPS4J - http://www.ops4j.org - 
ops4j@googlegroups.com

---
You received this message because you are subscribed to the Google Groups 
"OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
ops4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--

Apache Member
Apache Karaf  Committer & PMC
OPS4J Pax Web  Committer & 
Project Lead
blog 
Co-Author of Apache Karaf Cookbook 

Software Architect / Project Manager / Scrum Master

--
--
--
OPS4J - http://www.ops4j.org - 
ops4j@googlegroups.com

---
You received this message because you are subscribed to the Google Groups 
"OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
ops4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
-- 
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com

--- 
You received this message because you are subscribed to the Google Groups 
"OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ops4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Version increase required; detected 6.1.0.SNAPSHOT, suggested 7.0.0

[Lukasz Lech]

Hello,

I'm trying to build current pax-web version (6.1.0.SNAPSHOT) against my custom 
changes, but I get the following error:

[ERROR] org.ops4j.pax.web.service.spi: Version increase required; detected 
6.1.0.SNAPSHOT, suggested 7.0.0

Do I have some error in local environment, or the pom.xml in master is 
malformed?


Best Regards,
Lukasz Lech

-- 
-- 
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com

--- 
You received this message because you are subscribed to the Google Groups 
"OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ops4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.