[issues] Commented: (PAXWEB-97) Use of HttpContext to determine filter invocation makes filters unusable with OSGi service spec example section 102.3

[ http://issues.ops4j.org/jira/browse/PAXWEB-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_11449 ] Niclas Hedhman commented on PAXWEB-97: -- well, first of all registering a filter is not part of the OSGi spec at all.

[issues] Created: (PAXWEB-97) Use of HttpContext to determine filter invocation makes filters unusable with OSGi service spec example section 102.3

Use of HttpContext to determine filter invocation makes filters unusable with OSGi service spec example section 102.3 -- Key: PAXWEB-97 URL: http:

Re: [PAXRUNNER] Loader constraint violation when deployingprovisioningand scanner-dir bundles standalone

A very simple way to test them is to use pax runner itself to test them: pax-run mvn:org.ops4j.pax.runner/pax-runner-provision/[EMAIL PROTECTED] mvn:org.ops4j.pax.runner/pax-runner-scanner-dir/[EMAIL PROTECTED] mvn:org.ops4j.pax.runner/pax-runner-provision-console/0.13.0-SNAPSHOT "--p=e" --noconso

Re: [PAXRUNNER] Loader constraint violation when deployingprovisioningand scanner-dir bundles standalone

I resolved it. Can you please test it (I did) using the snapshot version 0.13.0-SNAPSHOt from our ops4j snapshot repository? On Tue, Jul 8, 2008 at 11:42 PM, Olaf Bergner <[EMAIL PROTECTED]> wrote: > Done: http://issues.ops4j.org/jira/browse/PAXRUNNER-152 > > Please let me know if you need any fur

AW: [PAXRUNNER] Loader constraint violation when deployingprovisioningand scanner-dir bundles standalone

Done: http://issues.ops4j.org/jira/browse/PAXRUNNER-152 Please let me know if you need any further information. Cheers, Olaf > -Ursprüngliche Nachricht- > Von: [EMAIL PROTECTED] [mailto:general- > [EMAIL PROTECTED] Im Auftrag von Alin Dreghiciu > Gesendet: Dienstag, 8. Juli 2008 22:35 >

[issues] Created: (PAXRUNNER-152) Loader constraint violation when using pax-runner-provision and pax-runner-scanner-dir standalone

Loader constraint violation when using pax-runner-provision and pax-runner-scanner-dir standalone - Key: PAXRUNNER-152 URL: http://issues.ops4j.org/jira/browse/PAXRUNN

Re: Spring-DM doesn't work

Thanx for taking the time to do the run with the debuging enabled. I will take a look and get back to you. On Tue, Jul 8, 2008 at 10:28 PM, Michael Greifeneder <[EMAIL PROTECTED]> wrote: > On Monday 07 July 2008 22:20:27 Alin Dreghiciu wrote: >> Can you set up the pax runner "log" option to trace

Re: [PAXRUNNER] Loader constraint violation when deploying provisioningand scanner-dir bundles standalone

I could replicate your problem. I is a long time since I did not used the two as a separate bundles not as part of Pax Runer so I did not saw this behavior. Plase raise an issue on jira so you get notified when is solved, thing that should happen very soon. On Tue, Jul 8, 2008 at 10:08 PM, Olaf Be

Re: Spring-DM doesn't work

On Monday 07 July 2008 22:20:27 Alin Dreghiciu wrote: > Can you set up the pax runner "log" option to trace and run again? Hello, Here is my output attached. It's on a new project which was created with pax-create-project. Regards, Mike [INFO] Scanning for projects... [INFO] Reactor build orde

Re: Spring-DM doesn't work

Hello, I tested with option --Drunner=0.9.0 and adding both repositories to my project. Both ways worked. So I think you are right with your conclusions. I don't want investigate why it works in an empty directory. It was something I find while bug hunting. If it works within a project I don'

AW: [PAXRUNNER] Loader constraint violation when deploying provisioningand scanner-dir bundles standalone

I just verified that I get the exact same error when starting equinox via java -jar org.eclipse.osgi-3.4.0.jar -console and installing pax-runner-provision-0.12.0.jar and pax-runner-scanner-dir-0.12.0.jar manually using the console. So this problem cannot be attributed to my running equinox insid

[issues] Commented: (PAXLOGGING-31) Pax Logging unusable with SpringSecurity 2.0.2.A

[ http://issues.ops4j.org/jira/browse/PAXLOGGING-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_11448 ] Jens Borrmann commented on PAXLOGGING-31: - The new versions integrate well into our environment. Our tests run

Re: Spring-DM doesn't work

2008/7/8 Alin Dreghiciu <[EMAIL PROTECTED]>: > sping-dm does not add any repo. The spring repos are already on the > default list. > If you specify extra repos and still want to use the default ones you > have to start the repo list with a + (plus). See here: > > http://wiki.ops4j.org/confluence/d

Re: Spring-DM doesn't work

sping-dm does not add any repo. The spring repos are already on the default list. If you specify extra repos and still want to use the default ones you have to start the repo list with a + (plus). See here: http://wiki.ops4j.org/confluence/display/ops4j/Pax+URL+-+mvn#PaxURL-mvn-repositories On Tue

[issues] Commented: (PAXLOGGING-31) Pax Logging unusable with SpringSecurity 2.0.2.A

[ http://issues.ops4j.org/jira/browse/PAXLOGGING-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_11447 ] Niclas Hedhman commented on PAXLOGGING-31: -- I have committed an initial version of this. Can you check out Pax

[issues] Commented: (PAXLOGGING-31) Pax Logging unusable with SpringSecurity 2.0.2.A

[ http://issues.ops4j.org/jira/browse/PAXLOGGING-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_11446 ] Niclas Hedhman commented on PAXLOGGING-31: -- Well, I found it... Funny enough JA-Sig CAS depends on OpenSAML 1

[issues] Commented: (PAXLOGGING-31) Pax Logging unusable with SpringSecurity 2.0.2.A

[ http://issues.ops4j.org/jira/browse/PAXLOGGING-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_11445 ] Jens Borrmann commented on PAXLOGGING-31: - Spring Security 2.0.3 depends on jasic 3.1.3, which is not yet (publ

[issues] Commented: (PAXLOGGING-31) Pax Logging unusable with SpringSecurity 2.0.2.A

[ http://issues.ops4j.org/jira/browse/PAXLOGGING-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_11444 ] Niclas Hedhman commented on PAXLOGGING-31: -- Can you quickly test Spring Security 2.0.3, since they seem to hav

[issues] Commented: (PAXLOGGING-31) Pax Logging unusable with SpringSecurity 2.0.2.A

[ http://issues.ops4j.org/jira/browse/PAXLOGGING-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_11443 ] Jens Borrmann commented on PAXLOGGING-31: - Okay, I was a bit unprecise. The bundle causing dependencies on log4

Re: Spring-DM doesn't work

2008/7/8 Alin Dreghiciu <[EMAIL PROTECTED]>: > Can you set up the pax runner "log" option to trace and run again? > You can do that by adding the following to your maven pax plugin something > like: > > org.ops4j > maven-pax-plugin > > > --log=TRACE >

[issues] Commented: (PAXLOGGING-31) Pax Logging unusable with SpringSecurity 2.0.2.A

[ http://issues.ops4j.org/jira/browse/PAXLOGGING-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_11442 ] Niclas Hedhman commented on PAXLOGGING-31: -- Interestingly enough... BND version 0.0.227 was used to generate t

[issues] Commented: (PAXLOGGING-31) Pax Logging unusable with SpringSecurity 2.0.2.A

[ http://issues.ops4j.org/jira/browse/PAXLOGGING-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_11441 ] Niclas Hedhman commented on PAXLOGGING-31: -- I think the description of the issue is incorrect. Spring Security

[issues] Created: (PAXLOGGING-31) Pax Logging unusable with SpringSecurity 2.0.2.A

Pax Logging unusable with SpringSecurity 2.0.2.A Key: PAXLOGGING-31 URL: http://issues.ops4j.org/jira/browse/PAXLOGGING-31 Project: Pax Logging Issue Type: Bug Affects Versions: 1.1.1