You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by David Sean Taylor <da...@bluesunrise.com> on 2004/12/05 18:41:13 UTC
missed the maven plugin
I put out the release last night, and discovered this morning that I
missed changing the release to 2.0-M1 on the maven-jetspeed-plugin.
Sorry about that. Its still at a snapshot.
The next step is to move the maven project.xml versions to 2.0-M2-dev.
Is everyone ok with this convention?
Regarding the version number, it would be great if the project.xml
version was inherited from the parent the directory, to keep down the
maintenance. Would it be alright if we removed the current version
<currentVersion>2.0-M1</currentVersion>
from subprojects, and instead inherit from the root (by default, it can
always be overriden).
NOTE: there is an (incomplete) release todo document found under
/docs/release. If you find any other steps that I missed (Im sure there
are lots), please add the steps to the release todo documentation.
--
David Sean Taylor
Bluesunrise Software
david@bluesunrise.com
[office] +01 707 773 4646
[mobile] +01 707 529 9194
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: missed the maven plugin
Posted by "Scott T. Weaver" <sc...@binary-designs.net>.
David Sean Taylor wrote:
>
> I put out the release last night, and discovered this morning that I
> missed changing the release to 2.0-M1 on the maven-jetspeed-plugin.
> Sorry about that. Its still at a snapshot.
>
>
> The next step is to move the maven project.xml versions to 2.0-M2-dev.
> Is everyone ok with this convention?
+1
>
> Regarding the version number, it would be great if the project.xml
> version was inherited from the parent the directory, to keep down the
> maintenance. Would it be alright if we removed the current version
>
> <currentVersion>2.0-M1</currentVersion>
>
> from subprojects, and instead inherit from the root (by default, it
> can always be overriden).
+1
> NOTE: there is an (incomplete) release todo document found under
> /docs/release. If you find any other steps that I missed (Im sure
> there are lots), please add the steps to the release todo documentation.
>
--
"Great minds discuss ideas. Average minds discuss events. Small minds discuss people." - Admiral Hyman Rickover
*******************************************
* Scott T. Weaver *
* <we...@apache.org> *
* <http://www.einnovation.com> *
* -------------------------------------- *
* Apache Jetspeed Enterprise Portal *
* Apache Pluto Portlet Container *
* *
* OpenEdit, Website Content Management *
* <http://www.openedit.org> *
*******************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: missed the maven plugin
Posted by Roger Ruttimann <ro...@apache.org>.
David Sean Taylor wrote:
>
> I put out the release last night, and discovered this morning that I
> missed changing the release to 2.0-M1 on the maven-jetspeed-plugin.
> Sorry about that. Its still at a snapshot.
>
>
> The next step is to move the maven project.xml versions to 2.0-M2-dev.
> Is everyone ok with this convention?
>
+1
> Regarding the version number, it would be great if the project.xml
> version was inherited from the parent the directory, to keep down the
> maintenance. Would it be alright if we removed the current version
>
> <currentVersion>2.0-M1</currentVersion>
>
+1 makes maintenance/releases much easier
> from subprojects, and instead inherit from the root (by default, it
> can always be overriden).
>
> NOTE: there is an (incomplete) release todo document found under
> /docs/release. If you find any other steps that I missed (Im sure
> there are lots), please add the steps to the release todo documentation.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org