Re: [DISCUSS] Remove Karaf specific SCR commands

2017-10-04 Thread J. Brebec 
The component name and the status of its instances are not on the same line 
(satisfied, activated, etc). you can't with a grep command find all components 
unsatisfied, or all the components active with the same package/prefix..
 

On 2017-10-04 19:30, David Jencks  wrote: 
> +1000 for removing the duplicated commands :-)
> 
> Does using grep for lines not starting with space give you what you are 
> interested in? The data shown is a tree and presenting it flat would conceal 
> this and duplicate information.
> 
> Thanks
> David Jencks
> 
> Sent from my iPhone
> 
> > On Oct 4, 2017, at 9:03 AM, J. Brebec  wrote:
> > 
> > Hello,
> > 
> > The only thing I personnaly dislikes in the default "scr:list" command is 
> > that the output is on multiple lines for each component : It's hard to read 
> > when there is a lot of components, and it's not possible to use "grep"
> > 
> > Regards,
> > Jérémie
> > 
> >> On 2017-10-04 11:02, Guillaume Nodet  wrote: 
> >> I'm working on KARAF-4785
> >>  and
> >> I've already fixed the completion of the native scr commands.  This means
> >> that we'll have some kind of duplication of all scr commands.  Kind of,
> >> because even though they are similar, the output is different.  The native
> >> commands provide a deeper view of the SCR components.
> >> 
> >> So, should I go ahead and just remove the Karaf specific commands ?
> >> 
> >> Below is the output of the native commands and then the karaf commands...
> >> 
> >> Cheers,
> >> Guillaume
> >> 
> >> *karaf*@root()> scr:list
> >> 
> >> BundleId Component Name Default State
> >> 
> >>Component Id State  PIDs (Factory PID)
> >> 
> >> [  38]   ScrServiceMBean  enabled
> >> 
> >>[   4] [active  ]
> >> 
> >> [ 145]   org.ops4j.pax.web.deployer.internal.WarDeployer  enabled
> >> 
> >>[   3] [active  ]
> >> 
> >> [ 151]   org.ops4j.pax.web.service.internal.WhiteboardDtoService  enabled
> >> 
> >>[   5] [active  ]
> >> 
> >> *karaf*@root()> scr:info org.ops4j.pax.web.deployer.internal.WarDeployer
> >> 
> >> 
> >> 
> >> *** Bundle: org.ops4j.pax.web.pax-web-deployer (145)
> >> 
> >> Component Description:
> >> 
> >>  Name: org.ops4j.pax.web.deployer.internal.WarDeployer
> >> 
> >>  Implementation Class: org.ops4j.pax.web.deployer.internal.WarDeployer
> >> 
> >>  Default State: enabled
> >> 
> >>  Activation: delayed
> >> 
> >>  Configuration Policy: optional
> >> 
> >>  Activate Method: activate
> >> 
> >>  Deactivate Method: deactivate
> >> 
> >>  Modified Method: -
> >> 
> >>  Configuration Pid: [org.ops4j.pax.web.deployer.internal.WarDeployer]
> >> 
> >>  Services:
> >> 
> >>org.apache.felix.fileinstall.ArtifactUrlTransformer
> >> 
> >>  Service Scope: singleton
> >> 
> >>  Component Description Properties:
> >> 
> >>  Component Configuration:
> >> 
> >>ComponentId: 3
> >> 
> >>State: active
> >> 
> >>Component Configuration Properties:
> >> 
> >>component.id = 3
> >> 
> >>component.name = org.ops4j.pax.web.deployer.internal.WarDeployer
> >> 
> >> 
> >> *karaf*@root()> scr:components
> >> 
> >> ID │ State  │ Component Name
> >> 
> >> ───┼────────┼────────────────────────────────────────────────────────
> >> 
> >> 3  │ ACTIVE │ org.ops4j.pax.web.deployer.internal.WarDeployer
> >> 
> >> 5  │ ACTIVE │ org.ops4j.pax.web.service.internal.WhiteboardDtoService
> >> 
> >> *karaf*@root()> scr:details org.ops4j.pax.web.deployer.internal.WarDeployer
> >> 
> >> *Component Details*
> >> 
> >> *  Name: *org.ops4j.pax.web.deployer.internal.WarDeployer
> >> 
> >> *  State   : *ACTIVE
> >> 
> >> *References*
> >> 
> >> *karaf*@root()>
> >> 
> >> 
> >> 
> >> 
> >> -- 
> >> 
> >> Guillaume Nodet
> >> 
> 
> 
> .
>

Re: [DISCUSS] Remove Karaf specific SCR commands

2017-10-04 Thread J. Brebec 
Hello,

The only thing I personnaly dislikes in the default "scr:list" command is that 
the output is on multiple lines for each component : It's hard to read when 
there is a lot of components, and it's not possible to use "grep"

Regards,
Jérémie

