On Jul 14, 2009, at 9:35 , Robert Burrell Donkin wrote:
On Tue, Jul 14, 2009 at 8:27 AM, Felix
Meschberger wrote:
Hi Carsten,
Definitely +1
Experience from past ApacheCon shows, that the OSGi BOF was very well
welcomed.
definitely +1
it'd be great to do some sort of distributed BOF with a
[
https://issues.apache.org/jira/browse/FELIX-1360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731127#action_12731127
]
Richard S. Hall commented on FELIX-1360:
The big issue is we need to make native li
[
https://issues.apache.org/jira/browse/FELIX-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall closed FELIX-26.
Resolution: Fixed
Closing this issue, since the patches were released a long time ago. I have
opened
[
https://issues.apache.org/jira/browse/FELIX-1360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall updated FELIX-1360:
---
Affects Version/s: felix-1.8.1
Fix Version/s: felix-2.0.0
> Improve native library ma
Improve native library matching algorithm (part 2)
--
Key: FELIX-1360
URL: https://issues.apache.org/jira/browse/FELIX-1360
Project: Felix
Issue Type: Improvement
Components: Framewor
[
https://issues.apache.org/jira/browse/FELIX-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731106#action_12731106
]
Felix Meschberger commented on FELIX-1015:
--
Thanks for the feedback.
I will commi
On 7/14/09 12:23 PM, David Savage wrote:
Ok, makes sense. I'll do that - I guess I have priviledges to set up
versions in the felix jira? I'll try and bounce back if I can't...
As an aside I was planning to try to build sigil with sigil vs via maven:
https://issues.apache.org/jira/browse/FELIX-
Ok, makes sense. I'll do that - I guess I have priviledges to set up
versions in the felix jira? I'll try and bounce back if I can't...
As an aside I was planning to try to build sigil with sigil vs via maven:
https://issues.apache.org/jira/browse/FELIX-1323
This would make it a good test scenar
Typically, we have trunk working on an odd numbered minor release as the
development version and then release an even numbered version. So,
perhaps Sigil should be 0.9.0-SNAPSHOT in trunk, working toward 1.0.0
(or 0.10.0 or whatever even number you want). This approach makes like a
little bette
[
https://issues.apache.org/jira/browse/FELIX-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Savage resolved FELIX-1326.
-
Resolution: Fixed
relevant patches applied to svn.
Not currently targetted at a release. Wonderi
On 7/14/09 11:48 AM, Hiram Chirino wrote:
I guess I'm biased :)
But really.. I don't care which shell variant TSL tries to emulate (Maybe
the windows cmd.exe shell??).. I just hope it tries to emulate an existing
one.
Folks tend love it when you get incremental innovation. If you look at it,
th
I guess I'm biased :)
But really.. I don't care which shell variant TSL tries to emulate (Maybe
the windows cmd.exe shell??).. I just hope it tries to emulate an existing
one.
Folks tend love it when you get incremental innovation. If you look at it,
the basics of all the popular shells are prett
On 7/14/09 10:58 AM, Hiram Chirino (JIRA) wrote:
[
https://issues.apache.org/jira/browse/FELIX-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730895#action_12730895
]
Hiram Chirino commented on FELIX-1325:
[
https://issues.apache.org/jira/browse/FELIX-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730899#action_12730899
]
Hiram Chirino commented on FELIX-1356:
--
I think it should be easy to argue that the RF
[
https://issues.apache.org/jira/browse/FELIX-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730895#action_12730895
]
Hiram Chirino commented on FELIX-1325:
--
I agree those test cases are kinda invalid. T
+1 on trying encouraging RFC132 to not surprise old unix gurus too much.
On Tue, Jul 14, 2009 at 3:59 AM, Derek Baum wrote:
> yes,
>
> ${x} actually defines a closure {...} and then immediately expands it.
> Commands typed directly into the shell also result in a closure being
> created and exec
[
https://issues.apache.org/jira/browse/FELIX-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Diesler closed FELIX-1124.
-
merci
> ResourceNotFoundException too verbose
> -
>
>
Ok that's basically what I was planning I'll get started on this next.
Thx for feedback.
Regards,
Dave
On 14 Jul 2009, at 14:12, "Richard S. Hall"
wrote:
On 7/14/09 4:03 AM, Derek Baum wrote:
I like this nested grouping.
If you decide to keep the structure flat, it would still be use
On 7/14/09 4:03 AM, Derek Baum wrote:
I like this nested grouping.
If you decide to keep the structure flat, it would still be useful to prefix
the directory names with ivy-, eclipse- to indicate where they belong.
We have typically tried to follow the package naming structure in our
dire
[
https://issues.apache.org/jira/browse/FELIX-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730824#action_12730824
]
David Savage commented on FELIX-1359:
-
Ok, shame I just noticed I had to update a load
[
https://issues.apache.org/jira/browse/FELIX-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730806#action_12730806
]
Derek Baum commented on FELIX-1359:
---
The above and are sub-elements of ivy-settings.
Th
sigil-ivy-plugin.jar should export ant tasks via properties file vs expecting
user to track classes that implement tasks
Key: FELIX-1359
URL:
I like this nested grouping.
If you decide to keep the structure flat, it would still be useful to prefix
the directory names with ivy-, eclipse- to indicate where they belong.
Derek
2009/7/14 David Savage (JIRA)
>
>[
> https://issues.apache.org/jira/browse/FELIX-1357?page=com.atlassian.ji
yes,
${x} actually defines a closure {...} and then immediately expands it.
Commands typed directly into the shell also result in a closure being
created and executed, so it is difficult to distinguish between:
> x
where we'd like it to fail with 'unknown command'
and
> ${x}
where we'd like i
No worries, thanks for the info Guillaume.
Cheers,
Eoghan
2009/7/14 Guillaume Nodet :
> I was plannig to work on that this week, but i had to change my plans
> and go in vacation this week ( and the next). The integration tests
> just need a bit of work because the bundles have changed, but i don
[
https://issues.apache.org/jira/browse/FELIX-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Savage reassigned FELIX-1326:
---
Assignee: David Savage
> Refactor package names in code to org.apache.felix.sigil
> -
[
https://issues.apache.org/jira/browse/FELIX-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730726#action_12730726
]
David Savage commented on FELIX-1357:
-
Suggestion to move to a nested directory structu
On Tue, Jul 14, 2009 at 8:27 AM, Felix Meschberger wrote:
> Hi Carsten,
>
> Definitely +1
>
> Experience from past ApacheCon shows, that the OSGi BOF was very well
> welcomed.
definitely +1
it'd be great to do some sort of distributed BOF with ad hoc groups
hooking up over the internet (but i'm n
Hi Carsten,
Definitely +1
Experience from past ApacheCon shows, that the OSGi BOF was very well
welcomed. So we might want to have something semi-structured: Basically
BOF but people could "pre-register" if they want to present something.
Regards
Felix
Carsten Ziegeler schrieb:
> Hi,
>
> we al
Hi,
we already have our own track at the ApacheCon US this year. But what
about a meetup? During the past conferences other projects did
successful meetups at the ApacheCon - and I think it makes sense to do
this for Felix as well.
The meetups take place during the evening (we have sunday, monday
30 matches
Mail list logo
