You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by Mark Struberg <st...@yahoo.de> on 2013/11/03 22:33:23 UTC
Re: release preparations for 2.3.0 [ABORTED]
I've rolled back the 2.3.0 release candidate.
We first need to take a deep look into OPENJPA-2335.
I will not have time this week as I'm busy at work and will give 3 talks at the W-JAX conference end of this week.
I can start with the release preparation on the next weekend again.
LieGrue,
strub
>________________________________
> From: Mark Struberg <st...@yahoo.de>
>To: "dev@openjpa.apache.org" <de...@openjpa.apache.org>; Mark Struberg <st...@yahoo.de>
>Sent: Saturday, 2 November 2013, 14:01
>Subject: Re: release preparations for 2.3.0
>
>
>DONE!
>
>FYI upfront.
>
>Here is the staging repo link for the release
>https://repository.apache.org/content/repositories/orgapacheopenjpa-055/
>
>Will write a proper vote mail later today.
>
>LieGrue,
>strub
>
>
>
>
>
>----- Original Message -----
>> From: Mark Struberg <st...@yahoo.de>
>> To: "dev@openjpa.apache.org" <de...@openjpa.apache.org>; Mark Struberg <st...@yahoo.de>
>> Cc:
>> Sent: Saturday, 2 November 2013, 11:20
>> Subject: Re: release preparations for 2.3.0
>>
>> damn, failed at site deploy :(
>>
>>
>> distributionManagement.site.url=scp://people.apache.org/home/${site.deploy.user.name}/public_html/openjpa/2.3.0/staging-site/.
>>
>> [INFO] Unsupported protocol: 'scp' for site deployment to
>> distributionManagement.site.url=scp://people.apache.org/home/${site.deploy.user.name}/public_html/openjpa/2.3.0/staging-site/.
>>
>>
>> will do the rest of the release process manually and fix this for the next
>> release iteration
>>
>> LieGrue,
>> strub
>>
>>
>>
>>
>>
>> ----- Original Message -----
>>> From: Mark Struberg <st...@yahoo.de>
>>> To: "dev@openjpa.apache.org" <de...@openjpa.apache.org>; Mark
>> Struberg <st...@yahoo.de>
>>> Cc:
>>> Sent: Saturday, 2 November 2013, 9:58
>>> Subject: Re: release preparations for 2.3.0
>>>
>>> Wohuuu, release:prepare went through finally. Now off for running the final
>>
>>> steps.
>>>
>>> We need to add a few things to our documentation
>>>
>>> * JAI is needed for docbook. We should add the installation instructions to
>> our
>>> release prerequisites.
>>> * we should remove -DskipTests from our release instructions. There were a
>> few
>>> tests which failed during release and which are now fixed.
>>>
>>> LieGrue,
>>> strub
>>>
>>>
>>>
>>>
>>>
>>>
>>> ----- Original Message -----
>>>> From: Mark Struberg <st...@yahoo.de>
>>>> To: "dev@openjpa.apache.org" <de...@openjpa.apache.org>
>>>> Cc:
>>>> Sent: Wednesday, 30 October 2013, 23:10
>>>> Subject: Re: release preparations for 2.3.0
>>>>
>>>> I finally installed jai. damnit...
>>>>
>>>> Now I am almost through. Just getting this error now
>>>>
>>>> <testcase time="2.124"
>>>>
>>>
>> classname="org.apache.openjpa.integration.validation.TestConstraints"
>>>> name="testNullConstraintIgnored">
>>>> <failure message="Caught unexpected exception =
>>>> <openjpa-2.3.0-r422266:1537254M fatal store error>
>>>> org.apache.openjpa.persistence.RollbackException: Table/View
>>>> 'OPENJPA_SEQUENCE_TABLE' does not exist
>>>> . {SELECT SEQUENCE_VALUE FROM OPENJPA_SEQUENCE_TABLE WHERE ID = ?
>> FOR
>>>> UPDATE WITH RR} [code=20000, state=42X05]"
>>>>
>>>
>> type="junit.framework.AssertionFailedError">junit.framework.AssertionFailedError:
>>
>>>
>>>> Caught unexpected except
>>>> ion = <openjpa-2.3.0-r422266:1537254M fatal store error>
>>
>>>> org.apache.openjpa.persistence.RollbackException: Table/View
>>>> 'OPENJPA_SEQUENCE_TABLE' does not exist.
>> {SELECT
>>>> SEQUENCE_VALUE FROM OPENJPA_SEQUENCE
>>>> _TABLE WHERE ID = ? FOR UPDATE WITH RR} [code=20000, state=42X05]
>>>> at junit.framework.Assert.fail(Assert.java:47)
>>>> at
>>>>
>>>
>> org.apache.openjpa.integration.validation.TestConstraints.testNullConstraintIgnored(TestConstraints.java:256)
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>>
>>>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>> at
>>>>
>>>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>> at junit.framework.TestCase.runTest(TestCase.java:154)
>>>> at
>>>>
>>>
>> org.apache.openjpa.persistence.test.AbstractPersistenceTestCase.runTest(AbstractPersistenceTestCase.java:579)
>>>> at junit.framework.TestCase.runBare(TestCase.java:127)
>>>> at
>>>>
>>>
>> org.apache.openjpa.persistence.test.AbstractPersistenceTestCase.runBare(AbstractPersistenceTestCase.java:566)
>>>> at
>>>>
>>>
>> org.apache.openjpa.persistence.test.AbstractPersistenceTestCase.runBare(AbstractPersistenceTestCase.java:542)
>>>> at junit.framework.TestResult$1.protect(TestResult.java:106)
>>>>
>>>> The following should bring you there:
>>>>
>>>> mvn -P apache-release,test-derby,bval,test-derbymem clean install
>>>>
>>>>
>>>> Anyone has a plan what's wrong? Too tired for searching today
>> alread.
>>>> Will continue tomorrow evening.
>>>>
>>>>
>>>> LieGrue,
>>>> strub
>>>>
>>>>
>>>>
>>>>
>>>> ----- Original Message -----
>>>>> From: Mark Struberg <st...@yahoo.de>
>>>>> To: "dev@openjpa.apache.org"
>> <de...@openjpa.apache.org>;
>>> Mark
>>>> Struberg <st...@yahoo.de>
>>>>> Cc:
>>>>> Sent: Wednesday, 30 October 2013, 21:15
>>>>> Subject: Re: release preparations for 2.3.0
>>>>>
>>>>> And another one
>>>>>
>>>>>
>>>>> Could not find artifact com.sun:jai_core:jar:1.1.3
>>>>>
>>>>> we should not recommend creating docbx during release. This does
>> just
>>> not
>>>> work
>>>>> out of the box but requires non ALv2 stuff manually installed on
>> a
>>> box.
>>>>> We can still create all the javadocs and documentation from the
>> tag
>>> later
>>>> on
>>>>> after the release went fine.
>>>>>
>>>>> LieGrue,
>>>>> strub
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ----- Original Message -----
>>>>>> From: Mark Struberg <st...@yahoo.de>
>>>>>> To: "dev@openjpa.apache.org"
>>> <de...@openjpa.apache.org>;
>>>> Mark
>>>>> Struberg <st...@yahoo.de>
>>>>>> Cc:
>>>>>> Sent: Wednesday, 30 October 2013, 16:41
>>>>>> Subject: Re: release preparations for 2.3.0
>>>>>>
>>>>>>
>>>>>>
>>>>>> just FYI.
>>>>>>
>>>>>> I'm still fighting with the javadoc-maven-plugin. Will
>> now
>>>> continue
>>>>> with
>>>>>> trying to create a cleansetup.
>>>>>>
>>>>>> The current problem I face is that the aggregate javadoc
>> needs
>>> the
>>>>> dependencies
>>>>>> built already. Means creating the javadoc upfront does not
>> work
>>> once
>>>> you
>>>>>> increase the project version (or build completely clean in
>>> offline
>>>> mode). I
>>>>> have
>>>>>> isolated the issue and am currently working on a solution
>> which I
>>> will
>>>>
>>>>> later
>>>>>> also commit to trunk (once all stuff is finally working as I
>> like
>>> it).
>>>>>>
>>>>>> LieGrue,
>>>>>> strub
>>>>>>
>>>>>>
>>>>>> PS: I'm in IRC if somebody likes to join the pain ;)
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> ________________________________
>>>>>>
>>>>>>> From: Mark Struberg <st...@yahoo.de>
>>>>>>> To: "dev@openjpa.apache.org"
>>>> <de...@openjpa.apache.org>
>>>>>>> Sent: Tuesday, 29 October 2013, 22:32
>>>>>>> Subject: Re: release preparations for 2.3.0
>>>>>>>
>>>>>>>
>>>>>>> seems I will fix all the checkstyle related stuff later.
>> This
>>>
>>>> needs
>>>>> some
>>>>>> serious cleanup.
>>>>>>>
>>>>>>> We should move all the stuff in our root pom.xml into an
>> own
>>>>> parent/pom.xml
>>>>>> and add a checkstyle module. Then we can add the checkstyle
>> rules
>>> as
>>>>> dependency
>>>>>> and do not need to carry around all the stuff via absolute
>> file
>>> paths.
>>>>>>>
>>>>>>>
>>>>>>> LieGrue,
>>>>>>> strub
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ----- Original Message -----
>>>>>>>> From: Rick Curtis <cu...@gmail.com>
>>>>>>>> To: dev@openjpa.apache.org
>>>>>>>> Cc:
>>>>>>>> Sent: Tuesday, 29 October 2013, 19:18
>>>>>>>> Subject: Re: release preparations for 2.3.0
>>>>>>>>
>>>>>>>> +1 on updating the checkstyle
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Oct 29, 2013 at 12:54 PM, Mark Struberg
>>>>>> <st...@yahoo.de> wrote:
>>>>>>>>
>>>>>>>>> I've already removed all unused imports in
>>
>>> 2.3.x and
>>>>
>>>>> trunk.
>>>>>>>>> Will remove all tabs and replace them with 4
>>> characters
>>>>> tonight as
>>>>>> well.
>>>>>>>>>
>>>>>>>>> We might also activate the
>> maven-checkstyle-plugin
>>> to
>>>> make
>>>>> sure
>>>>>> this
>>>>>>>>> doesn't get worse in the future.
>>>>>>>>>
>>>>>>>>> LieGrue,
>>>>>>>>> strub
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ----- Original Message -----
>>>>>>>>> > From: Mark Struberg
>> <st...@yahoo.de>
>>>>>>>>> > To: openjpa-dev
>> <de...@openjpa.apache.org>
>>>>>>>>> > Cc:
>>>>>>>>> > Sent: Tuesday, 29 October 2013, 9:27
>>>>>>>>> > Subject: release preparations for 2.3.0
>>>>>>>>> >
>>>>>>>>> > Hi!
>>>>>>>>> >
>>>>>>>>> > Could you please walk through the
>> unresolved
>>>>> OpenJPA-2.3.0
>>>>>> issues and
>>>>>>>>> set those
>>>>>>>>> > who you doubt should be fixed already to
>>>>> 'resolved'?
>>>>>>>>> >
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20OPENJPA%20AND%20fixVersion%20%3D%20%222.3.0%22%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
>>>>>>>>> >
>>>>>>>>> > I hope to start with the actual release
>> task
>>> either
>>>>
>>>>> tonight
>>>>>> or
>>>>>>>> tomorrow
>>>>>>>>> morning.
>>>>>>>>> > Means I gonna send another mail in 15
>> hours
>>> and
>>>> then
>>>>> will
>>>>>> transit the
>>>>>>>>> still
>>>>>>>>> > unresolved issues to 2.4.0.
>>>>>>>>> >
>>>>>>>>> > There is also another thing which I like
>> to
>>> do:
>>>> finally
>>>>> get
>>>>>> rid of all
>>>>>>>>> the bad
>>>>>>>>> > tabs and unused imports in 2.3.x and
>> trunk.
>>>>>>>>> > See OPENJPA-2200. I will _not_ change any
>>
>>> lines
>>>> other
>>>>> than
>>>>>> tabs and
>>>>>>>>> unused
>>>>>>>>> > imports so far.
>>>>>>>>> > Patches should thus still apply fine even
>>
>>> across
>>>> older
>>>>>> versions.
>>>>>>>>> >
>>>>>>>>> > LieGrue,
>>>>>>>>> > strub
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> *Rick Curtis*
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
>