problems. I will resolve
CLOUDSTACK-1421 with these details.
--Alex
> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Wednesday, February 27, 2013 12:17 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: Adding a java compat
013 11:45 AM
> > To: cloudstack-dev@incubator.apache.org
> > Subject: Re: Adding a java compat level to our pom.xml
> >
> > Alex,
> >
> > There be dragons having separate source and target versions. Namely, with
> > source compatibility at 1.7, developers mu
Ok...sounds good to me. I'll do that.
--Alex
> -Original Message-
> From: John Burwell [mailto:jburw...@basho.com]
> Sent: Wednesday, February 27, 2013 11:45 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: Adding a java compat level to our pom.xml
>
Alex,
There be dragons having separate source and target versions. Namely, with
source compatibility at 1.7, developers must compile with a JDK 7 which can
lead to usage of Java7 runtime features. Therefore, while the class files
might technically run on JRE 6, link exceptions will crop up be
> Does this imply that it requires 1.7 to compile, but should be compatible with
> 1.6?
I'm open to requiring 1.6 instead of 1.7 for source.
>
> Also, we're talking about master (i.e.: not 4.1), right?
I actually want this in 4.1 not just master. If a certain version of
cloudstack suddenly re
On Wed, Feb 27, 2013 at 10:19:49AM -0800, Alex Huang wrote:
> The discussion on java support level caused me to check the poms to see if
> there's a compat level set when compiling our source code. This used to be
> in ant but looks to be lost in maven. I propose that we add the following
> li
The discussion on java support level caused me to check the poms to see if
there's a compat level set when compiling our source code. This used to be in
ant but looks to be lost in maven. I propose that we add the following lines
to our maven configuration. This basically says that even the s
