2009/2/4 Jason Chaffee
> I found a workaround that works, but it really bothers me because there is
> an underlying issue here that is unresolved and could cause any number of
> plugins to not work properly.
>
yep, same here - I really hope it gets fixed sooner rather than later...
> Here is t
Hi Brett,
It's always hard to tell from the output - is the resources call in
the forked lifecycle or the main one afterwards? The latter would
not retain all the settings.
I'm not 100% certain, however it looks like the resources call is
happening as part of the forked lifecycle[1].
The
I found a workaround that works, but it really bothers me because there is an
underlying issue here that is unresolved and could cause any number of plugins
to not work properly.
Here is the workaround:
Instead of making a primary artifact, I attach the artifact.
projectHelper.attachAr
FYI, I looked into the workaround that was suggested...resetting the extension
in the ArtifactHandler. However, I found that the extension is set correctly
in both the reactor build and individual project build. It is almost as if
there is some code that isn't even using extension, but rather
Yep, that is it. I have the same problem with a servicemix plugin as well. It
must be a bug with some dependency that is used by maven because not everyone
is experiencing this behavior. I have a colleague at a former company that has
tried both plugins in his environment with maven-2.0.9 and
There's a further resolution step. The resources:resources in question
is for the app, and has both:
[DEBUG] com.fidelity.shares:shares-app:jar:1.0-SNAPSHOT (selected for
null)
[DEBUG] com.fidelity.shares:shares-domain:jar:clover:1.0-
SNAPSHOT:compile (selected for compile)
and
[DEBUG]
On Tue, Feb 3, 2009 at 4:20 AM, Oleg Gusakov
wrote:
> I guess, I phrased my question incorrectly: maven trunk depends on mercury
> 1.0.0-alpha-2, where did you get that error? Building what?
>
> Thanks,
> Oleg
I was trying to build maven from trunk. (At revision 740247.)
Here is the modules se
Hi Vincent,
Author: vsiveton
Date: Mon Feb 2 23:43:09 2009
New Revision: 740156
URL: http://svn.apache.org/viewvc?rev=740156&view=rev
Log:
o fixed to UTF-8
Modified:
maven/doxia/doxia/trunk/doxia-book/src/main/resources/book-renderer_fr.properties
Modified:
maven/doxia/doxia/trunk/doxi
Hi Jerome,
looks obvious to me.
Can you open an issue in the JIRA with the patch attached?
2009/2/2 jerome creignou :
>
> Hi,
>
> I'm trying to use file mappers inside a maven plugin with the
> file-management shared project.
>
> I've added a fileset definition in the plugin's configuration as