On 2017-10-04 11:02, Guillaume Nodet  wrote: 
> I'm working on KARAF-4785
>  and
> I've already fixed the completion of the native scr commands.  This means
> that we'll have some kind of duplication of all scr commands.  Kind of,
> because even though they are similar, the output is different.  The native
> commands provide a deeper view of the SCR components.
> 
> So, should I go ahead and just remove the Karaf specific commands ?
> 
> Below is the output of the native commands and then the karaf commands...
> 
> Cheers,
> Guillaume
> 
> *karaf*@root()> scr:list
> 
>  BundleId Component Name Default State
> 
> Component Id State  PIDs (Factory PID)
> 
>  [  38]   ScrServiceMBean  enabled
> 
> [   4] [active  ]
> 
>  [ 145]   org.ops4j.pax.web.deployer.internal.WarDeployer  enabled
> 
> [   3] [active  ]
> 
>  [ 151]   org.ops4j.pax.web.service.internal.WhiteboardDtoService  enabled
> 
> [   5] [active  ]
> 
> *karaf*@root()> scr:info org.ops4j.pax.web.deployer.internal.WarDeployer
> 
> 
> 
> *** Bundle: org.ops4j.pax.web.pax-web-deployer (145)
> 
> Component Description:
> 
>   Name: org.ops4j.pax.web.deployer.internal.WarDeployer
> 
>   Implementation Class: org.ops4j.pax.web.deployer.internal.WarDeployer
> 
>   Default State: enabled
> 
>   Activation: delayed
> 
>   Configuration Policy: optional
> 
>   Activate Method: activate
> 
>   Deactivate Method: deactivate
> 
>   Modified Method: -
> 
>   Configuration Pid: [org.ops4j.pax.web.deployer.internal.WarDeployer]
> 
>   Services:
> 
> org.apache.felix.fileinstall.ArtifactUrlTransformer
> 
>   Service Scope: singleton
> 
>   Component Description Properties:
> 
>   Component Configuration:
> 
> ComponentId: 3
> 
> State: active
> 
> Component Configuration Properties:
> 
> component.id = 3
> 
> component.name = org.ops4j.pax.web.deployer.internal.WarDeployer
> 
> 
> *karaf*@root()> scr:components
> 
> ID │ State  │ Component Name
> 
> ───┼────────┼────────────────────────────────────────────────────────
> 
> 3  │ ACTIVE │ org.ops4j.pax.web.deployer.internal.WarDeployer
> 
> 5  │ ACTIVE │ org.ops4j.pax.web.service.internal.WhiteboardDtoService
> 
> *karaf*@root()> scr:details org.ops4j.pax.web.deployer.internal.WarDeployer
> 
> *Component Details*
> 
> *  Name: *org.ops4j.pax.web.deployer.internal.WarDeployer
> 
> *  State   : *ACTIVE
> 
> *References*
> 
> *karaf*@root()>
> 
> 
> 
> 
> -- 
> 
> Guillaume Nodet
>

Re: [DISCUSS] Remove Karaf specific SCR commands

2017-10-04 Thread Jean-Baptiste Onofré 

+1

We have the same for some other commands. For instance shell:watch has an 
implementation in Karaf but also in jline. I would also propose to keep only the 
jline commands.


Regards
JB

On 10/04/2017 11:02 AM, Guillaume Nodet wrote:

I'm working on KARAF-4785
 and
I've already fixed the completion of the native scr commands.  This means
that we'll have some kind of duplication of all scr commands.  Kind of,
because even though they are similar, the output is different.  The native
commands provide a deeper view of the SCR components.

So, should I go ahead and just remove the Karaf specific commands ?

Below is the output of the native commands and then the karaf commands...

Cheers,
Guillaume

*karaf*@root()> scr:list

  BundleId Component Name Default State

 Component Id State  PIDs (Factory PID)

  [  38]   ScrServiceMBean  enabled

 [   4] [active  ]

  [ 145]   org.ops4j.pax.web.deployer.internal.WarDeployer  enabled

 [   3] [active  ]

  [ 151]   org.ops4j.pax.web.service.internal.WhiteboardDtoService  enabled

 [   5] [active  ]

*karaf*@root()> scr:info org.ops4j.pax.web.deployer.internal.WarDeployer



*** Bundle: org.ops4j.pax.web.pax-web-deployer (145)

Component Description:

   Name: org.ops4j.pax.web.deployer.internal.WarDeployer

   Implementation Class: org.ops4j.pax.web.deployer.internal.WarDeployer

   Default State: enabled

   Activation: delayed

   Configuration Policy: optional

   Activate Method: activate

   Deactivate Method: deactivate

   Modified Method: -

   Configuration Pid: [org.ops4j.pax.web.deployer.internal.WarDeployer]

   Services:

 org.apache.felix.fileinstall.ArtifactUrlTransformer

   Service Scope: singleton

   Component Description Properties:

   Component Configuration:

 ComponentId: 3

 State: active

 Component Configuration Properties:

 component.id = 3

 component.name = org.ops4j.pax.web.deployer.internal.WarDeployer


*karaf*@root()> scr:components

ID │ State  │ Component Name

───┼┼

3  │ ACTIVE │ org.ops4j.pax.web.deployer.internal.WarDeployer

5  │ ACTIVE │ org.ops4j.pax.web.service.internal.WhiteboardDtoService

*karaf*@root()> scr:details org.ops4j.pax.web.deployer.internal.WarDeployer

*Component Details*

*  Name: *org.ops4j.pax.web.deployer.internal.WarDeployer

*  State   : *ACTIVE

*References*

*karaf*@root()>






--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Java 9 work

2017-10-04 Thread Jean-Baptiste Onofré 

Agree,

I'm now focused on 4.1.3 (and Cellar/Cave) releases.

In the mean time, I gonna start testing and updates.

Regards
JB

On 10/04/2017 09:57 AM, Guillaume Nodet wrote:

I think we should aim for Karaf 4.3 which would include:
   * Jetty 9.4
   * Pax-Web 6.1
   * Asm 6
   * Xbean 4.6
   * aries proxy, spifly supporting asm 6
   * updated servicemix-specs for Java 9, see KARAF-3518
   * testing...

2017-10-03 17:06 GMT+02:00 Guillaume Nodet :




2017-10-03 16:23 GMT+02:00 Fabian Lange :


Hi Guys,
whats our plan to support Java 9?

Will that be karaf 4.2
5.0
or even 4.1/4.0 backports?



I'd say 4.3




The only real task is writing proper module-info files which should be
easy
for anything osgi.
I would like to look into this.



Those are definitely not needed afaik. What do you have in mind ?

What is needed is:
   * need a GA version of asm 6
   * support from downstream projects like xbean, jetty, undertow, pax-web,
