[jira] [Created] (APEXCORE-803) Update archetype version number in setup guide

[Thomas Weise (JIRA)]

Thomas Weise created APEXCORE-803:
-

 Summary: Update archetype version number in setup guide
 Key: APEXCORE-803
 URL: https://issues.apache.org/jira/browse/APEXCORE-803
 Project: Apache Apex Core
  Issue Type: Task
  Components: Documentation
Reporter: Thomas Weise
Assignee: Thomas Weise
 Fix For: 3.7.0






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [Proposal] Switch to Java 8

[Vlad Rozov]

There is difference between intention and how it works in reality. With 
large number of dependencies used by Apex, I won't be surprised that 
some of them use "sun" packages removed in Java 9.


Thank you,

Vlad

On 1/19/18 13:55, Pramod Immaneni wrote:

Thought you were suggesting to start using some java 9 features in the code.. 
otherwise wouldn’t something built with java 8 automatically work with java 9.


On Jan 19, 2018, at 1:29 PM, Vlad Rozov  wrote:

Yes, support for Java 9 does not mean that support for Java 8 is dropped.

Thank you,

Vlad

On 1/19/18 11:36, Sanjay Pujare wrote:

Are they mutually exclusive? Otherwise "start supporting Java 9" doesn't
have to imply stopping Java 8 support. I think Vlad implied supporting both.

Sanjay

On Fri, Jan 19, 2018 at 10:56 AM, Pramod Immaneni 
wrote:


Java 9 will shut people out as 8 is not yet eol. The majority of the
installations I have seen are running 8 and people are moving from 7 to 8.
Other projects in our space are also moving to 8.


On Jan 19, 2018, at 8:31 AM, Vlad Rozov  wrote:

+1. It will be good to start supporting Java 9.

Thank you,

Vlad

On 1/18/18 11:01, Hitesh Kapoor wrote:

+1.

--Hitesh

Re: [Proposal] Switch to Java 8

[Pramod Immaneni]

Thought you were suggesting to start using some java 9 features in the code.. 
otherwise wouldn’t something built with java 8 automatically work with java 9.

> On Jan 19, 2018, at 1:29 PM, Vlad Rozov  wrote:
> 
> Yes, support for Java 9 does not mean that support for Java 8 is dropped.
> 
> Thank you,
> 
> Vlad
> 
> On 1/19/18 11:36, Sanjay Pujare wrote:
>> Are they mutually exclusive? Otherwise "start supporting Java 9" doesn't
>> have to imply stopping Java 8 support. I think Vlad implied supporting both.
>> 
>> Sanjay
>> 
>> On Fri, Jan 19, 2018 at 10:56 AM, Pramod Immaneni 
>> wrote:
>> 
>>> Java 9 will shut people out as 8 is not yet eol. The majority of the
>>> installations I have seen are running 8 and people are moving from 7 to 8.
>>> Other projects in our space are also moving to 8.
>>> 
 On Jan 19, 2018, at 8:31 AM, Vlad Rozov  wrote:
 
 +1. It will be good to start supporting Java 9.
 
 Thank you,
 
 Vlad
 
 On 1/18/18 11:01, Hitesh Kapoor wrote:
> +1.
> 
> --Hitesh
> 
>>> 
> 

Re: [Proposal] Switch to Java 8

[Vlad Rozov]

Yes, support for Java 9 does not mean that support for Java 8 is dropped.

Thank you,

Vlad

On 1/19/18 11:36, Sanjay Pujare wrote:

Are they mutually exclusive? Otherwise "start supporting Java 9" doesn't
have to imply stopping Java 8 support. I think Vlad implied supporting both.

Sanjay

On Fri, Jan 19, 2018 at 10:56 AM, Pramod Immaneni 
wrote:


Java 9 will shut people out as 8 is not yet eol. The majority of the
installations I have seen are running 8 and people are moving from 7 to 8.
Other projects in our space are also moving to 8.


On Jan 19, 2018, at 8:31 AM, Vlad Rozov  wrote:

+1. It will be good to start supporting Java 9.

Thank you,

Vlad

On 1/18/18 11:01, Hitesh Kapoor wrote:

+1.

--Hitesh

Re: [Proposal] Switch to Java 8

[Sanjay Pujare]

Are they mutually exclusive? Otherwise "start supporting Java 9" doesn't
have to imply stopping Java 8 support. I think Vlad implied supporting both.

Sanjay

On Fri, Jan 19, 2018 at 10:56 AM, Pramod Immaneni 
wrote:

