+1 (non-binding)
--
Chris Custine
FUSESource :: http://fusesource.com
My Blog :: http://blog.organicelement.com
Apache ServiceMix :: http://servicemix.apache.org
Apache Felix :: http://felix.apache.org
Apache Directory Server :: http://directory.apache.org
On Mon, May 3, 2010 at 4:14 PM, Gert
A few things that would be missing imho to make that interesting:
* parameters annotation to mark parameters as optional or multi-valued
* flag and option could be merged (they are the same, maybe use an enum
value on the annotation to differentiate them and maybe have a smart default
value
[
https://issues.apache.org/jira/browse/FELIX-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12863697#action_12863697
]
Rob Walker commented on FELIX-2292:
---
I'm working in this area at present, so if everyone
[
https://issues.apache.org/jira/browse/FELIX-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12863712#action_12863712
]
Rob Walker commented on FELIX-2292:
---
Thinking about this some more - I wonder if there is
+1 (non-binding)
Freeman
On 2010-5-1, at 下午3:03, Guillaume Nodet wrote:
I would like to call a vote on the following subproject releases:
fileinstall 3.0.0
Staging repository:
https://repository.apache.org/content/repositories/orgapachefelix-039/
You can use this UNIX script to download the
+1 (non-binding)
Thanks
Freeman
On 2010-4-30, at 上午2:47, Guillaume Nodet wrote:
I would like to call a vote on the following subproject releases:
fileinstall 2.0.10
gogo 0.4.0
bundlerepository 1.6.2
bundleplugin 2.1.0
Staging repository:
Whenever I clean build I get this error?
Guessing it must just be my local setup. The version ssems out of sync
i.e the current OBR is 1.6.3, but the bundleplugin is asking for 1.6.2.
Even if I change this though I still get the error unless I manually
install the newly built OBR to my local
Well, this should be easy enough to test, right? Just re-compile the
eventadmin and see whether that fixes the issue or not - if it does,
that would be really useful to know :-)
regards,
Karl
On Tue, May 4, 2010 at 1:23 PM, Jackson, Bruce bru...@qualcomm.com wrote:
Hi All
Some time back, we
And like before, make sure you don't have other messages like class
resolved by unexpected dex in the log ...
regards,
Karl
On Tue, May 4, 2010 at 1:33 PM, Karl Pauls karlpa...@gmail.com wrote:
Well, this should be easy enough to test, right? Just re-compile the
eventadmin and see whether
[
https://issues.apache.org/jira/browse/FELIX-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12863779#action_12863779
]
Rob Walker commented on FELIX-2292:
---
Ok - both the new (jetty) and old (http.jetty)
I have the same issues with all Apple SDKs (tried 5 and 6) here.
Lets hope that Google's not dissing Apple Java this way.
So far it let to not more than those warn messages produced by dx.
Toni
On Tue, May 4, 2010 at 1:54 PM, Karl Pauls karlpa...@gmail.com wrote:
And like before, make sure
+1 (non-binding)
Jamie
On Tue, May 4, 2010 at 5:58 AM, Freeman Fang freeman.f...@gmail.com wrote:
+1 (non-binding)
Freeman
On 2010-5-1, at 下午3:03, Guillaume Nodet wrote:
I would like to call a vote on the following subproject releases:
fileinstall 3.0.0
Staging repository:
On 5/4/10 2:33, Guillaume Nodet wrote:
A few things that would be missing imho to make that interesting:
* parameters annotation to mark parameters as optional or multi-valued
Currently, flags are always optional, whereas options are only optional
if a default value is specified. We
I'm interested to see how your experiment develops.
Meanwhile, an alternative approach to writing RFC-147 commands is presented
here:
https://www.osgi.org/bugzilla/show_bug.cgi?id=53
I'm happy to donate this 500-line Options class to Felix, if there is any
interest.
Derek
On 4 May 2010 14:07,
Yes, that's easier said than done!
I seem to remember that the was no single place where you could set the
compiler version to use for building Felix. Is that correct?
On 04/05/2010 12:54, Karl Pauls karlpa...@gmail.com wrote:
And like before, make sure you don't have other messages like class
On 5/4/10 10:07, Derek Baum wrote:
I'm interested to see how your experiment develops.
Meanwhile, an alternative approach to writing RFC-147 commands is presented
here:
https://www.osgi.org/bugzilla/show_bug.cgi?id=53
I'm happy to donate this 500-line Options class to Felix, if there is any
Toni
I don't think its an Apple issue. The dx tool works fine for me with no
warnings as long as the source is compiled with either 1.5 or 1.6.
Thanks
Bruce
On 04/05/2010 13:22, Toni Menzel t...@okidokiteam.com wrote:
I have the same issues with all Apple SDKs (tried 5 and 6) here.
Lets
On 5/4/10 10:19, Jackson, Bruce wrote:
Yes, that's easier said than done!
I seem to remember that the was no single place where you could set the
compiler version to use for building Felix. Is that correct?
You should just be able to edit the Event Admin pom.xml file to include
this in
Unbind method should not be called during the invalidation process if the
invalidation does not come from a service departure
-
Key: FELIX-2323
[
https://issues.apache.org/jira/browse/FELIX-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12863839#action_12863839
]
Marco commented on FELIX-2318:
--
Yesterday, I stumbled exactly over this NPE, which was not
On 5/4/10 10:25 AM, Richard S. Hall wrote:
On 5/4/10 10:19, Jackson, Bruce wrote:
Yes, that's easier said than done!
I seem to remember that the was no single place where you could set the
compiler version to use for building Felix. Is that correct?
You should just be able to edit the
[
https://issues.apache.org/jira/browse/FELIX-2323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clement Escoffier resolved FELIX-2323.
--
Resolution: Fixed
Fixed in trunk.
Unbind methods are no more called when the
[
https://issues.apache.org/jira/browse/FELIX-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clement Escoffier resolved FELIX-2279.
--
Resolution: Fixed
Fixed in trunk.
Add the post-registration and post-unregistration
But i realized i the warnings just appear when using the stock felix 2.0.5
(and other bundles like event admin).
Self built stuff works just fine.
So Karl, what do you use to build the released artifacts ?
On Tue, May 4, 2010 at 5:27 PM, Justin Edelson justinedel...@gmail.comwrote:
On 5/4/10
Support execution environment so that OBR works properly
Key: FELIX-2324
URL: https://issues.apache.org/jira/browse/FELIX-2324
Project: Felix
Issue Type: Improvement
According to the manifest, Carsten, not Karl, built EventAdmin 1.2.2.
On 5/4/10 11:49 AM, Toni Menzel wrote:
But i realized i the warnings just appear when using the stock felix
2.0.5 (and other bundles like event admin).
Self built stuff works just fine.
So Karl, what do you use to build
then there are at least two broken compilers out in the wild
;)
2010/5/4 Justin Edelson justinedel...@gmail.com
According to the manifest, Carsten, not Karl, built EventAdmin 1.2.2.
On 5/4/10 11:49 AM, Toni Menzel wrote:
But i realized i the warnings just appear when using the stock felix
we compile for 1.4 by default.
regards,
Karl
2010/5/4 Toni Menzel t...@okidokiteam.com:
then there are at least two broken compilers out in the wild
;)
2010/5/4 Justin Edelson justinedel...@gmail.com
According to the manifest, Carsten, not Karl, built EventAdmin 1.2.2.
On 5/4/10 11:49
This is probably the valid explanation:
http://www.mailinglistarchive.com/html/derby-...@db.apache.org/2009-12/msg00072.html
http://www.mailinglistarchive.com/html/derby-...@db.apache.org/2009-12/msg00072.html
In fact, I believe the bytecode
spec changed between 1.4 and 1.5. dx's warning is
[
https://issues.apache.org/jira/browse/FELIX-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall updated FELIX-2324:
---
Fix Version/s: framework-3.0.0
Affects Version/s: framework-2.0.5
[
https://issues.apache.org/jira/browse/FELIX-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12863873#action_12863873
]
Guillaume Nodet commented on FELIX-2314:
Committing to
[
https://issues.apache.org/jira/browse/FELIX-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12863875#action_12863875
]
Richard S. Hall commented on FELIX-2324:
I was thinking about adding this in the
[
https://issues.apache.org/jira/browse/FELIX-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12863878#action_12863878
]
Christopher Blunck commented on FELIX-2324:
---
I don't know as I'm pretty new to
[
https://issues.apache.org/jira/browse/FELIX-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12863884#action_12863884
]
Richard S. Hall commented on FELIX-2324:
ok. Well, all I am thinking about doing is
But the compiler used is system-dependent. All the source/target bits do
is impact what the compiler does, not which compiler is used.
If you specify the fork, compilerVersion, and executable properties as I
described below, you can use an alternate javac. You can also use a
different compiler
[
https://issues.apache.org/jira/browse/FELIX-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Müller updated FELIX-2280:
Attachment: FELIX-2280.patch
Me again...
I provide a new patch (based on the current
[
https://issues.apache.org/jira/browse/FELIX-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12863920#action_12863920
]
Jamie goodyear commented on FELIX-2280:
---
Thanks, I'll take a look over this latest
Really, my guess is that you are running into the same issue as you
did the last time namely, the eventadmin contains the
org.osgi.service.event package and imports it as well. Do you have the
compendium bundle installed (or any other provider of the
org.osgi.service.event package)? Remember,
[
https://issues.apache.org/jira/browse/FELIX-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12864139#action_12864139
]
Christopher Blunck commented on FELIX-2324:
---
I looked up standardization on
I guess we should have tried this out in a sandbox but this experiment seems
rather harmless for existing users and potentially very powerful. And this
experiment is timely because I do have to update RFC 147. Will do different
next time :-)
On 4 mei 2010, at 08:33, Guillaume Nodet wrote:
A
40 matches
Mail list logo