aries-proxy, etc...
   * KARAF-3518 which I think requires a fair amount of work on
servicemix-specs and provide jigsaw modules for some implementations such
as xerces, xalan...
   * If you run master with java9, you should see a warning when the
console is started.  That would require some work in gogo/jline.





Fabian





--

Guillaume Nodet







--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [DISCUSS] Remove Karaf specific SCR commands

2017-10-04 Thread Achim Nierbeck 
+1 for removing the duplicated commands :)

2017-10-04 11:04 GMT+02:00 Christian Schneider :

> +1
>
> Christian
>
> 2017-10-04 11:02 GMT+02:00 Guillaume Nodet :
>
> > I'm working on KARAF-4785
> >  and
> > I've already fixed the completion of the native scr commands.  This means
> > that we'll have some kind of duplication of all scr commands.  Kind of,
> > because even though they are similar, the output is different.  The
> native
> > commands provide a deeper view of the SCR components.
> >
> > So, should I go ahead and just remove the Karaf specific commands ?
> >
> > Below is the output of the native commands and then the karaf commands...
> >
> > Cheers,
> > Guillaume
> >
> > *karaf*@root()> scr:list
> >
> >  BundleId Component Name Default State
> >
> > Component Id State  PIDs (Factory PID)
> >
> >  [  38]   ScrServiceMBean  enabled
> >
> > [   4] [active  ]
> >
> >  [ 145]   org.ops4j.pax.web.deployer.internal.WarDeployer  enabled
> >
> > [   3] [active  ]
> >
> >  [ 151]   org.ops4j.pax.web.service.internal.WhiteboardDtoService
> enabled
> >
> > [   5] [active  ]
> >
> > *karaf*@root()> scr:info org.ops4j.pax.web.deployer.internal.WarDeployer
> >
> >
> >
> > *** Bundle: org.ops4j.pax.web.pax-web-deployer (145)
> >
> > Component Description:
> >
> >   Name: org.ops4j.pax.web.deployer.internal.WarDeployer
> >
> >   Implementation Class: org.ops4j.pax.web.deployer.internal.WarDeployer
> >
> >   Default State: enabled
> >
> >   Activation: delayed
> >
> >   Configuration Policy: optional
> >
> >   Activate Method: activate
> >
> >   Deactivate Method: deactivate
> >
> >   Modified Method: -
> >
> >   Configuration Pid: [org.ops4j.pax.web.deployer.internal.WarDeployer]
> >
> >   Services:
> >
> > org.apache.felix.fileinstall.ArtifactUrlTransformer
> >
> >   Service Scope: singleton
> >
> >   Component Description Properties:
> >
> >   Component Configuration:
> >
> > ComponentId: 3
> >
> > State: active
> >
> > Component Configuration Properties:
> >
> > component.id = 3
> >
> > component.name = org.ops4j.pax.web.deployer.internal.WarDeployer
> >
> >
> > *karaf*@root()> scr:components
> >
> > ID │ State  │ Component Name
> >
> > ───┼┼
> >
> > 3  │ ACTIVE │ org.ops4j.pax.web.deployer.internal.WarDeployer
> >
> > 5  │ ACTIVE │ org.ops4j.pax.web.service.internal.WhiteboardDtoService
> >
> > *karaf*@root()> scr:details org.ops4j.pax.web.deployer.
> > internal.WarDeployer
> >
> > *Component Details*
> >
> > *  Name: *org.ops4j.pax.web.deployer.
> internal.WarDeployer
> >
> > *  State   : *ACTIVE
> >
> > *References*
> >
> > *karaf*@root()>
> >
> >
> >
> >
> > --
> > 
> > Guillaume Nodet
> >
>
>
>
> --
> --
> Christian Schneider
> http://www.liquid-reality.de
>  46=http%3a%2f%2fwww.liquid-reality.de>
>
> Computer Scientist
> http://www.adobe.com
>



-- 

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

Re: Jenkins + Maven + Pax-exam-karaf problem

2017-10-04 Thread Giuseppe Gerla 
Hi JB
on the console I have:

[INFO] Running mypackage.serializer.unit.TestJavaSerializer
[ERROR] Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time
elapsed: 184.204 s <<< FAILURE! - in
mypackage.serializer.unit.TestJavaSerializer
[ERROR] mypackage.serializer.unit.TestJavaSerializer  Time elapsed:
184.202 s  <<< ERROR!
java.lang.RuntimeException: Cannot get the remote bundle context
Caused by: java.rmi.NotBoundException: 6a684c8e-bbea-4b4b-9f57-7776020e6d13

[ERROR] mypackage.serializer.unit.TestJavaSerializer  Time elapsed:
184.204 s  <<< ERROR!
java.lang.RuntimeException: Container never came up
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:369)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:275)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:239)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:160)



In the karaf log I have:

Oct 04, 2017 9:59:33 AM org.apache.karaf.main.Main launch
INFO: Installing and starting initial bundles
Oct 04, 2017 9:59:33 AM org.apache.karaf.main.Main launch
INFO: All initial bundles installed and set to start
Oct 04, 2017 9:59:33 AM org.apache.karaf.main.lock.SimpleFileLock lock
INFO: Trying to lock
/var/lib/jenkins/workspace/itms-server-master-test/itms-integration-tests/itms-eventbus-itest/target/exam/0b7ac007-5aa6-4a7c-8c7a-328145f223c0/lock
Oct 04, 2017 9:59:33 AM org.apache.karaf.main.lock.SimpleFileLock lock
INFO: Lock acquired
Oct 04, 2017 9:59:33 AM org.apache.karaf.main.Main$KarafLockCallback
lockAquired
INFO: Lock acquired. Setting startlevel to 100
2017-10-04 09:59:35,462 | WARN  | FelixStartLevel  | JaxbUtil
   | 8 - org.apache.karaf.features.core - 4.0.9 | Old style feature
