Great, thanks Stian.
On Apr 6, 2015 12:50 AM, "Stian Soiland-Reyes" <[email protected]> wrote:

> No problem :)
>
> Snapshots now in
>
> https://repository.apache.org/content/repositories/snapshots/org/apache/commons/commons-rdf-api/
> and siblings.
>
>
>
> On 5 April 2015 at 23:45, John D. Ament <[email protected]> wrote:
> > On Sun, Apr 5, 2015 at 6:03 PM Stian Soiland-Reyes <[email protected]>
> wrote:
> >
> >> Not sure what was the conclusion to this, but as
> >>
> >> https://travis-ci.org/apache/incubator-commonsrdf/
> >>
> >> didn't deploy snapshots, I also enabled Jenkins to do so (on success),
> >> checking git every 7 minutes:
> >>
> >> https://builds.apache.org/job/incubator-commonsrdf/
> >>
> >>
> >>
> > My fault, that's what I said I'd take care of, never did.
> >
> >
> >> As you might have noticed already, I configured the Jenkins job to
> >> email dev@commonsrdf if something breaks the build -- but perhaps
> >> Travis would also do that?
> >>
> >> (Those HTML-picky javadoc-error which only happens on some machines is
> >> still a mystery to me)
> >>
> >> On 28 March 2015 at 21:32, Peter Ansell <[email protected]> wrote:
> >> > That is fine with me.
> >> >
> >> > I am not overly fascinated by internal Apache infrastructure though so
> >> > I would like to keep the .travis.yml file and the references to
> >> > coveralls if possible as there is nothing broken with that system
> >> > right now for CI and code coverage.
> >> >
> >> > Thanks,
> >> >
> >> > Peter
> >> >
> >> >
> >> > On 28 March 2015 at 23:12, John D. Ament <[email protected]>
> wrote:
> >> >> Unless anyone sees any issues with it, I'd like to enable Jenkins
> builds
> >> >> for CommonsRDF.
> >> >>
> >> >> Let me know.
> >> >>
> >> >> John
> >>
> >>
> >>
> >> --
> >> Stian Soiland-Reyes
> >> Apache Taverna (incubating), Apache Commons RDF (incubating)
> >> http://orcid.org/0000-0001-9842-9718
> >>
>
>
>
> --
> Stian Soiland-Reyes
> Apache Taverna (incubating), Apache Commons RDF (incubating)
> http://orcid.org/0000-0001-9842-9718
>

Reply via email to