Looks like its building now.  w00t.

On Sat, Nov 5, 2016 at 10:51 AM Anatole Tresch <[email protected]> wrote:

> +1 also for new people trying to build, if they parent has not been
> installed lovally the build will fail. Disadvantage is that we have
> redundancy regarding developers, sw version, so we have to keep an eye on
> it...
>
> J Anatole
>
>
> 2016-11-05 15:26 GMT+01:00 John D. Ament <[email protected]>:
>
> > Changing to Apache parent causes this, which is further:
> > https://paste.apache.org/p/bEBx
> >
> >
> > On Sat, Nov 5, 2016 at 10:23 AM John D. Ament <[email protected]>
> > wrote:
> >
> > > Oliver,
> > >
> > > I'll raise the same concern I raised in the past - if extensions
> require
> > > tamaya's core repo, it shouldn't be a separate repo.
> > >
> > > Right now the parent for extensions is tamaya-all.  I would recommend
> > that
> > > its standard apache parent.
> > >
> > > John
> > >
> > > On Sat, Nov 5, 2016 at 5:48 AM Oliver B. Fischer <
> > [email protected]>
> > > wrote:
> > >
> > > Hi, I need your help. I can locally not reproduce the build error on
> > > Jenkins. Depending on various settings sometimes it builds sometimes
> not.
> > >
> > > Can you please try to build the extensions project on your machine with
> > an
> > > empty Maven cache and an activated ASF snapshot repository? The
> > > configuration for the ASF repository can be found in the additional
> > > settings-with-*.xml.
> > >
> > > Oliver
> > >
> > > Von meinem iPhone gesendet
> > >
> > >
> >
>
>
>
> --
> *Anatole Tresch*
> PPMC Member Apache Tamaya
> JCP Star Spec Lead
> *Switzerland, Europe Zurich, GMT+1*
> *maketechsimple.wordpress.com <http://maketechsimple.wordpress.com/> *
> *Twitter:  @atsticks, @tamayaconf*
>

Reply via email to