> Java 9 will shut people out as 8 is not yet eol. The majority of the
> installations I have seen are running 8 and people are moving from 7 to 8.
> Other projects in our space are also moving to 8.
>
> > On Jan 19, 2018, at 8:31 AM, Vlad Rozov  wrote:
> >
> > +1. It will be good to start supporting Java 9.
> >
> > Thank you,
> >
> > Vlad
> >
> > On 1/18/18 11:01, Hitesh Kapoor wrote:
> >> +1.
> >>
> >> --Hitesh
> >>
>
>

Re: [Proposal] Switch to Java 8

[Pramod Immaneni]

Java 9 will shut people out as 8 is not yet eol. The majority of the 
installations I have seen are running 8 and people are moving from 7 to 8. 
Other projects in our space are also moving to 8. 

> On Jan 19, 2018, at 8:31 AM, Vlad Rozov  wrote:
> 
> +1. It will be good to start supporting Java 9.
> 
> Thank you,
> 
> Vlad
> 
> On 1/18/18 11:01, Hitesh Kapoor wrote:
>> +1.
>> 
>> --Hitesh
>> 
>> On Fri, Jan 19, 2018 at 12:28 AM, Ananth G  wrote:
>> 
>>> Hello All,
>>> 
>>> I was wondering if we can consider making java 8 as the minimum supported
>>> idk version going forward.
>>> 
>>> Since Apex core is moving to the next release cycle, perhaps we consider
>>> this ? My assumption is that the next release version for core after the
>>> 3.7.0 release is going to be a major version bump ?
>>> 
>>> My understanding is that core needs to move to idk 8 before we can move
>>> library/malhar to idk 8.
>>> 
>>> Here are some points to consider (There might be more points to the list
>>> below) :
>>> 
>>> - Java 7 has been deprecated from a support model more than 2 years back
>>> - Peer streaming frameworks like Flink are mandating Java 8
>>> - Apache Beam is moving to Java 8 from its next release cycle
>>> - Many hadoop vendors provide java 8 as the base for the platform.
>>> - Will help the community to use java8 streams and lambdas in operators and
>>> core
>>> - There are certain maven dependencies which might be more optimal if java8
>>> dependency is inherited as opposed to java 7version of the dependencies
>>> - Junit5 might help in richer unit tests.
>>> 
>>> Regards,
>>> Ananth
>>> 
> 

Re: Core release 3.7.0

[Vlad Rozov]

+1. Should be the last release to support Java 7.

Thank you,

Vlad

On 1/18/18 18:45, Bhupesh Chawda wrote:

+1 for release

~ Bhupesh

On Jan 19, 2018 12:14 AM, "Ananth G"  wrote:


+1 for the release.

Regards,
Ananth

On Fri, Jan 19, 2018 at 4:41 AM, Chinmay Kolhatkar 
wrote:


+1 for the release.

- Chinmay.

On 18 Jan 2018 8:58 pm, "Tushar Gosavi"  wrote:


+1 for the release

Regards,
- Tushar.


On Thu, Jan 18, 2018 at 3:28 AM, Amol Kekre 

wrote:

+1

Thks,
Amol


E:a...@datatorrent.com | M: 510-449-2606 | Twitter: @*amolhkekre*

www.datatorrent.com


On Wed, Jan 17, 2018 at 1:55 PM, Pramod Immaneni <

pra...@datatorrent.com

wrote:


+1


On Jan 17, 2018, at 7:25 AM, Thomas Weise 

wrote:

Last release was 3.6.0 in May and following issues are ready for

release:

https://issues.apache.org/jira/issues/?jql=fixVersion%

20%3D%203.7.0%20AND%20project%20%3D%20APEXCORE%20ORDER%20BY%

20status%20ASC

Any opinions on cutting a release?

Any committer interested running the release?

Thanks,
Thomas

Re: [Proposal] Switch to Java 8

[Vlad Rozov]

+1. It will be good to start supporting Java 9.

Thank you,

Vlad

On 1/18/18 11:01, Hitesh Kapoor wrote:

+1.

--Hitesh

On Fri, Jan 19, 2018 at 12:28 AM, Ananth G  wrote:


Hello All,

I was wondering if we can consider making java 8 as the minimum supported
idk version going forward.

Since Apex core is moving to the next release cycle, perhaps we consider
this ? My assumption is that the next release version for core after the
3.7.0 release is going to be a major version bump ?

My understanding is that core needs to move to idk 8 before we can move
library/malhar to idk 8.

Here are some points to consider (There might be more points to the list
below) :

- Java 7 has been deprecated from a support model more than 2 years back
- Peer streaming frameworks like Flink are mandating Java 8
- Apache Beam is moving to Java 8 from its next release cycle
- Many hadoop vendors provide java 8 as the base for the platform.
- Will help the community to use java8 streams and lambdas in operators and
core
- There are certain maven dependencies which might be more optimal if java8
dependency is inherited as opposed to java 7version of the dependencies
- Junit5 might help in richer unit tests.

Regards,
Ananth