Brett, 1) Has the release plugin been replaced by another plugin(s) or a "suggested release procedure"?
2) Please document plugin deprecation. A good place to do this is on the plugin's home page, i.e. http://maven.apache.org/reference/plugins/release/.
3) Additional, a "plugin status" page that contains each plugin, it's
status (Current, Deprecated,..), current release number, and release
date would be very useful to the community. This sounds like a report
that can be generated by the multiproject plugin. Most of the
information is in project.xml and changes.xml
name = <project><name>
status = ?
current release and release number are the latest in changes.xml.
Paul Spencer
Brett Porter wrote:
No, we don't. We use a portion of the release plugin (the java code tag library) for another plugin, but the rest will be deprecated. We didn't want to chop it out before 1.0 in case anyone was using it...
On Thu, 15 Jul 2004 18:23:03 -0400, STRAYER, JON (SBCSI) <[EMAIL PROTECTED]> wrote:
Am I correct in thinking that the Maven team doesn't use the release plugin to build the distributions?
I finally figured out how to get release:build-distribution-bin to include the dependency jars, but I can't figure out how to get it to include the project jar.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
