juneau-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Bognar <jamesbog...@gmail.com>
Subject Re: Java version in Jenkins build.
Date Sat, 02 Sep 2017 16:34:07 GMT
On Jenkins...

https://builds.apache.org/job/Juneau-Java-1.8/479/console

On Sat, Sep 2, 2017 at 12:33 PM, John D. Ament <johndament@apache.org>
wrote:

> On Sat, Sep 2, 2017 at 12:30 PM James Bognar <jamesbognar@gmail.com>
> wrote:
>
> > Thanks John,
> >
> > *your build JDK should be Java 8, but your source/targets remain 1.6.*
> >
> > That's what I'm trying.  We'll see if it works.
> >
> > On another note, I'm now seeing this error.  Any ideas?
> >
> >
> Is this error local or on jenkins?
>
>
> > [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
> > (default-deploy) on project juneau-microservice-template: Failed to
> > deploy artifacts: Could not transfer artifact
> > org.apache.juneau:juneau-microservice-template:jar:6.3.2 from/to
> > apache.releases.https
> > (https://repository.apache.org/service/local/staging/deploy/maven2):
> > Failed to transfer file:
> >
> > https://repository.apache.org/service/local/staging/deploy/
> maven2/org/apache/juneau/juneau-microservice-template/
> 6.3.2/juneau-microservice-template-6.3.2.jar
> > .
> > Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1]
> >
> >
> >
> > On Sat, Sep 2, 2017 at 12:12 PM, John D. Ament <johndament@apache.org>
> > wrote:
> >
> > > James,
> > >
> > > I've given you access to jenkins to manage jobs (I actually thought I
> did
> > > previously, but I must have set up the job).  I'm not sure how infra
> can
> > > help you here.  What you're looking to do just doesn't work well in
> > Maven.
> > > I would recommend that if this is what you want (Java 6 for everything
> > but
> > > MicroServices, Java 8 for MicroServices) that your build JDK should be
> > Java
> > > 8, but your source/targets remain 1.6.
> > >
> > > Note that this has some problems with it.  If you have any cases of
> > default
> > > methods, it won't work.
> > >
> > > John
> > >
> > > On Sat, Sep 2, 2017 at 11:34 AM James Bognar <jamesbognar@apache.org>
> > > wrote:
> > >
> > > > Only the microservice requires Java 8 due to Jetty (and by extension
> > the
> > > > rest-test which uses microservice).  All other artifacts require only
> > > Java
> > > > 6.
> > > >
> > > > David's team is using only the RDF marshalling APIs and cannot move
> up
> > to
> > > > Java 8.
> > > >
> > > >
> > > >
> > > > On Sat, Sep 2, 2017 at 11:01 AM, Jochen Wiedmann <
> > > > jochen.wiedmann@gmail.com>
> > > > wrote:
> > > >
> > > > > If there is a dependency, which requires Java 8: What's the point
> in
> > > > > declaring 1.6? As for the Jenkins job: Create an INFRA issue in
> Kira.
> > > > >
> > > > > On Sep 2, 2017 4:49 PM, "James Bognar" <jamesbognar@apache.org>
> > wrote:
> > > > >
> > > > > > How do I change the Java version in the Jenkins build?
> > > > > >
> > > > > > I see the JAVA_HOME environment variable set to
> > > > /home/jenkins/tools/java
> > > > > > /latest1.7.  We need to change this to Java 1.8 since that's
> what's
> > > > > > prereq'ed by Jetty.  I don't think I have authority to change
it.
> > > > > >
> > > > > > I've added <maven.compiler.source|target> to 1.6 on all
the
> > projects
> > > > > except
> > > > > > the rest-test and microservice projects, so we should be able
to
> > > build
> > > > > with
> > > > > > Java 8.
> > > > > >
> > > > >
> > > >
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message