Re: The first step of java 1.5(Re: jde-import-kill-extra-imports not working)

> P.S. Can you also check with the following, it seems a bug:
>
> String s;
> s.
>   ^ 
>   If I try to jde-complete here. It comes nothing, and automatically 
> imports javax.crypto.SunJCE_c.s;

I tried it and can't confirm this problem in both winxp and linux.
jde-complete works well in this case.
My platform is gnu emacs 22.1,jde-2.3.5.1,cedet1.0pre4 and
sun jdk 1.5.

poppyer <[email protected]> writes:

> Ke Lu <[email protected]> writes:
>
>> Hi Paul,
>>
>> Do you change your mind of moving the JDEE myself to Sourceforge?
>> I can't see anyting of the progress.
>> If you changed your mind, please come back and lead the develop
>> of jdee.
>>
>> To jdee users.
>>
>> I have done some change of jde-parse.el to support java 1.5
>> generic.
>> Sample:
>>
>> List<String> list = new ArrayList<String>();
>> list.
>>      ^
>>      M-x jde-complete and it works now
>>      
>> The modified file can be downloaded from:
>> http://www.luxdo.jp/~lu/emacs_backup/jde-parse.el
>>
>> Anybody can do some test and feedback?
>
>
> Cool, works well here.
>
> P.S. Can you also check with the following, it seems a bug:
>
> String s;
> s.
>   ^ 
>   If I try to jde-complete here. It comes nothing, and automatically 
> imports javax.crypto.SunJCE_c.s;
>
> Cheers,
> poppyer
>
>>
>> "Paul Kinnucan" <[email protected]> writes:
>>
>>> Hi Carlos,
>>>
>>> I think it would be best if I moved the JDEE myself to Sourceforge. I
>>> will have this completed by next weekend.
>>>
>>> Paul
>>>
>>>> -----Original Message-----
>>>> From: Carlos Konstanski [mailto:[email protected]]
>>>> Sent: Saturday, November 03, 2007 5:06 PM
>>>> To: [email protected]
>>>> Subject: Re: jde-import-kill-extra-imports not working
>>>> 
>>>> At Wed, 31 Oct 2007 11:58:25 +0000,
>>>> Phillip Lord wrote:
>>>> > I would move to sourceforge or gna.org. This is straightforward
>>> enough.
>>>> Then
>>>> > pull the current cvs into a svn as quite a lot more people are using
>>>> this
>>>> > nowadays (it's not essential though).
>>>> >
>>>> > The jobs that need doing are:
>>>> >
>>>> > 1) checking patches for people without svn/cvs access.
>>>> > 2) adding people to svn/cvs where appropriate
>>>> > 3) organising a release schedule. In practice, this means doing a
>>> new
>>>> release
>>>> >    when ever enough patches have come in.
>>>> > 4) Updating the website with new tarballs, new zips.
>>>> >
>>>> > As an added extra:
>>>> >
>>>> > 5) add a top level makefile to build packages for the various
>>> linuxes --
>>>> rpm,
>>>> >    gentoo and the like. Or add autoconf support which should bring
>>> the
>>>> former
>>>> >    nearly for free I think. I'm not a real package expert.
>>>> >
>>>> > Once the release mechanism is fixed, then use can be made of
>>> existing
>>>> > patches. This would at least keep JDE ticking over.
>>>> >
>>>> > I'm afraid I am not volunteering here; I rarely code Java these
>>> days, so
>>>> I can
>>>> > live without. But it would be nice to have the option to use Emacs
>>> for
>>>> those
>>>> > occasions that I do.
>>>> >
>>>> > Phil
>>>> 
>>>> OK, the weekend is here and I am ready to do this thing.  First of
>>>> all, do we have buyoff from the author/current maintainer to move JDEE
>>>> to sourceforge?  I hereby officially ask the individual(s) in charge
>>>> if it's all right for me to set up a JDEE sourceforge project and move
>>>> the CVS repository there, in accordance with the promises I made
>>>> earlier in this thread.
>
> --