You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by Matei Zaharia <ma...@gmail.com> on 2013/08/01 20:24:41 UTC
Re: java7 jars
BTW, out of curiosity, are the earlier Mesos JARS (like 0.11) built with Java 6? I'd like to switch back to one that depends on Java 6 temporarily in Spark, since we now switched to 0.12 and some people have trouble building it. There's no code change required to use an older version AFAIK so users could still link a new one.
Matei
On Jul 29, 2013, at 5:29 PM, Matei Zaharia <ma...@gmail.com> wrote:
> Unfortunately I believe it's quite hard to delete published JARs from Maven because of the signature files there -- you might need to make a new release number. However, you can try asking Apache infra.
>
> Matei
>
> On Jul 29, 2013, at 12:21 PM, Vinod Kone <vi...@gmail.com> wrote:
>
>> Does anyone on the list know what is the policy for deleting already
>> published (and likely mirrored) jars in apache repository.
>>
>> We would like to upload jars built to java 6 instead of java 7.
>>
>> thanks,
>>
>>
>> On Fri, Jun 21, 2013 at 11:21 AM, Vinod Kone <vi...@gmail.com> wrote:
>>
>>> +mesos-dev
>>>
>>> Hey Andy,
>>>
>>> Looks like we have been (unintentionally?) publishing mesos jars (starting
>>> from mesos-0.10.0) compiled to java 7 bytecode, to the apache maven repo.
>>> AFAIK, we are not using any java 7 features. So, I propose we compile the
>>> jars to java 6 and upload them. We should probably update our build tool
>>> chain to make this explicit. I'm sure there is an option somewhere in mvn
>>> to the set the target byte code.
>>>
>>> Does that make sense?
>>>
>>> P.S: Not sure what is the apache policy for deleting publicly published
>>> jars.
>>>
>
Re: java7 jars
Posted by Matei Zaharia <ma...@gmail.com>.
Cool! As soon as it's on Maven I'll change back to it. Thanks for fixing this.
Matei
On Aug 1, 2013, at 3:53 PM, Vinod Kone <vi...@gmail.com> wrote:
> yes, we updated our makefile to build all our jars to 6. all our releases
> from now on (starting from 0.12.1) will be built for java 6.
>
>
> On Thu, Aug 1, 2013 at 3:46 PM, Matei Zaharia <ma...@gmail.com>wrote:
>
>> I've just reverted to 0.9 until there's another JAR in Maven Central that
>> I can use. Note that it's fine if you build it with Java 7, just set the
>> target to Java 6.
>>
>> Matei
>>
>> On Aug 1, 2013, at 12:04 PM, Benjamin Hindman <be...@eecs.berkeley.edu>
>> wrote:
>>
>>> Flo's stop-gap will get things building Matei (I was building Spark with
>>> 0.14.0 for the past week). The 0.12.1 vote will be out today, and
>> hopefully
>>> released 72 hours after that!
>>>
>>>
>>> On Thu, Aug 1, 2013 at 12:00 PM, Florian Leibert <fl...@mesosphe.re>
>> wrote:
>>>
>>>> We have a 0.14.0 jar in our public repo:
>>>>
>>>>
>> https://s3.amazonaws.com/mesosphere-maven-public/org/apache/mesos/mesos_jdk6/0.14.0/mesos_jdk6-0.14.0.pom
>>>>
>>>> Please note, that we have renamed the artifact to mesos_jdk6!
>>>>
>>>> That might be a good stop-gap. Including this section in your pom.xml
>> file
>>>> should do the trick:
>>>>
>>>> <repository>
>>>> <id>mesosphere-public-repo</id>
>>>> <name>Mesosphere Public Repo</name>
>>>> <url>http://s3.amazonaws.com/mesosphere-maven-public/</url>
>>>> </repository>
>>>>
>>>> --Flo
>>>>
>>>>
>>>> On Thu, Aug 1, 2013 at 11:42 AM, Vinod Kone <vi...@gmail.com>
>> wrote:
>>>>
>>>>> 0.11.0 and 0.10.0 were built *with source *jdk7 and *target *java7.
>> 0.9.0
>>>>> was built with source and target as java6.
>>>>>
>>>>> fwiw, we are prepping a release (0.12.1) this week that should be built
>>>>> with source and target set to java6. would that work for you?
>>>>>
>>>>>
>>>>> On Thu, Aug 1, 2013 at 11:24 AM, Matei Zaharia <
>> matei.zaharia@gmail.com
>>>>>> wrote:
>>>>>
>>>>>> BTW, out of curiosity, are the earlier Mesos JARS (like 0.11) built
>>>> with
>>>>>> Java 6? I'd like to switch back to one that depends on Java 6
>>>> temporarily
>>>>>> in Spark, since we now switched to 0.12 and some people have trouble
>>>>>> building it. There's no code change required to use an older version
>>>>> AFAIK
>>>>>> so users could still link a new one.
>>>>>>
>>>>>> Matei
>>>>>>
>>>>>> On Jul 29, 2013, at 5:29 PM, Matei Zaharia <ma...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Unfortunately I believe it's quite hard to delete published JARs from
>>>>>> Maven because of the signature files there -- you might need to make a
>>>>> new
>>>>>> release number. However, you can try asking Apache infra.
>>>>>>>
>>>>>>> Matei
>>>>>>>
>>>>>>> On Jul 29, 2013, at 12:21 PM, Vinod Kone <vi...@gmail.com>
>>>> wrote:
>>>>>>>
>>>>>>>> Does anyone on the list know what is the policy for deleting already
>>>>>>>> published (and likely mirrored) jars in apache repository.
>>>>>>>>
>>>>>>>> We would like to upload jars built to java 6 instead of java 7.
>>>>>>>>
>>>>>>>> thanks,
>>>>>>>>
>>>>>>>>
>>>>>>>> On Fri, Jun 21, 2013 at 11:21 AM, Vinod Kone <vi...@gmail.com>
>>>>>> wrote:
>>>>>>>>
>>>>>>>>> +mesos-dev
>>>>>>>>>
>>>>>>>>> Hey Andy,
>>>>>>>>>
>>>>>>>>> Looks like we have been (unintentionally?) publishing mesos jars
>>>>>> (starting
>>>>>>>>> from mesos-0.10.0) compiled to java 7 bytecode, to the apache maven
>>>>>> repo.
>>>>>>>>> AFAIK, we are not using any java 7 features. So, I propose we
>>>> compile
>>>>>> the
>>>>>>>>> jars to java 6 and upload them. We should probably update our build
>>>>>> tool
>>>>>>>>> chain to make this explicit. I'm sure there is an option somewhere
>>>> in
>>>>>> mvn
>>>>>>>>> to the set the target byte code.
>>>>>>>>>
>>>>>>>>> Does that make sense?
>>>>>>>>>
>>>>>>>>> P.S: Not sure what is the apache policy for deleting publicly
>>>>> published
>>>>>>>>> jars.
>>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>
>>
Re: java7 jars
Posted by Vinod Kone <vi...@gmail.com>.
yes, we updated our makefile to build all our jars to 6. all our releases
from now on (starting from 0.12.1) will be built for java 6.
On Thu, Aug 1, 2013 at 3:46 PM, Matei Zaharia <ma...@gmail.com>wrote:
> I've just reverted to 0.9 until there's another JAR in Maven Central that
> I can use. Note that it's fine if you build it with Java 7, just set the
> target to Java 6.
>
> Matei
>
> On Aug 1, 2013, at 12:04 PM, Benjamin Hindman <be...@eecs.berkeley.edu>
> wrote:
>
> > Flo's stop-gap will get things building Matei (I was building Spark with
> > 0.14.0 for the past week). The 0.12.1 vote will be out today, and
> hopefully
> > released 72 hours after that!
> >
> >
> > On Thu, Aug 1, 2013 at 12:00 PM, Florian Leibert <fl...@mesosphe.re>
> wrote:
> >
> >> We have a 0.14.0 jar in our public repo:
> >>
> >>
> https://s3.amazonaws.com/mesosphere-maven-public/org/apache/mesos/mesos_jdk6/0.14.0/mesos_jdk6-0.14.0.pom
> >>
> >> Please note, that we have renamed the artifact to mesos_jdk6!
> >>
> >> That might be a good stop-gap. Including this section in your pom.xml
> file
> >> should do the trick:
> >>
> >> <repository>
> >> <id>mesosphere-public-repo</id>
> >> <name>Mesosphere Public Repo</name>
> >> <url>http://s3.amazonaws.com/mesosphere-maven-public/</url>
> >> </repository>
> >>
> >> --Flo
> >>
> >>
> >> On Thu, Aug 1, 2013 at 11:42 AM, Vinod Kone <vi...@gmail.com>
> wrote:
> >>
> >>> 0.11.0 and 0.10.0 were built *with source *jdk7 and *target *java7.
> 0.9.0
> >>> was built with source and target as java6.
> >>>
> >>> fwiw, we are prepping a release (0.12.1) this week that should be built
> >>> with source and target set to java6. would that work for you?
> >>>
> >>>
> >>> On Thu, Aug 1, 2013 at 11:24 AM, Matei Zaharia <
> matei.zaharia@gmail.com
> >>>> wrote:
> >>>
> >>>> BTW, out of curiosity, are the earlier Mesos JARS (like 0.11) built
> >> with
> >>>> Java 6? I'd like to switch back to one that depends on Java 6
> >> temporarily
> >>>> in Spark, since we now switched to 0.12 and some people have trouble
> >>>> building it. There's no code change required to use an older version
> >>> AFAIK
> >>>> so users could still link a new one.
> >>>>
> >>>> Matei
> >>>>
> >>>> On Jul 29, 2013, at 5:29 PM, Matei Zaharia <ma...@gmail.com>
> >>>> wrote:
> >>>>
> >>>>> Unfortunately I believe it's quite hard to delete published JARs from
> >>>> Maven because of the signature files there -- you might need to make a
> >>> new
> >>>> release number. However, you can try asking Apache infra.
> >>>>>
> >>>>> Matei
> >>>>>
> >>>>> On Jul 29, 2013, at 12:21 PM, Vinod Kone <vi...@gmail.com>
> >> wrote:
> >>>>>
> >>>>>> Does anyone on the list know what is the policy for deleting already
> >>>>>> published (and likely mirrored) jars in apache repository.
> >>>>>>
> >>>>>> We would like to upload jars built to java 6 instead of java 7.
> >>>>>>
> >>>>>> thanks,
> >>>>>>
> >>>>>>
> >>>>>> On Fri, Jun 21, 2013 at 11:21 AM, Vinod Kone <vi...@gmail.com>
> >>>> wrote:
> >>>>>>
> >>>>>>> +mesos-dev
> >>>>>>>
> >>>>>>> Hey Andy,
> >>>>>>>
> >>>>>>> Looks like we have been (unintentionally?) publishing mesos jars
> >>>> (starting
> >>>>>>> from mesos-0.10.0) compiled to java 7 bytecode, to the apache maven
> >>>> repo.
> >>>>>>> AFAIK, we are not using any java 7 features. So, I propose we
> >> compile
> >>>> the
> >>>>>>> jars to java 6 and upload them. We should probably update our build
> >>>> tool
> >>>>>>> chain to make this explicit. I'm sure there is an option somewhere
> >> in
> >>>> mvn
> >>>>>>> to the set the target byte code.
> >>>>>>>
> >>>>>>> Does that make sense?
> >>>>>>>
> >>>>>>> P.S: Not sure what is the apache policy for deleting publicly
> >>> published
> >>>>>>> jars.
> >>>>>>>
> >>>>>
> >>>>
> >>>>
> >>>
> >>
>
>
Re: java7 jars
Posted by Matei Zaharia <ma...@gmail.com>.
I've just reverted to 0.9 until there's another JAR in Maven Central that I can use. Note that it's fine if you build it with Java 7, just set the target to Java 6.
Matei
On Aug 1, 2013, at 12:04 PM, Benjamin Hindman <be...@eecs.berkeley.edu> wrote:
> Flo's stop-gap will get things building Matei (I was building Spark with
> 0.14.0 for the past week). The 0.12.1 vote will be out today, and hopefully
> released 72 hours after that!
>
>
> On Thu, Aug 1, 2013 at 12:00 PM, Florian Leibert <fl...@mesosphe.re> wrote:
>
>> We have a 0.14.0 jar in our public repo:
>>
>> https://s3.amazonaws.com/mesosphere-maven-public/org/apache/mesos/mesos_jdk6/0.14.0/mesos_jdk6-0.14.0.pom
>>
>> Please note, that we have renamed the artifact to mesos_jdk6!
>>
>> That might be a good stop-gap. Including this section in your pom.xml file
>> should do the trick:
>>
>> <repository>
>> <id>mesosphere-public-repo</id>
>> <name>Mesosphere Public Repo</name>
>> <url>http://s3.amazonaws.com/mesosphere-maven-public/</url>
>> </repository>
>>
>> --Flo
>>
>>
>> On Thu, Aug 1, 2013 at 11:42 AM, Vinod Kone <vi...@gmail.com> wrote:
>>
>>> 0.11.0 and 0.10.0 were built *with source *jdk7 and *target *java7. 0.9.0
>>> was built with source and target as java6.
>>>
>>> fwiw, we are prepping a release (0.12.1) this week that should be built
>>> with source and target set to java6. would that work for you?
>>>
>>>
>>> On Thu, Aug 1, 2013 at 11:24 AM, Matei Zaharia <matei.zaharia@gmail.com
>>>> wrote:
>>>
>>>> BTW, out of curiosity, are the earlier Mesos JARS (like 0.11) built
>> with
>>>> Java 6? I'd like to switch back to one that depends on Java 6
>> temporarily
>>>> in Spark, since we now switched to 0.12 and some people have trouble
>>>> building it. There's no code change required to use an older version
>>> AFAIK
>>>> so users could still link a new one.
>>>>
>>>> Matei
>>>>
>>>> On Jul 29, 2013, at 5:29 PM, Matei Zaharia <ma...@gmail.com>
>>>> wrote:
>>>>
>>>>> Unfortunately I believe it's quite hard to delete published JARs from
>>>> Maven because of the signature files there -- you might need to make a
>>> new
>>>> release number. However, you can try asking Apache infra.
>>>>>
>>>>> Matei
>>>>>
>>>>> On Jul 29, 2013, at 12:21 PM, Vinod Kone <vi...@gmail.com>
>> wrote:
>>>>>
>>>>>> Does anyone on the list know what is the policy for deleting already
>>>>>> published (and likely mirrored) jars in apache repository.
>>>>>>
>>>>>> We would like to upload jars built to java 6 instead of java 7.
>>>>>>
>>>>>> thanks,
>>>>>>
>>>>>>
>>>>>> On Fri, Jun 21, 2013 at 11:21 AM, Vinod Kone <vi...@gmail.com>
>>>> wrote:
>>>>>>
>>>>>>> +mesos-dev
>>>>>>>
>>>>>>> Hey Andy,
>>>>>>>
>>>>>>> Looks like we have been (unintentionally?) publishing mesos jars
>>>> (starting
>>>>>>> from mesos-0.10.0) compiled to java 7 bytecode, to the apache maven
>>>> repo.
>>>>>>> AFAIK, we are not using any java 7 features. So, I propose we
>> compile
>>>> the
>>>>>>> jars to java 6 and upload them. We should probably update our build
>>>> tool
>>>>>>> chain to make this explicit. I'm sure there is an option somewhere
>> in
>>>> mvn
>>>>>>> to the set the target byte code.
>>>>>>>
>>>>>>> Does that make sense?
>>>>>>>
>>>>>>> P.S: Not sure what is the apache policy for deleting publicly
>>> published
>>>>>>> jars.
>>>>>>>
>>>>>
>>>>
>>>>
>>>
>>
Re: java7 jars
Posted by Benjamin Hindman <be...@eecs.berkeley.edu>.
Flo's stop-gap will get things building Matei (I was building Spark with
0.14.0 for the past week). The 0.12.1 vote will be out today, and hopefully
released 72 hours after that!
On Thu, Aug 1, 2013 at 12:00 PM, Florian Leibert <fl...@mesosphe.re> wrote:
> We have a 0.14.0 jar in our public repo:
>
> https://s3.amazonaws.com/mesosphere-maven-public/org/apache/mesos/mesos_jdk6/0.14.0/mesos_jdk6-0.14.0.pom
>
> Please note, that we have renamed the artifact to mesos_jdk6!
>
> That might be a good stop-gap. Including this section in your pom.xml file
> should do the trick:
>
> <repository>
> <id>mesosphere-public-repo</id>
> <name>Mesosphere Public Repo</name>
> <url>http://s3.amazonaws.com/mesosphere-maven-public/</url>
> </repository>
>
> --Flo
>
>
> On Thu, Aug 1, 2013 at 11:42 AM, Vinod Kone <vi...@gmail.com> wrote:
>
> > 0.11.0 and 0.10.0 were built *with source *jdk7 and *target *java7. 0.9.0
> > was built with source and target as java6.
> >
> > fwiw, we are prepping a release (0.12.1) this week that should be built
> > with source and target set to java6. would that work for you?
> >
> >
> > On Thu, Aug 1, 2013 at 11:24 AM, Matei Zaharia <matei.zaharia@gmail.com
> > >wrote:
> >
> > > BTW, out of curiosity, are the earlier Mesos JARS (like 0.11) built
> with
> > > Java 6? I'd like to switch back to one that depends on Java 6
> temporarily
> > > in Spark, since we now switched to 0.12 and some people have trouble
> > > building it. There's no code change required to use an older version
> > AFAIK
> > > so users could still link a new one.
> > >
> > > Matei
> > >
> > > On Jul 29, 2013, at 5:29 PM, Matei Zaharia <ma...@gmail.com>
> > > wrote:
> > >
> > > > Unfortunately I believe it's quite hard to delete published JARs from
> > > Maven because of the signature files there -- you might need to make a
> > new
> > > release number. However, you can try asking Apache infra.
> > > >
> > > > Matei
> > > >
> > > > On Jul 29, 2013, at 12:21 PM, Vinod Kone <vi...@gmail.com>
> wrote:
> > > >
> > > >> Does anyone on the list know what is the policy for deleting already
> > > >> published (and likely mirrored) jars in apache repository.
> > > >>
> > > >> We would like to upload jars built to java 6 instead of java 7.
> > > >>
> > > >> thanks,
> > > >>
> > > >>
> > > >> On Fri, Jun 21, 2013 at 11:21 AM, Vinod Kone <vi...@gmail.com>
> > > wrote:
> > > >>
> > > >>> +mesos-dev
> > > >>>
> > > >>> Hey Andy,
> > > >>>
> > > >>> Looks like we have been (unintentionally?) publishing mesos jars
> > > (starting
> > > >>> from mesos-0.10.0) compiled to java 7 bytecode, to the apache maven
> > > repo.
> > > >>> AFAIK, we are not using any java 7 features. So, I propose we
> compile
> > > the
> > > >>> jars to java 6 and upload them. We should probably update our build
> > > tool
> > > >>> chain to make this explicit. I'm sure there is an option somewhere
> in
> > > mvn
> > > >>> to the set the target byte code.
> > > >>>
> > > >>> Does that make sense?
> > > >>>
> > > >>> P.S: Not sure what is the apache policy for deleting publicly
> > published
> > > >>> jars.
> > > >>>
> > > >
> > >
> > >
> >
>
Re: java7 jars
Posted by Florian Leibert <fl...@mesosphe.re>.
We have a 0.14.0 jar in our public repo:
https://s3.amazonaws.com/mesosphere-maven-public/org/apache/mesos/mesos_jdk6/0.14.0/mesos_jdk6-0.14.0.pom
Please note, that we have renamed the artifact to mesos_jdk6!
That might be a good stop-gap. Including this section in your pom.xml file
should do the trick:
<repository>
<id>mesosphere-public-repo</id>
<name>Mesosphere Public Repo</name>
<url>http://s3.amazonaws.com/mesosphere-maven-public/</url>
</repository>
--Flo
On Thu, Aug 1, 2013 at 11:42 AM, Vinod Kone <vi...@gmail.com> wrote:
> 0.11.0 and 0.10.0 were built *with source *jdk7 and *target *java7. 0.9.0
> was built with source and target as java6.
>
> fwiw, we are prepping a release (0.12.1) this week that should be built
> with source and target set to java6. would that work for you?
>
>
> On Thu, Aug 1, 2013 at 11:24 AM, Matei Zaharia <matei.zaharia@gmail.com
> >wrote:
>
> > BTW, out of curiosity, are the earlier Mesos JARS (like 0.11) built with
> > Java 6? I'd like to switch back to one that depends on Java 6 temporarily
> > in Spark, since we now switched to 0.12 and some people have trouble
> > building it. There's no code change required to use an older version
> AFAIK
> > so users could still link a new one.
> >
> > Matei
> >
> > On Jul 29, 2013, at 5:29 PM, Matei Zaharia <ma...@gmail.com>
> > wrote:
> >
> > > Unfortunately I believe it's quite hard to delete published JARs from
> > Maven because of the signature files there -- you might need to make a
> new
> > release number. However, you can try asking Apache infra.
> > >
> > > Matei
> > >
> > > On Jul 29, 2013, at 12:21 PM, Vinod Kone <vi...@gmail.com> wrote:
> > >
> > >> Does anyone on the list know what is the policy for deleting already
> > >> published (and likely mirrored) jars in apache repository.
> > >>
> > >> We would like to upload jars built to java 6 instead of java 7.
> > >>
> > >> thanks,
> > >>
> > >>
> > >> On Fri, Jun 21, 2013 at 11:21 AM, Vinod Kone <vi...@gmail.com>
> > wrote:
> > >>
> > >>> +mesos-dev
> > >>>
> > >>> Hey Andy,
> > >>>
> > >>> Looks like we have been (unintentionally?) publishing mesos jars
> > (starting
> > >>> from mesos-0.10.0) compiled to java 7 bytecode, to the apache maven
> > repo.
> > >>> AFAIK, we are not using any java 7 features. So, I propose we compile
> > the
> > >>> jars to java 6 and upload them. We should probably update our build
> > tool
> > >>> chain to make this explicit. I'm sure there is an option somewhere in
> > mvn
> > >>> to the set the target byte code.
> > >>>
> > >>> Does that make sense?
> > >>>
> > >>> P.S: Not sure what is the apache policy for deleting publicly
> published
> > >>> jars.
> > >>>
> > >
> >
> >
>
Re: java7 jars
Posted by Vinod Kone <vi...@gmail.com>.
0.11.0 and 0.10.0 were built *with source *jdk7 and *target *java7. 0.9.0
was built with source and target as java6.
fwiw, we are prepping a release (0.12.1) this week that should be built
with source and target set to java6. would that work for you?
On Thu, Aug 1, 2013 at 11:24 AM, Matei Zaharia <ma...@gmail.com>wrote:
> BTW, out of curiosity, are the earlier Mesos JARS (like 0.11) built with
> Java 6? I'd like to switch back to one that depends on Java 6 temporarily
> in Spark, since we now switched to 0.12 and some people have trouble
> building it. There's no code change required to use an older version AFAIK
> so users could still link a new one.
>
> Matei
>
> On Jul 29, 2013, at 5:29 PM, Matei Zaharia <ma...@gmail.com>
> wrote:
>
> > Unfortunately I believe it's quite hard to delete published JARs from
> Maven because of the signature files there -- you might need to make a new
> release number. However, you can try asking Apache infra.
> >
> > Matei
> >
> > On Jul 29, 2013, at 12:21 PM, Vinod Kone <vi...@gmail.com> wrote:
> >
> >> Does anyone on the list know what is the policy for deleting already
> >> published (and likely mirrored) jars in apache repository.
> >>
> >> We would like to upload jars built to java 6 instead of java 7.
> >>
> >> thanks,
> >>
> >>
> >> On Fri, Jun 21, 2013 at 11:21 AM, Vinod Kone <vi...@gmail.com>
> wrote:
> >>
> >>> +mesos-dev
> >>>
> >>> Hey Andy,
> >>>
> >>> Looks like we have been (unintentionally?) publishing mesos jars
> (starting
> >>> from mesos-0.10.0) compiled to java 7 bytecode, to the apache maven
> repo.
> >>> AFAIK, we are not using any java 7 features. So, I propose we compile
> the
> >>> jars to java 6 and upload them. We should probably update our build
> tool
> >>> chain to make this explicit. I'm sure there is an option somewhere in
> mvn
> >>> to the set the target byte code.
> >>>
> >>> Does that make sense?
> >>>
> >>> P.S: Not sure what is the apache policy for deleting publicly published
> >>> jars.
> >>>
> >
>
>