It is not enough to just say target 1.4 when compiling. You really
need to
avoid compiling against the 5.0 class libs to catch mistakes in using
5.0
introduced classes and methods.
BJ Hargrave
Senior Technical Staff Member, IBM
OSGi Fellow and CTO of the OSGi Alliance
[EMAIL PROTECTED]
office: +1 386 848 1781
mobile: +1 386 848 3788
"Felix Meschberger" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
2007-04-12 02:23
Please respond to
[EMAIL PROTECTED]
To
[EMAIL PROTECTED]
cc
Subject
Re: Configuration Admin Service and Metatype Service
Hi Richard,
I tend to use Java 1.4.2 - but I have to admit, that I did not
crosscheck.
So I quickly crosschecked the class file versions of the snapshots I
deployed lately (OSGi core, scr, metatype and configadmin) and they all
are
Version 48, i.e pre-1.5 class files. Looking at the parent pom in
felix/trunk, this is expected as the compiler plugin is configured to
generate Java 1.4 class files (lines 295-301).
Hope this helps.
Regards
Felix
On 4/11/07, Richard S. Hall <[EMAIL PROTECTED]> wrote:
>
> Felix,
>
> A question just came to mind...
>
> Which version of Java are you using to build and deploy to the
snapshot
> repo? I generally discourage using >= Java5 unless necessary (e.g., I
> think MOSGi requires Java5), otherwise I have been using Java 1.4.2...
>
> -> richard
>
> Felix Meschberger wrote:
> > Hi all,
> >
> > I finally came around to committing the Configuration Admin Service
and
> > Metatype Service implementations. I also added the modules to the
parent
> > pom.xml in felix/trunk and tested it on my local linux box.
Finally I
> > deployed snapshots to the Apache Snapshot Repository.
> >
> > Looking forward to any comments, bug reports, etc. :-)
> >
> > I try to find some time in the near future to write up some
> > tutorial-style
> > text on the wiki. But basically, the services implement the
> specification
> > and may just be used as specified.
> >
> > Regards
> > Felix
> >
>
