Re: I would like to put together an MCF 2.7 release candidate by the end of the week

Yes, I agree. I put some effort into trying to get ManifoldCF to work with log4j 2.x, and was partly successful, but logs still are going to stdout so obviously I'm not done yet. It's too destabilizing; this will have to wait until 2.8. Karl On Sat, Apr 15, 2017 at 5:12 AM, Rafa Haro

Re: I would like to put together an MCF 2.7 release candidate by the end of the week

Hi Karl, I honestly have just downloaded the new connector from the student GitHub, I have not checked anything else, so that's the main source of the problems. I know he has been testing it so far by packaging it in a single jar and including it into manifold classpath I would suggest to then

Re: I would like to put together an MCF 2.7 release candidate by the end of the week

FWIW, the reason for the job crawl failure is due to the version mismatch for log4j, so we'll need to figure out what to do about that: >> org.nuxeo.client.internals.spi.NuxeoClientException: org/apache/logging/log4j/Lo gManager at

Re: I would like to put together an MCF 2.7 release candidate by the end of the week

Well, when I run it using made-up host names, the job dies with the following: >> Error: Repeated service interruptions during startup: Could not initialize class org.nuxeo.client.api.marshaller.NuxeoResponseConverterFactory << This is against client version 2.5, not version

Re: I would like to put together an MCF 2.7 release candidate by the end of the week

There were a lot of problems with the code -- everything from missing Apache headers to broken HTML to broken password management. I've fixed what I could find. It would be great if someone could try this connector out enough to confirm that it's working. It's also a bit disconcerting that you

Re: I would like to put together an MCF 2.7 release candidate by the end of the week

Ok, I've added everything needed. There is a version difference that I don't want to tackle though right now: the nuxeo client depends on log4j 2.4, and everything else depends on log4j 1.2. I'm hoping this isn't going to cause things to blow up, but I suppose I'll find out soon enough. Karl

Re: I would like to put together an MCF 2.7 release candidate by the end of the week

Also, for what it's worth, these are the dependencies from the nuxeo-java-client.jar: >> [INFO] \- org.nuxeo.client:nuxeo-java-client:jar:2.5:compile [INFO]+- com.squareup.retrofit2:retrofit:jar:2.0.2:compile [INFO]+- com.squareup.okhttp3:okhttp:jar:3.0.0-RC1:compile [INFO]| \-

Re: I would like to put together an MCF 2.7 release candidate by the end of the week

The 2.6 snapshot is blank. There is no available 2.5-snapshot anywhere I can find. I have to conclude it's not available except when built privately? I guess we can release the connector with the 2.5 jar? Karl On Fri, Apr 14, 2017 at 5:56 PM, Karl Wright wrote: > It

Re: I would like to put together an MCF 2.7 release candidate by the end of the week

It looks like there isn't a 2.5 snapshot; there's just a 2.6 snapshot, uploaded yesterday. Should we use that instead? Karl On Fri, Apr 14, 2017 at 5:53 PM, Karl Wright wrote: > Hi Rafa, > > I can't seem to download the client jar: > > >> > [get] Getting:

Re: I would like to put together an MCF 2.7 release candidate by the end of the week

Hi Rafa, I can't seem to download the client jar: >> [get] Getting: http://maven.nuxeo.com/nexus/content/repositories/public-snapshots/org/nuxeo/client/nuxeo-java-client/2.5-SNAPSHOT/nuxeo-java-client-2.5-SNAPSHOT.jar [get] To:

Re: I would like to put together an MCF 2.7 release candidate by the end of the week

Built successfully. Initially only nuxeo-java-client library dependency is needed. I have included it and I already checked the compatibility some time ago. On Fri, Apr 14, 2017 at 11:37 PM Karl Wright wrote: > Are there new dependencies downloaded into lib? If so, what

Re: I would like to put together an MCF 2.7 release candidate by the end of the week

Looks like NuxeoClient is missing but required in the ant build. Karl On Fri, Apr 14, 2017 at 5:37 PM, Karl Wright wrote: > Are there new dependencies downloaded into lib? If so, what are they? > How are they licensed? Have you run "mvn dependencies:tree" to make sure >

