[news.eclipse.tools] Re: rmic classes ==> jar

[Genady <genadyb@xxxxxxxxxxxx>]

The deprecation warnings are due to the fact that the RMI skeletons
(that are created for JDK1.1 compatability) indeed use deprecated 
methods. You can get rid of these by specifying the "-v12" flag in the
RMI properties of your project.

Genady

rkm wrote:
> That did it, and it works as advertised, though I get a lot of deprecation
> warnings.  That's ok for the throughput testing I'm doing  however.
>
> Thanks,
> Rick
>
> I tried the 2.1 version first,
> "Genady" <genadyb@xxxxxxxxxxxx> wrote in message
> news:b7op0n$q34$2@xxxxxxxxxxxxxxxx
>
> > Are you using the RMI plugin?
> > (http://lunar-eclipse.sf.net/)
> >
> > Genady
> >
> > rkm wrote:
> >
> > > I managed to get Eclipse to run rmic to compile my java code, and it put
>
> the
>
> > > generated class files in the bin tree where I told it.  But now that I
>
> want
>
> > > to package those class files into a jar, the jar packager mechanism
>
> doesn't
>
> > > let me pick those class files.  It only allows me to select the source
> > > files, not the ultimate class files I want.  Unfortunately, those rmic
> > > generated source files are ultimately deleted by rmic, so Eclipse is
>
> never
>
> > > aware of them.  How do I get the jar packager to allow me to package up
>
> rmic
>
> > > generated class files?  Do I have to tell rmic that it's working
>
> directory
>
> > > is my source folder, and to not delete the source files?  Then have a
> > > Eclipse compile the rmic generated source.  Seems like the long way
>
> around
>
> > > the block.
> > >
> > > Rick