Mailing-List: contact user-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Users List" <user@commons.apache.org>
Received-SPF: pass (nike.apache.org: domain of joelittlejohn@gmail.com
 designates 209.85.210.171 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        b=gk1R7YDAxgaFS+rm6b4ovkzJqJaId2y4WE0/prfXJP5LdVGfNSOj7Qngqry9XITq65
         WIQ/rq8qVSiFPF3SrsxWqOp5wsGE1qfK+FKqnWsHFwQYzNZUT3ckZG21L3BUj5kNKqql
         CbX+Xt2penHTQSLye7uMdy77g/q9O82x9Bb38=
MIME-Version: 1.0
In-Reply-To: <AANLkTikMGd06-sscXoY-+yD4TsWUjidi=GPxgG6Wj_fv@mail.gmail.com>
References: <AANLkTiktdKyVt1HqTb1+JcxHZYLrwDzfRjvzrhHH7HKg@mail.gmail.com>
	<AANLkTike-fPpwHW1Uf+FjJAxBtV1hYyLgOJ=PPzGbBnX@mail.gmail.com>
	<AANLkTi=mw81baxTuRoV1f3uB_j4EUUw=DpNJ+2Jqy1q0@mail.gmail.com>
	<AANLkTiksGFPwPTby79LTCVz6Hz8bkj+05LPQ=zCT1Z-h@mail.gmail.com>
	<AANLkTimiAZOqFx2Ow21=0OhT6zA4EngyqkQFZJ8zYHKB@mail.gmail.com>
	<AANLkTi=91g8nfXcWKKwLr907gieGG=BYoYq7Z-SFa=RE@mail.gmail.com>
	<AANLkTik69D-ydftz=bg5a=mRDnjsjEA6hA825M9u5M1s@mail.gmail.com>
	<AANLkTimrvtR+kSODQxsP8FhGfo0Ba-9Gr7y70LoUjcc0@mail.gmail.com>
	<AANLkTinUAAiwysJ6yQOAj5otyka61vEDQ5aqDqYs+E1C@mail.gmail.com>
	<02AA127CD8DCDE48BC7D2DFB6C87083A07E68BE8@nwt-s-mbx2.rocketsoftware.com>
	<AANLkTi=S4T49=qSwhWfbwxv0u2PW-0vZuFsXQtwTi6H-@mail.gmail.com>
	<AANLkTikeYe-5=RBoMxKvnL18oBXcOUeFOW5NjbdXpCFC@mail.gmail.com>
	<AANLkTimsPDZyYfAnCR-fJF6Gwu2d5+O1H2V_sXAz7MUZ@mail.gmail.com>
	<FE8CACDA-C1E1-473B-A2FD-1D91F1BCA1A2@seagullsoftware.com>
	<AANLkTi=tNKGcuz1OrrM9w68FJGZfjG1dnuKCxdJL8=_n@mail.gmail.com>
	<AANLkTikWtK1Svz5qKnRV1-44r2VKTdnk9E8pXiaBz--a@mail.gmail.com>
	<AANLkTin6xr7AmmrjyifjLmTK+DnH4na5+DbezcvdPy1B@mail.gmail.com>
	<AANLkTikMGd06-sscXoY-+yD4TsWUjidi=GPxgG6Wj_fv@mail.gmail.com>
Date: Sun, 20 Feb 2011 18:24:19 +0000
Message-ID: <AANLkTinjCPOjY93MpGf0b8azFcoCh5HV1p22K-4J54w-@mail.gmail.com>
Subject: Re: [jci] Can someone please make a 1.1 release?
From: Joe Littlejohn <joelittlejohn@gmail.com>
To: Commons Users List <user@commons.apache.org>
Cc: Christian Grobmeier <grobmeier@gmail.com>
Content-Type: text/plain; charset=UTF-8

I did notice that the trunk build currently requires jdk 1.5. Using
jdk 6 the javac compiler implementation doesn't work and some tests
fail (I believe this is down to JCI-43). I note that the reason I can
compile trunk using jdk 1.5 is that the JSR-199 compiler is currently
not include as a module in the parent pom (it's commented out)

Maybe it's best to leave JSR-199 support aside for now? It's clear
that it's going to require some thought on how to maintain Java 1.5
compatibility whilst delivering a JSR-199 based compiler
implementation.

Given that a JSR-199 compiler was pegged for v1.1, maybe a build of
the current trunk would be better tagged as v1.0.1?


On 20 February 2011 18:11, Christian Grobmeier <grobmeier@gmail.com> wrote:
>> I am with you guys ...but bumping to 1.5 doesn't buy us much.
>> Only bumping to 1.6 would make things much easier.
>
> Just to make sure I understood right... jci depended on 1.4, but then
> we started to implement jsr199 which is currently unfinished. Even
> when unfinished we now need j6 b/c of the interfaces used.
>
> If so, there are these options:
>
> 1) deliver unfinished jsr199 (would would this mean exactly)?
> 2) remove jsr199 and move it to a branch (have there been many changes
> except jsr199 after the last release?)
> 3) complete jsr199 (how difficult is this?)
>
> Thanks :-)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
> For additional commands, e-mail: user-help@commons.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
For additional commands, e-mail: user-help@commons.apache.org