[Bug 232719] maven2-2.0.4-10jpp.3 - Java project management and project comprehension tool

bugzilla at redhat.com bugzilla at redhat.com
Sat Mar 17 00:29:55 UTC 2007


Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: maven2-2.0.4-10jpp.3 - Java project management and project comprehension tool


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=232719





------- Additional Comments From mwringe at redhat.com  2007-03-16 20:29 EST -------
(In reply to comment #2)
> The plugin sources need to be cut at the time maven was cut. Because the plugins
> have a different release cycle, maintaining them separately could invite a host
> of copmpatibility issues as one version of a plugin may require one version of
> maven, while another requires another version. The current cut of plugins in the
> plugins is as close as possible to the time that maven2 2.0.4 was cut.

So, your argument is that since maven and its plugins constantly update, that
the only way to properly package it is to take a snapshot of everthing at one time? 
I guess in this situation the plugins would no longer be considered separate
projects, but part of the larger maven whole (at that point in time).

I am not entirely confortable with having multiple tarballs in there, but I
guess it this might have to be the case for this situation ...

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.




More information about the package-review mailing list