For this effort I created a JIRA task in common package
https://jira.jboss.org/jira/browse/GTNCOMMON-6
I copied a few classes that are in GateIn portal that provides
concurrent facilities to the common package (AtomicPositiveLong,
BoundedBuffer, LongSampler) that were obvious and easy candidate for
this effort. They will be deleted from the portal once a new release
of the common module is available.
I have also sanitized the common module pom.xml from obsolete
dependencies and I changed its junit dependency scope to the test scope.
On Nov 4, 2009, at 2:56 PM, Julien Viet wrote:
I agree with Thomas that it is not a priority.
I want to add that there is some code in GateIn portal common like
the IO oriented stuff that I would not like to move to a common of
common.
So I'm open for discussing the things that could be moved to common
package.
I'm also open for doing gatein common sanitization, I think there
are a few things that could be removed (alhtough we removed a lot of
obsolete code).
On Nov 4, 2009, at 2:44 PM, Christophe Laprun wrote:
>
> On Nov 4, 2009, at 12:30 PM, Thomas Heute wrote:
>
>>
>> You should open a JIRA, it was pointed out a couple of times already
>> but
>> there are many other higher priorities and there is no trace of that
>> one
>> in Jira.
>
> Yeah, was planning on opening a JIRA for it but wanted to open the
> discussion as well on the ML. :)
>
>
https://jira.jboss.org/jira/browse/GTNPORTAL-189
>
> Cordialement / Best,
> Chris
>
> ==
> Principal Software Engineer / JBoss Enterprise Middleware Red Hat,
> Inc.
> Follow JBoss Portal:
http://jbossportal.blogspot.com /
http://twitter.com/jbossportal
> Follow me:
http://metacosm.codepuccino.com /
http://twitter.com/metacosm
>
> _______________________________________________
> gatein-dev mailing list
> gatein-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/gatein-dev