On 7 June 2016 at 18:11, Benedikt Ritter <brit...@apache.org> wrote:
> Hello Sebb,
>
> sebb <seb...@gmail.com> schrieb am Di., 7. Juni 2016 um 18:09 Uhr:
>
>> Does the project *need* to use any Java7 features?
>>
>> Is it working OK now with Java 6 as the minimum?
>>
>> If the answers are No and Yes then moving to Java 7 seems to me to be
>> unnecessary for the initial release.
^^^^^^^^^^^^^^^^^^^^
>>
>
> I think people have expressed in various ways that they don't want to work
> on projects which are stuck on dead Java version. I think we have to
> respect this.
I think you have misunderstood my point.
I'm not saying that the code needs to stay on Java 6 for future releases.
However, assuming that it is working OK on Java 6, it seems silly to
insist that the developers update it to use Java 7 *now*.
Especially since the code appears to be about ready for a release.
Changing to Java 7 now would require additional work which would delay
the release.
But by all means move to Java 7 for the next release if the developers
who are actually working on it agree that it is necessary.
> Benedikt
>
>
>>
>>
>> On 7 June 2016 at 16:49, Marcelo Vanzin <van...@cloudera.com> wrote:
>> > I thought there was a discussion after the project was set up to move to
>> Java 7?
>> >
>> > That being said I see that the pom still defines 1.6 as the target...
>> >
>> > On Mon, Jun 6, 2016 at 7:18 PM, Gary Gregory <garydgreg...@gmail.com>
>> wrote:
>> >> Are we really starting a new component on a dead platform like Java 6?
>> >>
>> >> Gary
>> >>
>> >> --
>> >> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>> >> Java Persistence with Hibernate, Second Edition
>> >> <http://www.manning.com/bauer3/>
>> >> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
>> >> Spring Batch in Action <http://www.manning.com/templier/>
>> >> Blog: http://garygregory.wordpress.com
>> >> Home: http://garygregory.com/
>> >> Tweet! http://twitter.com/GaryGregory
>> >
>> >
>> >
>> > --
>> > Marcelo
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> > For additional commands, e-mail: dev-h...@commons.apache.org
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
