Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ice-dev] Build failures

Jay,


The JDK seems fine, though I'm still double checking on my desktop. The problem is that some viz.service.javafx.mesh tests made it into viz.service.javafx.test, where they aren't resolving their classes properly because they aren't supposed to be in that package (or in the build at all, yet). I've push a commit to fix it after finishing a successful build to ensure that's the only issue.


There is another problem I've found. I'm getting this error message:


RROR] The build could not read 2 projects -> [Help 1]
[ERROR]   
[ERROR]   The project ICE:org.eclipse.ice.dependencies:[unknown-version] (/home/r8s/Desktop/ice.product-linux.gtk.x86_64(2)/workspace/ICEDeps/org.eclipse.ice.dependencies/pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM for ICE:org.eclipse.ice.dependencies:[unknown-version]: Failure to find ICE:org.eclipse.ice.build:pom:2.1.8.20160208 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 6, column 10 -> [Help 2]
[ERROR]   
[ERROR]   The project ICE:gov.lbnl.visit.swt:2.1.8.20160208 (/home/r8s/Desktop/ice.product-linux.gtk.x86_64(2)/workspace/visit_java_client/gov.lbnl.visit.swt/pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM for ICE:gov.lbnl.visit.swt:2.1.8.20160208: Failure to find ICE:org.eclipse.ice.build:pom:2.1.8.20160208 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 6, column 10 -> [Help 2]
[ERROR]


but only when I try to build off a fresh clone of the repo, not when I pull the latest version into an old workspace. It appears that ICEDeps and the VisIt Java client are looking for the wrong version number for ICE, but only in the latest commits, while Habilis is avoiding the problem because it's using earlier versions of those two packages.


Robert


From: ice-dev-bounces@xxxxxxxxxxx <ice-dev-bounces@xxxxxxxxxxx> on behalf of Jay Jay Billings <jayjaybillings@xxxxxxxxx>
Sent: Tuesday, February 09, 2016 3:15 PM
To: ice developer discussions
Subject: Re: [ice-dev] Build failures
 
Everyone,

Robert and I are still looking into this. It appears that the build machine ignores the proper JDK.

Jay

On Mon, Feb 8, 2016 at 4:42 PM, Jay Jay Billings <jayjaybillings@xxxxxxxxx> wrote:
Everyone,

We have a whole bunch of build failures popping off. This is pretty normal when I update the version numbers and do these types of mergers. I should have them fixed by COB tomorrow. Sorry for the spam in the meantime.

Jay

--
Jay Jay Billings
Oak Ridge National Laboratory
Twitter Handle: @jayjaybillings



--
Jay Jay Billings
Oak Ridge National Laboratory
Twitter Handle: @jayjaybillings

Back to the top