Re: [jboss-as7-dev] What to do about jboss-common-core?
On 03/08/2012 08:33 AM, Bartosz Baranowski wrote:
I can move PEs to some lib just to kill this issue. Where should this
thing end up ?
----- Original Message -----
From: "Brian Stansberry"<brian.stansberry(a)redhat.com>
To: jboss-as7-dev(a)lists.jboss.org
Sent: Wednesday, March 7, 2012 7:13:28 PM
Subject: Re: [jboss-as7-dev] What to do about jboss-common-core?
On 3/7/12 9:37 AM, David M. Lloyd wrote:
> On 03/07/2012 08:35 AM, Brian Stansberry wrote:
>> We need to decide what we want to do about usage of the
>> jboss-common-core library.
> Pulling things into AS is definitely the wrong thing to do. I
> definitely agree on that score. I think the thing to do is to start
> fragmenting common-core into categories until everything we use has been
> put into its own library, and everything we don't use can then be dropped.
>
I assume you with categories you mean maven modules under a single maven
project with a single release cycle?
We can start of with 'jboss-common' and a legacy module 'core' which is
deprecated by design.
PEs can then go into a module 'beans'.
Let it only have a dependency on JRE and nothing else for the moment.
I think we'll find a reason to include logging stuff at some point.
http://github.com/jboss/jboss-common ?
Carlo
Any volunteers?
We've talked about the need for this for a long time, but no one has
done it.
>> A pull request[1] has come in that brings a bunch of jboss-common-core
>> classes into the AS 7 codebase.
>> [...]
> For the property editor stuff, which seems to be the bulk of this
> change, if it's widely used, perhaps a dedicated property editor library
> is called for. Aleš, does the POJO deployment subsystem use this code?
>