You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "STRAYER, JON (SBCSI)" <js...@sbc.com> on 2004/07/16 00:23:03 UTC
Release plugin
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Release plugin
Posted by Dion Gillard <di...@gmail.com>.
On Fri, 16 Jul 2004 17:13:57 -0400, Paul Spencer
<pa...@mindspring.com> wrote:
> Brett,
> 1) Has the release plugin been replaced by another plugin(s) or a
> "suggested release procedure"?
No, the release plugin was never really finished AFAIK. We have a
release procedure for plugins at
http://maven.apache.org/reference/developers/releasing-plugins.html
> 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/.
Will do.
> 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) <js...@sbc.com> 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: users-unsubscribe@maven.apache.org
> >>For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
http://www.multitask.com.au/people/dion/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Release plugin
Posted by Paul Spencer <pa...@mindspring.com>.
Dion,
I found the report, "Project Reports" -> Releases.
http://maven.apache.org/reference/plugins/multichanges-report.html
With the exception deprecation information, the report resolves #3.
This is a nice report!
Questions 1 and 2 are still unanswered. Should I open an issued in JIRA?
Paul Spencer
Dion Gillard wrote:
> Something like the multichanges report?
>
> On Fri, 16 Jul 2004 17:13:57 -0400, Paul Spencer
> <pa...@mindspring.com> wrote:
>
>>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) <js...@sbc.com> 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: users-unsubscribe@maven.apache.org
>>>>For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Release plugin
Posted by Dion Gillard <di...@gmail.com>.
Something like the multichanges report?
On Fri, 16 Jul 2004 17:13:57 -0400, Paul Spencer
<pa...@mindspring.com> wrote:
> 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) <js...@sbc.com> 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: users-unsubscribe@maven.apache.org
> >>For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
http://www.multitask.com.au/people/dion/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Release plugin
Posted by Paul Spencer <pa...@mindspring.com>.
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) <js...@sbc.com> 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: users-unsubscribe@maven.apache.org
>>For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Release plugin
Posted by Brett Porter <br...@gmail.com>.
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) <js...@sbc.com> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org