You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Henning P. Schmiedehausen" <hp...@intermeta.de> on 2007/04/09 17:47:36 UTC
Releasing the site tools
Hi,
public holidays are a good thing. Today I finally found time to update
the docs for the various site related maven tools and plugins located
at http://velocity.apache.org/site/tools/
How about doing a release? There is one minor drawback IMHO: The
plugins work best when run in conjunction with the not-yet-released
Doxia 1.0-alpha-9 and the Doxia Sitetools 1.0 (those of you with an
account on velocity.zones might notice that I tricked a bit there).
However, they do run and with the mess that the maven developers
created by unconditionally adding Velocity parsing to Doxia, it might
even be an interesting alternative to release now (I would have simply
given them the Doxia Renderer code for inclusion as is, but well,
Maven is a terminal case of "not invented here").
Some status:
* Velocity Site Skin. That is stable. No problems releasing this.
* Velocity Site News Plugin. Uses some probably illegal maven
trickery. Jason told me that he wants to help me making it really
maven-compliant but I found no time to contact him about it. Maybe
he will have some time in Amsterdam. Release wise, this is now
stable and works we. Could use some more exposure; I know that some
projects are interested in this (James e.g.)
* Velocity Site Doxia Renderer. Doxia sprouted something similar without
our capabilities to load macros and tools and the current Doxia trunk
renders every apt and xdoc page through Velocity (the singleton one from
the Plexus component) which certainly wreaked havoc with many sites that
rely on maven to build. Once Doxia has shaken out these problems (with
the current cycle of one alpha release per year probably 2021), I think
that this plugin will just go away. Until then, having it makes our life
easy for the dynamic part of the site.
Everything builds against released parts of Maven. No Snapshots, trunk
or anything else.
So what do you think? Shall we release this stuff? If no one objects,
I will CfV sometime Thursday or Friday.
Best regards
Henning
--
Henning P. Schmiedehausen -- hps@intermeta.de | J2EE, Linux, |gls
91054 Buckenhof, Germany -- +49 9131 506540 | Apache person |eau
Open Source Consulting, Development, Design | Velocity - Turbine guy |rwc
|m k
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350 |a s
Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen |n
"Save the cheerleader. Save the world."
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
Re: Releasing the site tools
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
"Will Glass-Husain" <wg...@gmail.com> writes:
>Seems pretty good to me. Especially now since the site builds with released
>Maven.
>Based on your email, I'm a little worried about the "Velocity Site Doxia
>Renderer" that it may break with future versions of Maven. Don't think this
Yes. Maven internals are such a turmoil, you would not believe it. The
internal container hierarchy changed between 2.0.4 and 2.0.5 (note the
minor version change) and as the plugin try to do something new and
unexpected, they broke, too.
I'd say that at least for maven 2.0.x I do not really expect as big
changes as there, but that is the main reason why the maven on
velocity.zones is somewhat 'frozen' in a known, working configuration.
>is worth stopping a release (and I haven't followed the technical details)
>but I'd be happier if we could migrate this to remove "illegal Maven
>trickery". Does the readme file note the issues you raised in your email?
>(To help future users debug any problems from strange version issues?)
It is not really illegal. More sort of "immoral" because I use
internal knowledge of the Plexus Container to introspect a private
field. If you are interested, take a look at the PlexusKludge stuff.
>The Doxia plug-in sounds like a useful workaround. Do we have a README file
>that explains what this does and why it is needed?
What it does: yes. http://velocity.apache.org/site/tools/ has all the
docs. Why: Actually, I don't bother.
Releasing is important to me because it allows distribution of the
plugins to the maven repo and our users can rebuild the site with
maven picking up the plugins automatically. Something that is good.
Everything builds against stock Maven 2.0.6, everything runs with
stock Maven 2.0.6 If you do not apply the patches that we have on
velocity.zones, some of the links (mainly the links from the changes
report to the "who-we-are" page) are broken. No big deal.
Best regards
Henning
--
Henning P. Schmiedehausen -- hps@intermeta.de | J2EE, Linux, |gls
91054 Buckenhof, Germany -- +49 9131 506540 | Apache person |eau
Open Source Consulting, Development, Design | Velocity - Turbine guy |rwc
|m k
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350 |a s
Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen |n
"Save the cheerleader. Save the world."
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
Re: Releasing the site tools
Posted by Will Glass-Husain <wg...@gmail.com>.
Seems pretty good to me. Especially now since the site builds with released
Maven.
Based on your email, I'm a little worried about the "Velocity Site Doxia
Renderer" that it may break with future versions of Maven. Don't think this
is worth stopping a release (and I haven't followed the technical details)
but I'd be happier if we could migrate this to remove "illegal Maven
trickery". Does the readme file note the issues you raised in your email?
(To help future users debug any problems from strange version issues?)
The Doxia plug-in sounds like a useful workaround. Do we have a README file
that explains what this does and why it is needed?
WILL
On 4/9/07, Henning P. Schmiedehausen <hp...@intermeta.de> wrote:
>
> Hi,
>
> public holidays are a good thing. Today I finally found time to update
> the docs for the various site related maven tools and plugins located
> at http://velocity.apache.org/site/tools/
>
> How about doing a release? There is one minor drawback IMHO: The
> plugins work best when run in conjunction with the not-yet-released
> Doxia 1.0-alpha-9 and the Doxia Sitetools 1.0 (those of you with an
> account on velocity.zones might notice that I tricked a bit there).
>
> However, they do run and with the mess that the maven developers
> created by unconditionally adding Velocity parsing to Doxia, it might
> even be an interesting alternative to release now (I would have simply
> given them the Doxia Renderer code for inclusion as is, but well,
> Maven is a terminal case of "not invented here").
>
> Some status:
>
> * Velocity Site Skin. That is stable. No problems releasing this.
>
> * Velocity Site News Plugin. Uses some probably illegal maven
> trickery. Jason told me that he wants to help me making it really
> maven-compliant but I found no time to contact him about it. Maybe
> he will have some time in Amsterdam. Release wise, this is now
> stable and works we. Could use some more exposure; I know that some
> projects are interested in this (James e.g.)
>
> * Velocity Site Doxia Renderer. Doxia sprouted something similar without
> our capabilities to load macros and tools and the current Doxia trunk
> renders every apt and xdoc page through Velocity (the singleton one from
> the Plexus component) which certainly wreaked havoc with many sites that
> rely on maven to build. Once Doxia has shaken out these problems (with
> the current cycle of one alpha release per year probably 2021), I think
> that this plugin will just go away. Until then, having it makes our life
> easy for the dynamic part of the site.
>
> Everything builds against released parts of Maven. No Snapshots, trunk
> or anything else.
>
> So what do you think? Shall we release this stuff? If no one objects,
> I will CfV sometime Thursday or Friday.
>
> Best regards
> Henning
>
> --
> Henning P. Schmiedehausen -- hps@intermeta.de | J2EE,
> Linux, |gls
> 91054 Buckenhof, Germany -- +49 9131 506540 | Apache
> person |eau
> Open Source Consulting, Development, Design | Velocity - Turbine
> guy |rwc
> |m
> k
> INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB
> 7350 |a s
> Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning
> Schmiedehausen |n
>
> "Save the cheerleader. Save the world."
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
> For additional commands, e-mail: dev-help@velocity.apache.org
>
>
--
Forio Business Simulations
Will Glass-Husain
wglass@forio.com
www.forio.com