There are good reasons for not having overlapping packages in separate jars.
Namely when alves security manager is running, our if the jar is signed then
they are treated as separate packages

- Stephen

---
Sent from my Android phone, so random spelling mistakes are a direct result
of using swype to type on the screen

On 26 Nov 2010 17:31, "Jesse Farinacci" <[email protected]> wrote:

Greetings Emerson,


On Fri, Nov 26, 2010 at 10:30 AM, emerson <[email protected]>
wrote:
> I believe it is cor...
That does appear to be the case, but I would be remiss if I didn't
point out the somewhat contradictory requests you're making. You want
the aggregation to maintain the separation. :-)

To address your previous observation about Hudson splitting out by
package, I suppose that may be true but I have structured my projects
in such a way (and I suspect most users have) where this is not an
issue. More specifically, for every project I can remember, there have
been no Java-package/Maven-module path name conflicts.

You could open an enhancement request at the plugin's JIRA instance[0]
but I would expect this enhancement to be fairly unpopular (not
negatively popular, but disinterested) given the aforementioned
opposing philosophical goals.

-Jesse

[0] http://jira.codehaus.org/browse/SUREFIRE


-- 
There are 10 types of people in this world, those
that can read binary and those that can not.
...

To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: users-he...

Reply via email to