You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by helio frota <00...@gmail.com> on 2014/04/03 02:11:41 UTC
[build] feedback 4
How to contribute with our cool Apache TomEE fighting against warning
messages:
1) Do the full build and save on log file or use jenkins
2) Run this command on your distribution
$ grep "WARNING" complete_output_aborted_stalled.txt | sort | uniq -u >
seek_and_destroy_warning_messages.txt
( This is like a Collections.sort ( on a List ) + plus HashSet in java )
full output attached
this is only warning messages from full build.
-------------------------------------------
http://eprogramming.github.io
Re: [build] feedback 4
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Take care a lot of warnings are normal. Maven warnings are not surefire
output warning will be hard to solve but both are greppable differently ;)
Le 3 avr. 2014 01:33, "helio frota" <00...@gmail.com> a écrit :
> Cool !
>
> Going to spread on CEJUG mailing list right now following the path:
>
> 1) Try to solve a waning
> 2) Open Jira issue ( with link to jira )
>
> BWT talk about the current TomEE debian package too and initiative of
> native packages this is really cool !
>
> cheers,
> helio
>
>
>
>
>
> -------------------------------------------
> http://eprogramming.github.io
>
>
>
> On Wed, Apr 2, 2014 at 9:24 PM, Thiago Veronezi <th...@veronezi.org>
> wrote:
>
> > Yup... good idea!
> > On Apr 2, 2014 8:21 PM, "helio frota" <00...@gmail.com> wrote:
> >
> > > Hi Thiago,
> > >
> > > Yes this is true, great point !
> > >
> > > But discarding INFO people can contribute with TomEE trying to solve
> some
> > > of this warnings.
> > >
> > > What do you think ?
> > >
> > > Tks !
> > >
> > >
> > >
> > > -------------------------------------------
> > > http://eprogramming.github.io
> > >
> > >
> > >
> > > On Wed, Apr 2, 2014 at 9:17 PM, Thiago Veronezi <th...@veronezi.org>
> > > wrote:
> > >
> > > > Hi Helio,
> > > >
> > > > Note that the build throws lots of warnings and exceptions as part of
> > the
> > > > unit tests.
> > > >
> > > > []s,
> > > > Thiago
> > > > On Apr 2, 2014 8:12 PM, "helio frota" <00...@gmail.com> wrote:
> > > >
> > > > > How to contribute with our cool Apache TomEE fighting against
> warning
> > > > > messages:
> > > > >
> > > > > 1) Do the full build and save on log file or use jenkins
> > > > > 2) Run this command on your distribution
> > > > >
> > > > > $ grep "WARNING" complete_output_aborted_stalled.txt | sort | uniq
> > -u >
> > > > > seek_and_destroy_warning_messages.txt
> > > > >
> > > > >
> > > > > ( This is like a Collections.sort ( on a List ) + plus HashSet in
> > java
> > > )
> > > > >
> > > > > full output attached
> > > > >
> > > > > this is only warning messages from full build.
> > > > >
> > > > > -------------------------------------------
> > > > > http://eprogramming.github.io
> > > > >
> > > > >
> > > >
> > >
> >
>
Re: [build] feedback 4
Posted by helio frota <00...@gmail.com>.
Cool !
Going to spread on CEJUG mailing list right now following the path:
1) Try to solve a waning
2) Open Jira issue ( with link to jira )
BWT talk about the current TomEE debian package too and initiative of
native packages this is really cool !
cheers,
helio
-------------------------------------------
http://eprogramming.github.io
On Wed, Apr 2, 2014 at 9:24 PM, Thiago Veronezi <th...@veronezi.org> wrote:
> Yup... good idea!
> On Apr 2, 2014 8:21 PM, "helio frota" <00...@gmail.com> wrote:
>
> > Hi Thiago,
> >
> > Yes this is true, great point !
> >
> > But discarding INFO people can contribute with TomEE trying to solve some
> > of this warnings.
> >
> > What do you think ?
> >
> > Tks !
> >
> >
> >
> > -------------------------------------------
> > http://eprogramming.github.io
> >
> >
> >
> > On Wed, Apr 2, 2014 at 9:17 PM, Thiago Veronezi <th...@veronezi.org>
> > wrote:
> >
> > > Hi Helio,
> > >
> > > Note that the build throws lots of warnings and exceptions as part of
> the
> > > unit tests.
> > >
> > > []s,
> > > Thiago
> > > On Apr 2, 2014 8:12 PM, "helio frota" <00...@gmail.com> wrote:
> > >
> > > > How to contribute with our cool Apache TomEE fighting against warning
> > > > messages:
> > > >
> > > > 1) Do the full build and save on log file or use jenkins
> > > > 2) Run this command on your distribution
> > > >
> > > > $ grep "WARNING" complete_output_aborted_stalled.txt | sort | uniq
> -u >
> > > > seek_and_destroy_warning_messages.txt
> > > >
> > > >
> > > > ( This is like a Collections.sort ( on a List ) + plus HashSet in
> java
> > )
> > > >
> > > > full output attached
> > > >
> > > > this is only warning messages from full build.
> > > >
> > > > -------------------------------------------
> > > > http://eprogramming.github.io
> > > >
> > > >
> > >
> >
>
Re: [build] feedback 4
Posted by Thiago Veronezi <th...@veronezi.org>.
Yup... good idea!
On Apr 2, 2014 8:21 PM, "helio frota" <00...@gmail.com> wrote:
> Hi Thiago,
>
> Yes this is true, great point !
>
> But discarding INFO people can contribute with TomEE trying to solve some
> of this warnings.
>
> What do you think ?
>
> Tks !
>
>
>
> -------------------------------------------
> http://eprogramming.github.io
>
>
>
> On Wed, Apr 2, 2014 at 9:17 PM, Thiago Veronezi <th...@veronezi.org>
> wrote:
>
> > Hi Helio,
> >
> > Note that the build throws lots of warnings and exceptions as part of the
> > unit tests.
> >
> > []s,
> > Thiago
> > On Apr 2, 2014 8:12 PM, "helio frota" <00...@gmail.com> wrote:
> >
> > > How to contribute with our cool Apache TomEE fighting against warning
> > > messages:
> > >
> > > 1) Do the full build and save on log file or use jenkins
> > > 2) Run this command on your distribution
> > >
> > > $ grep "WARNING" complete_output_aborted_stalled.txt | sort | uniq -u >
> > > seek_and_destroy_warning_messages.txt
> > >
> > >
> > > ( This is like a Collections.sort ( on a List ) + plus HashSet in java
> )
> > >
> > > full output attached
> > >
> > > this is only warning messages from full build.
> > >
> > > -------------------------------------------
> > > http://eprogramming.github.io
> > >
> > >
> >
>
Re: [build] feedback 4
Posted by helio frota <00...@gmail.com>.
Hi Thiago,
Yes this is true, great point !
But discarding INFO people can contribute with TomEE trying to solve some
of this warnings.
What do you think ?
Tks !
-------------------------------------------
http://eprogramming.github.io
On Wed, Apr 2, 2014 at 9:17 PM, Thiago Veronezi <th...@veronezi.org> wrote:
> Hi Helio,
>
> Note that the build throws lots of warnings and exceptions as part of the
> unit tests.
>
> []s,
> Thiago
> On Apr 2, 2014 8:12 PM, "helio frota" <00...@gmail.com> wrote:
>
> > How to contribute with our cool Apache TomEE fighting against warning
> > messages:
> >
> > 1) Do the full build and save on log file or use jenkins
> > 2) Run this command on your distribution
> >
> > $ grep "WARNING" complete_output_aborted_stalled.txt | sort | uniq -u >
> > seek_and_destroy_warning_messages.txt
> >
> >
> > ( This is like a Collections.sort ( on a List ) + plus HashSet in java )
> >
> > full output attached
> >
> > this is only warning messages from full build.
> >
> > -------------------------------------------
> > http://eprogramming.github.io
> >
> >
>
Re: [build] feedback 4
Posted by Thiago Veronezi <th...@veronezi.org>.
Hi Helio,
Note that the build throws lots of warnings and exceptions as part of the
unit tests.
[]s,
Thiago
On Apr 2, 2014 8:12 PM, "helio frota" <00...@gmail.com> wrote:
> How to contribute with our cool Apache TomEE fighting against warning
> messages:
>
> 1) Do the full build and save on log file or use jenkins
> 2) Run this command on your distribution
>
> $ grep "WARNING" complete_output_aborted_stalled.txt | sort | uniq -u >
> seek_and_destroy_warning_messages.txt
>
>
> ( This is like a Collections.sort ( on a List ) + plus HashSet in java )
>
> full output attached
>
> this is only warning messages from full build.
>
> -------------------------------------------
> http://eprogramming.github.io
>
>