I reconfigured the Jenkins job to use a workspace-local m2 folder. That didn't seem to help. Since built 384 (before I reconfigured), we have these problems:
Failed to transfer Could not find artifact org.apache.uima:parent-pom:pom:8 in eclipsePlugins (http://repo1.maven.org/eclipse) Downloaded artifact http://repo1.maven.org/maven2/org/apache/uima/parent-pom/8/parent-pom-8.pom Failed to transfer Could not find artifact org.apache:apache:pom:13 in eclipsePlugins (http://repo1.maven.org/eclipse) Downloaded artifact http://repo1.maven.org/maven2/org/apache/apache/13/apache-13.pom Before build 384, we had this problems: [ERROR] Failed to execute goal on project ruta-ep-caseditor: Could not resolve dependencies for project org.apache.uima:ruta-ep-caseditor:jar:2.2.0-SNAPSHOT: Could not find artifact org.eclipse.equinox:app:jar:1.0.0 in eclipsePlugins (http://repo1.maven.org/eclipse) -> [Help 1] While the pre-384 could be solvable by the reconfiguration to the workspace-local m2, I have no idea what causes the 384-and-post problem... Cheers, -- Richard On 26.03.2014, at 10:57, Peter Klügl <[email protected]> wrote: > Well, I could try if that's really the problem by depending temporarily > on the snapshot version and changing the dependency in the CAS Editor > plugin. > > The changes can easily be taken back. > > Peter > > Am 25.03.2014 21:06, schrieb Peter Klügl: >> Am 25.03.2014 20:37, schrieb Marshall Schor: >>> I see the Jenkins Ruta build is still broken - is that important? is >>> that hard >>> to fix? Sound like it's something to do with the fact that the build >>> uses some >>> "shared" local .m2 repo on the build machine, and that repo has some >>> artifacts >>> which get included, and which in turn require other artifacts, which >>> can't be >>> resolved? >>> >>> If these could be identified, maybe a build step (on Jenkins only?) >>> could be >>> added to remove the offending artifacts from the local .m2? >> >> I not sure, but I think it's the equniox.app dependencies of the CAS >> Editor plugins. They are set to [1.0.0,1.0.1) which is not available >> in maven central. I think that range is excluded in the ruta plugins >> and they are using a range that is available. I thought about >> changing the dependency in the CAS Editor plugin, but that would help >> not until uima 2.5.1 is released since I do not really want to depend >> on a snapshot version. Maybe the jenkins build tries to download it >> because I activated -U. I don't know. >> >> Anyways, that's just a guess and it should not matter for the release. >> It's a bit annoying... >> >> Peter >> >>> -Marshall
