You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by Julian Reschke <ju...@gmx.de> on 2016/07/04 15:37:03 UTC

Jackrabbit 2.13.0 release plan

Hi,

we'll need to cut Jackrabbit 2.13.0 in the next few days.


There are currently two unresolved issues; can we re-schedule them?

https://issues.apache.org/jira/browse/JCR-3913

https://issues.apache.org/jira/browse/JCR-3944

Also, I'm looking for a volunteer for the release, or alternatively for 
somebody who would be available for hand holding (back when I releases 
the last time a long time ago, I had to struggle with Cygwin/Windows 
issues).

Best regards, Julian

Re: Jackrabbit 2.13.0 release plan

Posted by Julian Reschke <ju...@greenbytes.de>.
On 2016-07-05 15:00, Woonsan Ko wrote:
> Hi Julian,
>
> I'd like to give a hand if there's anything I can help with. Do you
> have jira issue list or task list we can have look at?
>
> Regards,
>
> Woonsan

Woonsan,

the release process is documented at 
<http://jackrabbit.apache.org/jcr/creating-releases.html>...

The steps per se arenn't complicated, except for that some tools behave 
weird on Cygwin (such as the maven scm plugin) -- and that's what's 
making it harder than it should for me.

Best regards, Julian

Re: Jackrabbit 2.13.0 release plan

Posted by Woonsan Ko <wo...@apache.org>.
Hi Julian,

I'd like to give a hand if there's anything I can help with. Do you
have jira issue list or task list we can have look at?

Regards,

Woonsan


On Mon, Jul 4, 2016 at 11:37 AM, Julian Reschke <ju...@gmx.de> wrote:
> Hi,
>
> we'll need to cut Jackrabbit 2.13.0 in the next few days.
>
>
> There are currently two unresolved issues; can we re-schedule them?
>
> https://issues.apache.org/jira/browse/JCR-3913
>
> https://issues.apache.org/jira/browse/JCR-3944
>
> Also, I'm looking for a volunteer for the release, or alternatively for
> somebody who would be available for hand holding (back when I releases the
> last time a long time ago, I had to struggle with Cygwin/Windows issues).
>
> Best regards, Julian

Re: Jackrabbit 2.13.0 release plan

Posted by Julian Reschke <ju...@gmx.de>.
On 2016-07-06 15:45, Woonsan Ko wrote:
> Hi Julian,
>
> Don't know the cause exactly, but looks like the maven-release-plugin
> 2.1 might be incompatible with your maven version. What's your maven
> version (`mvn -v`)?
> Also, maven-release-plugin 2.1 is a bit older version. [1]
> So, could you try with the latest version like the following instead?
>
> $ mvn org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare
>
> (We can specify the full qualified name instead. e.g. mvn
> org.apache.maven.plugins:maven-release-plugin:2.5.3:perform)
>
> Regards,
>
> Woonsan
>
> [1] http://maven.apache.org/maven-release/maven-release-plugin/usage.html

Ah, thanks! That gets me past the error.

Thanks so far!

Re: Jackrabbit 2.13.0 release plan

Posted by Woonsan Ko <wo...@apache.org>.
Hi Julian,

Don't know the cause exactly, but looks like the maven-release-plugin
2.1 might be incompatible with your maven version. What's your maven
version (`mvn -v`)?
Also, maven-release-plugin 2.1 is a bit older version. [1]
So, could you try with the latest version like the following instead?

$ mvn org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare

(We can specify the full qualified name instead. e.g. mvn
org.apache.maven.plugins:maven-release-plugin:2.5.3:perform)

Regards,

Woonsan

[1] http://maven.apache.org/maven-release/maven-release-plugin/usage.html