file without namespace found (URI:
mvn:org.apache.activemq/activemq-karaf/5.15.0/xml/features). This format is
deprecated and support for it will soon be removed




in attach an extract of effective pom and the abstract class from wich I
derived all my tests.




regards
Giuseppe





2017-10-04 7:09 GMT+02:00 Jean-Baptiste Onofré :

> Surefire >= 2.19 ?
>
> I also depends what you do in the itest. What's your failing tests ?
>
> Regards
> JB
>
>
> On 10/03/2017 04:55 PM, Giuseppe Gerla wrote:
>
>> I don't understand
>> I try to build activemq project on my jenkins machine and integration
>> tests
>> work fine...
>> I use same version of pax-exam, same version of surefire plugin, same
>> version of karaf... why my tests don't work?
>>
>>
>>
>>
>> 2017-10-02 14:32 GMT+02:00 Giuseppe Gerla :
>>
>> Hi JB
>>> I have a big doubt...
>>> If the problem is the surefire plugin vesion, what is the version used by
>>> pax-exam?
>>> 2.19
>>> So although I specify in my pom that version is 2.20.1, what is the
>>> version really used by pax-exam?
>>>
>>>
>>>
>>> Regards
>>> Giuseppe
>>>
>>>
>>>
>>>
>>>
>>> 2017-10-02 12:28 GMT+02:00 Giuseppe Gerla :
>>>
>>> Hi JB
 Unfortunately I tryed on jenkins machine and I have always the same
 problem.
 In the surfire dumpstream file I have this error

 # Created on 2017-10-02T10:03:04.024
 [SUREFIRE] std/in stream corrupted
 java.io.IOException: Command NOOP unexpectedly read Void data with
 length
 4.
 at org.apache.maven.surefire.booter.MasterProcessCommand.decode
 (MasterProcessCommand.java:130)
 at org.apache.maven.surefire.booter.CommandReader$CommandRunnab
 le.run(CommandReader.java:391)
 at java.lang.Thread.run(Thread.java:745)

 The problem is always randomic and occurs if I run with jenkins but also
 if I run command by bash.




 Regards
 Giuseppe



 2017-10-01 21:41 GMT+02:00 Jean-Baptiste Onofré :

 Hi Giuseppe,
