ok, I know what the issue is.
When I do the mcf release build, which does clean all the mcf downloaded
artifacts, apparently it misses the test-materials directory under
connectors/mongodb :
Directory of
C:\wip\mcf\release-2.22-branch\connectors\mongodb\test-materials
04/27/2022 09:07 AM
Hmm, now I get the same thing as well.
Ok, let's call this fixed. I'll spin a new RC.
Karl
On Fri, Apr 29, 2022 at 8:57 AM Piergiorgio Lucidi
wrote:
> Nope, no errors, I have a BUILD SUCCESSFUL
>
> Il giorno ven 29 apr 2022 alle ore 14:54 Karl Wright
> ha scritto:
>
> > once again, I have
Nope, no errors, I have a BUILD SUCCESSFUL
Il giorno ven 29 apr 2022 alle ore 14:54 Karl Wright
ha scritto:
> once again, I have the same.
>
> Can you try this:
>
> cd connectors/mongodb
> ant run-tests
>
> Do you get a compilation exception?
>
> Karl
>
>
> On Fri, Apr 29, 2022 at 8:49 AM
once again, I have the same.
Can you try this:
cd connectors/mongodb
ant run-tests
Do you get a compilation exception?
Karl
On Fri, Apr 29, 2022 at 8:49 AM Piergiorgio Lucidi
wrote:
> -rw-r--r-- 1 pjlucidi staff 613352 29 Apr 11:46
> mongo-java-driver-2.14.3.jar
>
> Il giorno ven 29 apr
-rw-r--r-- 1 pjlucidi staff 613352 29 Apr 11:46
mongo-java-driver-2.14.3.jar
Il giorno ven 29 apr 2022 alle ore 14:48 Karl Wright
ha scritto:
> I have same:
>
> 04/28/2022 06:24 AM .
> 04/28/2022 06:24 AM ..
> 04/28/2022 06:24 AM 189,132
I have same:
04/28/2022 06:24 AM .
04/28/2022 06:24 AM ..
04/28/2022 06:24 AM 189,132 de.flapdoodle.embed.mongo-3.4.5.jar
04/28/2022 06:24 AM 111,113
de.flapdoodle.embed.mongo.packageresolver-1.0.3.jar
04/28/2022 06:24 AM 215,729
-rw-r--r-- 1 pjlucidi staff 107870 29 Apr 11:47
de.flapdoodle.os-1.1.8.jar
-rw-r--r-- 1 pjlucidi staff 215729 29 Apr 11:47
de.flapdoodle.embed.process-3.1.10.jar
-rw-r--r-- 1 pjlucidi staff 13 29 Apr 11:47
de.flapdoodle.embed.mongo.packageresolver-1.0.3.jar
-rw-r--r-- 1 pjlucidi
;> error: incompatible types: MongodConfig cannot be converted to
> > IMongodConfig
> > >> [javac] mongodExecutable =
> > starter.prepare(mongodConfig);
> > >> [javac]^
> > >> [javac] Note:
^
> >> [javac] Note: Some messages have been simplified; recompile with
> >> -Xdiags:verbose to get full output
> >> [javac] 1 error
> >> [javac] 1 warning
> >>
> >> BUILD FAILED
> >>
> >> Please let m
[javac] 1 error
>> [javac] 1 warning
>>
>> BUILD FAILED
>>
>> Please let me know if I missed something
>>
>> Julien
>>
>> -Message d'origine-
>> De : Karl Wright
>> Envoyé : mercredi 27 avril 2022 17:43
>&
essage d'origine-
> De : Karl Wright
> Envoyé : mercredi 27 avril 2022 17:43
> À : dev
> Objet : Re: [CANCEL] [VOTE] Release Apache ManifoldCF 2.22, RC2
>
> Perhaps the user didn't actually make the proper deps? There is a check
> in the ant build for whether the dependency i
The infrastructure team fixed the GitHub mirror sync issue.
See the comments in
https://issues.apache.org/jira/browse/INFRA-23212
Markus
Am 27. April 2022 21:29:31 MESZ schrieb Karl Wright :
>The 2.22 release artifacts got inadvertently committed to that release
>branch but they have been
t; >>> [junit] at
> > >>> org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> > >>> [junit] at
> > >>> org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> > >>> [junit] at
> >
The 2.22 release artifacts got inadvertently committed to that release
branch but they have been deleted. We can't remove them from SVN history
however, because we don't have the rights.
If you committed to trunk I will try to pull up your changes to the release
branch.
Karl
On Wed, Apr 27,
Hi,
I still miss the 2.22 release in JIRA to be able to tag all the issues
properly. Can someone create this? I don't have the rights.
Another open issue is that the 2.22 release branch causes a problem with
the GitHub sync: https://issues.apache.org/jira/browse/INFRA-23212
Somehow we have to
server-inmemory-1.1.0-patched.war}
BUILD FAILED
-Message d'origine-
De : Karl Wright
Envoyé : mercredi 27 avril 2022 15:50
À : dev
Objet : [VOTE] Release Apache ManifoldCF 2.22, RC2
Hi,
Please vote on whether to release Apache ManifoldCF 2.22, RC2. The
release artifact is at
rentRunner.run(ParentRunner.java:363)
> > >>> [junit] at
> > >>> junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:38)
> > >>> [junit] at
> > >>>
> >
> org.apache.tools.ant.taskdefs.optional.junit.J
t
> >>>
> org.apache.chemistry.opencmis.client.runtime.SessionFactoryImpl.getRepositories(SessionFactoryImpl.java:107)
> >>> [junit] at
> >>>
> org.apache.manifoldcf.agents.output.cmisoutput.tests.APISanityHSQLDBIT.getCmisSourceClientSession(APISanityHSQLDBIT.java:8
unChild(BlockJUnit4ClassRunner.java:57)
>>> [junit] at
>>> org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>>> [junit] at
>>> org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>>> [junit] at
>>> org.
gt; [junit] [main] INFO org.eclipse.jetty.server.handler.ContextHandler -
>> Stopped o.e.j.w.WebAppContext@7692cd34{ManifoldCF Authorities API
>> Webapp,/mcf-authority-service,null,UNAVAILABLE}{/home/francelabs/workspace/mcf-svn/dist/web/war/mcf-authority-service.war}
>> [junit]
; [junit] at
> org.apache.chemistry.opencmis.client.bindings.impl.RepositoryServiceImpl.getRepositoryInfos(RepositoryServiceImpl.java:92)
> [junit] at
> org.apache.chemistry.opencmis.client.runtime.SessionFactoryImpl.getRepositories(SessionFactoryImpl.java:120)
> [junit]
-opencmis-server-inmemory,null,UNAVAILABLE}{../test-materials/chemistry-opencmis-server-inmemory-1.1.0-patched.war}
BUILD FAILED
-Message d'origine-
De : Karl Wright
Envoyé : mercredi 27 avril 2022 15:50
À : dev
Objet : [VOTE] Release Apache ManifoldCF 2.22, RC2
Hi,
Please vote on whether
Hi,
Please vote on whether to release Apache ManifoldCF 2.22, RC2. The release
artifact is at
https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.22 .
There is also a release tag at
https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.22-RC2 .
This release contains a
23 matches
Mail list logo