Re: I would like to put together an MCF 2.7 release candidate by the end of the week

Are there new dependencies downloaded into lib? If so, what are they? How are they licensed? Have you run "mvn dependencies:tree" to make sure all the child dependencies are also included? Thanks, Karl On Fri, Apr 14, 2017 at 5:33 PM, Rafa Haro wrote: > No problem. Sorry

Re: I would like to put together an MCF 2.7 release candidate by the end of the week

No problem. Sorry for the delay. In some minutes I will inform about the build result On Fri, Apr 14, 2017 at 11:29 PM Karl Wright wrote: > Thanks; I'll check out the ant build. > > Karl > > > On Fri, Apr 14, 2017 at 5:29 PM, Rafa Haro wrote: > > > Hi all,

Re: I would like to put together an MCF 2.7 release candidate by the end of the week

Thanks; I'll check out the ant build. Karl On Fri, Apr 14, 2017 at 5:29 PM, Rafa Haro wrote: > Hi all, > > I have updated CONNECTORS-1290-2 branch with the new Nuxeo Connector code. > Running mvn clean package now. > > Build.xml is updated but I have not tested it > > > > On

Re: I would like to put together an MCF 2.7 release candidate by the end of the week

Hi all, I have updated CONNECTORS-1290-2 branch with the new Nuxeo Connector code. Running mvn clean package now. Build.xml is updated but I have not tested it On Fri, Apr 14, 2017 at 1:06 PM Piergiorgio Lucidi wrote: > Hi, > > I'm sorry but I didn't find enough time

Re: I would like to put together an MCF 2.7 release candidate by the end of the week

Hi, I'm sorry but I didn't find enough time for working on this new connector so we should postpone it to the 2.8 version. I have to confess that probably I should port the initial implementation to a new branch based on 2.7 because I see a lot of improvements and changes. Anyway during the

Re: I would like to put together an MCF 2.7 release candidate by the end of the week

Ok Karl, I finally couldn't contact David so I will commit it to the rebased branch today. I will change the build.xml file myself but I'm not going to be able to test it at least today. I will let you know. I'm out now, but I expect to reach home and do it in a couple of hours El El vie, 14 abr

Re: I would like to put together an MCF 2.7 release candidate by the end of the week

Hi Rafa, I'd like to create the 2.7 release branch today, if possible, but I will wait until Sunday if the Nuxeo connector is expected to be committed to the branch by then. I really can't wait after Sunday, though, because I will be unavailable for the last week of April, even for Apache tasks.

Re: I would like to put together an MCF 2.7 release candidate by the end of the week

Is this still looking plausible? Karl On Mon, Apr 10, 2017 at 4:40 AM, Rafa Haro wrote: > Hi Karl, > > Nuxeo connector should be ready by then. I will meet with David (the > student) today or tomorrow and will try to commit everything > > Cheers, > Rafa > > On Mon, Apr 10,

Re: I would like to put together an MCF 2.7 release candidate by the end of the week

Hi Karl, Nuxeo connector should be ready by then. I will meet with David (the student) today or tomorrow and will try to commit everything Cheers, Rafa On Mon, Apr 10, 2017 at 9:46 AM Piergiorgio Lucidi wrote: > Hi Karl, > > thank you for this message. > > I had some

Re: I would like to put together an MCF 2.7 release candidate by the end of the week

Hi Karl, thank you for this message. I had some problems for working on the new CMIS Output connector, I hope to finish it this week. Otherwise we have to put it on the next release. Cheers, PJ 2017-04-10 9:02 GMT+02:00 Karl Wright : > Hi folks, > > I would like to put

I would like to put together an MCF 2.7 release candidate by the end of the week

Hi folks, I would like to put together a ManifoldCF 2.7 release candidate by the beginning of next week. However, there are a number of open tickets. Some of them appear to be near complete, such as the Nuxeo connector; others seem to be forgotten for the moment. But we need to finish things