[
https://issues.apache.org/jira/browse/FELIX-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eoghan Glynn updated FELIX-2063:
Attachment: felix_2063.patch
Patch attached, please review and commit if OK.
> [karaf] hardcod
Key: FELIX-2063
URL: https://issues.apache.org/jira/browse/FELIX-2063
Project: Felix
Issue Type: Bug
Components: Karaf
Affects Versions: karaf-1.4.0
Reporter: Eoghan Glynn
Fix For: karaf-1.4.0
Pax-runner calculates
[
https://issues.apache.org/jira/browse/FELIX-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eoghan Glynn updated FELIX-2061:
Attachment: felix_2061.patch
Patch attached, please review and apply if considered OK.
> [ka
Issue Type: Improvement
Components: Karaf
Affects Versions: karaf-1.2.0
Reporter: Eoghan Glynn
Fix For: karaf-1.4.0
I've seen the odd timeout in the Karaf integration tests, and I noticed that
waitForFrameworkStartup pax-exam option was not being used.
[
https://issues.apache.org/jira/browse/FELIX-2049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12831403#action_12831403
]
Eoghan Glynn edited comment on FELIX-2049 at 2/9/10 10:4
[
https://issues.apache.org/jira/browse/FELIX-2049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eoghan Glynn updated FELIX-2049:
Attachment: felix_2249_2.patch
Just noticed a linger println() in the initial patch, please use
[
https://issues.apache.org/jira/browse/FELIX-2049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eoghan Glynn updated FELIX-2049:
Attachment: felix_2249.patch
Turns out the execution environment approach isn't sufficient, a
://issues.apache.org/jira/browse/FELIX-2049
Project: Felix
Issue Type: Improvement
Components: Karaf
Affects Versions: karaf-1.4.0
Reporter: Eoghan Glynn
Fix For: karaf-1.4.0
I've been looking into rebasing an existing test on th
[
https://issues.apache.org/jira/browse/FELIX-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eoghan Glynn updated FELIX-1915:
Attachment: felix_1915.patch
Can some committer please review this patch and apply if considered
Components: Karaf
Affects Versions: karaf-1.2.0
Reporter: Eoghan Glynn
Priority: Minor
Fix For: karaf-1.4.0
The properties specified in etc/system.properties take precedence over those
set via -Dname=value in the JAVA_OPTS. It would be more
[
https://issues.apache.org/jira/browse/FELIX-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eoghan Glynn updated FELIX-1902:
Attachment: felix_1902.patch
Can some committer please review the attached patch and apply if
: Task
Affects Versions: karaf-1.2.0
Reporter: Eoghan Glynn
Priority: Minor
Fix For: karaf-1.4.0
Just noticed in the 1.2.0 kit that the web demo README refers to the
1.1.0.0-fuse-SNAPSHOT version.
This needs to be replaced with a generic version reference
+1
(non-binding, obviously)
Cheers,
Eoghan
2009/11/27 Guillaume Nodet
> I've uploaded a release for Karaf 1.2.0.
>
> The staging site is available at:
> https://repository.apache.org/content/repositories/orgapachefelix-023/
>
> The release page is available at
> http://cwiki.apache.org/FELI
[
https://issues.apache.org/jira/browse/FELIX-1882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eoghan Glynn updated FELIX-1882:
Description:
When using the karaf-client to run some automated set-up commands on a newly
started
[
https://issues.apache.org/jira/browse/FELIX-1882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eoghan Glynn updated FELIX-1882:
Attachment: felix_1882.patch
Can some committer please review this patch and apply if considered
[
https://issues.apache.org/jira/browse/FELIX-1882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eoghan Glynn updated FELIX-1882:
Component/s: Karaf
Fix Version/s: karaf-1.2.0
karaf-1.0.2
Issue Type: Improvement
Reporter: Eoghan Glynn
When using the karaf-client to run some automated set-up commands on a newly
started karaf instances, there's a slight race condition between the ssh server
being ready to accept incoming connections and the point at which the
[
https://issues.apache.org/jira/browse/FELIX-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12776979#action_12776979
]
Eoghan Glynn commented on FELIX-1850:
-
Fixed by patch for FELIX-1849
(h
[
https://issues.apache.org/jira/browse/FELIX-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eoghan Glynn updated FELIX-1849:
Attachment: felix_1849.patch
Can some committer review this patch and apply if considered kosher
[
https://issues.apache.org/jira/browse/FELIX-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eoghan Glynn updated FELIX-1848:
Attachment: felix_1848.patch
Can some committer review the attached patch and apply if kosher
It would be quite useful to have the AdminServiceMBean.getInstances()
operation exposed, as it would allow for remote probing that a particular
instance has been successfully started. I'm thinking of a scenario where
this probe is done programmatically via JMX/RMI as opposed to manually using
some
[
https://issues.apache.org/jira/browse/FELIX-1655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766014#action_12766014
]
Eoghan Glynn commented on FELIX-1655:
-
What would be useful also would be the abi
[
https://issues.apache.org/jira/browse/FELIX-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eoghan Glynn updated FELIX-1751:
Attachment: felix_1751.patch
Can some committer review and apply the attached patch.
> [ka
[
https://issues.apache.org/jira/browse/FELIX-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eoghan Glynn updated FELIX-1751:
Description:
"admin:start foobar" fails silently, i.e. no process is launched for foobar
: Karaf
Affects Versions: karaf-1.0.2
Reporter: Eoghan Glynn
Fix For: karaf-1.0.2
admin:start foobar fail silently, i.e. no process is launched for foobar
instance
After running the equivalent command directly I see a FileNotFound on the
framework jar
[
https://issues.apache.org/jira/browse/FELIX-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eoghan Glynn updated FELIX-1675:
Attachment: felix_1675.patch
Can some commiter apply this trivial patch?
> karaf web demo REA
[
https://issues.apache.org/jira/browse/FELIX-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eoghan Glynn updated FELIX-1675:
Description: The karaf web demo README.txt instructions need to be
sanitized of ServiceMix Kernel
Components: Karaf
Affects Versions: karaf-1.0.0
Reporter: Eoghan Glynn
Priority: Minor
Fix For: karaf-1.0.2
The karaf web demo README.txt instructions need to be snaitized of ServiceMix
Kernel references.
--
This message is automatically generated by JIRA
[
https://issues.apache.org/jira/browse/FELIX-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759491#action_12759491
]
Eoghan Glynn commented on FELIX-1642:
-
Here's a thread dump from a cli
[
https://issues.apache.org/jira/browse/FELIX-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759482#action_12759482
]
Eoghan Glynn commented on FELIX-1642:
-
Could the client "hang" occ
the configurations for the config admin, but it's
> really tedious and a better way need to be found.
>
> I guess we'd need a generic mechanism to handle port conflicts, not sure
> what's the best way yet.
>
> Thoughts welcomed !
>
> On Mon, Sep 7, 2009 at
Hi Folks,
If I launch an admin:create'd instance via admin:start from the master karaf
instance, all is hunky-dorey.
However, if instead the child instance is run from the command line via the
generated instances/ directory tree, then I'm see a port clash on the
JMX RMI connector[1] if the master
ed, but i don't
> think there is any major problem.
>
> On Monday, July 13, 2009, Eoghan Glynn wrote:
>> Hi Folks,
>>
>> I'm wondering why the pax.exam-based AbstractIntegrationTest isn't
>> built at the moment, as the itests module is excluded from the
Hi Folks,
I'm wondering why the pax.exam-based AbstractIntegrationTest isn't
built at the moment, as the itests module is excluded from the
top-level pom[1].
Also, in order to re-use this AbstractIntegrationTest else-where (for
example to take a dependency on it from the SMX codebase), it would
p
34 matches
Mail list logo
