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
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
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
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
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
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
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
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
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,
14 matches
Mail list logo
