It's pure Java, so the localization should be significantly easier.
There are a couple of approaches:
- for Maven 1.0.x, we could make a jelly wrapper that mimics the
existing functionality, and calls into the java plugin jar.
- for Maven 1.1.x, we can probably have the core load them directly
fai
...
>
> Are you sure you wouldn't rather invest this effort into the
> m2 localization? :)
How could we investigate on this ?
Is there some tests on how to integrate a m2 plugin in m1 ?
Arnaud
-
To unsubscribe, e-mail: [EMA
If you have an enclosing tag, you probably want a method like:
{
get classloader
construct new classloader, add resource
set new classloader
invokeBody( output );
set old classloader back
}
Are you sure you wouldn't rather invest this effort into the m2
localization? :)
- Bre
t: Sunday, May 01, 2005 8:32 AM
> To: Maven Developers List
> Cc: 'Brett Porter'; 'Arnaud HERITIER'
> Subject: Re: I18n site
>
> Ah, I see. It was working inside the reactor for me, but not when you
> run a few projects. Because the classloader accumulates, you g
Ah, I see. It was working inside the reactor for me, but not when you
run a few projects. Because the classloader accumulates, you gather up
other stuff, so the result never changes.
You can develop a tag that does the following:
- grab the existing classloader
- create a new classloader that inhe
Hi Brett,
> Sorry for the really long time it took to respond.
No problem :o)
> I didn't feel confident about copying files into the plugin cache
> directory, so I investigated it more. What I suggest is placing the
> bundles under the project directory somewhere - perhaps xdocs, or
> perhaps
