Yes .. I think this is what I experienced. I guess I got the 5.1.2 from
some internal Adobe build.
So upgrading to 5.1.3 makes a lot of sense.
Christian
2017-10-30 8:34 GMT+01:00 Davide Giannella :
> On 27/10/2017 15:08, Julian Reschke wrote:
> > Yes. There are indeed two different versions of t
On 2017-10-30 08:34, Davide Giannella wrote:
...
I see that xmpcore is not up to version 6.1.10. Maybe by simply updating
tikka to 5.1.3 could solve this issue for good.
...
https://issues.apache.org/jira/browse/TIKA-2486
Best regards, Julian
On 27/10/2017 15:08, Julian Reschke wrote:
> Yes. There are indeed two different versions of this artifact. I have
> no idea why.
I think the main reason is that before 5.1.2 xmpcore were a closed
source project within Adobe. the 5.1.2 version has been release both
internally in adobe and later o
On 2017-10-27 14:46, Davide Giannella wrote:
On 27/10/2017 14:28, Christian Schneider wrote:
Hi all,
I am currently trying to build oak from master. When doing mvn clean
install I get an error in the oak-lucene module.
It looks like the referenced adobe granite parent pom is missing. I guess
th
On 27/10/2017 14:28, Christian Schneider wrote:
> Hi all,
>
> I am currently trying to build oak from master. When doing mvn clean
> install I get an error in the oak-lucene module.
> It looks like the referenced adobe granite parent pom is missing. I guess
> this error does not occur when someone
Hi all,
I am currently trying to build oak from master. When doing mvn clean
install I get an error in the oak-lucene module.
It looks like the referenced adobe granite parent pom is missing. I guess
this error does not occur when someone builds using the Adobe vpn.
So I think we need to publish
