oak-upgrade blocking the 1.7.1 release

[Davide Giannella <da...@apache.org>]

Hello team,

can anyone with knowledge of the oak-upgrade module take a look at
https://issues.apache.org/jira/browse/OAK-6306 ?

It's currently blocking the release of 1.7.1

We may as well have the same problem with `oak-blob-plugins` but I don't
have time today for a deeper look. you can easily trigger the error with
`mvn clean site -Pjavadoc` from the reactor.

Cheers
Davide

Re: oak-upgrade blocking the 1.7.1 release

[Davide Giannella <da...@apache.org>]

On 06/06/2017 08:23, Julian Reschke wrote:
> Davide, you did the 1.7.0 release, right? Do you recall how you got
> past the error? 

Nope. I did the release with the same jdk as I remember I was stuck with
the javadoc errors. These for some reasons came up only for this
release. I assume it's new stuff but I didn't check.

D.

Re: oak-upgrade blocking the 1.7.1 release

[Tomek Rękawek <re...@adobe.com>]

Hi,

In OAK-6306 Davide provided a workaround for the broken javadocs (using a different Lucene version for the javadocs generation only). We can’t upgrade the Lucene version used by oak-upgrade, because it’ll break the Jackrabbit 2 - and we need to have this working in this module.

Regards,
Tomek

-- 
Tomek Rękawek | Adobe Research | www.adobe.com
rekawek@adobe.com

> On 6 Jun 2017, at 09:23, Julian Reschke <ju...@gmx.de> wrote:
> 
> On 2017-06-06 09:09, Alex Parvulescu wrote:
>> I'm not convinced. If you look at the javadoc error it is exactly like the
>> one from OAK-6150 (blocking 1.7.0 release at that time) that seemed to
>> magically go away.
> 
> Actually, I meant to make that a question....
> 
> Davide, you did the 1.7.0 release, right? Do you recall how you got past the error?
> 
> We may want to do this for 1.7.1 again, but in the mid term, we need to fix this somehow...
> 
> Best regards, Julian

Re: oak-upgrade blocking the 1.7.1 release

[Julian Reschke <ju...@gmx.de>]

On 2017-06-06 09:09, Alex Parvulescu wrote:
> I'm not convinced. If you look at the javadoc error it is exactly like the
> one from OAK-6150 (blocking 1.7.0 release at that time) that seemed to
> magically go away.

Actually, I meant to make that a question....

Davide, you did the 1.7.0 release, right? Do you recall how you got past 
the error?

We may want to do this for 1.7.1 again, but in the mid term, we need to 
fix this somehow...

Best regards, Julian

Re: oak-upgrade blocking the 1.7.1 release

[Alex Parvulescu <al...@gmail.com>]

I'm not convinced. If you look at the javadoc error it is exactly like the
one from OAK-6150 (blocking 1.7.0 release at that time) that seemed to
magically go away.

On Tue, Jun 6, 2017 at 8:53 AM, Julian Reschke <ju...@gmx.de>
wrote:

> On 2017-06-05 16:30, Davide Giannella wrote:
>
>> Hello team,
>>
>> can anyone with knowledge of the oak-upgrade module take a look at
>> https://issues.apache.org/jira/browse/OAK-6306 ?
>>
>> It's currently blocking the release of 1.7.1
>>
>> We may as well have the same problem with `oak-blob-plugins` but I don't
>> have time today for a deeper look. you can easily trigger the error with
>> `mvn clean site -Pjavadoc` from the reactor.
>>
>> Cheers
>> Davide
>>
>
> Just checking: so this was caused by something that changed between 1.7.0
> and 1.7.1.
>
> Best regards, Julian
>

Re: oak-upgrade blocking the 1.7.1 release

[Julian Reschke <ju...@gmx.de>]

On 2017-06-05 16:30, Davide Giannella wrote:
> Hello team,
> 
> can anyone with knowledge of the oak-upgrade module take a look at
> https://issues.apache.org/jira/browse/OAK-6306 ?
> 
> It's currently blocking the release of 1.7.1
> 
> We may as well have the same problem with `oak-blob-plugins` but I don't
> have time today for a deeper look. you can easily trigger the error with
> `mvn clean site -Pjavadoc` from the reactor.
> 
> Cheers
> Davide

Just checking: so this was caused by something that changed between 
1.7.0 and 1.7.1.

Best regards, Julian