It turned out that the issue is gone the specified in
the plugin.xml [3] (lines 679-682) is manually commented out.
I don't get why this error causes. I have a feeling that this could be
because of an issue related to Plexus components. Commenting out that
section is not really a solution since th
.maven:maven-toolchain but something like
gentoo.groupid:gentoo12 if it matters.
Thanks,
--Kasun
>
>
> -Robert
>
>
>
>
> > From: kasu...@gmail.com
> > Date: Sat, 13 Aug 2011 15:07:17 +0530
> > Subject: Re: Issue in m-compile
ssue in m-compiler-p probably related to maven-toolchain
> To: dev@maven.apache.org
> CC: kio...@cryptelium.net; ser...@gentoo.org; ali_b...@gentoo.org
>
> Mark,
>
> On Sat, Aug 13, 2011 at 2:19 PM, Mark Struberg wrote:
>
> > Hi!
> >
> > Lets try to follow the logica
Mark,
On Sat, Aug 13, 2011 at 2:19 PM, Mark Struberg wrote:
> Hi!
>
> Lets try to follow the logical route. It's either
>
> a.) cannot find the 'compile' mojo
>
> or
>
> b.) 'or one of its required components'
>
>
> Ad a.): Maven plugins have xdoc annotations which will be used to generate
> a M
Hi!
Lets try to follow the logical route. It's either
a.) cannot find the 'compile' mojo
or
b.) 'or one of its required components'
Ad a.): Maven plugins have xdoc annotations which will be used to generate a
META-INF/maven/plugin.xml file in the plugins jar.
Can you check if this exists a