>
> just tried to upgrade to surefire 2.20.1 on Karaf, and the itests seem
> overall OK (just an issue with BundleTest that I'm checking now).
>
> Regards
> JB
>
>
> On 10/01/2017 08:12 PM, Giuseppe Gerla wrote:
>
> Hi JB
>> thanks for your support. Today I do some progress...
>> In cxf pom (https://github.com/apache/cxf/blob/master/pom.xml) I
>> found
>> a
>> comment about an issue of surefire plugin (SUREFIRE-1302). Because
>> this
>> issue was solved in 2.20.1 I configure correctly this version (before
>> I
>> have a wrong configuration) and in this way I have success with itests
>> on
>> my pc.
>> Tomorrow I will try in office and I will inform you about results.
>>
>>
>>
>> Thanks
>> Regards
>> Giuseppe
>>
>>
>>
>>
>> 2017-10-01 18:27 GMT+02:00 Jean-Baptiste Onofré :
>>
>> Hi Giuseppe,
>>
>>>
>>> I remember that I got Pax Exam failure with maven-surefire-plugin
>>>

Re: [DISCUSS] Remove Karaf specific SCR commands

2017-10-04 Thread Christian Schneider 
+1

Christian

2017-10-04 11:02 GMT+02:00 Guillaume Nodet :

> I'm working on KARAF-4785
>  and
> I've already fixed the completion of the native scr commands.  This means
> that we'll have some kind of duplication of all scr commands.  Kind of,
> because even though they are similar, the output is different.  The native
> commands provide a deeper view of the SCR components.
>
> So, should I go ahead and just remove the Karaf specific commands ?
>
> Below is the output of the native commands and then the karaf commands...
>
> Cheers,
> Guillaume
>
> *karaf*@root()> scr:list
>
>  BundleId Component Name Default State
>
> Component Id State  PIDs (Factory PID)
>
>  [  38]   ScrServiceMBean  enabled
>
> [   4] [active  ]
>
>  [ 145]   org.ops4j.pax.web.deployer.internal.WarDeployer  enabled
>
> [   3] [active  ]
>
>  [ 151]   org.ops4j.pax.web.service.internal.WhiteboardDtoService  enabled
>
> [   5] [active  ]
>
> *karaf*@root()> scr:info org.ops4j.pax.web.deployer.internal.WarDeployer
>
>
>
> *** Bundle: org.ops4j.pax.web.pax-web-deployer (145)
>
> Component Description:
>
>   Name: org.ops4j.pax.web.deployer.internal.WarDeployer
>
>   Implementation Class: org.ops4j.pax.web.deployer.internal.WarDeployer
>
>   Default State: enabled
>
>   Activation: delayed
>
>   Configuration Policy: optional
>
>   Activate Method: activate
>
>   Deactivate Method: deactivate
>
>   Modified Method: -
>
>   Configuration Pid: [org.ops4j.pax.web.deployer.internal.WarDeployer]
>
>   Services:
>
> org.apache.felix.fileinstall.ArtifactUrlTransformer
>
>   Service Scope: singleton
>
>   Component Description Properties:
>
>   Component Configuration:
>
> ComponentId: 3
>
> State: active
>
> Component Configuration Properties:
>
> component.id = 3
>
> component.name = org.ops4j.pax.web.deployer.internal.WarDeployer
>
>
> *karaf*@root()> scr:components
>
> ID │ State  │ Component Name
>
> ───┼┼
>
> 3  │ ACTIVE │ org.ops4j.pax.web.deployer.internal.WarDeployer
>
> 5  │ ACTIVE │ org.ops4j.pax.web.service.internal.WhiteboardDtoService
>
> *karaf*@root()> scr:details org.ops4j.pax.web.deployer.
> internal.WarDeployer
>
> *Component Details*
>
> *  Name: *org.ops4j.pax.web.deployer.internal.WarDeployer
>
> *  State   : *ACTIVE
>
> *References*
>
> *karaf*@root()>
>
>
>
>
> --
> 
> Guillaume Nodet
>



-- 
-- 
Christian Schneider
http://www.liquid-reality.de


Computer Scientist
http://www.adobe.com

[DISCUSS] Remove Karaf specific SCR commands

2017-10-04 Thread Guillaume Nodet 
I'm working on KARAF-4785
 and
I've already fixed the completion of the native scr commands.  This means
that we'll have some kind of duplication of all scr commands.  Kind of,
because even though they are similar, the output is different.  The native
commands provide a deeper view of the SCR components.

So, should I go ahead and just remove the Karaf specific commands ?

Below is the output of the native commands and then the karaf commands...

Cheers,
Guillaume

*karaf*@root()> scr:list

 BundleId Component Name Default State

Component Id State  PIDs (Factory PID)

 [  38]   ScrServiceMBean  enabled

[   4] [active  ]

 [ 145]   org.ops4j.pax.web.deployer.internal.WarDeployer  enabled

[   3] [active  ]

 [ 151]   org.ops4j.pax.web.service.internal.WhiteboardDtoService  enabled

[   5] [active  ]

*karaf*@root()> scr:info org.ops4j.pax.web.deployer.internal.WarDeployer



*** Bundle: org.ops4j.pax.web.pax-web-deployer (145)

Component Description:

  Name: org.ops4j.pax.web.deployer.internal.WarDeployer

  Implementation Class: org.ops4j.pax.web.deployer.internal.WarDeployer

  Default State: enabled

  Activation: delayed

  Configuration Policy: optional

  Activate Method: activate

  Deactivate Method: deactivate

  Modified Method: -

  Configuration Pid: [org.ops4j.pax.web.deployer.internal.WarDeployer]

  Services:

org.apache.felix.fileinstall.ArtifactUrlTransformer

  Service Scope: singleton

  Component Description Properties:

  Component Configuration:

ComponentId: 3

State: active

Component Configuration Properties:

component.id = 3

component.name = org.ops4j.pax.web.deployer.internal.WarDeployer


*karaf*@root()> scr:components

ID │ State  │ Component Name

───┼┼

3  │ ACTIVE │ org.ops4j.pax.web.deployer.internal.WarDeployer

5  │ ACTIVE │ org.ops4j.pax.web.service.internal.WhiteboardDtoService

*karaf*@root()> scr:details org.ops4j.pax.web.deployer.internal.WarDeployer

*Component Details*

*  Name: *org.ops4j.pax.web.deployer.internal.WarDeployer

*  State   : *ACTIVE

*References*

*karaf*@root()>




-- 

Guillaume Nodet

Re: Java 9 work

2017-10-04 Thread Guillaume Nodet 
I've reopened PAXWEB-1047  for
Pax-Web 6.1 upgrade to asm 6 / xbean 4.6 ...

2017-10-04 9:57 GMT+02:00 Guillaume Nodet :

> I think we should aim for Karaf 4.3 which would include:
>   * Jetty 9.4
>   * Pax-Web 6.1
>   * Asm 6
>   * Xbean 4.6
>   * aries proxy, spifly supporting asm 6
>   * updated servicemix-specs for Java 9, see KARAF-3518
>   * testing...
>
> 2017-10-03 17:06 GMT+02:00 Guillaume Nodet :
>
>>
>>
>> 2017-10-03 16:23 GMT+02:00 Fabian Lange :
>>
>>> Hi Guys,
>>> whats our plan to support Java 9?
>>>
>>> Will that be karaf 4.2
>>> 5.0
>>> or even 4.1/4.0 backports?
>>>
>>
>> I'd say 4.3
>>
>>
>>>
>>> The only real task is writing proper module-info files which should be
>>> easy
>>> for anything osgi.
>>> I would like to look into this.
>>>
>>
>> Those are definitely not needed afaik. What do you have in mind ?
>>
>> What is needed is:
>>   * need a GA version of asm 6
>>   * support from downstream projects like xbean, jetty, undertow,
>> pax-web, aries-proxy, etc...
>>   * KARAF-3518 which I think requires a fair amount of work on
>> servicemix-specs and provide jigsaw modules for some implementations such
>> as xerces, xalan...
>>   * If you run master with java9, you should see a warning when the
>> console is started.  That would require some work in gogo/jline.
>>
>>
>>>
>>>
>>> Fabian
>>>
>>
>>
>>
>> --
>> 
>> Guillaume Nodet
>>
>>
>
>
> --
> 
> Guillaume Nodet
>
>


-- 

Guillaume Nodet

Re: Java 9 work

2017-10-04 Thread Guillaume Nodet 
I think we should aim for Karaf 4.3 which would include:
  * Jetty 9.4
  * Pax-Web 6.1
  * Asm 6
  * Xbean 4.6
  * aries proxy, spifly supporting asm 6
  * updated servicemix-specs for Java 9, see KARAF-3518
  * testing...

2017-10-03 17:06 GMT+02:00 Guillaume Nodet :

>
>
> 2017-10-03 16:23 GMT+02:00 Fabian Lange :
>
>> Hi Guys,
>> whats our plan to support Java 9?
>>
>> Will that be karaf 4.2
>> 5.0
>> or even 4.1/4.0 backports?
>>
>
> I'd say 4.3
>
>
>>
>> The only real task is writing proper module-info files which should be
>> easy
>> for anything osgi.
>> I would like to look into this.
>>
>
> Those are definitely not needed afaik. What do you have in mind ?
>
> What is needed is:
>   * need a GA version of asm 6
>   * support from downstream projects like xbean, jetty, undertow, pax-web,
> aries-proxy, etc...
>   * KARAF-3518 which I think requires a fair amount of work on
> servicemix-specs and provide jigsaw modules for some implementations such
> as xerces, xalan...
>   * If you run master with java9, you should see a warning when the
> console is started.  That would require some work in gogo/jline.
>
>
>>
>>
>> Fabian
>>
>
>
>
> --
> 
> Guillaume Nodet
>
>


-- 

Guillaume Nodet

Re: Java 9 work

2017-10-04 Thread Jean-Baptiste Onofré 
Good point. I only checked asm-all.

Yeah, it makes sense to use small jar files.

Regards
JB

On Oct 4, 2017, 08:58, at 08:58, Guillaume Nodet  wrote:
>It's actually on central, but only small jars are deployed:
>  http://repo1.maven.org/maven2/org/ow2/asm/asm/6.0/
>The one we usually use has not been deployed:
>  http://repo1.maven.org/maven2/org/ow2/asm/asm-all/
>
>It's not a problem in itself, we can easily switch to the smaller jars.
>
>2017-10-04 8:16 GMT+02:00 Jean-Baptiste Onofré :
>
>> It's not url we are using for central.We use
>repo.maven.apache.org/maven2.
>>
>> That explains why I found only alpha and beta there.
>>
>> It would mean that we have to add this new repo for ASM 6.
>> Regards
>> JB
>>
>> On Oct 4, 2017, 08:14, at 08:14, Fabian Lange
>
>> wrote:
>> >http://central.maven.org/maven2/org/ow2/asm/asm/6.0/asm-6.0.jar
>> >
>> >Sent from my iPhone
>> >
>> >> On 3. Oct 2017, at 23:12, Jean-Baptiste Onofré 
>> >wrote:
>> >>
>> >> That's not central, right ?
>> >>
>> >> Regards
>> >> JB
>> >>
>> >>> On Oct 4, 2017, 08:08, at 08:08, Fabian Lange
>> > wrote:
>> >>> https://mvnrepository.com/artifact/org.ow2.asm/asm/6.0
>> >>>
>> >>> Sent from my iPhone
>> >>>
>>  On 3. Oct 2017, at 22:08, Jean-Baptiste Onofré 
>> >>> wrote:
>> 
>>  Hi,
>> 
>>  there's no GA on Central, only 6.0 ALPHA and 6.0 BETA.
>> 
>>  Regards
>>  JB
>> 
>> > On 10/03/2017 05:51 PM, Fabian Lange wrote:
>> > Its actually on central
>> > Fabian
>> > Sent from my iPhone
>> >> On 3. Oct 2017, at 08:47, Guillaume Nodet 
>> >>> wrote:
>> >>
>> >> Good catch, I only looked on maven central...
>> >> I guess we need to ask for an upload there... Wanna take care
>of
>> >it
>> >>> ?
>> >>
>> >> Guillaume
>> >>
>> >> 2017-10-03 17:13 GMT+02:00 Fabian Lange
>> >>> :
>> >>
>> >>> Asm 6 is GA now
>> >>> Fabiann
>> >>>
>> >>> Sent from my iPhone
>> >>>
>>  On 3. Oct 2017, at 08:06, Guillaume Nodet
>
>> >>> wrote:
>> 
>>  2017-10-03 16:23 GMT+02:00 Fabian Lange
>> >>> :
>> 
>> > Hi Guys,
>> > whats our plan to support Java 9?
>> >
>> > Will that be karaf 4.2
>> > 5.0
>> > or even 4.1/4.0 backports?
>> >
>> 
>>  I'd say 4.3
>> 
>> 
>> >
>> > The only real task is writing proper module-info files
>which
>> >>> should be
>> >>> easy
>> > for anything osgi.
>> > I would like to look into this.
>> >
>> 
>>  Those are definitely not needed afaik. What do you have in
>mind
>> >?
>> 
>>  What is needed is:
>>  * need a GA version of asm 6
>>  * support from downstream projects like xbean, jetty,
>undertow,
>> >>> pax-web,
>>  aries-proxy, etc...
>>  * KARAF-3518 which I think requires a fair amount of work on
>>  servicemix-specs and provide jigsaw modules for some
>> >>> implementations such
>>  as xerces, xalan...
>>  * If you run master with java9, you should see a warning
>when
>> >the
>> >>> console
>>  is started.  That would require some work in gogo/jline.
>> 
>> 
>> >
>> >
>> > Fabian
>> >
>> 
>> 
>> 
>>  --
>>  
>>  Guillaume Nodet
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> 
>> >> Guillaume Nodet
>> 
>>  --
>>  Jean-Baptiste Onofré
>>  jbono...@apache.org
>>  http://blog.nanthrax.net
>>  Talend - http://www.talend.com
>>
>
>
>
>--
>
>Guillaume Nodet

Re: Java 9 work

2017-10-04 Thread Guillaume Nodet 
It's actually on central, but only small jars are deployed:
  http://repo1.maven.org/maven2/org/ow2/asm/asm/6.0/
The one we usually use has not been deployed:
  http://repo1.maven.org/maven2/org/ow2/asm/asm-all/

It's not a problem in itself, we can easily switch to the smaller jars.

2017-10-04 8:16 GMT+02:00 Jean-Baptiste Onofré :

> It's not url we are using for central.We use repo.maven.apache.org/maven2.
>
> That explains why I found only alpha and beta there.
>
> It would mean that we have to add this new repo for ASM 6.
> Regards
> JB
>
> On Oct 4, 2017, 08:14, at 08:14, Fabian Lange 
> wrote:
> >http://central.maven.org/maven2/org/ow2/asm/asm/6.0/asm-6.0.jar
> >
> >Sent from my iPhone
> >
> >> On 3. Oct 2017, at 23:12, Jean-Baptiste Onofré 
> >wrote:
> >>
> >> That's not central, right ?
> >>
> >> Regards
> >> JB
> >>
> >>> On Oct 4, 2017, 08:08, at 08:08, Fabian Lange
> > wrote:
> >>> https://mvnrepository.com/artifact/org.ow2.asm/asm/6.0
> >>>
> >>> Sent from my iPhone
> >>>
>  On 3. Oct 2017, at 22:08, Jean-Baptiste Onofré 
> >>> wrote:
> 
>  Hi,
> 
>  there's no GA on Central, only 6.0 ALPHA and 6.0 BETA.
> 
>  Regards
>  JB
> 
> > On 10/03/2017 05:51 PM, Fabian Lange wrote:
> > Its actually on central
> > Fabian
> > Sent from my iPhone
> >> On 3. Oct 2017, at 08:47, Guillaume Nodet 
> >>> wrote:
> >>
> >> Good catch, I only looked on maven central...
> >> I guess we need to ask for an upload there... Wanna take care of
> >it
> >>> ?
> >>
> >> Guillaume
> >>
> >> 2017-10-03 17:13 GMT+02:00 Fabian Lange
> >>> :
> >>
> >>> Asm 6 is GA now
> >>> Fabiann
> >>>
> >>> Sent from my iPhone
> >>>
>  On 3. Oct 2017, at 08:06, Guillaume Nodet 
> >>> wrote:
> 
>  2017-10-03 16:23 GMT+02:00 Fabian Lange
> >>> :
> 
> > Hi Guys,
> > whats our plan to support Java 9?
> >
> > Will that be karaf 4.2
> > 5.0
> > or even 4.1/4.0 backports?
> >
> 
>  I'd say 4.3
> 
> 
> >
> > The only real task is writing proper module-info files which
> >>> should be
> >>> easy
> > for anything osgi.
> > I would like to look into this.
> >
> 
>  Those are definitely not needed afaik. What do you have in mind
> >?
> 
>  What is needed is:
>  * need a GA version of asm 6
>  * support from downstream projects like xbean, jetty, undertow,
> >>> pax-web,
>  aries-proxy, etc...
>  * KARAF-3518 which I think requires a fair amount of work on
>  servicemix-specs and provide jigsaw modules for some
> >>> implementations such
>  as xerces, xalan...
>  * If you run master with java9, you should see a warning when
> >the
> >>> console
>  is started.  That would require some work in gogo/jline.
> 
> 
> >
> >
> > Fabian
> >
> 
> 
> 
>  --
>  
>  Guillaume Nodet
> >>>
> >>
> >>
> >>
> >> --
> >> 
> >> Guillaume Nodet
> 
>  --
>  Jean-Baptiste Onofré
>  jbono...@apache.org
>  http://blog.nanthrax.net
>  Talend - http://www.talend.com
>



-- 

Guillaume Nodet

Re: Java 9 work

2017-10-04 Thread Jean-Baptiste Onofré 
It's not url we are using for central.We use repo.maven.apache.org/maven2.

That explains why I found only alpha and beta there.

It would mean that we have to add this new repo for ASM 6.
Regards
JB

On Oct 4, 2017, 08:14, at 08:14, Fabian Lange  
wrote:
>http://central.maven.org/maven2/org/ow2/asm/asm/6.0/asm-6.0.jar
>
>Sent from my iPhone
>
>> On 3. Oct 2017, at 23:12, Jean-Baptiste Onofré 
>wrote:
>>
>> That's not central, right ?
>> 
>> Regards
>> JB
>>
>>> On Oct 4, 2017, 08:08, at 08:08, Fabian Lange
> wrote:
>>> https://mvnrepository.com/artifact/org.ow2.asm/asm/6.0
>>>
>>> Sent from my iPhone
>>>
 On 3. Oct 2017, at 22:08, Jean-Baptiste Onofré 
>>> wrote:

 Hi,

 there's no GA on Central, only 6.0 ALPHA and 6.0 BETA.

 Regards
 JB

> On 10/03/2017 05:51 PM, Fabian Lange wrote:
> Its actually on central
> Fabian
> Sent from my iPhone
>> On 3. Oct 2017, at 08:47, Guillaume Nodet 
>>> wrote:
>>
>> Good catch, I only looked on maven central...
>> I guess we need to ask for an upload there... Wanna take care of
>it
>>> ?
>>
>> Guillaume
>>
>> 2017-10-03 17:13 GMT+02:00 Fabian Lange
>>> :
>>
>>> Asm 6 is GA now
>>> Fabiann
>>>
>>> Sent from my iPhone
>>>
 On 3. Oct 2017, at 08:06, Guillaume Nodet 
>>> wrote:

 2017-10-03 16:23 GMT+02:00 Fabian Lange
>>> :

> Hi Guys,
> whats our plan to support Java 9?
>
> Will that be karaf 4.2
> 5.0
> or even 4.1/4.0 backports?
>

 I'd say 4.3


>
> The only real task is writing proper module-info files which
>>> should be
>>> easy
> for anything osgi.
> I would like to look into this.
>

 Those are definitely not needed afaik. What do you have in mind
>?

 What is needed is:
 * need a GA version of asm 6
 * support from downstream projects like xbean, jetty, undertow,
>>> pax-web,
 aries-proxy, etc...
 * KARAF-3518 which I think requires a fair amount of work on
 servicemix-specs and provide jigsaw modules for some
>>> implementations such
 as xerces, xalan...
 * If you run master with java9, you should see a warning when
>the
>>> console
 is started.  That would require some work in gogo/jline.


>
>
> Fabian
>



 --
 
 Guillaume Nodet
>>>
>>
>>
>>
>> --
>> 
>> Guillaume Nodet

 --
 Jean-Baptiste Onofré
 jbono...@apache.org
 http://blog.nanthrax.net
 Talend - http://www.talend.com

Re: Java 9 work

2017-10-04 Thread Fabian Lange 
http://central.maven.org/maven2/org/ow2/asm/asm/6.0/asm-6.0.jar

Sent from my iPhone

> On 3. Oct 2017, at 23:12, Jean-Baptiste Onofré  wrote:
> 
> That's not central, right ?
> 
> Regards
> JB
> 
>> On Oct 4, 2017, 08:08, at 08:08, Fabian Lange  
>> wrote:
>> https://mvnrepository.com/artifact/org.ow2.asm/asm/6.0
>> 
>> Sent from my iPhone
>> 
>>> On 3. Oct 2017, at 22:08, Jean-Baptiste Onofré 
>> wrote:
>>> 
>>> Hi,
>>> 
>>> there's no GA on Central, only 6.0 ALPHA and 6.0 BETA.
>>> 
>>> Regards
>>> JB
>>> 
 On 10/03/2017 05:51 PM, Fabian Lange wrote:
 Its actually on central
 Fabian
 Sent from my iPhone
> On 3. Oct 2017, at 08:47, Guillaume Nodet 
>> wrote:
> 
> Good catch, I only looked on maven central...
> I guess we need to ask for an upload there... Wanna take care of it
>> ?
> 
> Guillaume
> 
> 2017-10-03 17:13 GMT+02:00 Fabian Lange
>> :
> 
>> Asm 6 is GA now
>> Fabiann
>> 
>> Sent from my iPhone
>> 
>>> On 3. Oct 2017, at 08:06, Guillaume Nodet 
>> wrote:
>>> 
>>> 2017-10-03 16:23 GMT+02:00 Fabian Lange
>> :
>>> 
 Hi Guys,
 whats our plan to support Java 9?
 
 Will that be karaf 4.2
 5.0
 or even 4.1/4.0 backports?
 
>>> 
>>> I'd say 4.3
>>> 
>>> 
 
 The only real task is writing proper module-info files which
>> should be
>> easy
 for anything osgi.
 I would like to look into this.
 
>>> 
>>> Those are definitely not needed afaik. What do you have in mind ?
>>> 
>>> What is needed is:
>>> * need a GA version of asm 6
>>> * support from downstream projects like xbean, jetty, undertow,
>> pax-web,
>>> aries-proxy, etc...
>>> * KARAF-3518 which I think requires a fair amount of work on
>>> servicemix-specs and provide jigsaw modules for some
>> implementations such
>>> as xerces, xalan...
>>> * If you run master with java9, you should see a warning when the
>> console
>>> is started.  That would require some work in gogo/jline.
>>> 
>>> 
 
 
 Fabian
 
>>> 
>>> 
>>> 
>>> --
>>> 
>>> Guillaume Nodet
>> 
> 
> 
> 
> -- 
> 
> Guillaume Nodet
>>> 
>>> -- 
>>> Jean-Baptiste Onofré
>>> jbono...@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com

Re: Java 9 work

2017-10-04 Thread Jean-Baptiste Onofré 
That's not central, right ?

Regards
JB

On Oct 4, 2017, 08:08, at 08:08, Fabian Lange  
wrote:
>https://mvnrepository.com/artifact/org.ow2.asm/asm/6.0
>
>Sent from my iPhone
>
>> On 3. Oct 2017, at 22:08, Jean-Baptiste Onofré 
>wrote:
>>
>> Hi,
>>
>> there's no GA on Central, only 6.0 ALPHA and 6.0 BETA.
>>
>> Regards
>> JB
>>
>>> On 10/03/2017 05:51 PM, Fabian Lange wrote:
>>> Its actually on central
>>> Fabian
>>> Sent from my iPhone
 On 3. Oct 2017, at 08:47, Guillaume Nodet 
>wrote:

 Good catch, I only looked on maven central...
 I guess we need to ask for an upload there... Wanna take care of it
>?

 Guillaume

 2017-10-03 17:13 GMT+02:00 Fabian Lange
>:

> Asm 6 is GA now
> Fabiann
>
> Sent from my iPhone
>
>> On 3. Oct 2017, at 08:06, Guillaume Nodet 
>wrote:
>>
>> 2017-10-03 16:23 GMT+02:00 Fabian Lange
>:
>>
>>> Hi Guys,
>>> whats our plan to support Java 9?
>>>
>>> Will that be karaf 4.2
>>> 5.0
>>> or even 4.1/4.0 backports?
>>>
>>
>> I'd say 4.3
>>
>>
>>>
>>> The only real task is writing proper module-info files which
>should be
> easy
>>> for anything osgi.
>>> I would like to look into this.
>>>
>>
>> Those are definitely not needed afaik. What do you have in mind ?
>>
>> What is needed is:
>> * need a GA version of asm 6
>> * support from downstream projects like xbean, jetty, undertow,
>pax-web,
>> aries-proxy, etc...
>> * KARAF-3518 which I think requires a fair amount of work on
>> servicemix-specs and provide jigsaw modules for some
>implementations such
>> as xerces, xalan...
>> * If you run master with java9, you should see a warning when the
> console
>> is started.  That would require some work in gogo/jline.
>>
>>
>>>
>>>
>>> Fabian
>>>
>>
>>
>>
>> --
>> 
>> Guillaume Nodet
>



 --
 
 Guillaume Nodet
>>
>> --
>> Jean-Baptiste Onofré
>> jbono...@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com