Re: [VOTE] Release Apache ManifoldCF 2.17, RC1

I'll take a look at the build this AM. On Sat, Sep 12, 2020 at 5:13 AM Karl Wright wrote: > Hi all, > > I don't have a Mac, so if we can't figure out how to get ES to start > properly on a Mac, I have no ability to debug it myself. I would be forced > to recommend we just disable the test - or

Re: [VOTE] Release Apache ManifoldCF 2.17, RC1

Ok, I didn't realize this was from Maven only. It may be a working directory or dependency version issue. On Sat, Sep 12, 2020 at 11:37 AM Michael Cizmar wrote: > I reproduced the infinite Elastic Search Loop when building from maven. > I'm investigating it now. > > On Sat, Sep 12, 2020 at

Re: [VOTE] Release Apache ManifoldCF 2.17, RC1

I reproduced the infinite Elastic Search Loop when building from maven. I'm investigating it now. On Sat, Sep 12, 2020 at 9:30 AM Michael Cizmar wrote: > I'll take a look at the build this AM. > > On Sat, Sep 12, 2020 at 5:13 AM Karl Wright wrote: > >> Hi all, >> >> I don't have a Mac, so if

Re: [VOTE] Release Apache ManifoldCF 2.17, RC1

Hi Michael, JAVA_HOME is not usually a requirement for Maven building but it's not unreasonable to have it, especially since maven itself looks for it. I suspect that, in order for the Maven build to work, you currently need to do this: - Set JAVA_HOME - Run the ant build first That's a little

Re: [VOTE] Release Apache ManifoldCF 2.17, RC1

What changes did you make? Karl On Sat, Sep 12, 2020 at 2:41 PM Michael Cizmar wrote: > Didn't reach ES; waiting... > Didn't reach ES; waiting... > Didn't reach ES; waiting... > Response from ES: HTTP/1.1 200 OK > ES came up! > ElasticSearch is started on port 9200 > > @Karl - How would you

Re: [VOTE] Release Apache ManifoldCF 2.17, RC1

I figured it out. Just working through it. There was a path issue. When I start the process it's looking for a JAVA_HOME. I've got that now set to the JDK that comes with elastic. The download of elastic that ant is doing is specific for linx Linux so that's failing. Does the build require

Re: [VOTE] Release Apache ManifoldCF 2.17, RC1

Didn't reach ES; waiting... Didn't reach ES; waiting... Didn't reach ES; waiting... Response from ES: HTTP/1.1 200 OK ES came up! ElasticSearch is started on port 9200 @Karl - How would you like this packaged up? On Sat, Sep 12, 2020 at 12:52 PM Michael Cizmar wrote: > Agreed. We want to

Re: [VOTE] Release Apache ManifoldCF 2.17, RC1

Two in BaseITHSQLDB's setupElasticSearch method First to set the Java_HOME Map envs = pb.environment(); if (System.getenv("JAVA_HOME")!= null) { envs.put("JAVA_HOME",System.getenv("JAVA_HOME")); } else { throw new Exception("Missing JAVA_HOME as a system environment variable"); } The second

Re: [VOTE] Release Apache ManifoldCF 2.17, RC1

I think you are right. The es.log file contains the following: bash: ../test-materials/unix/elasticsearch-7.6.2/bin/elasticsearch: No such file or directory bash: ../test-materials/unix/elasticsearch-7.6.2/bin/elasticsearch: No such file or directory bash:

Re: [VOTE] Release Apache ManifoldCF 2.17, RC1

Ok. What about an environmental variable that is used for the download and then is read in the test case? On Sat, Sep 12, 2020 at 7:14 PM Karl Wright wrote: > Ok, the path change will break the Ant test. The maven test seems to have > the current directory set connectors/elasticsearch during

Re: [VOTE] Release Apache ManifoldCF 2.17, RC1

Ok, I committed code that should work in the following environment: when you run ant first to download the ES jar and unpack it. After that the maven build should be able to run the test. r1881672 Karl On Sat, Sep 12, 2020 at 8:14 PM Karl Wright wrote: > Ok, the path change will break the

Build failed in Jenkins: ManifoldCF » ManifoldCF-Artifacts-Ant-JDK11 #5

See Changes: [Karl Wright] Pass in the pointer to the test-materials area for both maven and ant, so the test doesn't have to care --

Re: [VOTE] Release Apache ManifoldCF 2.17, RC1

Ok, the path change will break the Ant test. The maven test seems to have the current directory set connectors/elasticsearch during testing; the ant test explicitly sets it to one of the build directories below that. But in any case I will need to consider how the test can be changed to use a

Re: [VOTE] Release Apache ManifoldCF 2.17, RC1

I used a -D variable that is set differently by maven and ant builds. It works fine for ant. Bandwidth limitations tonight mean I will try tomorrow morning for maven. Karl On Sat, Sep 12, 2020 at 9:26 PM Michael Cizmar wrote: > Ok. What about an environmental variable that is used for the