[JBoss JIRA] (ARQ-1368) Warp: reverse order of chaining of request builder
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1368?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated ARQ-1368:
----------------------------
Original Estimate: 30 minutes
Remaining Estimate: 30 minutes
> Warp: reverse order of chaining of request builder
> --------------------------------------------------
>
> Key: ARQ-1368
> URL: https://issues.jboss.org/browse/ARQ-1368
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Reporter: Lukáš Fryč
> Assignee: Lukáš Fryč
> Priority: Critical
> Fix For: warp_1.0.0.Alpha3
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> If we are following observer:
> {code}.observe(request().uri().contains("__richfacesPushAsync").index(1)){code}
> we want observe first request matching criteria - (URI containing given string), however that is not what happens:
> the {{index(1)}} calls method [{{addFilter}}|https://github.com/arquillian/arquillian-extension-warp/blob/1.0.0.Alpha2/impl/src/main/java/org/jboss/arquillian/warp/impl/client/filter/http/DefaultHttpFilterBuilder.java#L111] which allows chaining, but this chain [evaluates the newly passed filter before it evaluates previous one|https://github.com/arquillian/arquillian-extension-warp/blob/1.0.0.Al...].
> ----
> Reverse the order of evaluation in order to fix semantics of fluent API.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (ARQ-1286) Support Warp on Java EE 5 (Servlets 2.5) compliant containers
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1286?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč reassigned ARQ-1286:
-------------------------------
Assignee: (was: Lukáš Fryč)
> Support Warp on Java EE 5 (Servlets 2.5) compliant containers
> -------------------------------------------------------------
>
> Key: ARQ-1286
> URL: https://issues.jboss.org/browse/ARQ-1286
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Alpha2
> Reporter: Lukáš Fryč
> Priority: Critical
> Fix For: warp_1.0.0.Alpha3
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> Warp is currently focused on Java EE 6 and higher, since it uses {{@WebFilter}} annotation to intercept incoming requests.
> We may decide to support Servlets 2.5 containers as well in case there is enough interest (please vote if you are interested).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (ARQ-1325) Warp: replace piggy-backing on request/response with direct test->filter communication
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1325?page=com.atlassian.jira.plugin.s... ]
Work on ARQ-1325 stopped by Lukáš Fryč.
> Warp: replace piggy-backing on request/response with direct test->filter communication
> --------------------------------------------------------------------------------------
>
> Key: ARQ-1325
> URL: https://issues.jboss.org/browse/ARQ-1325
> Project: Arquillian
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Reporter: Lukáš Fryč
> Assignee: Lukáš Fryč
> Priority: Critical
> Fix For: warp_1.0.0.Alpha3
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> We can do similar processing as we did with CommandService here:
> https://github.com/arquillian/arquillian-extension-warp/blob/aa0745237f5d...
> The CommandService communicates with the WarpFilter asynchronously and its requests are not processed directly, they delegates to the request-serving routine.
> ----
> This way, Warp could:
> 0. request is issued against proxy
> 1. catch the request on the proxy
> 2. register the RequestPayload (with Inspection) in the registry via the WarpFilter (under generated request-specific UUID)
> 3. proxy passes request to WarpFilter with a request header which contains UUID
> 4. WarpFilter associates Inspection from the registry with given request
> 5. Warp proceeds with a request inspection
> 6. response is commited and sent back to the proxy (with given UUID as response header)
> 7. proxy catches the response and obtains ResponsePayload (with Inspection result) from the WarpFilter (using UUID)
> 8. proxy processes the ResponsePayload and passes the request to the client
> 9. the client processes response
> This would avoid a need for piggy-backing on request/response, so it will also eliminate need for response-wrapping (NonWritingResponse).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (ARQ-1368) Warp: reverse order of chaining of request builder
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1368?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated ARQ-1368:
----------------------------
Sprint: Warp Alpha3
> Warp: reverse order of chaining of request builder
> --------------------------------------------------
>
> Key: ARQ-1368
> URL: https://issues.jboss.org/browse/ARQ-1368
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Reporter: Lukáš Fryč
> Assignee: Lukáš Fryč
> Priority: Critical
> Fix For: warp_1.0.0.Alpha3
>
>
> If we are following observer:
> {code}.observe(request().uri().contains("__richfacesPushAsync").index(1)){code}
> we want observe first request matching criteria - (URI containing given string), however that is not what happens:
> the {{index(1)}} calls method [{{addFilter}}|https://github.com/arquillian/arquillian-extension-warp/blob/1.0.0.Alpha2/impl/src/main/java/org/jboss/arquillian/warp/impl/client/filter/http/DefaultHttpFilterBuilder.java#L111] which allows chaining, but this chain [evaluates the newly passed filter before it evaluates previous one|https://github.com/arquillian/arquillian-extension-warp/blob/1.0.0.Al...].
> ----
> Reverse the order of evaluation in order to fix semantics of fluent API.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (ARQ-1367) Warp: wrapped response causes NPE
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1367?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated ARQ-1367:
----------------------------
Sprint: Warp Alpha3
> Warp: wrapped response causes NPE
> ---------------------------------
>
> Key: ARQ-1367
> URL: https://issues.jboss.org/browse/ARQ-1367
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Reporter: Lukáš Fryč
> Assignee: Lukáš Fryč
> Priority: Critical
> Fix For: warp_1.0.0.Alpha3
>
>
> {code}
> 11:24:43,314 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/ITPushServletMapping].[FacesServlet]] (http--127.0.0.1-8080-7) Servlet.service() for servlet FacesServlet threw exception: java.lang.NullPointerException
> at org.apache.tomcat.util.http.MimeHeaders.setValue(MimeHeaders.java:379) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.http11.Http11Processor.prepareResponse(Http11Processor.java:1582) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.http11.Http11Processor.action(Http11Processor.java:998) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.Response.action(Response.java:190) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.Response.sendHeaders(Response.java:390) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:335) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:301) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.connector.CoyoteOutputStream.close(CoyoteOutputStream.java:104) [jbossweb-7.0.13.Final.jar:]
> at java.nio.channels.Channels$WritableByteChannelImpl.implCloseChannel(Channels.java:469) [rt.jar:1.7.0_09-icedtea]
> at java.nio.channels.spi.AbstractInterruptibleChannel.close(AbstractInterruptibleChannel.java:115) [rt.jar:1.7.0_09-icedtea]
> at com.sun.faces.application.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:296) [jsf-impl-2.1.7-jbossorg-2.jar:]
> at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:264) [richfaces-framework.jar:5.0.0-SNAPSHOT]
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:591) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
> at org.jboss.arquillian.warp.impl.server.execution.HttpRequestProcessor.processHttpRequest(HttpRequestProcessor.java:70) [arquillian-warp.jar:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_09-icedtea]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_09-icedtea]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_09-icedtea]
> at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_09-icedtea]
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) [arquillian-core.jar:]
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) [arquillian-core.jar:]
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) [arquillian-core.jar:]
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) [arquillian-core.jar:]
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) [arquillian-core.jar:]
> at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:139) [arquillian-warp.jar:]
> at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterHttp(WarpFilter.java:112) [arquillian-warp.jar:]
> at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilter(WarpFilter.java:89) [arquillian-warp.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09-icedtea]
> 11:24:43,314 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/ITPushServletMapping].[FacesServlet]] (http--127.0.0.1-8080-4) Servlet.service() for servlet FacesServlet threw exception: java.lang.IllegalStateException: test result was already set
> at org.jboss.arquillian.warp.impl.shared.ResponsePayload.setTestResult(ResponsePayload.java:62) [arquillian-warp.jar:]
> at org.jboss.arquillian.warp.impl.server.test.TestResultObserver.storeFirstFailure(TestResultObserver.java:49) [arquillian-warp.jar:]
> at org.jboss.arquillian.warp.impl.server.test.TestResultObserver.propagateThrowableAsTestResultAndRethrow(TestResultObserver.java:37) [arquillian-warp.jar:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_09-icedtea]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_09-icedtea]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_09-icedtea]
> at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_09-icedtea]
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) [arquillian-core.jar:]
> at org.jboss.arquillian.core.impl.ManagerImpl.fireException(ManagerImpl.java:370) [arquillian-core.jar:]
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:110) [arquillian-core.jar:]
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) [arquillian-core.jar:]
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) [arquillian-core.jar:]
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) [arquillian-core.jar:]
> at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:139) [arquillian-warp.jar:]
> at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterHttp(WarpFilter.java:112) [arquillian-warp.jar:]
> at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilter(WarpFilter.java:89) [arquillian-warp.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09-icedtea]
> 11:24:43,330 ERROR [org.apache.catalina.connector.CoyoteAdapter] (http--127.0.0.1-8080-7) An exception or error occurred in the container during the request processing: java.lang.NullPointerException
> at org.apache.tomcat.util.http.MimeHeaders.clear(MimeHeaders.java:240) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.Response.recycle(Response.java:613) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.Response.reset(Response.java:310) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.connector.Response.reset(Response.java:671) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09-icedtea]
> 11:24:43,335 ERROR [org.apache.coyote.http11.Http11Processor] (http--127.0.0.1-8080-7) Error finishing response: java.lang.NullPointerException
> at org.apache.tomcat.util.http.MimeHeaders.setValue(MimeHeaders.java:377) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.http11.Http11Processor.prepareResponse(Http11Processor.java:1617) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.http11.Http11Processor.action(Http11Processor.java:998) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.Response.action(Response.java:188) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.http11.InternalOutputBuffer.endRequest(InternalOutputBuffer.java:363) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.http11.Http11Processor.endRequest(Http11Processor.java:958) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:904) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09-icedtea]
> 11:24:43,337 ERROR [org.apache.coyote.http11.Http11Protocol] (http--127.0.0.1-8080-7) Error reading request, ignored: java.lang.NullPointerException
> at org.apache.tomcat.util.http.MimeHeaders.clear(MimeHeaders.java:240) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.Response.recycle(Response.java:613) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.http11.InternalOutputBuffer.nextRequest(InternalOutputBuffer.java:333) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:917) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09-icedtea]
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (ARQ-1372) Document dependency set up for OSGi containers
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/ARQ-1372?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler resolved ARQ-1372.
---------------------------------
Resolution: Won't Fix
> Document dependency set up for OSGi containers
> ----------------------------------------------
>
> Key: ARQ-1372
> URL: https://issues.jboss.org/browse/ARQ-1372
> Project: Arquillian
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: OSGi Containers
> Reporter: Richard Vitek
>
> Copying my [question from Arquillian forum|https://community.jboss.org/message/806176#806176]:
> I just started with Arquillian as I like its idea and the way how its done but unfortunately I run into total lack of documentation for (remote) OSGI container. I've been trying to implement an integration test on real running OSGi framework (Equinox, in case it matters) but not much joy so far - I ran into JAR hell when trying to setup maven dependencies for OSGi remote container. I haven't found a single piece of docs or article anywhere on internet about this and lost almost on day on classpath setup issues .
> I use Maven (3.0.4) to get the setup done, followed the general instructions from the Getting started guide but didn't really get anywhere - all the time I've been getting ClassNotFound/MethodNotFound and other invalid-classpath-related exceptions. Please, somebody provide a working pom.xml and for Arquillian team - please document this somewhere as it is royal pain in the ass! This is how my pom.xml looks like:
> {code:xml}
> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
> <modelVersion>4.0.0</modelVersion>
> <groupId>com.orchestral.notification</groupId>
> <artifactId>notification.test.integration</artifactId>
> <version>0.0.1-SNAPSHOT</version>
> <name>Notifications Integration Tests</name>
> <properties>
> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
> </properties>
> <repositories>
> <repository>
> <id>jboss-public-repository-group</id>
> <name>JBoss Public Repository Group</name>
> <url>http://repository.jboss.org/nexus/content/groups/public/</url>
> </repository>
> <repository>
> <releases>
> <enabled>true</enabled>
> </releases>
> <snapshots>
> <enabled>true</enabled>
> </snapshots>
> <id>jboss-central</id>
> <name>JBoss Central</name>
> <url>https://repository.jboss.org/nexus/content/repositories/central/</url>
> </repository>
> <repository>
> <releases>
> <enabled>true</enabled>
> </releases>
> <snapshots>
> <enabled>true</enabled>
> </snapshots>
> <id>jboss-public</id>
> <name>JBoss Public</name>
> <url>https://repository.jboss.org/nexus/content/repositories/public-jboss/</url>
> </repository>
> </repositories>
> <dependencyManagement>
> <dependencies>
> <dependency>
> <groupId>org.jboss.arquillian</groupId>
> <artifactId>arquillian-bom</artifactId>
> <version>1.0.3.Final</version>
> <scope>import</scope>
> <type>pom</type>
> </dependency>
> </dependencies>
> </dependencyManagement>
> <dependencies>
> <dependency>
> <groupId>org.jboss.arquillian.container</groupId>
> <artifactId>arquillian-container-osgi-remote</artifactId>
> <version>1.0.2.Final</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.arquillian.junit</groupId>
> <artifactId>arquillian-junit-container</artifactId>
> <scope>test</scope>
> </dependency>
> <!-- <dependency> -->
> <!-- <groupId>org.jboss.osgi.bundles</groupId> -->
> <!-- <artifactId>jboss-osgi-jmx</artifactId> -->
> <!-- <version>1.0.3</version> -->
> <!-- </dependency> -->
> <dependency>
> <groupId>javax.inject</groupId>
> <artifactId>javax.inject</artifactId>
> <version>1</version>
> </dependency>
> <dependency>
> <groupId>junit</groupId>
> <artifactId>junit</artifactId>
> <version>4.8.1</version>
> <scope>test</scope>
> </dependency>
> </dependencies>
> <build>
> <plugins>
> <plugin>
> <artifactId>maven-compiler-plugin</artifactId>
> <version>2.3.2</version>
> <configuration>
> <source>1.7</source>
> <target>1.7</target>
> </configuration>
> </plugin>
> <plugin>
> <artifactId>maven-surefire-plugin</artifactId>
> <version>2.12</version>
> </plugin>
> </plugins>
> </build>
> </project>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months