On 11 Apr 07, at 2:24 AM 11 Apr 07, Carlos Sanchez wrote:
There are a number of packages that are spread in different jars.
As best practice and to play well with OSGi the same package shouldn't
be in two modules
We should copy classes to a new package, make old ones extend them and
deprecate t
On 4/11/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
I'm unclear as to what you are actually proposing. Does this apply to
new JARs, existing JARs. What is it that you're actually going to do
and why does this apply to the core of Maven?
I'd like to make sure a package is not used in two differ
There are a number of packages that are spread in different jars.
As best practice and to play well with OSGi the same package shouldn't
be in two modules
We should copy classes to a new package, make old ones extend them and
deprecate to retain compatibility.
I filed it as MNG-2943
Let me know