On Wed, Jul 6, 2016 at 8:47 AM, Julian Reschke <ju...@gmx.de> wrote:
> On 2016-07-06 14:11, Julian Reschke wrote:
>>
>> On 2016-07-04 17:37, Julian Reschke wrote:
>>>
>>> Hi,
>>>
>>> we'll need to cut Jackrabbit 2.13.0 in the next few days.
>>>
>>>
>>> There are currently two unresolved issues; can we re-schedule them?
>>>
>>> https://issues.apache.org/jira/browse/JCR-3913
>>>
>>> https://issues.apache.org/jira/browse/JCR-3944
>>>
>>> Also, I'm looking for a volunteer for the release, or alternatively for
>>> somebody who would be available for hand holding (back when I releases
>>> the last time a long time ago, I had to struggle with Cygwin/Windows
>>> issues).
>>>
>>> Best regards, Julian
>>
>>
>> OK, I have now postponed both issues to 2.13.1.
>>
>> Best regards, Julian
>
>
> Ok, for now I'm stuck at the release:prepare step, which gives the following
> error:
>
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-release-plugin:2.1
>> :prepare (default-cli) on project jackrabbit: Execution default-cli of
>> goal org.
>> apache.maven.plugins:maven-release-plugin:2.1:prepare failed: An API
>> incompatibi
>> lity was encountered while executing
>> org.apache.maven.plugins:maven-release-plug
>> in:2.1:prepare: java.lang.NoSuchMethodError:
>> org.apache.maven.settings.Settings.
>> getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
>
>
> Any ideas what's wrong?
>
> Best regards, Julian

Re: Jackrabbit 2.13.0 release plan

Posted by Julian Reschke <ju...@gmx.de>.
On 2016-07-07 16:34, Woonsan Ko wrote:
> On Thu, Jul 7, 2016 at 5:34 AM, Julian Reschke <ju...@gmx.de> wrote:
>> On 2016-07-07 10:52, Davide Giannella wrote:
>>>
>>> On 06/07/2016 13:47, Julian Reschke wrote:
>>>>>
>>>>> [ERROR] Failed to execute goal
>>>>> org.apache.maven.plugins:maven-release-plugin:2.1
>>>>> :prepare (default-cli) on project jackrabbit: Execution default-cli
>>>>> of goal org.
>>>>> apache.maven.plugins:maven-release-plugin:2.1:prepare failed: An API
>>>>> incompatibi
>>>>> lity was encountered while executing
>>>>> org.apache.maven.plugins:maven-release-plug
>>>>> in:2.1:prepare: java.lang.NoSuchMethodError:
>>>>> org.apache.maven.settings.Settings.
>>>>> getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
>>>>
>>>>
>>>> Any ideas what's wrong?
>>>
>>> Not really but...
>>>
>>> did you follow
>>>
>>> http://jackrabbit.apache.org/jcr/creating-releases.html#Prerequisites_for_release_managers
>>>
>>> http://jackrabbit.apache.org/jcr/creating-releases.html#Appendix_A:_Create_and_add_your_key_to_the_Jackrabbit_KEYS_file
>>>
>>> http://jackrabbit.apache.org/jcr/creating-releases.html#Appendix_B:_Maven_settings
>>
>>
>> Yes.
>>>
>>> what is your maven version? My side is:
>>
>>
>> The latest and greatest 3.3.*.
>>
>>> Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17
>>> 16:22:22+0100)
>>> Maven home: /usr/local/maven
>>> Java version: 1.7.0_60, vendor: Oracle Corporation
>>> Java home:
>>> /Library/Java/JavaVirtualMachines/jdk1.7.0_60.jdk/Contents/Home/jre
>>> Default locale: en_US, platform encoding: UTF-8
>>> OS name: "mac os x", version: "10.9.5", arch: "x86_64", family: "mac"
>>>
>>> In case on OSX is easy to have more than one maven versions switching
>>> between those using env variables. Or even better, spinning up a
>>> dedicated VM with pinned packages.
>>>
>>> If it turnsout to be the maven version we have two options
>>>
>>> 1) change the plugin versions for supporting new mavens. Hopefully it
>>> won't break
>>> 2) document the maven requirements in the release doc.
>>
>>
>> For now, I'll document the workaround that Woonsan came up with.
>
> Maybe it might be a good idea to bump up the release-plugin in
> jackrabbit-parent/pom.xml to 2.5.3.
> Or, you can try to bump up the apache parent pom from 10 to 18 since
> 18 uses 2.5.3:
> - http://repo1.maven.org/maven2/org/apache/apache/18/apache-18.pom

FWIW, Oak is at 13.

Best regards, Julian

Re: Jackrabbit 2.13.0 release plan

