Lifecycle site has this phases [1] :
<lifecycle>
<id>site</id>
<phases>
<phase>pre-site</phase>
<phase>site</phase>
<phase>post-site</phase>
<phase>site-deploy</phase>
</phases>
<default-phases>
<site>org.apache.maven.plugins:maven-site-plugin:site</site>
<site-deploy>org.apache.maven.plugins:maven-site-plugin:deploy</site-deploy>
</default-phases>
</lifecycle>
You can do what you want if you attached plugins to phase pre-site.
--
Olivier
[1]
https://svn.apache.org/repos/asf/maven/components/trunk/maven-core/src/main/resources/META-INF/plexus/components.xml
-----Message d'origine-----
De : Nate [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 11 octobre 2006 18:11
À : Maven Users List
Objet : Re: Maven XSLT Plugin Question
Andreas,
Writing a plugin sounds like an interesting endeavor. I'll try that this
weekend. This appears cleaner to me in the long run since it will just be
another plugin execution.
Marco,
Since I need a short-term fix for this week's release, I think I'll use your
ant "xslt task" idea. What execute phase should I set for this to execute
every time before the changes plugin is executed during the site generation?
Thanks for responding so quickly,
-Nate
> Hello,
> my 2 cents.... ant has an xslt task, you could use maven antrun
> plugin to run it
>
> will that be a possible solution?
>
> hth
> marco
>
>
>
> On 10/11/06, Andreas Guther <[EMAIL PROTECTED]> wrote:
>>
>> I am not aware of an XSLT plug-in, but writing one should be a pretty
>> straight forward task. I guess I then would try to associate the
>> plug-in with source code generation or something similar during the
>> site creation life cycle.
>>
>> Writing Maven 2 plug-ins is an easy to achieve task and there are
>> plenty of examples available.
>>
>>
>> Andreas
>>
>>
>>
>>
>> -----Original Message-----
>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>> Sent: Wednesday, October 11, 2006 7:24 AM
>> To: [email protected]
>> Subject: Maven XSLT Plugin Question
>>
>> I have an application that using XML to define the features added to
>> each release version. I wrote an XSLT to convert this XML into the
>> changes plugin XML format. This allows me to have the same
>> information in the application and the generated site, but the XSLT
>> execution is a manual step. I have a couple of ideas for a solution,
>> but I'm not sure what is available.
>>
>> 1. Does the changes plugin allow a mapping XSL to be included to
>> convert a different XML into a changes plugin?
>> 2. If not, is there plugin to executes XSL transforms during the site
>> cycle?
>> 3. If not, can an ant script be setup to run before the changes plugin?
>> Or is there a "pre-site" cycle that it can be executed.
>>
>> If you have a different idea, I would be interested in hearing it.
>> Especially if the ant script is the only solution, since it seems
>> hackish to call java with a Saxon jar to transform during the site
>> generation.
>>
>> Thanks for the help,
>> -Nate
>>
>>
>>
>> ---------------------------------------------------------------------
>> 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]
This e-mail, any attachments and the information contained therein ("this
message") are confidential and intended solely for the use of the addressee(s).
If you have received this message in error please send it back to the sender
and delete it. Unauthorized publication, use, dissemination or disclosure of
this message, either in whole or in part is strictly prohibited.
--------------------------------------------------------------------------------------------------------------
Ce message électronique et tous les fichiers joints ainsi que les informations
contenues dans ce message ( ci après "le message" ), sont confidentiels et
destinés exclusivement à l'usage de la personne à laquelle ils sont adressés.
Si vous avez reçu ce message par erreur, merci de le renvoyer à son émetteur
et de le détruire. Toutes diffusion, publication, totale ou partielle ou
divulgation sous quelque forme que se soit non expressément autorisées de ce
message, sont interdites.
-------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
