[
https://issues.apache.org/jira/browse/FELIX-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881852#action_12881852
]
Richard S. Hall commented on FELIX-2437:
I have reproduced this issue and will look
[
https://issues.apache.org/jira/browse/FELIX-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall updated FELIX-2437:
---
Fix Version/s: framework-3.2.0
> Deadlock on refrsh Import and refresh
>
[
https://issues.apache.org/jira/browse/FELIX-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall reassigned FELIX-2437:
--
Assignee: Richard S. Hall
> Deadlock on refrsh Import and refresh
> ---
[
https://issues.apache.org/jira/browse/FELIX-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated FELIX-2440:
---
Fix Version/s: karaf 1.8.0
> [Karaf] JDK 1.5 build issue - FeaturesServiceTest failure
>
[
https://issues.apache.org/jira/browse/FELIX-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jamie goodyear resolved FELIX-2440.
---
Resolution: Fixed
JDK 1.5 users will now no longer see FeaturesServiceTest failure, however t
[
https://issues.apache.org/jira/browse/FELIX-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881840#action_12881840
]
Jamie goodyear commented on FELIX-2440:
---
Sending
features/core/src/main/java/
[This email is really intended for Felix developers unlike my previous
couple of emails.]
Hi,
In my environment, we have multiple OSGi/HTTP Service available - one
per HTTP port. I had brief look at Felix Web Console code and did not
find any extension point to customize selection of HTTP Ser
[
https://issues.apache.org/jira/browse/FELIX-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881830#action_12881830
]
Guillaume Nodet commented on FELIX-2441:
Yeah, at least the wrapper layer would buy
Once again sorry for sending to wrong alias. I think I should call it a
day. I am really sorry. This time I realized just after hitting the send
button and tried to cancel, but it was too late. Pl. excuse me. I will
be more careful from now on.
Sahoo
On Thursday 24 June 2010 12:02 AM, Sanjeeb
If you have a glassfish workspace, then to run OSGi web console, you
need to do the following:
cd $WS/v3
cp
packager/glassfish-osgi-http/target/stage/glassfishv3/glassfish/modules/autostart/osgi-http.jar
packager/glassfish-osgi-admin-console/target/stage/glassfishv3/glassfish/modules/autostart/
I am sorry for sending to wrong alias. Thanks for pointing it out.
Sahoo
On Wednesday 23 June 2010 11:37 PM, Richard S. Hall wrote:
Did you get the correct dev@ mailing list?
-> richard
On 6/23/10 14:04, Sanjeeb Sahoo wrote:
This is a follow up to our discussion in today's gf-engg. meeting. T
Did you get the correct dev@ mailing list?
-> richard
On 6/23/10 14:04, Sanjeeb Sahoo wrote:
This is a follow up to our discussion in today's gf-engg. meeting. To
know the status of OSGi bundles just before the server startup is
complete, please set following property in logging.properties fi
This is a follow up to our discussion in today's gf-engg. meeting. To
know the status of OSGi bundles just before the server startup is
complete, please set following property in logging.properties file:
javax.enterprise.system.core.level=FINE
before starting server. You shall see the module s
On 6/23/10 13:11, Guillaume Nodet wrote:
On Wed, Jun 23, 2010 at 18:39, Richard S. Hall wrote:
On 6/23/10 12:08, Guillaume Nodet wrote:
Letting a project evolve and breaking the compatibility for the sake
of it is a different problem. In that case, your modifications could
have bee
On Wed, Jun 23, 2010 at 18:39, Richard S. Hall wrote:
> On 6/23/10 12:08, Guillaume Nodet wrote:
>>
>> Letting a project evolve and breaking the compatibility for the sake
>> of it is a different problem. In that case, your modifications could
>> have been done without infringing the IP and keep
[
https://issues.apache.org/jira/browse/FELIX-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881741#action_12881741
]
Richard S. Hall edited comment on FELIX-2441 at 6/23/10 1:00 PM:
I might be misunderstood here, I do intend to introduce the annotations in the
RFC for discussion in Ottawa, they do seem to have a lot of value. If they do
not provide certain features that you want to provide then please provide
feedback. However, I've to take a deeper look at all the details
[
https://issues.apache.org/jira/browse/FELIX-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881740#action_12881740
]
Jamie goodyear commented on FELIX-2440:
---
Updated bug description into two separate is
[
https://issues.apache.org/jira/browse/FELIX-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jamie goodyear reassigned FELIX-2440:
-
Assignee: Jamie goodyear
> [Karaf] JDK 1.5 build issue - FeaturesServiceTest failure
> --
[
https://issues.apache.org/jira/browse/FELIX-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881741#action_12881741
]
Richard S. Hall commented on FELIX-2441:
However, if we can add package the command
[
https://issues.apache.org/jira/browse/FELIX-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881737#action_12881737
]
Richard S. Hall commented on FELIX-2441:
This doesn't make sense because it just de
[Karaf] JDK 1.5 build issue - StandardEmitterMBean is JDK 1.6 specific
--
Key: FELIX-2442
URL: https://issues.apache.org/jira/browse/FELIX-2442
Project: Felix
Issue Type: Bu
[
https://issues.apache.org/jira/browse/FELIX-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jamie goodyear updated FELIX-2440:
--
Summary: [Karaf] JDK 1.5 build issue - FeaturesServiceTest failure
(was: [Karaf] JDK 1.5 b
On 6/23/10 12:08, Guillaume Nodet wrote:
Letting a project evolve and breaking the compatibility for the sake
of it is a different problem. In that case, your modifications could
have been done without infringing the IP and keeping backward
compatibility.
Given how easy is it, i'm going to do t
[
https://issues.apache.org/jira/browse/FELIX-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jamie goodyear updated FELIX-2440:
--
Attachment: FELIX-2440-part1.patch
File: FELIX-2440-part1.patch
Contains a fix for a failing u
Restore backward compatibility on gogo
--
Key: FELIX-2441
URL: https://issues.apache.org/jira/browse/FELIX-2441
Project: Felix
Issue Type: Task
Components: Gogo Runtime
Reporter: Guil
Letting a project evolve and breaking the compatibility for the sake
of it is a different problem. In that case, your modifications could
have been done without infringing the IP and keeping backward
compatibility.
Given how easy is it, i'm going to do that in trunk.I'd rather
have those as a
[Karaf] JDK 1.5 build issues
Key: FELIX-2440
URL: https://issues.apache.org/jira/browse/FELIX-2440
Project: Felix
Issue Type: Bug
Components: Karaf
Environment: Java 1.5
Reporter: J
On 6/23/10 11:22, Guillaume Nodet wrote:
On Wed, Jun 23, 2010 at 16:38, Peter Kriens wrote:
As the author of the RFC 147 and original author of the gogo code I concur with
Richard and the work we did is very much aligned with the next version of the
RFC which will be discussed in Ottawa.
On Wed, Jun 23, 2010 at 16:38, Peter Kriens wrote:
> As the author of the RFC 147 and original author of the gogo code I concur
> with Richard and the work we did is very much aligned with the next version
> of the RFC which will be discussed in Ottawa. The original RFC has very
> strong focus
As the author of the RFC 147 and original author of the gogo code I concur with
Richard and the work we did is very much aligned with the next version of the
RFC which will be discussed in Ottawa. The original RFC has very strong focus
on allowing existing objects (instances!) to very cheaply pr
On 6/23/10 10:14, Guillaume Nodet wrote:
We actually did discuss that on skype. The initial thoughts were to
modify and reuse all the existing karaf commands and make them a bit
more generic, and at some point you found some naming issues on the
interface and annotations defined. I was not awar
[
https://issues.apache.org/jira/browse/FELIX-2436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881701#action_12881701
]
Peter Lawrey commented on FELIX-2436:
-
Using the last modified date of the directory cu
We actually did discuss that on skype. The initial thoughts were to
modify and reuse all the existing karaf commands and make them a bit
more generic, and at some point you found some naming issues on the
interface and annotations defined. I was not aware you were to rewrite
everything from scrat
On 6/23/10 9:45, Guillaume Nodet wrote:
On Wed, Jun 23, 2010 at 15:37, Richard S. Hall wrote:
On 6/23/10 9:14, Guillaume Nodet wrote:
On Wed, Jun 23, 2010 at 14:31, Richard S. Hall
wrote:
On 6/23/10 5:45, Guillaume Sauthier wrote:
Hi guys
Maybe I react after
On Wed, Jun 23, 2010 at 15:37, Richard S. Hall wrote:
> On 6/23/10 9:14, Guillaume Nodet wrote:
>>
>> On Wed, Jun 23, 2010 at 14:31, Richard S. Hall
>> wrote:
>>
>>>
>>> On 6/23/10 5:45, Guillaume Sauthier wrote:
>>>
Hi guys
Maybe I react after the battle but, I was quite happ
On 6/23/10 9:14, Guillaume Nodet wrote:
On Wed, Jun 23, 2010 at 14:31, Richard S. Hall wrote:
On 6/23/10 5:45, Guillaume Sauthier wrote:
Hi guys
Maybe I react after the battle but, I was quite happy with the commands
module in gogo :)
I thought it was really some kind of extension t
[
https://issues.apache.org/jira/browse/FELIX-2436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881690#action_12881690
]
Peter Lawrey commented on FELIX-2436:
-
jnotify does sound like a better solution. There
On Wed, Jun 23, 2010 at 14:31, Richard S. Hall wrote:
> On 6/23/10 5:45, Guillaume Sauthier wrote:
>>
>> Hi guys
>>
>> Maybe I react after the battle but, I was quite happy with the commands
>> module in gogo :)
>> I thought it was really some kind of extension to the gogo framework, not
>> so clo
On 6/23/10 5:45, Guillaume Sauthier wrote:
Hi guys
Maybe I react after the battle but, I was quite happy with the
commands module in gogo :)
I thought it was really some kind of extension to the gogo framework,
not so closely related to karaf.
We're using it in a chameleon subproject [1] to
[
https://issues.apache.org/jira/browse/FELIX-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881661#action_12881661
]
Guillaume Nodet commented on FELIX-2361:
A workaround on ubuntu server is to set th
[
https://issues.apache.org/jira/browse/FELIX-2439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881660#action_12881660
]
Guillaume Nodet commented on FELIX-2439:
A workaround is to set the JAVA_HOME syste
The JRE provided ciphers are not used on ubuntu server
--
Key: FELIX-2439
URL: https://issues.apache.org/jira/browse/FELIX-2439
Project: Felix
Issue Type: Bug
Components: Karaf
I don't think it was related to Karaf either (I actually spent some
time to extract those bits and make them reusable outside of Karaf),
but I guess the reason as you understood is that nobody was aware of
any other use outside karaf.
I don't have any problems in moving it back, i think it makes se
Hi guys
Maybe I react after the battle but, I was quite happy with the commands
module in gogo :)
I thought it was really some kind of extension to the gogo framework,
not so closely related to karaf.
We're using it in a chameleon subproject [1] to provide commands/actions
as iPOJO component
45 matches
Mail list logo