Posted by Woonsan Ko <wo...@apache.org>.
On Thu, Jul 7, 2016 at 5:34 AM, Julian Reschke <ju...@gmx.de> wrote:
> On 2016-07-07 10:52, Davide Giannella wrote:
>>
>> On 06/07/2016 13:47, Julian Reschke wrote:
>>>>
>>>> [ERROR] Failed to execute goal
>>>> org.apache.maven.plugins:maven-release-plugin:2.1
>>>> :prepare (default-cli) on project jackrabbit: Execution default-cli
>>>> of goal org.
>>>> apache.maven.plugins:maven-release-plugin:2.1:prepare failed: An API
>>>> incompatibi
>>>> lity was encountered while executing
>>>> org.apache.maven.plugins:maven-release-plug
>>>> in:2.1:prepare: java.lang.NoSuchMethodError:
>>>> org.apache.maven.settings.Settings.
>>>> getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
>>>
>>>
>>> Any ideas what's wrong?
>>
>> Not really but...
>>
>> did you follow
>>
>> http://jackrabbit.apache.org/jcr/creating-releases.html#Prerequisites_for_release_managers
>>
>> http://jackrabbit.apache.org/jcr/creating-releases.html#Appendix_A:_Create_and_add_your_key_to_the_Jackrabbit_KEYS_file
>>
>> http://jackrabbit.apache.org/jcr/creating-releases.html#Appendix_B:_Maven_settings
>
>
> Yes.
>>
>> what is your maven version? My side is:
>
>
> The latest and greatest 3.3.*.
>
>> Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17
>> 16:22:22+0100)
>> Maven home: /usr/local/maven
>> Java version: 1.7.0_60, vendor: Oracle Corporation
>> Java home:
>> /Library/Java/JavaVirtualMachines/jdk1.7.0_60.jdk/Contents/Home/jre
>> Default locale: en_US, platform encoding: UTF-8
>> OS name: "mac os x", version: "10.9.5", arch: "x86_64", family: "mac"
>>
>> In case on OSX is easy to have more than one maven versions switching
>> between those using env variables. Or even better, spinning up a
>> dedicated VM with pinned packages.
>>
>> If it turnsout to be the maven version we have two options
>>
>> 1) change the plugin versions for supporting new mavens. Hopefully it
>> won't break
>> 2) document the maven requirements in the release doc.
>
>
> For now, I'll document the workaround that Woonsan came up with.

Maybe it might be a good idea to bump up the release-plugin in
jackrabbit-parent/pom.xml to 2.5.3.
Or, you can try to bump up the apache parent pom from 10 to 18 since
18 uses 2.5.3:
- http://repo1.maven.org/maven2/org/apache/apache/18/apache-18.pom

Kind regards,

Woonsan

>
>
> Best regards, Julian
>
>
>

Re: Jackrabbit 2.13.0 release plan

Posted by Julian Reschke <ju...@gmx.de>.
On 2016-07-07 10:52, Davide Giannella wrote:
> On 06/07/2016 13:47, Julian Reschke wrote:
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-release-plugin:2.1
>>> :prepare (default-cli) on project jackrabbit: Execution default-cli
>>> of goal org.
>>> apache.maven.plugins:maven-release-plugin:2.1:prepare failed: An API
>>> incompatibi
>>> lity was encountered while executing
>>> org.apache.maven.plugins:maven-release-plug
>>> in:2.1:prepare: java.lang.NoSuchMethodError:
>>> org.apache.maven.settings.Settings.
>>> getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
>>
>> Any ideas what's wrong?
> Not really but...
>
> did you follow
> http://jackrabbit.apache.org/jcr/creating-releases.html#Prerequisites_for_release_managers
> http://jackrabbit.apache.org/jcr/creating-releases.html#Appendix_A:_Create_and_add_your_key_to_the_Jackrabbit_KEYS_file
> http://jackrabbit.apache.org/jcr/creating-releases.html#Appendix_B:_Maven_settings

Yes.
> what is your maven version? My side is:

The latest and greatest 3.3.*.

> Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17
> 16:22:22+0100)
> Maven home: /usr/local/maven
> Java version: 1.7.0_60, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.7.0_60.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.9.5", arch: "x86_64", family: "mac"
>
> In case on OSX is easy to have more than one maven versions switching
> between those using env variables. Or even better, spinning up a
> dedicated VM with pinned packages.
>
> If it turnsout to be the maven version we have two options
>
> 1) change the plugin versions for supporting new mavens. Hopefully it
> won't break
> 2) document the maven requirements in the release doc.

For now, I'll document the workaround that Woonsan came up with.


Best regards, Julian

Re: Jackrabbit 2.13.0 release plan

Posted by Davide Giannella <da...@apache.org>.
On 06/07/2016 13:47, Julian Reschke wrote:
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-release-plugin:2.1
>> :prepare (default-cli) on project jackrabbit: Execution default-cli
>> of goal org.
>> apache.maven.plugins:maven-release-plugin:2.1:prepare failed: An API
>> incompatibi
>> lity was encountered while executing
>> org.apache.maven.plugins:maven-release-plug
>> in:2.1:prepare: java.lang.NoSuchMethodError:
>> org.apache.maven.settings.Settings.
>> getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
>
> Any ideas what's wrong? 
Not really but...

did you follow
http://jackrabbit.apache.org/jcr/creating-releases.html#Prerequisites_for_release_managers
http://jackrabbit.apache.org/jcr/creating-releases.html#Appendix_A:_Create_and_add_your_key_to_the_Jackrabbit_KEYS_file
http://jackrabbit.apache.org/jcr/creating-releases.html#Appendix_B:_Maven_settings

what is your maven version? My side is:

Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17
16:22:22+0100)
Maven home: /usr/local/maven
Java version: 1.7.0_60, vendor: Oracle Corporation
Java home:
/Library/Java/JavaVirtualMachines/jdk1.7.0_60.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.9.5", arch: "x86_64", family: "mac"

In case on OSX is easy to have more than one maven versions switching
between those using env variables. Or even better, spinning up a
dedicated VM with pinned packages.

If it turnsout to be the maven version we have two options

1) change the plugin versions for supporting new mavens. Hopefully it
won't break
2) document the maven requirements in the release doc.

HTH
Davide

Re: Jackrabbit 2.13.0 release plan

Posted by Julian Reschke <ju...@gmx.de>.
On 2016-07-06 14:11, Julian Reschke wrote:
> On 2016-07-04 17:37, Julian Reschke wrote:
>> Hi,
>>
>> we'll need to cut Jackrabbit 2.13.0 in the next few days.
>>
>>
>> There are currently two unresolved issues; can we re-schedule them?
>>
>> https://issues.apache.org/jira/browse/JCR-3913
>>
>> https://issues.apache.org/jira/browse/JCR-3944
>>
>> Also, I'm looking for a volunteer for the release, or alternatively for
>> somebody who would be available for hand holding (back when I releases
>> the last time a long time ago, I had to struggle with Cygwin/Windows
>> issues).
>>
>> Best regards, Julian
>
> OK, I have now postponed both issues to 2.13.1.
>
> Best regards, Julian

Ok, for now I'm stuck at the release:prepare step, which gives the 
following error:

> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.1
> :prepare (default-cli) on project jackrabbit: Execution default-cli of goal org.
> apache.maven.plugins:maven-release-plugin:2.1:prepare failed: An API incompatibi
> lity was encountered while executing org.apache.maven.plugins:maven-release-plug
> in:2.1:prepare: java.lang.NoSuchMethodError: org.apache.maven.settings.Settings.
> getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;

Any ideas what's wrong?

Best regards, Julian

Re: Jackrabbit 2.13.0 release plan

Posted by Julian Reschke <ju...@gmx.de>.
On 2016-07-04 17:37, Julian Reschke wrote:
> Hi,
>
> we'll need to cut Jackrabbit 2.13.0 in the next few days.
>
>
> There are currently two unresolved issues; can we re-schedule them?
>
> https://issues.apache.org/jira/browse/JCR-3913
>
> https://issues.apache.org/jira/browse/JCR-3944
>
> Also, I'm looking for a volunteer for the release, or alternatively for
> somebody who would be available for hand holding (back when I releases
> the last time a long time ago, I had to struggle with Cygwin/Windows
> issues).
>
> Best regards, Julian

OK, I have now postponed both issues to 2.13.1.

Best regards, Julian