You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by David Blevins <da...@gmail.com> on 2014/07/17 17:18:00 UTC
TomEE 1.7.0 blockers
Wondering if we can get a complete list of issues holding up 1.7 on a single thread.
On the legal side, we still need:
- Library diff
- Review/adjust LICENSE and NOTICE files
The last one on the list frequently tanks releases. Doesn't affect security releases, but with larger versions is just a bear. Let's make sure we do that one before we put up another vote as voting drastically decreases each time we reroll.
--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
Re: TomEE 1.7.0 blockers
Posted by David Blevins <da...@gmail.com>.
On Jul 17, 2014, at 8:18 AM, David Blevins <da...@gmail.com> wrote:
> On the legal side, we still need:
>
> - Library diff
> - Review/adjust LICENSE and NOTICE files
We still need a report of the changed libraries from this release to the previous. I guarantee there will be adjustments that will need to be made to all our LICENSE/NOTICE files.
Run this:
- http://svn.apache.org/repos/asf/tomee/sandbox/release-tools/src/main/java/org/apache/openejb/tools/release/cmd/CompareLibraries.java
Then we need to edit every single NOTICE file to:
- remove mention of jars we no longer ship
- add mention of new jars we are including
- ensure the LICENSE file contains the license of said new jars
I suspect the plume distro doesn't yet mention Mojarra or EclipseLink.
The 1.0, 1.5 and 1.6 releases were all super big pains in the butt on this task specifically. Between the three we probably had a least dozen sets of binaries fail out of the voting process just due to legal files.
-David
Re: TomEE 1.7.0 blockers
Posted by Andy Gumbrecht <ag...@tomitribe.com>.
Hi,
Not seeing this on the Buildbot or local - I'll try and replicate, but
if you're in a position to debug and maybe shed some light on it that
would be cool.
If you need help debugging maven surefire let me know - There is some
info here:
http://maven.apache.org/surefire/maven-surefire-plugin/examples/debugging.html
Andy.
On 25/07/2014 22:25, hanasaki@gmail.com wrote:
>
>
> ------------------------------------------------------------------------
>
> *From:* Andy Gumbrecht
> *Sent:* Friday, July 25, 2014 6:20AM
> *To:* dev@tomee.apache.org
> *Subject:* Re: TomEE 1.7.0 blockers
>
> Still getting build failures on 1.7.x branch.
> using mvn 3.2.1 linux command line build (no ide)
>
>
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.apache.tomee.jaxrs.ReloadingLoaderTest
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.248
> sec <<< FAILURE! - in org.apache.tomee.jaxrs.ReloadingLoaderTest
> tomcatClassLoaderParentShouldntBeNulAfterAStopStartOtherwiseReloadIsBroken(org.apache.tomee.jaxrs.ReloadingLoaderTest)
> Time elapsed: 0.103 sec <<< ERROR!
> java.lang.NullPointerException: null
> at
> org.apache.catalina.loader.WebappClassLoader.start(WebappClassLoader.java:1463)
> at
> org.apache.tomee.catalina.TomEEWebappClassLoader.start(TomEEWebappClassLoader.java:234)
> at
> org.apache.tomee.jaxrs.ReloadingLoaderTest.initContext(ReloadingLoaderTest.java:81)
>
>
> Results :
>
> Tests in error:
> ReloadingLoaderTest.initContext:81 » NullPointer
>
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
>
>
>
> ------------------------------------------------------------------------
>
> *From:* Andy Gumbrecht
> *Sent:* Friday, July 25, 2014 6:20AM
> *To:* dev@tomee.apache.org
> *Subject:* Re: TomEE 1.7.0 blockers
>
>> Sure,
>>
>> http://ci.apache.org/builders/tomee-1.7.x-ubuntu
>>
>> After much more work we finally have a stable green build - at least two
>> in a row. I am in the process of preparing the the release roll as I
>> write.
>> There are a few crappy jobs to crawl through to polish the release, I
>> will be done in an hour or two.
>>
>> The vote should go out today, so if it makes it through we could have an
>> announcement for Monday morning!
>>
>> For interest, the SVN history should give a good indication of how
>> things have developed over the last few weeks.
>> A plus side on the delay is that we have managed to get some significant
>> fixes into the 1.7.0 release.
>>
>> Andy.
>>
>> On 25/07/2014 08:49, Jean-Louis Monteiro wrote:
>>> Andy, can you provide a status about the release?
>>>
>>> Thanks
>>>
>>> --
>>> Jean-Louis Monteiro
>>> http://twitter.com/jlouismonteiro
>>> http://www.tomitribe.com
>>>
>>>
>>> On Mon, Jul 21, 2014 at 10:06 AM, Jean-Louis Monteiro <
>>> jlmonteiro@tomitribe.com> wrote:
>>>
>>>> Cool thx Mark
>>>>
>>>> --
>>>> Jean-Louis Monteiro
>>>> http://twitter.com/jlouismonteiro
>>>> http://www.tomitribe.com
>>>>
>>>>
>>>> On Mon, Jul 21, 2014 at 8:38 AM, Mark Struberg <st...@yahoo.de>
>>>> wrote:
>>>>
>>>>> tomee-1.7.x branch builds fine.
>>>>> Sample app works fine.
>>>>> Will test with a few production apps today.
>>>>>
>>>>>
>>>>> LieGrue,
>>>>> strub
>>>>>
>>>>>
>>>>>
>>>>> On Sunday, 20 July 2014, 20:11, Mark Struberg <st...@yahoo.de>
>>>>> wrote:
>>>>>
>>>>>
>>>>>>
>>>>>> oh gee, yea should have told you :)
>>>>>>
>>>>>> I'm on trunk. Will checkout 4.7.0 branch...
>>>>>>
>>>>>> LieGrue,
>>>>>> strub
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sunday, 20 July 2014, 16:10, Romain Manni-Bucau <
>>>>> rmannibucau@gmail.com> wrote:
>>>>>>
>>>>>>>
>>>>>>> sure but need to know where is the issue first
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Romain Manni-Bucau
>>>>>>> Twitter: @rmannibucau
>>>>>>> Blog: http://rmannibucau.wordpress.com/
>>>>>>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>>>>>> Github: https://github.com/rmannibucau
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> 2014-07-20 16:07 GMT+02:00 Jean-Louis Monteiro <
>>>>> jlmonteiro@tomitribe.com>:
>>>>>>> fix on trunk but maybe not merged to branch?
>>>>>>>>
>>>>>>>> --
>>>>>>>> Jean-Louis Monteiro
>>>>>>>> http://twitter.com/jlouismonteiro
>>>>>>>> http://www.tomitribe.com
>>>>>>>>
>>>>>>>>
>>>>>>>> On Sun, Jul 20, 2014 at 1:12 PM, Romain Manni-Bucau <
>>>>> rmannibucau@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>> Hi Mark,
>>>>>>>>>
>>>>>>>>> on trunk? should have been fixed
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Romain Manni-Bucau
>>>>>>>>> Twitter: @rmannibucau
>>>>>>>>> Blog: http://rmannibucau.wordpress.com/
>>>>>>>>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>>>>>>>> Github: https://github.com/rmannibucau
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2014-07-20 12:46 GMT+02:00 Mark Struberg <st...@yahoo.de>:
>>>>>>>>>
>>>>>>>>>> currently tomee doesn't build locally
>>>>>>>>>>
>>>>>>>>>> Tests in error:
>>>>>>>>>> SubjectServiceTest.start:56 » EJB Provider error. No provider
>>>>>>>>> definition
>>>>>>>>>> found
>>>>>>>>>> SubjectServiceTest.stop:67 NullPointer
>>>>>>>>>>
>>>>>>>>>> Tests run: 3, Failures: 0, Errors: 2, Skipped: 0
>>>>>>>>>>
>>>>>>>>>> Environment: mbp, OSX 10.9.4, java Orcl 1.7.0_51
>>>>>>>>>>
>>>>>>>>>> LieGrue,
>>>>>>>>>> strub
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Thursday, 17 July 2014, 23:44, Romain Manni-Bucau <
>>>>>>>>>> rmannibucau@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Yeah, a lot of work done!
>>>>>>>>>>>
>>>>>>>>>>> Side node: the fact we need the javaagent is an openjpa
>>>>>>>>>>> issue of
>>>>>>>>>>> subclassing (known but kind of regression for them without the
>>>>> javaagent
>>>>>>>>>> or
>>>>>>>>>>> build time enhancement :()
>>>>>>>>>>> Le 17 juil. 2014 22:11, "Andy Gumbrecht" <
>>>>> agumbrecht@tomitribe.com> a
>>>>>>>>>>> écrit :
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> To sum up what was wrong with the failed release on Sunday.
>>>>>>>>>>>>
>>>>>>>>>>>> There was a SNAPSHOT dependency added to the parent POM and
>>>>> missed on
>>>>>>>>>>>> deploy - This was a breaking issue on the staging.
>>>>>>>>>>>>
>>>>>>>>>>>> The builds could not be run in parallel, as many tests were
>>>>> using the
>>>>>>>>>> same
>>>>>>>>>>>> conflicting ports. We have not had concurrent builders running
>>>>> on the
>>>>>>>>>> same
>>>>>>>>>>>> buildbot for some time, but we have just been 'lucky' that
>>>>>>>>>>>> this
>>>>> was
>>>>>>>>>>>> 'mostly' working.
>>>>>>>>>>>> I think I have most, if not all, the tests that bind to ports
>>>>> changed
>>>>>>>>> so
>>>>>>>>>>>> that the ports are random - There will surely be more issues,
>>>>> but
>>>>>>>>>>>> concurrent builds have become significantly more stable.
>>>>>>>>>>>> We have to be able to cope with this as we now run builds of
>>>>> TomEE
>>>>>>>>> 1.7.x
>>>>>>>>>>>> on Java 6/7 and TomEE 2.0.x on Java 7/8/9EA - Most of these
>>>>> will fire
>>>>>>>>> at
>>>>>>>>>>>> the same time on commits and merges.
>>>>>>>>>>>>
>>>>>>>>>>>> Another big issue that cost significant effort was that the
>>>>> javaagent
>>>>>>>>>> had
>>>>>>>>>>>> been commented out in the openejb-core.pom during testing on
>>>>> Java 7,
>>>>>>>>> and
>>>>>>>>>>>> unfortunately forgotten. This broke the enhancement for
>>>>>>>>>>>> several
>>>>> tests
>>>>>>>>>> in a
>>>>>>>>>>>> very subtle way so that it was not obvious what was going
>>>>> wrong, the
>>>>>>>>>> issues
>>>>>>>>>>>> were only apparent on Java 7 build. This was also done at time
>>>>> that
>>>>>>>>> the
>>>>>>>>>>>> build was not green, so made tracking down additionally hard.
>>>>>>>>> Obviously
>>>>>>>>>>>> this led us to believe that the Java 8 support we were
>>>>>>>>>>>> about to
>>>>>>>>> announce
>>>>>>>>>>>> was broken.
>>>>>>>>>>>>
>>>>>>>>>>>> As trunk had already had significant formatting and finals
>>>>> changes
>>>>>>>>>>>> committed it was necessary to make the 1.7.x branch comparable
>>>>> for
>>>>>>>>>>>> successful merges. This also led to several test failures that
>>>>> needed
>>>>>>>>>> to be
>>>>>>>>>>>> rectified. The upside is that many tests were tweaked and
>>>>> updated
>>>>>>>>> during
>>>>>>>>>>>> this process.
>>>>>>>>>>>>
>>>>>>>>>>>> Java 7 builds on Windows platforms also revealed several
>>>>> 'slightly'
>>>>>>>>>> flawed
>>>>>>>>>>>> tests, again the upside is that some minor issues were
>>>>>>>>>>>> addressed
>>>>>>>>> during
>>>>>>>>>>>> analysis.
>>>>>>>>>>>>
>>>>>>>>>>>> We are now really close to getting all issues resolved - We
>>>>> will have
>>>>>>>>>>>> green builds by the end of the day.
>>>>>>>>>>>>
>>>>>>>>>>>> Andy.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On 17/07/2014 17:18, David Blevins wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Wondering if we can get a complete list of issues holding up
>>>>> 1.7 on a
>>>>>>>>>>>>> single thread.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On the legal side, we still need:
>>>>>>>>>>>>>
>>>>>>>>>>>>> - Library diff
>>>>>>>>>>>>> - Review/adjust LICENSE and NOTICE files
>>>>>>>>>>>>>
>>>>>>>>>>>>> The last one on the list frequently tanks releases. Doesn't
>>>>> affect
>>>>>>>>>>>>> security releases, but with larger versions is just a bear.
>>>>> Let's
>>>>>>>>> make
>>>>>>>>>>>>> sure we do that one before we put up another vote as voting
>>>>>>>>> drastically
>>>>>>>>>>>>> decreases each time we reroll.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Andy Gumbrecht
>>>>>>>>>>>>
>>>>>>>>>>>> http://www.tomitribe.com
>>>>>>>>>>>> agumbrecht@tomitribe.com
>>>>>>>>>>>> https://twitter.com/AndyGeeDe
>>>>>>>>>>>>
>>>>>>>>>>>> TomEE treibt Tomitribe! | http://tomee.apache.org
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>
>>
>
>
--
Andy Gumbrecht
http://www.tomitribe.com
agumbrecht@tomitribe.com
https://twitter.com/AndyGeeDe
TomEE treibt Tomitribe! | http://tomee.apache.org
Re: TomEE 1.7.0 blockers
Posted by "hanasaki@gmail.com" <ha...@gmail.com>.
------------------------------------------------------------------------
*From:* Andy Gumbrecht
*Sent:* Friday, July 25, 2014 6:20AM
*To:* dev@tomee.apache.org
*Subject:* Re: TomEE 1.7.0 blockers
Still getting build failures on 1.7.x branch.
using mvn 3.2.1 linux command line build (no ide)
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.apache.tomee.jaxrs.ReloadingLoaderTest
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.248
sec <<< FAILURE! - in org.apache.tomee.jaxrs.ReloadingLoaderTest
tomcatClassLoaderParentShouldntBeNulAfterAStopStartOtherwiseReloadIsBroken(org.apache.tomee.jaxrs.ReloadingLoaderTest)
Time elapsed: 0.103 sec <<< ERROR!
java.lang.NullPointerException: null
at
org.apache.catalina.loader.WebappClassLoader.start(WebappClassLoader.java:1463)
at
org.apache.tomee.catalina.TomEEWebappClassLoader.start(TomEEWebappClassLoader.java:234)
at
org.apache.tomee.jaxrs.ReloadingLoaderTest.initContext(ReloadingLoaderTest.java:81)
Results :
Tests in error:
ReloadingLoaderTest.initContext:81 » NullPointer
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
------------------------------------------------------------------------
*From:* Andy Gumbrecht
*Sent:* Friday, July 25, 2014 6:20AM
*To:* dev@tomee.apache.org
*Subject:* Re: TomEE 1.7.0 blockers
> Sure,
>
> http://ci.apache.org/builders/tomee-1.7.x-ubuntu
>
> After much more work we finally have a stable green build - at least two
> in a row. I am in the process of preparing the the release roll as I write.
> There are a few crappy jobs to crawl through to polish the release, I
> will be done in an hour or two.
>
> The vote should go out today, so if it makes it through we could have an
> announcement for Monday morning!
>
> For interest, the SVN history should give a good indication of how
> things have developed over the last few weeks.
> A plus side on the delay is that we have managed to get some significant
> fixes into the 1.7.0 release.
>
> Andy.
>
> On 25/07/2014 08:49, Jean-Louis Monteiro wrote:
>> Andy, can you provide a status about the release?
>>
>> Thanks
>>
>> --
>> Jean-Louis Monteiro
>> http://twitter.com/jlouismonteiro
>> http://www.tomitribe.com
>>
>>
>> On Mon, Jul 21, 2014 at 10:06 AM, Jean-Louis Monteiro <
>> jlmonteiro@tomitribe.com> wrote:
>>
>>> Cool thx Mark
>>>
>>> --
>>> Jean-Louis Monteiro
>>> http://twitter.com/jlouismonteiro
>>> http://www.tomitribe.com
>>>
>>>
>>> On Mon, Jul 21, 2014 at 8:38 AM, Mark Struberg <st...@yahoo.de>
>>> wrote:
>>>
>>>> tomee-1.7.x branch builds fine.
>>>> Sample app works fine.
>>>> Will test with a few production apps today.
>>>>
>>>>
>>>> LieGrue,
>>>> strub
>>>>
>>>>
>>>>
>>>> On Sunday, 20 July 2014, 20:11, Mark Struberg <st...@yahoo.de>
>>>> wrote:
>>>>
>>>>
>>>>>
>>>>> oh gee, yea should have told you :)
>>>>>
>>>>> I'm on trunk. Will checkout 4.7.0 branch...
>>>>>
>>>>> LieGrue,
>>>>> strub
>>>>>
>>>>>
>>>>>
>>>>> On Sunday, 20 July 2014, 16:10, Romain Manni-Bucau <
>>>> rmannibucau@gmail.com> wrote:
>>>>>
>>>>>>
>>>>>> sure but need to know where is the issue first
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Romain Manni-Bucau
>>>>>> Twitter: @rmannibucau
>>>>>> Blog: http://rmannibucau.wordpress.com/
>>>>>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>>>>> Github: https://github.com/rmannibucau
>>>>>>
>>>>>>
>>>>>>
>>>>>> 2014-07-20 16:07 GMT+02:00 Jean-Louis Monteiro <
>>>> jlmonteiro@tomitribe.com>:
>>>>>> fix on trunk but maybe not merged to branch?
>>>>>>>
>>>>>>> --
>>>>>>> Jean-Louis Monteiro
>>>>>>> http://twitter.com/jlouismonteiro
>>>>>>> http://www.tomitribe.com
>>>>>>>
>>>>>>>
>>>>>>> On Sun, Jul 20, 2014 at 1:12 PM, Romain Manni-Bucau <
>>>> rmannibucau@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>
>>>>>>>> Hi Mark,
>>>>>>>>
>>>>>>>> on trunk? should have been fixed
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Romain Manni-Bucau
>>>>>>>> Twitter: @rmannibucau
>>>>>>>> Blog: http://rmannibucau.wordpress.com/
>>>>>>>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>>>>>>> Github: https://github.com/rmannibucau
>>>>>>>>
>>>>>>>>
>>>>>>>> 2014-07-20 12:46 GMT+02:00 Mark Struberg <st...@yahoo.de>:
>>>>>>>>
>>>>>>>>> currently tomee doesn't build locally
>>>>>>>>>
>>>>>>>>> Tests in error:
>>>>>>>>> SubjectServiceTest.start:56 » EJB Provider error. No provider
>>>>>>>> definition
>>>>>>>>> found
>>>>>>>>> SubjectServiceTest.stop:67 NullPointer
>>>>>>>>>
>>>>>>>>> Tests run: 3, Failures: 0, Errors: 2, Skipped: 0
>>>>>>>>>
>>>>>>>>> Environment: mbp, OSX 10.9.4, java Orcl 1.7.0_51
>>>>>>>>>
>>>>>>>>> LieGrue,
>>>>>>>>> strub
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Thursday, 17 July 2014, 23:44, Romain Manni-Bucau <
>>>>>>>>> rmannibucau@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Yeah, a lot of work done!
>>>>>>>>>>
>>>>>>>>>> Side node: the fact we need the javaagent is an openjpa issue of
>>>>>>>>>> subclassing (known but kind of regression for them without the
>>>> javaagent
>>>>>>>>> or
>>>>>>>>>> build time enhancement :()
>>>>>>>>>> Le 17 juil. 2014 22:11, "Andy Gumbrecht" <
>>>> agumbrecht@tomitribe.com> a
>>>>>>>>>> écrit :
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> To sum up what was wrong with the failed release on Sunday.
>>>>>>>>>>>
>>>>>>>>>>> There was a SNAPSHOT dependency added to the parent POM and
>>>> missed on
>>>>>>>>>>> deploy - This was a breaking issue on the staging.
>>>>>>>>>>>
>>>>>>>>>>> The builds could not be run in parallel, as many tests were
>>>> using the
>>>>>>>>> same
>>>>>>>>>>> conflicting ports. We have not had concurrent builders running
>>>> on the
>>>>>>>>> same
>>>>>>>>>>> buildbot for some time, but we have just been 'lucky' that this
>>>> was
>>>>>>>>>>> 'mostly' working.
>>>>>>>>>>> I think I have most, if not all, the tests that bind to ports
>>>> changed
>>>>>>>> so
>>>>>>>>>>> that the ports are random - There will surely be more issues,
>>>> but
>>>>>>>>>>> concurrent builds have become significantly more stable.
>>>>>>>>>>> We have to be able to cope with this as we now run builds of
>>>> TomEE
>>>>>>>> 1.7.x
>>>>>>>>>>> on Java 6/7 and TomEE 2.0.x on Java 7/8/9EA - Most of these
>>>> will fire
>>>>>>>> at
>>>>>>>>>>> the same time on commits and merges.
>>>>>>>>>>>
>>>>>>>>>>> Another big issue that cost significant effort was that the
>>>> javaagent
>>>>>>>>> had
>>>>>>>>>>> been commented out in the openejb-core.pom during testing on
>>>> Java 7,
>>>>>>>> and
>>>>>>>>>>> unfortunately forgotten. This broke the enhancement for several
>>>> tests
>>>>>>>>> in a
>>>>>>>>>>> very subtle way so that it was not obvious what was going
>>>> wrong, the
>>>>>>>>> issues
>>>>>>>>>>> were only apparent on Java 7 build. This was also done at time
>>>> that
>>>>>>>> the
>>>>>>>>>>> build was not green, so made tracking down additionally hard.
>>>>>>>> Obviously
>>>>>>>>>>> this led us to believe that the Java 8 support we were about to
>>>>>>>> announce
>>>>>>>>>>> was broken.
>>>>>>>>>>>
>>>>>>>>>>> As trunk had already had significant formatting and finals
>>>> changes
>>>>>>>>>>> committed it was necessary to make the 1.7.x branch comparable
>>>> for
>>>>>>>>>>> successful merges. This also led to several test failures that
>>>> needed
>>>>>>>>> to be
>>>>>>>>>>> rectified. The upside is that many tests were tweaked and
>>>> updated
>>>>>>>> during
>>>>>>>>>>> this process.
>>>>>>>>>>>
>>>>>>>>>>> Java 7 builds on Windows platforms also revealed several
>>>> 'slightly'
>>>>>>>>> flawed
>>>>>>>>>>> tests, again the upside is that some minor issues were addressed
>>>>>>>> during
>>>>>>>>>>> analysis.
>>>>>>>>>>>
>>>>>>>>>>> We are now really close to getting all issues resolved - We
>>>> will have
>>>>>>>>>>> green builds by the end of the day.
>>>>>>>>>>>
>>>>>>>>>>> Andy.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On 17/07/2014 17:18, David Blevins wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Wondering if we can get a complete list of issues holding up
>>>> 1.7 on a
>>>>>>>>>>>> single thread.
>>>>>>>>>>>>
>>>>>>>>>>>> On the legal side, we still need:
>>>>>>>>>>>>
>>>>>>>>>>>> - Library diff
>>>>>>>>>>>> - Review/adjust LICENSE and NOTICE files
>>>>>>>>>>>>
>>>>>>>>>>>> The last one on the list frequently tanks releases. Doesn't
>>>> affect
>>>>>>>>>>>> security releases, but with larger versions is just a bear.
>>>> Let's
>>>>>>>> make
>>>>>>>>>>>> sure we do that one before we put up another vote as voting
>>>>>>>> drastically
>>>>>>>>>>>> decreases each time we reroll.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Andy Gumbrecht
>>>>>>>>>>>
>>>>>>>>>>> http://www.tomitribe.com
>>>>>>>>>>> agumbrecht@tomitribe.com
>>>>>>>>>>> https://twitter.com/AndyGeeDe
>>>>>>>>>>>
>>>>>>>>>>> TomEE treibt Tomitribe! | http://tomee.apache.org
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>
>
Re: TomEE 1.7.0 blockers
Posted by Andy Gumbrecht <ag...@tomitribe.com>.
Sure,
http://ci.apache.org/builders/tomee-1.7.x-ubuntu
After much more work we finally have a stable green build - at least two
in a row. I am in the process of preparing the the release roll as I write.
There are a few crappy jobs to crawl through to polish the release, I
will be done in an hour or two.
The vote should go out today, so if it makes it through we could have an
announcement for Monday morning!
For interest, the SVN history should give a good indication of how
things have developed over the last few weeks.
A plus side on the delay is that we have managed to get some significant
fixes into the 1.7.0 release.
Andy.
On 25/07/2014 08:49, Jean-Louis Monteiro wrote:
> Andy, can you provide a status about the release?
>
> Thanks
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Mon, Jul 21, 2014 at 10:06 AM, Jean-Louis Monteiro <
> jlmonteiro@tomitribe.com> wrote:
>
>> Cool thx Mark
>>
>> --
>> Jean-Louis Monteiro
>> http://twitter.com/jlouismonteiro
>> http://www.tomitribe.com
>>
>>
>> On Mon, Jul 21, 2014 at 8:38 AM, Mark Struberg <st...@yahoo.de> wrote:
>>
>>> tomee-1.7.x branch builds fine.
>>> Sample app works fine.
>>> Will test with a few production apps today.
>>>
>>>
>>> LieGrue,
>>> strub
>>>
>>>
>>>
>>> On Sunday, 20 July 2014, 20:11, Mark Struberg <st...@yahoo.de> wrote:
>>>
>>>
>>>>
>>>> oh gee, yea should have told you :)
>>>>
>>>> I'm on trunk. Will checkout 4.7.0 branch...
>>>>
>>>> LieGrue,
>>>> strub
>>>>
>>>>
>>>>
>>>> On Sunday, 20 July 2014, 16:10, Romain Manni-Bucau <
>>> rmannibucau@gmail.com> wrote:
>>>>
>>>>>
>>>>> sure but need to know where is the issue first
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Romain Manni-Bucau
>>>>> Twitter: @rmannibucau
>>>>> Blog: http://rmannibucau.wordpress.com/
>>>>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>>>> Github: https://github.com/rmannibucau
>>>>>
>>>>>
>>>>>
>>>>> 2014-07-20 16:07 GMT+02:00 Jean-Louis Monteiro <
>>> jlmonteiro@tomitribe.com>:
>>>>> fix on trunk but maybe not merged to branch?
>>>>>>
>>>>>> --
>>>>>> Jean-Louis Monteiro
>>>>>> http://twitter.com/jlouismonteiro
>>>>>> http://www.tomitribe.com
>>>>>>
>>>>>>
>>>>>> On Sun, Jul 20, 2014 at 1:12 PM, Romain Manni-Bucau <
>>> rmannibucau@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>
>>>>>>> Hi Mark,
>>>>>>>
>>>>>>> on trunk? should have been fixed
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Romain Manni-Bucau
>>>>>>> Twitter: @rmannibucau
>>>>>>> Blog: http://rmannibucau.wordpress.com/
>>>>>>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>>>>>> Github: https://github.com/rmannibucau
>>>>>>>
>>>>>>>
>>>>>>> 2014-07-20 12:46 GMT+02:00 Mark Struberg <st...@yahoo.de>:
>>>>>>>
>>>>>>>> currently tomee doesn't build locally
>>>>>>>>
>>>>>>>> Tests in error:
>>>>>>>> SubjectServiceTest.start:56 » EJB Provider error. No provider
>>>>>>> definition
>>>>>>>> found
>>>>>>>> SubjectServiceTest.stop:67 NullPointer
>>>>>>>>
>>>>>>>> Tests run: 3, Failures: 0, Errors: 2, Skipped: 0
>>>>>>>>
>>>>>>>> Environment: mbp, OSX 10.9.4, java Orcl 1.7.0_51
>>>>>>>>
>>>>>>>> LieGrue,
>>>>>>>> strub
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thursday, 17 July 2014, 23:44, Romain Manni-Bucau <
>>>>>>>> rmannibucau@gmail.com> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Yeah, a lot of work done!
>>>>>>>>>
>>>>>>>>> Side node: the fact we need the javaagent is an openjpa issue of
>>>>>>>>> subclassing (known but kind of regression for them without the
>>> javaagent
>>>>>>>> or
>>>>>>>>> build time enhancement :()
>>>>>>>>> Le 17 juil. 2014 22:11, "Andy Gumbrecht" <
>>> agumbrecht@tomitribe.com> a
>>>>>>>>> écrit :
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> To sum up what was wrong with the failed release on Sunday.
>>>>>>>>>>
>>>>>>>>>> There was a SNAPSHOT dependency added to the parent POM and
>>> missed on
>>>>>>>>>> deploy - This was a breaking issue on the staging.
>>>>>>>>>>
>>>>>>>>>> The builds could not be run in parallel, as many tests were
>>> using the
>>>>>>>> same
>>>>>>>>>> conflicting ports. We have not had concurrent builders running
>>> on the
>>>>>>>> same
>>>>>>>>>> buildbot for some time, but we have just been 'lucky' that this
>>> was
>>>>>>>>>> 'mostly' working.
>>>>>>>>>> I think I have most, if not all, the tests that bind to ports
>>> changed
>>>>>>> so
>>>>>>>>>> that the ports are random - There will surely be more issues,
>>> but
>>>>>>>>>> concurrent builds have become significantly more stable.
>>>>>>>>>> We have to be able to cope with this as we now run builds of
>>> TomEE
>>>>>>> 1.7.x
>>>>>>>>>> on Java 6/7 and TomEE 2.0.x on Java 7/8/9EA - Most of these
>>> will fire
>>>>>>> at
>>>>>>>>>> the same time on commits and merges.
>>>>>>>>>>
>>>>>>>>>> Another big issue that cost significant effort was that the
>>> javaagent
>>>>>>>> had
>>>>>>>>>> been commented out in the openejb-core.pom during testing on
>>> Java 7,
>>>>>>> and
>>>>>>>>>> unfortunately forgotten. This broke the enhancement for several
>>> tests
>>>>>>>> in a
>>>>>>>>>> very subtle way so that it was not obvious what was going
>>> wrong, the
>>>>>>>> issues
>>>>>>>>>> were only apparent on Java 7 build. This was also done at time
>>> that
>>>>>>> the
>>>>>>>>>> build was not green, so made tracking down additionally hard.
>>>>>>> Obviously
>>>>>>>>>> this led us to believe that the Java 8 support we were about to
>>>>>>> announce
>>>>>>>>>> was broken.
>>>>>>>>>>
>>>>>>>>>> As trunk had already had significant formatting and finals
>>> changes
>>>>>>>>>> committed it was necessary to make the 1.7.x branch comparable
>>> for
>>>>>>>>>> successful merges. This also led to several test failures that
>>> needed
>>>>>>>> to be
>>>>>>>>>> rectified. The upside is that many tests were tweaked and
>>> updated
>>>>>>> during
>>>>>>>>>> this process.
>>>>>>>>>>
>>>>>>>>>> Java 7 builds on Windows platforms also revealed several
>>> 'slightly'
>>>>>>>> flawed
>>>>>>>>>> tests, again the upside is that some minor issues were addressed
>>>>>>> during
>>>>>>>>>> analysis.
>>>>>>>>>>
>>>>>>>>>> We are now really close to getting all issues resolved - We
>>> will have
>>>>>>>>>> green builds by the end of the day.
>>>>>>>>>>
>>>>>>>>>> Andy.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 17/07/2014 17:18, David Blevins wrote:
>>>>>>>>>>
>>>>>>>>>>> Wondering if we can get a complete list of issues holding up
>>> 1.7 on a
>>>>>>>>>>> single thread.
>>>>>>>>>>>
>>>>>>>>>>> On the legal side, we still need:
>>>>>>>>>>>
>>>>>>>>>>> - Library diff
>>>>>>>>>>> - Review/adjust LICENSE and NOTICE files
>>>>>>>>>>>
>>>>>>>>>>> The last one on the list frequently tanks releases. Doesn't
>>> affect
>>>>>>>>>>> security releases, but with larger versions is just a bear.
>>> Let's
>>>>>>> make
>>>>>>>>>>> sure we do that one before we put up another vote as voting
>>>>>>> drastically
>>>>>>>>>>> decreases each time we reroll.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Andy Gumbrecht
>>>>>>>>>>
>>>>>>>>>> http://www.tomitribe.com
>>>>>>>>>> agumbrecht@tomitribe.com
>>>>>>>>>> https://twitter.com/AndyGeeDe
>>>>>>>>>>
>>>>>>>>>> TomEE treibt Tomitribe! | http://tomee.apache.org
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>>
>>>>
>>
--
Andy Gumbrecht
http://www.tomitribe.com
agumbrecht@tomitribe.com
https://twitter.com/AndyGeeDe
TomEE treibt Tomitribe! | http://tomee.apache.org
Re: TomEE 1.7.0 blockers
Posted by Jean-Louis Monteiro <jl...@tomitribe.com>.
Andy, can you provide a status about the release?
Thanks
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Mon, Jul 21, 2014 at 10:06 AM, Jean-Louis Monteiro <
jlmonteiro@tomitribe.com> wrote:
> Cool thx Mark
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Mon, Jul 21, 2014 at 8:38 AM, Mark Struberg <st...@yahoo.de> wrote:
>
>> tomee-1.7.x branch builds fine.
>> Sample app works fine.
>> Will test with a few production apps today.
>>
>>
>> LieGrue,
>> strub
>>
>>
>>
>> On Sunday, 20 July 2014, 20:11, Mark Struberg <st...@yahoo.de> wrote:
>>
>>
>> >
>> >
>> >oh gee, yea should have told you :)
>> >
>> >I'm on trunk. Will checkout 4.7.0 branch...
>> >
>> >LieGrue,
>> >strub
>> >
>> >
>> >
>> >On Sunday, 20 July 2014, 16:10, Romain Manni-Bucau <
>> rmannibucau@gmail.com> wrote:
>> >
>> >
>> >>
>> >>
>> >>sure but need to know where is the issue first
>> >>
>> >>
>> >>
>> >>
>> >>Romain Manni-Bucau
>> >>Twitter: @rmannibucau
>> >>Blog: http://rmannibucau.wordpress.com/
>> >>LinkedIn: http://fr.linkedin.com/in/rmannibucau
>> >>Github: https://github.com/rmannibucau
>> >>
>> >>
>> >>
>> >>2014-07-20 16:07 GMT+02:00 Jean-Louis Monteiro <
>> jlmonteiro@tomitribe.com>:
>> >>
>> >>fix on trunk but maybe not merged to branch?
>> >>>
>> >>>
>> >>>--
>> >>>Jean-Louis Monteiro
>> >>>http://twitter.com/jlouismonteiro
>> >>>http://www.tomitribe.com
>> >>>
>> >>>
>> >>>On Sun, Jul 20, 2014 at 1:12 PM, Romain Manni-Bucau <
>> rmannibucau@gmail.com>
>> >>>wrote:
>> >>>
>> >>>
>> >>>> Hi Mark,
>> >>>>
>> >>>> on trunk? should have been fixed
>> >>>>
>> >>>>
>> >>>>
>> >>>> Romain Manni-Bucau
>> >>>> Twitter: @rmannibucau
>> >>>> Blog: http://rmannibucau.wordpress.com/
>> >>>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>> >>>> Github: https://github.com/rmannibucau
>> >>>>
>> >>>>
>> >>>> 2014-07-20 12:46 GMT+02:00 Mark Struberg <st...@yahoo.de>:
>> >>>>
>> >>>> > currently tomee doesn't build locally
>> >>>> >
>> >>>> > Tests in error:
>> >>>> > SubjectServiceTest.start:56 » EJB Provider error. No provider
>> >>>> definition
>> >>>> > found
>> >>>> > SubjectServiceTest.stop:67 NullPointer
>> >>>> >
>> >>>> > Tests run: 3, Failures: 0, Errors: 2, Skipped: 0
>> >>>> >
>> >>>> > Environment: mbp, OSX 10.9.4, java Orcl 1.7.0_51
>> >>>> >
>> >>>> > LieGrue,
>> >>>> > strub
>> >>>> >
>> >>>> >
>> >>>> > On Thursday, 17 July 2014, 23:44, Romain Manni-Bucau <
>> >>>> > rmannibucau@gmail.com> wrote:
>> >>>> >
>> >>>> >
>> >>>> > >
>> >>>> > >
>> >>>> > >Yeah, a lot of work done!
>> >>>> > >
>> >>>> > >Side node: the fact we need the javaagent is an openjpa issue of
>> >>>> > >subclassing (known but kind of regression for them without the
>> javaagent
>> >>>> > or
>> >>>> > >build time enhancement :()
>> >>>> > >Le 17 juil. 2014 22:11, "Andy Gumbrecht" <
>> agumbrecht@tomitribe.com> a
>> >>>> > >écrit :
>> >>>> > >
>> >>>> > >
>> >>>> > >> To sum up what was wrong with the failed release on Sunday.
>> >>>> > >>
>> >>>> > >> There was a SNAPSHOT dependency added to the parent POM and
>> missed on
>> >>>> > >> deploy - This was a breaking issue on the staging.
>> >>>> > >>
>> >>>> > >> The builds could not be run in parallel, as many tests were
>> using the
>> >>>> > same
>> >>>> > >> conflicting ports. We have not had concurrent builders running
>> on the
>> >>>> > same
>> >>>> > >> buildbot for some time, but we have just been 'lucky' that this
>> was
>> >>>> > >> 'mostly' working.
>> >>>> > >> I think I have most, if not all, the tests that bind to ports
>> changed
>> >>>> so
>> >>>> > >> that the ports are random - There will surely be more issues,
>> but
>> >>>> > >> concurrent builds have become significantly more stable.
>> >>>> > >> We have to be able to cope with this as we now run builds of
>> TomEE
>> >>>> 1.7.x
>> >>>> > >> on Java 6/7 and TomEE 2.0.x on Java 7/8/9EA - Most of these
>> will fire
>> >>>> at
>> >>>> > >> the same time on commits and merges.
>> >>>> > >>
>> >>>> > >> Another big issue that cost significant effort was that the
>> javaagent
>> >>>> > had
>> >>>> > >> been commented out in the openejb-core.pom during testing on
>> Java 7,
>> >>>> and
>> >>>> > >> unfortunately forgotten. This broke the enhancement for several
>> tests
>> >>>> > in a
>> >>>> > >> very subtle way so that it was not obvious what was going
>> wrong, the
>> >>>> > issues
>> >>>> > >> were only apparent on Java 7 build. This was also done at time
>> that
>> >>>> the
>> >>>> > >> build was not green, so made tracking down additionally hard.
>> >>>> Obviously
>> >>>> > >> this led us to believe that the Java 8 support we were about to
>> >>>> announce
>> >>>> > >> was broken.
>> >>>> > >>
>> >>>> > >> As trunk had already had significant formatting and finals
>> changes
>> >>>> > >> committed it was necessary to make the 1.7.x branch comparable
>> for
>> >>>> > >> successful merges. This also led to several test failures that
>> needed
>> >>>> > to be
>> >>>> > >> rectified. The upside is that many tests were tweaked and
>> updated
>> >>>> during
>> >>>> > >> this process.
>> >>>> > >>
>> >>>> > >> Java 7 builds on Windows platforms also revealed several
>> 'slightly'
>> >>>> > flawed
>> >>>> > >> tests, again the upside is that some minor issues were addressed
>> >>>> during
>> >>>> > >> analysis.
>> >>>> > >>
>> >>>> > >> We are now really close to getting all issues resolved - We
>> will have
>> >>>> > >> green builds by the end of the day.
>> >>>> > >>
>> >>>> > >> Andy.
>> >>>> > >>
>> >>>> > >>
>> >>>> > >> On 17/07/2014 17:18, David Blevins wrote:
>> >>>> > >>
>> >>>> > >>> Wondering if we can get a complete list of issues holding up
>> 1.7 on a
>> >>>> > >>> single thread.
>> >>>> > >>>
>> >>>> > >>> On the legal side, we still need:
>> >>>> > >>>
>> >>>> > >>> - Library diff
>> >>>> > >>> - Review/adjust LICENSE and NOTICE files
>> >>>> > >>>
>> >>>> > >>> The last one on the list frequently tanks releases. Doesn't
>> affect
>> >>>> > >>> security releases, but with larger versions is just a bear.
>> Let's
>> >>>> make
>> >>>> > >>> sure we do that one before we put up another vote as voting
>> >>>> drastically
>> >>>> > >>> decreases each time we reroll.
>> >>>> > >>>
>> >>>> > >>>
>> >>>> > >>>
>> >>>> > >>>
>> >>>> > >> --
>> >>>> > >> Andy Gumbrecht
>> >>>> > >>
>> >>>> > >> http://www.tomitribe.com
>> >>>> > >> agumbrecht@tomitribe.com
>> >>>> > >> https://twitter.com/AndyGeeDe
>> >>>> > >>
>> >>>> > >> TomEE treibt Tomitribe! | http://tomee.apache.org
>> >>>> > >>
>> >>>> > >>
>> >>>> > >
>> >>>> > >
>> >>>> >
>> >>>>
>> >>>
>> >>
>> >>
>> >>
>> >
>> >
>>
>
>
Re: TomEE 1.7.0 blockers
Posted by Jean-Louis Monteiro <jl...@tomitribe.com>.
Cool thx Mark
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Mon, Jul 21, 2014 at 8:38 AM, Mark Struberg <st...@yahoo.de> wrote:
> tomee-1.7.x branch builds fine.
> Sample app works fine.
> Will test with a few production apps today.
>
>
> LieGrue,
> strub
>
>
>
> On Sunday, 20 July 2014, 20:11, Mark Struberg <st...@yahoo.de> wrote:
>
>
> >
> >
> >oh gee, yea should have told you :)
> >
> >I'm on trunk. Will checkout 4.7.0 branch...
> >
> >LieGrue,
> >strub
> >
> >
> >
> >On Sunday, 20 July 2014, 16:10, Romain Manni-Bucau <rm...@gmail.com>
> wrote:
> >
> >
> >>
> >>
> >>sure but need to know where is the issue first
> >>
> >>
> >>
> >>
> >>Romain Manni-Bucau
> >>Twitter: @rmannibucau
> >>Blog: http://rmannibucau.wordpress.com/
> >>LinkedIn: http://fr.linkedin.com/in/rmannibucau
> >>Github: https://github.com/rmannibucau
> >>
> >>
> >>
> >>2014-07-20 16:07 GMT+02:00 Jean-Louis Monteiro <jlmonteiro@tomitribe.com
> >:
> >>
> >>fix on trunk but maybe not merged to branch?
> >>>
> >>>
> >>>--
> >>>Jean-Louis Monteiro
> >>>http://twitter.com/jlouismonteiro
> >>>http://www.tomitribe.com
> >>>
> >>>
> >>>On Sun, Jul 20, 2014 at 1:12 PM, Romain Manni-Bucau <
> rmannibucau@gmail.com>
> >>>wrote:
> >>>
> >>>
> >>>> Hi Mark,
> >>>>
> >>>> on trunk? should have been fixed
> >>>>
> >>>>
> >>>>
> >>>> Romain Manni-Bucau
> >>>> Twitter: @rmannibucau
> >>>> Blog: http://rmannibucau.wordpress.com/
> >>>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> >>>> Github: https://github.com/rmannibucau
> >>>>
> >>>>
> >>>> 2014-07-20 12:46 GMT+02:00 Mark Struberg <st...@yahoo.de>:
> >>>>
> >>>> > currently tomee doesn't build locally
> >>>> >
> >>>> > Tests in error:
> >>>> > SubjectServiceTest.start:56 » EJB Provider error. No provider
> >>>> definition
> >>>> > found
> >>>> > SubjectServiceTest.stop:67 NullPointer
> >>>> >
> >>>> > Tests run: 3, Failures: 0, Errors: 2, Skipped: 0
> >>>> >
> >>>> > Environment: mbp, OSX 10.9.4, java Orcl 1.7.0_51
> >>>> >
> >>>> > LieGrue,
> >>>> > strub
> >>>> >
> >>>> >
> >>>> > On Thursday, 17 July 2014, 23:44, Romain Manni-Bucau <
> >>>> > rmannibucau@gmail.com> wrote:
> >>>> >
> >>>> >
> >>>> > >
> >>>> > >
> >>>> > >Yeah, a lot of work done!
> >>>> > >
> >>>> > >Side node: the fact we need the javaagent is an openjpa issue of
> >>>> > >subclassing (known but kind of regression for them without the
> javaagent
> >>>> > or
> >>>> > >build time enhancement :()
> >>>> > >Le 17 juil. 2014 22:11, "Andy Gumbrecht" <ag...@tomitribe.com>
> a
> >>>> > >écrit :
> >>>> > >
> >>>> > >
> >>>> > >> To sum up what was wrong with the failed release on Sunday.
> >>>> > >>
> >>>> > >> There was a SNAPSHOT dependency added to the parent POM and
> missed on
> >>>> > >> deploy - This was a breaking issue on the staging.
> >>>> > >>
> >>>> > >> The builds could not be run in parallel, as many tests were
> using the
> >>>> > same
> >>>> > >> conflicting ports. We have not had concurrent builders running
> on the
> >>>> > same
> >>>> > >> buildbot for some time, but we have just been 'lucky' that this
> was
> >>>> > >> 'mostly' working.
> >>>> > >> I think I have most, if not all, the tests that bind to ports
> changed
> >>>> so
> >>>> > >> that the ports are random - There will surely be more issues, but
> >>>> > >> concurrent builds have become significantly more stable.
> >>>> > >> We have to be able to cope with this as we now run builds of
> TomEE
> >>>> 1.7.x
> >>>> > >> on Java 6/7 and TomEE 2.0.x on Java 7/8/9EA - Most of these will
> fire
> >>>> at
> >>>> > >> the same time on commits and merges.
> >>>> > >>
> >>>> > >> Another big issue that cost significant effort was that the
> javaagent
> >>>> > had
> >>>> > >> been commented out in the openejb-core.pom during testing on
> Java 7,
> >>>> and
> >>>> > >> unfortunately forgotten. This broke the enhancement for several
> tests
> >>>> > in a
> >>>> > >> very subtle way so that it was not obvious what was going wrong,
> the
> >>>> > issues
> >>>> > >> were only apparent on Java 7 build. This was also done at time
> that
> >>>> the
> >>>> > >> build was not green, so made tracking down additionally hard.
> >>>> Obviously
> >>>> > >> this led us to believe that the Java 8 support we were about to
> >>>> announce
> >>>> > >> was broken.
> >>>> > >>
> >>>> > >> As trunk had already had significant formatting and finals
> changes
> >>>> > >> committed it was necessary to make the 1.7.x branch comparable
> for
> >>>> > >> successful merges. This also led to several test failures that
> needed
> >>>> > to be
> >>>> > >> rectified. The upside is that many tests were tweaked and updated
> >>>> during
> >>>> > >> this process.
> >>>> > >>
> >>>> > >> Java 7 builds on Windows platforms also revealed several
> 'slightly'
> >>>> > flawed
> >>>> > >> tests, again the upside is that some minor issues were addressed
> >>>> during
> >>>> > >> analysis.
> >>>> > >>
> >>>> > >> We are now really close to getting all issues resolved - We will
> have
> >>>> > >> green builds by the end of the day.
> >>>> > >>
> >>>> > >> Andy.
> >>>> > >>
> >>>> > >>
> >>>> > >> On 17/07/2014 17:18, David Blevins wrote:
> >>>> > >>
> >>>> > >>> Wondering if we can get a complete list of issues holding up
> 1.7 on a
> >>>> > >>> single thread.
> >>>> > >>>
> >>>> > >>> On the legal side, we still need:
> >>>> > >>>
> >>>> > >>> - Library diff
> >>>> > >>> - Review/adjust LICENSE and NOTICE files
> >>>> > >>>
> >>>> > >>> The last one on the list frequently tanks releases. Doesn't
> affect
> >>>> > >>> security releases, but with larger versions is just a bear.
> Let's
> >>>> make
> >>>> > >>> sure we do that one before we put up another vote as voting
> >>>> drastically
> >>>> > >>> decreases each time we reroll.
> >>>> > >>>
> >>>> > >>>
> >>>> > >>>
> >>>> > >>>
> >>>> > >> --
> >>>> > >> Andy Gumbrecht
> >>>> > >>
> >>>> > >> http://www.tomitribe.com
> >>>> > >> agumbrecht@tomitribe.com
> >>>> > >> https://twitter.com/AndyGeeDe
> >>>> > >>
> >>>> > >> TomEE treibt Tomitribe! | http://tomee.apache.org
> >>>> > >>
> >>>> > >>
> >>>> > >
> >>>> > >
> >>>> >
> >>>>
> >>>
> >>
> >>
> >>
> >
> >
>
Re: TomEE 1.7.0 blockers
Posted by Mark Struberg <st...@yahoo.de>.
tomee-1.7.x branch builds fine.
Sample app works fine.
Will test with a few production apps today.
LieGrue,
strub
On Sunday, 20 July 2014, 20:11, Mark Struberg <st...@yahoo.de> wrote:
>
>
>oh gee, yea should have told you :)
>
>I'm on trunk. Will checkout 4.7.0 branch...
>
>LieGrue,
>strub
>
>
>
>On Sunday, 20 July 2014, 16:10, Romain Manni-Bucau <rm...@gmail.com> wrote:
>
>
>>
>>
>>sure but need to know where is the issue first
>>
>>
>>
>>
>>Romain Manni-Bucau
>>Twitter: @rmannibucau
>>Blog: http://rmannibucau.wordpress.com/
>>LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>Github: https://github.com/rmannibucau
>>
>>
>>
>>2014-07-20 16:07 GMT+02:00 Jean-Louis Monteiro <jl...@tomitribe.com>:
>>
>>fix on trunk but maybe not merged to branch?
>>>
>>>
>>>--
>>>Jean-Louis Monteiro
>>>http://twitter.com/jlouismonteiro
>>>http://www.tomitribe.com
>>>
>>>
>>>On Sun, Jul 20, 2014 at 1:12 PM, Romain Manni-Bucau <rm...@gmail.com>
>>>wrote:
>>>
>>>
>>>> Hi Mark,
>>>>
>>>> on trunk? should have been fixed
>>>>
>>>>
>>>>
>>>> Romain Manni-Bucau
>>>> Twitter: @rmannibucau
>>>> Blog: http://rmannibucau.wordpress.com/
>>>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>>> Github: https://github.com/rmannibucau
>>>>
>>>>
>>>> 2014-07-20 12:46 GMT+02:00 Mark Struberg <st...@yahoo.de>:
>>>>
>>>> > currently tomee doesn't build locally
>>>> >
>>>> > Tests in error:
>>>> > SubjectServiceTest.start:56 » EJB Provider error. No provider
>>>> definition
>>>> > found
>>>> > SubjectServiceTest.stop:67 NullPointer
>>>> >
>>>> > Tests run: 3, Failures: 0, Errors: 2, Skipped: 0
>>>> >
>>>> > Environment: mbp, OSX 10.9.4, java Orcl 1.7.0_51
>>>> >
>>>> > LieGrue,
>>>> > strub
>>>> >
>>>> >
>>>> > On Thursday, 17 July 2014, 23:44, Romain Manni-Bucau <
>>>> > rmannibucau@gmail.com> wrote:
>>>> >
>>>> >
>>>> > >
>>>> > >
>>>> > >Yeah, a lot of work done!
>>>> > >
>>>> > >Side node: the fact we need the javaagent is an openjpa issue of
>>>> > >subclassing (known but kind of regression for them without the javaagent
>>>> > or
>>>> > >build time enhancement :()
>>>> > >Le 17 juil. 2014 22:11, "Andy Gumbrecht" <ag...@tomitribe.com> a
>>>> > >écrit :
>>>> > >
>>>> > >
>>>> > >> To sum up what was wrong with the failed release on Sunday.
>>>> > >>
>>>> > >> There was a SNAPSHOT dependency added to the parent POM and missed on
>>>> > >> deploy - This was a breaking issue on the staging.
>>>> > >>
>>>> > >> The builds could not be run in parallel, as many tests were using the
>>>> > same
>>>> > >> conflicting ports. We have not had concurrent builders running on the
>>>> > same
>>>> > >> buildbot for some time, but we have just been 'lucky' that this was
>>>> > >> 'mostly' working.
>>>> > >> I think I have most, if not all, the tests that bind to ports changed
>>>> so
>>>> > >> that the ports are random - There will surely be more issues, but
>>>> > >> concurrent builds have become significantly more stable.
>>>> > >> We have to be able to cope with this as we now run builds of TomEE
>>>> 1.7.x
>>>> > >> on Java 6/7 and TomEE 2.0.x on Java 7/8/9EA - Most of these will fire
>>>> at
>>>> > >> the same time on commits and merges.
>>>> > >>
>>>> > >> Another big issue that cost significant effort was that the javaagent
>>>> > had
>>>> > >> been commented out in the openejb-core.pom during testing on Java 7,
>>>> and
>>>> > >> unfortunately forgotten. This broke the enhancement for several tests
>>>> > in a
>>>> > >> very subtle way so that it was not obvious what was going wrong, the
>>>> > issues
>>>> > >> were only apparent on Java 7 build. This was also done at time that
>>>> the
>>>> > >> build was not green, so made tracking down additionally hard.
>>>> Obviously
>>>> > >> this led us to believe that the Java 8 support we were about to
>>>> announce
>>>> > >> was broken.
>>>> > >>
>>>> > >> As trunk had already had significant formatting and finals changes
>>>> > >> committed it was necessary to make the 1.7.x branch comparable for
>>>> > >> successful merges. This also led to several test failures that needed
>>>> > to be
>>>> > >> rectified. The upside is that many tests were tweaked and updated
>>>> during
>>>> > >> this process.
>>>> > >>
>>>> > >> Java 7 builds on Windows platforms also revealed several 'slightly'
>>>> > flawed
>>>> > >> tests, again the upside is that some minor issues were addressed
>>>> during
>>>> > >> analysis.
>>>> > >>
>>>> > >> We are now really close to getting all issues resolved - We will have
>>>> > >> green builds by the end of the day.
>>>> > >>
>>>> > >> Andy.
>>>> > >>
>>>> > >>
>>>> > >> On 17/07/2014 17:18, David Blevins wrote:
>>>> > >>
>>>> > >>> Wondering if we can get a complete list of issues holding up 1.7 on a
>>>> > >>> single thread.
>>>> > >>>
>>>> > >>> On the legal side, we still need:
>>>> > >>>
>>>> > >>> - Library diff
>>>> > >>> - Review/adjust LICENSE and NOTICE files
>>>> > >>>
>>>> > >>> The last one on the list frequently tanks releases. Doesn't affect
>>>> > >>> security releases, but with larger versions is just a bear. Let's
>>>> make
>>>> > >>> sure we do that one before we put up another vote as voting
>>>> drastically
>>>> > >>> decreases each time we reroll.
>>>> > >>>
>>>> > >>>
>>>> > >>>
>>>> > >>>
>>>> > >> --
>>>> > >> Andy Gumbrecht
>>>> > >>
>>>> > >> http://www.tomitribe.com
>>>> > >> agumbrecht@tomitribe.com
>>>> > >> https://twitter.com/AndyGeeDe
>>>> > >>
>>>> > >> TomEE treibt Tomitribe! | http://tomee.apache.org
>>>> > >>
>>>> > >>
>>>> > >
>>>> > >
>>>> >
>>>>
>>>
>>
>>
>>
>
>
Re: TomEE 1.7.0 blockers
Posted by Mark Struberg <st...@yahoo.de>.
oh gee, yea should have told you :)
I'm on trunk. Will checkout 4.7.0 branch...
LieGrue,
strub
On Sunday, 20 July 2014, 16:10, Romain Manni-Bucau <rm...@gmail.com> wrote:
>
>
>sure but need to know where is the issue first
>
>
>
>
>Romain Manni-Bucau
>Twitter: @rmannibucau
>Blog: http://rmannibucau.wordpress.com/
>LinkedIn: http://fr.linkedin.com/in/rmannibucau
>Github: https://github.com/rmannibucau
>
>
>
>2014-07-20 16:07 GMT+02:00 Jean-Louis Monteiro <jl...@tomitribe.com>:
>
>fix on trunk but maybe not merged to branch?
>>
>>
>>--
>>Jean-Louis Monteiro
>>http://twitter.com/jlouismonteiro
>>http://www.tomitribe.com
>>
>>
>>On Sun, Jul 20, 2014 at 1:12 PM, Romain Manni-Bucau <rm...@gmail.com>
>>wrote:
>>
>>
>>> Hi Mark,
>>>
>>> on trunk? should have been fixed
>>>
>>>
>>>
>>> Romain Manni-Bucau
>>> Twitter: @rmannibucau
>>> Blog: http://rmannibucau.wordpress.com/
>>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>> Github: https://github.com/rmannibucau
>>>
>>>
>>> 2014-07-20 12:46 GMT+02:00 Mark Struberg <st...@yahoo.de>:
>>>
>>> > currently tomee doesn't build locally
>>> >
>>> > Tests in error:
>>> > SubjectServiceTest.start:56 » EJB Provider error. No provider
>>> definition
>>> > found
>>> > SubjectServiceTest.stop:67 NullPointer
>>> >
>>> > Tests run: 3, Failures: 0, Errors: 2, Skipped: 0
>>> >
>>> > Environment: mbp, OSX 10.9.4, java Orcl 1.7.0_51
>>> >
>>> > LieGrue,
>>> > strub
>>> >
>>> >
>>> > On Thursday, 17 July 2014, 23:44, Romain Manni-Bucau <
>>> > rmannibucau@gmail.com> wrote:
>>> >
>>> >
>>> > >
>>> > >
>>> > >Yeah, a lot of work done!
>>> > >
>>> > >Side node: the fact we need the javaagent is an openjpa issue of
>>> > >subclassing (known but kind of regression for them without the javaagent
>>> > or
>>> > >build time enhancement :()
>>> > >Le 17 juil. 2014 22:11, "Andy Gumbrecht" <ag...@tomitribe.com> a
>>> > >écrit :
>>> > >
>>> > >
>>> > >> To sum up what was wrong with the failed release on Sunday.
>>> > >>
>>> > >> There was a SNAPSHOT dependency added to the parent POM and missed on
>>> > >> deploy - This was a breaking issue on the staging.
>>> > >>
>>> > >> The builds could not be run in parallel, as many tests were using the
>>> > same
>>> > >> conflicting ports. We have not had concurrent builders running on the
>>> > same
>>> > >> buildbot for some time, but we have just been 'lucky' that this was
>>> > >> 'mostly' working.
>>> > >> I think I have most, if not all, the tests that bind to ports changed
>>> so
>>> > >> that the ports are random - There will surely be more issues, but
>>> > >> concurrent builds have become significantly more stable.
>>> > >> We have to be able to cope with this as we now run builds of TomEE
>>> 1.7.x
>>> > >> on Java 6/7 and TomEE 2.0.x on Java 7/8/9EA - Most of these will fire
>>> at
>>> > >> the same time on commits and merges.
>>> > >>
>>> > >> Another big issue that cost significant effort was that the javaagent
>>> > had
>>> > >> been commented out in the openejb-core.pom during testing on Java 7,
>>> and
>>> > >> unfortunately forgotten. This broke the enhancement for several tests
>>> > in a
>>> > >> very subtle way so that it was not obvious what was going wrong, the
>>> > issues
>>> > >> were only apparent on Java 7 build. This was also done at time that
>>> the
>>> > >> build was not green, so made tracking down additionally hard.
>>> Obviously
>>> > >> this led us to believe that the Java 8 support we were about to
>>> announce
>>> > >> was broken.
>>> > >>
>>> > >> As trunk had already had significant formatting and finals changes
>>> > >> committed it was necessary to make the 1.7.x branch comparable for
>>> > >> successful merges. This also led to several test failures that needed
>>> > to be
>>> > >> rectified. The upside is that many tests were tweaked and updated
>>> during
>>> > >> this process.
>>> > >>
>>> > >> Java 7 builds on Windows platforms also revealed several 'slightly'
>>> > flawed
>>> > >> tests, again the upside is that some minor issues were addressed
>>> during
>>> > >> analysis.
>>> > >>
>>> > >> We are now really close to getting all issues resolved - We will have
>>> > >> green builds by the end of the day.
>>> > >>
>>> > >> Andy.
>>> > >>
>>> > >>
>>> > >> On 17/07/2014 17:18, David Blevins wrote:
>>> > >>
>>> > >>> Wondering if we can get a complete list of issues holding up 1.7 on a
>>> > >>> single thread.
>>> > >>>
>>> > >>> On the legal side, we still need:
>>> > >>>
>>> > >>> - Library diff
>>> > >>> - Review/adjust LICENSE and NOTICE files
>>> > >>>
>>> > >>> The last one on the list frequently tanks releases. Doesn't affect
>>> > >>> security releases, but with larger versions is just a bear. Let's
>>> make
>>> > >>> sure we do that one before we put up another vote as voting
>>> drastically
>>> > >>> decreases each time we reroll.
>>> > >>>
>>> > >>>
>>> > >>>
>>> > >>>
>>> > >> --
>>> > >> Andy Gumbrecht
>>> > >>
>>> > >> http://www.tomitribe.com
>>> > >> agumbrecht@tomitribe.com
>>> > >> https://twitter.com/AndyGeeDe
>>> > >>
>>> > >> TomEE treibt Tomitribe! | http://tomee.apache.org
>>> > >>
>>> > >>
>>> > >
>>> > >
>>> >
>>>
>>
>
>
>
Re: TomEE 1.7.0 blockers
Posted by Romain Manni-Bucau <rm...@gmail.com>.
sure but need to know where is the issue first
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-07-20 16:07 GMT+02:00 Jean-Louis Monteiro <jl...@tomitribe.com>:
> fix on trunk but maybe not merged to branch?
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Sun, Jul 20, 2014 at 1:12 PM, Romain Manni-Bucau <rmannibucau@gmail.com
> >
> wrote:
>
> > Hi Mark,
> >
> > on trunk? should have been fixed
> >
> >
> >
> > Romain Manni-Bucau
> > Twitter: @rmannibucau
> > Blog: http://rmannibucau.wordpress.com/
> > LinkedIn: http://fr.linkedin.com/in/rmannibucau
> > Github: https://github.com/rmannibucau
> >
> >
> > 2014-07-20 12:46 GMT+02:00 Mark Struberg <st...@yahoo.de>:
> >
> > > currently tomee doesn't build locally
> > >
> > > Tests in error:
> > > SubjectServiceTest.start:56 » EJB Provider error. No provider
> > definition
> > > found
> > > SubjectServiceTest.stop:67 NullPointer
> > >
> > > Tests run: 3, Failures: 0, Errors: 2, Skipped: 0
> > >
> > > Environment: mbp, OSX 10.9.4, java Orcl 1.7.0_51
> > >
> > > LieGrue,
> > > strub
> > >
> > >
> > > On Thursday, 17 July 2014, 23:44, Romain Manni-Bucau <
> > > rmannibucau@gmail.com> wrote:
> > >
> > >
> > > >
> > > >
> > > >Yeah, a lot of work done!
> > > >
> > > >Side node: the fact we need the javaagent is an openjpa issue of
> > > >subclassing (known but kind of regression for them without the
> javaagent
> > > or
> > > >build time enhancement :()
> > > >Le 17 juil. 2014 22:11, "Andy Gumbrecht" <ag...@tomitribe.com> a
> > > >écrit :
> > > >
> > > >
> > > >> To sum up what was wrong with the failed release on Sunday.
> > > >>
> > > >> There was a SNAPSHOT dependency added to the parent POM and missed
> on
> > > >> deploy - This was a breaking issue on the staging.
> > > >>
> > > >> The builds could not be run in parallel, as many tests were using
> the
> > > same
> > > >> conflicting ports. We have not had concurrent builders running on
> the
> > > same
> > > >> buildbot for some time, but we have just been 'lucky' that this was
> > > >> 'mostly' working.
> > > >> I think I have most, if not all, the tests that bind to ports
> changed
> > so
> > > >> that the ports are random - There will surely be more issues, but
> > > >> concurrent builds have become significantly more stable.
> > > >> We have to be able to cope with this as we now run builds of TomEE
> > 1.7.x
> > > >> on Java 6/7 and TomEE 2.0.x on Java 7/8/9EA - Most of these will
> fire
> > at
> > > >> the same time on commits and merges.
> > > >>
> > > >> Another big issue that cost significant effort was that the
> javaagent
> > > had
> > > >> been commented out in the openejb-core.pom during testing on Java 7,
> > and
> > > >> unfortunately forgotten. This broke the enhancement for several
> tests
> > > in a
> > > >> very subtle way so that it was not obvious what was going wrong, the
> > > issues
> > > >> were only apparent on Java 7 build. This was also done at time that
> > the
> > > >> build was not green, so made tracking down additionally hard.
> > Obviously
> > > >> this led us to believe that the Java 8 support we were about to
> > announce
> > > >> was broken.
> > > >>
> > > >> As trunk had already had significant formatting and finals changes
> > > >> committed it was necessary to make the 1.7.x branch comparable for
> > > >> successful merges. This also led to several test failures that
> needed
> > > to be
> > > >> rectified. The upside is that many tests were tweaked and updated
> > during
> > > >> this process.
> > > >>
> > > >> Java 7 builds on Windows platforms also revealed several 'slightly'
> > > flawed
> > > >> tests, again the upside is that some minor issues were addressed
> > during
> > > >> analysis.
> > > >>
> > > >> We are now really close to getting all issues resolved - We will
> have
> > > >> green builds by the end of the day.
> > > >>
> > > >> Andy.
> > > >>
> > > >>
> > > >> On 17/07/2014 17:18, David Blevins wrote:
> > > >>
> > > >>> Wondering if we can get a complete list of issues holding up 1.7
> on a
> > > >>> single thread.
> > > >>>
> > > >>> On the legal side, we still need:
> > > >>>
> > > >>> - Library diff
> > > >>> - Review/adjust LICENSE and NOTICE files
> > > >>>
> > > >>> The last one on the list frequently tanks releases. Doesn't affect
> > > >>> security releases, but with larger versions is just a bear. Let's
> > make
> > > >>> sure we do that one before we put up another vote as voting
> > drastically
> > > >>> decreases each time we reroll.
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > > >> --
> > > >> Andy Gumbrecht
> > > >>
> > > >> http://www.tomitribe.com
> > > >> agumbrecht@tomitribe.com
> > > >> https://twitter.com/AndyGeeDe
> > > >>
> > > >> TomEE treibt Tomitribe! | http://tomee.apache.org
> > > >>
> > > >>
> > > >
> > > >
> > >
> >
>
Re: TomEE 1.7.0 blockers
Posted by Jean-Louis Monteiro <jl...@tomitribe.com>.
fix on trunk but maybe not merged to branch?
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Sun, Jul 20, 2014 at 1:12 PM, Romain Manni-Bucau <rm...@gmail.com>
wrote:
> Hi Mark,
>
> on trunk? should have been fixed
>
>
>
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
> 2014-07-20 12:46 GMT+02:00 Mark Struberg <st...@yahoo.de>:
>
> > currently tomee doesn't build locally
> >
> > Tests in error:
> > SubjectServiceTest.start:56 » EJB Provider error. No provider
> definition
> > found
> > SubjectServiceTest.stop:67 NullPointer
> >
> > Tests run: 3, Failures: 0, Errors: 2, Skipped: 0
> >
> > Environment: mbp, OSX 10.9.4, java Orcl 1.7.0_51
> >
> > LieGrue,
> > strub
> >
> >
> > On Thursday, 17 July 2014, 23:44, Romain Manni-Bucau <
> > rmannibucau@gmail.com> wrote:
> >
> >
> > >
> > >
> > >Yeah, a lot of work done!
> > >
> > >Side node: the fact we need the javaagent is an openjpa issue of
> > >subclassing (known but kind of regression for them without the javaagent
> > or
> > >build time enhancement :()
> > >Le 17 juil. 2014 22:11, "Andy Gumbrecht" <ag...@tomitribe.com> a
> > >écrit :
> > >
> > >
> > >> To sum up what was wrong with the failed release on Sunday.
> > >>
> > >> There was a SNAPSHOT dependency added to the parent POM and missed on
> > >> deploy - This was a breaking issue on the staging.
> > >>
> > >> The builds could not be run in parallel, as many tests were using the
> > same
> > >> conflicting ports. We have not had concurrent builders running on the
> > same
> > >> buildbot for some time, but we have just been 'lucky' that this was
> > >> 'mostly' working.
> > >> I think I have most, if not all, the tests that bind to ports changed
> so
> > >> that the ports are random - There will surely be more issues, but
> > >> concurrent builds have become significantly more stable.
> > >> We have to be able to cope with this as we now run builds of TomEE
> 1.7.x
> > >> on Java 6/7 and TomEE 2.0.x on Java 7/8/9EA - Most of these will fire
> at
> > >> the same time on commits and merges.
> > >>
> > >> Another big issue that cost significant effort was that the javaagent
> > had
> > >> been commented out in the openejb-core.pom during testing on Java 7,
> and
> > >> unfortunately forgotten. This broke the enhancement for several tests
> > in a
> > >> very subtle way so that it was not obvious what was going wrong, the
> > issues
> > >> were only apparent on Java 7 build. This was also done at time that
> the
> > >> build was not green, so made tracking down additionally hard.
> Obviously
> > >> this led us to believe that the Java 8 support we were about to
> announce
> > >> was broken.
> > >>
> > >> As trunk had already had significant formatting and finals changes
> > >> committed it was necessary to make the 1.7.x branch comparable for
> > >> successful merges. This also led to several test failures that needed
> > to be
> > >> rectified. The upside is that many tests were tweaked and updated
> during
> > >> this process.
> > >>
> > >> Java 7 builds on Windows platforms also revealed several 'slightly'
> > flawed
> > >> tests, again the upside is that some minor issues were addressed
> during
> > >> analysis.
> > >>
> > >> We are now really close to getting all issues resolved - We will have
> > >> green builds by the end of the day.
> > >>
> > >> Andy.
> > >>
> > >>
> > >> On 17/07/2014 17:18, David Blevins wrote:
> > >>
> > >>> Wondering if we can get a complete list of issues holding up 1.7 on a
> > >>> single thread.
> > >>>
> > >>> On the legal side, we still need:
> > >>>
> > >>> - Library diff
> > >>> - Review/adjust LICENSE and NOTICE files
> > >>>
> > >>> The last one on the list frequently tanks releases. Doesn't affect
> > >>> security releases, but with larger versions is just a bear. Let's
> make
> > >>> sure we do that one before we put up another vote as voting
> drastically
> > >>> decreases each time we reroll.
> > >>>
> > >>>
> > >>>
> > >>>
> > >> --
> > >> Andy Gumbrecht
> > >>
> > >> http://www.tomitribe.com
> > >> agumbrecht@tomitribe.com
> > >> https://twitter.com/AndyGeeDe
> > >>
> > >> TomEE treibt Tomitribe! | http://tomee.apache.org
> > >>
> > >>
> > >
> > >
> >
>
Re: TomEE 1.7.0 blockers
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi Mark,
on trunk? should have been fixed
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-07-20 12:46 GMT+02:00 Mark Struberg <st...@yahoo.de>:
> currently tomee doesn't build locally
>
> Tests in error:
> SubjectServiceTest.start:56 » EJB Provider error. No provider definition
> found
> SubjectServiceTest.stop:67 NullPointer
>
> Tests run: 3, Failures: 0, Errors: 2, Skipped: 0
>
> Environment: mbp, OSX 10.9.4, java Orcl 1.7.0_51
>
> LieGrue,
> strub
>
>
> On Thursday, 17 July 2014, 23:44, Romain Manni-Bucau <
> rmannibucau@gmail.com> wrote:
>
>
> >
> >
> >Yeah, a lot of work done!
> >
> >Side node: the fact we need the javaagent is an openjpa issue of
> >subclassing (known but kind of regression for them without the javaagent
> or
> >build time enhancement :()
> >Le 17 juil. 2014 22:11, "Andy Gumbrecht" <ag...@tomitribe.com> a
> >écrit :
> >
> >
> >> To sum up what was wrong with the failed release on Sunday.
> >>
> >> There was a SNAPSHOT dependency added to the parent POM and missed on
> >> deploy - This was a breaking issue on the staging.
> >>
> >> The builds could not be run in parallel, as many tests were using the
> same
> >> conflicting ports. We have not had concurrent builders running on the
> same
> >> buildbot for some time, but we have just been 'lucky' that this was
> >> 'mostly' working.
> >> I think I have most, if not all, the tests that bind to ports changed so
> >> that the ports are random - There will surely be more issues, but
> >> concurrent builds have become significantly more stable.
> >> We have to be able to cope with this as we now run builds of TomEE 1.7.x
> >> on Java 6/7 and TomEE 2.0.x on Java 7/8/9EA - Most of these will fire at
> >> the same time on commits and merges.
> >>
> >> Another big issue that cost significant effort was that the javaagent
> had
> >> been commented out in the openejb-core.pom during testing on Java 7, and
> >> unfortunately forgotten. This broke the enhancement for several tests
> in a
> >> very subtle way so that it was not obvious what was going wrong, the
> issues
> >> were only apparent on Java 7 build. This was also done at time that the
> >> build was not green, so made tracking down additionally hard. Obviously
> >> this led us to believe that the Java 8 support we were about to announce
> >> was broken.
> >>
> >> As trunk had already had significant formatting and finals changes
> >> committed it was necessary to make the 1.7.x branch comparable for
> >> successful merges. This also led to several test failures that needed
> to be
> >> rectified. The upside is that many tests were tweaked and updated during
> >> this process.
> >>
> >> Java 7 builds on Windows platforms also revealed several 'slightly'
> flawed
> >> tests, again the upside is that some minor issues were addressed during
> >> analysis.
> >>
> >> We are now really close to getting all issues resolved - We will have
> >> green builds by the end of the day.
> >>
> >> Andy.
> >>
> >>
> >> On 17/07/2014 17:18, David Blevins wrote:
> >>
> >>> Wondering if we can get a complete list of issues holding up 1.7 on a
> >>> single thread.
> >>>
> >>> On the legal side, we still need:
> >>>
> >>> - Library diff
> >>> - Review/adjust LICENSE and NOTICE files
> >>>
> >>> The last one on the list frequently tanks releases. Doesn't affect
> >>> security releases, but with larger versions is just a bear. Let's make
> >>> sure we do that one before we put up another vote as voting drastically
> >>> decreases each time we reroll.
> >>>
> >>>
> >>>
> >>>
> >> --
> >> Andy Gumbrecht
> >>
> >> http://www.tomitribe.com
> >> agumbrecht@tomitribe.com
> >> https://twitter.com/AndyGeeDe
> >>
> >> TomEE treibt Tomitribe! | http://tomee.apache.org
> >>
> >>
> >
> >
>
Re: TomEE 1.7.0 blockers
Posted by Mark Struberg <st...@yahoo.de>.
currently tomee doesn't build locally
Tests in error:
SubjectServiceTest.start:56 » EJB Provider error. No provider definition found
SubjectServiceTest.stop:67 NullPointer
Tests run: 3, Failures: 0, Errors: 2, Skipped: 0
Environment: mbp, OSX 10.9.4, java Orcl 1.7.0_51
LieGrue,
strub
On Thursday, 17 July 2014, 23:44, Romain Manni-Bucau <rm...@gmail.com> wrote:
>
>
>Yeah, a lot of work done!
>
>Side node: the fact we need the javaagent is an openjpa issue of
>subclassing (known but kind of regression for them without the javaagent or
>build time enhancement :()
>Le 17 juil. 2014 22:11, "Andy Gumbrecht" <ag...@tomitribe.com> a
>écrit :
>
>
>> To sum up what was wrong with the failed release on Sunday.
>>
>> There was a SNAPSHOT dependency added to the parent POM and missed on
>> deploy - This was a breaking issue on the staging.
>>
>> The builds could not be run in parallel, as many tests were using the same
>> conflicting ports. We have not had concurrent builders running on the same
>> buildbot for some time, but we have just been 'lucky' that this was
>> 'mostly' working.
>> I think I have most, if not all, the tests that bind to ports changed so
>> that the ports are random - There will surely be more issues, but
>> concurrent builds have become significantly more stable.
>> We have to be able to cope with this as we now run builds of TomEE 1.7.x
>> on Java 6/7 and TomEE 2.0.x on Java 7/8/9EA - Most of these will fire at
>> the same time on commits and merges.
>>
>> Another big issue that cost significant effort was that the javaagent had
>> been commented out in the openejb-core.pom during testing on Java 7, and
>> unfortunately forgotten. This broke the enhancement for several tests in a
>> very subtle way so that it was not obvious what was going wrong, the issues
>> were only apparent on Java 7 build. This was also done at time that the
>> build was not green, so made tracking down additionally hard. Obviously
>> this led us to believe that the Java 8 support we were about to announce
>> was broken.
>>
>> As trunk had already had significant formatting and finals changes
>> committed it was necessary to make the 1.7.x branch comparable for
>> successful merges. This also led to several test failures that needed to be
>> rectified. The upside is that many tests were tweaked and updated during
>> this process.
>>
>> Java 7 builds on Windows platforms also revealed several 'slightly' flawed
>> tests, again the upside is that some minor issues were addressed during
>> analysis.
>>
>> We are now really close to getting all issues resolved - We will have
>> green builds by the end of the day.
>>
>> Andy.
>>
>>
>> On 17/07/2014 17:18, David Blevins wrote:
>>
>>> Wondering if we can get a complete list of issues holding up 1.7 on a
>>> single thread.
>>>
>>> On the legal side, we still need:
>>>
>>> - Library diff
>>> - Review/adjust LICENSE and NOTICE files
>>>
>>> The last one on the list frequently tanks releases. Doesn't affect
>>> security releases, but with larger versions is just a bear. Let's make
>>> sure we do that one before we put up another vote as voting drastically
>>> decreases each time we reroll.
>>>
>>>
>>>
>>>
>> --
>> Andy Gumbrecht
>>
>> http://www.tomitribe.com
>> agumbrecht@tomitribe.com
>> https://twitter.com/AndyGeeDe
>>
>> TomEE treibt Tomitribe! | http://tomee.apache.org
>>
>>
>
>
Re: TomEE 1.7.0 blockers
Posted by "hanasaki@gmail.com" <ha...@gmail.com>.
[INFO] OpenEJB :: Examples :: JSF2/CDI/BV/JPA/DeltaSpike .. FAILURE [
20.204 s]
SEVERE - ==> a bad OS was mentionned
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.superbiz.deltaspike.exceptionhandling.ExceptionHandlingDemoTest
INFO -
********************************************************************************
INFO - OpenEJB http://openejb.apache.org/
INFO - Startup: Sun Jul 20 13:08:01 CDT 2014
INFO - Copyright 1999-2013 (C) Apache OpenEJB Project, All Rights Reserved.
INFO - Version: 5.0.0-SNAPSHOT
INFO - Build date: 20140720
INFO - Build time: 12:42
INFO -
********************************************************************************
INFO - openejb.home =
/home/export/hanasaki/NetBeansProjects/tomee/trunk/examples/deltaspike-exception-handling
INFO - openejb.base =
/home/export/hanasaki/NetBeansProjects/tomee/trunk/examples/deltaspike-exception-handling
INFO - Created new singletonService
org.apache.openejb.cdi.ThreadSingletonServiceImpl@473b46c3
INFO - Succeeded in installing singleton service
INFO - Cannot find the configuration file [conf/openejb.xml]. Will
attempt to create one for the beans deployed.
INFO - Configuring Service(id=Default Security Service,
type=SecurityService, provider-id=Default Security Service)
INFO - Configuring Service(id=Default Transaction Manager,
type=TransactionManager, provider-id=Default Transaction Manager)
INFO - Using 'openejb.deployments.classpath=false'
INFO - Creating TransactionManager(id=Default Transaction Manager)
INFO - Creating SecurityService(id=Default Security Service)
INFO - Configuring enterprise application:
/home/export/hanasaki/NetBeansProjects/tomee/trunk/examples/deltaspike-exception-handling/d0388df5-4c7a-4d1d-9579-2b7516069f81.war
INFO - Configuring Service(id=Default Managed Container, type=Container,
provider-id=Default Managed Container)
INFO - Auto-creating a container for bean
d0388df5-4c7a-4d1d-9579-2b7516069f81_org.superbiz.deltaspike.exceptionhandling.ExceptionHandlingDemoTest:
Container(type=MANAGED, id=Default Managed Container)
INFO - Creating Container(id=Default Managed Container)
INFO - Using directory /tmp for stateful session passivation
INFO - Enterprise application
"/home/export/hanasaki/NetBeansProjects/tomee/trunk/examples/deltaspike-exception-handling/d0388df5-4c7a-4d1d-9579-2b7516069f81.war"
loaded.
INFO - Assembling app:
/home/export/hanasaki/NetBeansProjects/tomee/trunk/examples/deltaspike-exception-handling/d0388df5-4c7a-4d1d-9579-2b7516069f81.war
INFO - Existing thread singleton service in SystemInstance():
org.apache.openejb.cdi.ThreadSingletonServiceImpl@473b46c3
INFO - OpenWebBeans Container is starting...
INFO - Adding OpenWebBeansPlugin : [CdiPlugin]
INFO - class:
org.apache.deltaspike.core.impl.config.ConfigurationExtension activated=true
INFO - class:
org.apache.deltaspike.core.impl.scope.DeltaSpikeContextExtension
activated=true
INFO - class: org.apache.deltaspike.core.impl.jmx.MBeanExtension
activated=true
INFO - class:
org.apache.deltaspike.core.impl.message.MessageBundleExtension
activated=true
INFO - class:
org.apache.deltaspike.core.impl.message.NamedMessageBundleInvocationHandler
activated=true
INFO - class:
org.apache.deltaspike.core.impl.exclude.extension.ExcludeExtension
activated=true
INFO - class:
org.apache.deltaspike.core.impl.exclude.CustomProjectStageBeanFilter
activated=true
INFO - class: org.apache.deltaspike.core.impl.exclude.GlobalAlternative
activated=true
INFO - class:
org.apache.deltaspike.core.impl.exception.control.extension.ExceptionControlExtension
activated=true
INFO - Computed the following DeltaSpike ProjectStage: Production
INFO - All injection points were validated successfully.
INFO - OpenWebBeans Container has started, it took 274 ms.
INFO - Deployed
Application(path=...../tomee/trunk/examples/deltaspike-exception-handling/d0388df5-4c7a-4d1d-9579-2b7516069f81.war)
*********** SEVERE - ==> a bad OS was mentionned
------------------------------------------------------------------------
*From:* Romain Manni-Bucau <rm...@gmail.com>
*Sent:* Thursday, July 17, 2014 4:42PM
*To:* dev@tomee.apache.org
*Subject:* Re: TomEE 1.7.0 blockers
failed : full trunk build @ 22:45 CST on 2014-07-17
"mvn clean install"
------------------------------------------------------------------------
*From:* Romain Manni-Bucau <rm...@gmail.com>
*Sent:* Thursday, July 17, 2014 4:42PM
*To:* dev@tomee.apache.org
*Subject:* Re: TomEE 1.7.0 blockers
> Yeah, a lot of work done!
>
> Side node: the fact we need the javaagent is an openjpa issue of
> subclassing (known but kind of regression for them without the javaagent or
> build time enhancement :()
> Le 17 juil. 2014 22:11, "Andy Gumbrecht" <ag...@tomitribe.com> a
> écrit :
>
>> To sum up what was wrong with the failed release on Sunday.
>>
>> There was a SNAPSHOT dependency added to the parent POM and missed on
>> deploy - This was a breaking issue on the staging.
>>
>> The builds could not be run in parallel, as many tests were using the same
>> conflicting ports. We have not had concurrent builders running on the same
>> buildbot for some time, but we have just been 'lucky' that this was
>> 'mostly' working.
>> I think I have most, if not all, the tests that bind to ports changed so
>> that the ports are random - There will surely be more issues, but
>> concurrent builds have become significantly more stable.
>> We have to be able to cope with this as we now run builds of TomEE 1.7.x
>> on Java 6/7 and TomEE 2.0.x on Java 7/8/9EA - Most of these will fire at
>> the same time on commits and merges.
>>
>> Another big issue that cost significant effort was that the javaagent had
>> been commented out in the openejb-core.pom during testing on Java 7, and
>> unfortunately forgotten. This broke the enhancement for several tests in a
>> very subtle way so that it was not obvious what was going wrong, the issues
>> were only apparent on Java 7 build. This was also done at time that the
>> build was not green, so made tracking down additionally hard. Obviously
>> this led us to believe that the Java 8 support we were about to announce
>> was broken.
>>
>> As trunk had already had significant formatting and finals changes
>> committed it was necessary to make the 1.7.x branch comparable for
>> successful merges. This also led to several test failures that needed to be
>> rectified. The upside is that many tests were tweaked and updated during
>> this process.
>>
>> Java 7 builds on Windows platforms also revealed several 'slightly' flawed
>> tests, again the upside is that some minor issues were addressed during
>> analysis.
>>
>> We are now really close to getting all issues resolved - We will have
>> green builds by the end of the day.
>>
>> Andy.
>>
>>
>> On 17/07/2014 17:18, David Blevins wrote:
>>
>>> Wondering if we can get a complete list of issues holding up 1.7 on a
>>> single thread.
>>>
>>> On the legal side, we still need:
>>>
>>> - Library diff
>>> - Review/adjust LICENSE and NOTICE files
>>>
>>> The last one on the list frequently tanks releases. Doesn't affect
>>> security releases, but with larger versions is just a bear. Let's make
>>> sure we do that one before we put up another vote as voting drastically
>>> decreases each time we reroll.
>>>
>>>
>>>
>>>
>> --
>> Andy Gumbrecht
>>
>> http://www.tomitribe.com
>> agumbrecht@tomitribe.com
>> https://twitter.com/AndyGeeDe
>>
>> TomEE treibt Tomitribe! | http://tomee.apache.org
>>
>>
>
Re: TomEE 1.7.0 blockers
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Yeah, a lot of work done!
Side node: the fact we need the javaagent is an openjpa issue of
subclassing (known but kind of regression for them without the javaagent or
build time enhancement :()
Le 17 juil. 2014 22:11, "Andy Gumbrecht" <ag...@tomitribe.com> a
écrit :
> To sum up what was wrong with the failed release on Sunday.
>
> There was a SNAPSHOT dependency added to the parent POM and missed on
> deploy - This was a breaking issue on the staging.
>
> The builds could not be run in parallel, as many tests were using the same
> conflicting ports. We have not had concurrent builders running on the same
> buildbot for some time, but we have just been 'lucky' that this was
> 'mostly' working.
> I think I have most, if not all, the tests that bind to ports changed so
> that the ports are random - There will surely be more issues, but
> concurrent builds have become significantly more stable.
> We have to be able to cope with this as we now run builds of TomEE 1.7.x
> on Java 6/7 and TomEE 2.0.x on Java 7/8/9EA - Most of these will fire at
> the same time on commits and merges.
>
> Another big issue that cost significant effort was that the javaagent had
> been commented out in the openejb-core.pom during testing on Java 7, and
> unfortunately forgotten. This broke the enhancement for several tests in a
> very subtle way so that it was not obvious what was going wrong, the issues
> were only apparent on Java 7 build. This was also done at time that the
> build was not green, so made tracking down additionally hard. Obviously
> this led us to believe that the Java 8 support we were about to announce
> was broken.
>
> As trunk had already had significant formatting and finals changes
> committed it was necessary to make the 1.7.x branch comparable for
> successful merges. This also led to several test failures that needed to be
> rectified. The upside is that many tests were tweaked and updated during
> this process.
>
> Java 7 builds on Windows platforms also revealed several 'slightly' flawed
> tests, again the upside is that some minor issues were addressed during
> analysis.
>
> We are now really close to getting all issues resolved - We will have
> green builds by the end of the day.
>
> Andy.
>
>
> On 17/07/2014 17:18, David Blevins wrote:
>
>> Wondering if we can get a complete list of issues holding up 1.7 on a
>> single thread.
>>
>> On the legal side, we still need:
>>
>> - Library diff
>> - Review/adjust LICENSE and NOTICE files
>>
>> The last one on the list frequently tanks releases. Doesn't affect
>> security releases, but with larger versions is just a bear. Let's make
>> sure we do that one before we put up another vote as voting drastically
>> decreases each time we reroll.
>>
>>
>>
>>
> --
> Andy Gumbrecht
>
> http://www.tomitribe.com
> agumbrecht@tomitribe.com
> https://twitter.com/AndyGeeDe
>
> TomEE treibt Tomitribe! | http://tomee.apache.org
>
>
Re: TomEE 1.7.0 blockers
Posted by Andy Gumbrecht <ag...@tomitribe.com>.
To sum up what was wrong with the failed release on Sunday.
There was a SNAPSHOT dependency added to the parent POM and missed on
deploy - This was a breaking issue on the staging.
The builds could not be run in parallel, as many tests were using the
same conflicting ports. We have not had concurrent builders running on
the same buildbot for some time, but we have just been 'lucky' that this
was 'mostly' working.
I think I have most, if not all, the tests that bind to ports changed so
that the ports are random - There will surely be more issues, but
concurrent builds have become significantly more stable.
We have to be able to cope with this as we now run builds of TomEE 1.7.x
on Java 6/7 and TomEE 2.0.x on Java 7/8/9EA - Most of these will fire at
the same time on commits and merges.
Another big issue that cost significant effort was that the javaagent
had been commented out in the openejb-core.pom during testing on Java 7,
and unfortunately forgotten. This broke the enhancement for several
tests in a very subtle way so that it was not obvious what was going
wrong, the issues were only apparent on Java 7 build. This was also done
at time that the build was not green, so made tracking down additionally
hard. Obviously this led us to believe that the Java 8 support we were
about to announce was broken.
As trunk had already had significant formatting and finals changes
committed it was necessary to make the 1.7.x branch comparable for
successful merges. This also led to several test failures that needed to
be rectified. The upside is that many tests were tweaked and updated
during this process.
Java 7 builds on Windows platforms also revealed several 'slightly'
flawed tests, again the upside is that some minor issues were addressed
during analysis.
We are now really close to getting all issues resolved - We will have
green builds by the end of the day.
Andy.
On 17/07/2014 17:18, David Blevins wrote:
> Wondering if we can get a complete list of issues holding up 1.7 on a single thread.
>
> On the legal side, we still need:
>
> - Library diff
> - Review/adjust LICENSE and NOTICE files
>
> The last one on the list frequently tanks releases. Doesn't affect security releases, but with larger versions is just a bear. Let's make sure we do that one before we put up another vote as voting drastically decreases each time we reroll.
>
>
>
--
Andy Gumbrecht
http://www.tomitribe.com
agumbrecht@tomitribe.com
https://twitter.com/AndyGeeDe
TomEE treibt Tomitribe! | http://tomee.apache.org
Re: TomEE 1.7.0 blockers
Posted by Jean-Louis Monteiro <jl...@tomitribe.com>.
Nothing in my bucket
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Thu, Jul 17, 2014 at 5:24 PM, Romain Manni-Bucau <rm...@gmail.com>
wrote:
> Hi David
>
> Regading code/setup/binaries we just need to check all is green (tck
> and buildbot) with latests fixes IMHO.
>
>
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
> 2014-07-17 17:18 GMT+02:00 David Blevins <da...@gmail.com>:
> > Wondering if we can get a complete list of issues holding up 1.7 on a
> single thread.
> >
> > On the legal side, we still need:
> >
> > - Library diff
> > - Review/adjust LICENSE and NOTICE files
> >
> > The last one on the list frequently tanks releases. Doesn't affect
> security releases, but with larger versions is just a bear. Let's make
> sure we do that one before we put up another vote as voting drastically
> decreases each time we reroll.
> >
> >
> >
> > --
> > David Blevins
> > http://twitter.com/dblevins
> > http://www.tomitribe.com
> >
>
Re: TomEE 1.7.0 blockers
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi David
Regading code/setup/binaries we just need to check all is green (tck
and buildbot) with latests fixes IMHO.
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-07-17 17:18 GMT+02:00 David Blevins <da...@gmail.com>:
> Wondering if we can get a complete list of issues holding up 1.7 on a single thread.
>
> On the legal side, we still need:
>
> - Library diff
> - Review/adjust LICENSE and NOTICE files
>
> The last one on the list frequently tanks releases. Doesn't affect security releases, but with larger versions is just a bear. Let's make sure we do that one before we put up another vote as voting drastically decreases each time we reroll.
>
>
>
> --
> David Blevins
> http://twitter.com/dblevins
> http://www.tomitribe.com
>