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 <[email protected]> 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 <[email protected]
> >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 <[email protected]>
> > 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 <[email protected]> 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 <[email protected]>
> > 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.
> > >>>
> > >
> >
> >
>
