Vincent,

I've read this a couple of times and I still can't understand what you mean.

So you are trying to create a file under the plugin cache directory in
a temporary folder?

Maybe you can send me a copy of the plugin and test case privately. I
assume this is for the work on i18n of the docs?

- Brett


On Sat, 12 Feb 2005 06:21:16 -0500, Siveton Vincent
<[EMAIL PROTECTED]> wrote:
> Hi every body,
> 
> I have a question regarding maven:reactor.
> 
> I am currently updating a plugin that is using the fmt tags.
> http://jakarta.apache.org/commons/jelly/libs/fmt/tags.html
> 
> To achieve it, the first step is to copy my bundle directly in the following
> plugin directory ie:
> ${user.home}\.maven\cache\thePlugin\plugin-resources\temp\${myBundle}.proper
> ties
> Why? Because of the setBundle tags:
> <fmt:setBundle basename="plugin-resources.temp.${myBundle}" var="myMsg" />
> 
> I have no problem to call the main goal of the plugin: I find the bundle
> that I copied and fmt tags worked.
> 
> However, if I am using maven:reactor, a loader problem appears:
> * if the bundle was already copied in the plugin resources, the bundle is
> correctly found, then it works very well.
> * if the bundle doesnt exist on the start up, I need to copy my bundle in
> the plugin resources. In the specific case, Maven reactor doesnt find the
> bundle (exactly the goal of the plugin called by maven:reactor).
> 
> Well, my god feeling is that the maven:reactor loads the environment of all
> plugins at the start up and doesnt update it if it changes.
> Is there a way to reload (automatically or manually) the environment for a
> given plugin?
> 
> Thanks for your response!
> 
> Cheers,
> 
> Vincent
> 
> ---------------------------------------------------------------------
> 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]

Reply via email to