Hi Everyone - I'm having a problem checking out the code from my multi
module project - it's very frustrating and I've been working on it for a
few days, so any help anyone can provide will be greatly appreciated. I
posted this question to the user's list and didn't get much of a
response so I
I googled for an answer with no luck, so I posted this to the user list on
June 7 but have had no response. I'm hoping somebody on the dev list can
help.
Using the following configuration, the site reports end up
C:/opt/builds/releases/${branch}/${module}/siteReports as I expect. The
test
Dear valued Maven Developers
I would greatly appreciate if someone could shed a more detailed light on the
algorithm/strategy behind snapshot checking/downloading.
I already posted this on the user list, but did not receive a reaction:
Thomas,
you asked the very same question yesterday. And also a few days before that,
IIRC. Please don't spam the list!
As Justin pointed out yesterday, there may be several reasons that nobody
answers. Posting the same question every day will not make people give you
the solution any quicker.
Giuseppe.Greco wrote:
private void execute() throws MojoExecutionException
{
/* I need to get the execution id here */
}
/**
* @parameter default-value=${mojoExecution}
* @readonly
*/
private MojoExecution mojoExecution;
and
mojoExecution.getId();
should
no..if your plugin is bound to a phase of the default-lifecycle (unless
overidden at command-line)
i dont know if this requested enhancement has been coded?
http://docs.codehaus.org/display/MAVENUSER/Default+Plugin+Execution+IDs
is there an enhancement underway?
Martin Gainty
... it does not compile because the central repository does not contain
artifact maven-plugin-plugin :-(
Jeff
-Original Message-
From: Benjamin Bentmann [mailto:benjamin.bentm...@udo.edu]
Sent: Tuesday, June 15, 2010 3:49 PM
To: Maven Developers List
Subject: Re: How to get the
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-plugin-plugin/
On Jun 15, 2010, at 10:49 AM, giuseppe.gr...@b-source.ch
giuseppe.gr...@b-source.ch wrote:
... it does not compile because the central repository does not contain
artifact maven-plugin-plugin :-(
Jeff
Found... but version 2.6 does not contain class MojoExecution and the
code below does not compile.
-Original Message-
From: Jason van Zyl [mailto:ja...@sonatype.com]
Sent: Tuesday, June 15, 2010 4:51 PM
To: Maven Developers List
Subject: Re: How to get the execution id from a plugin
Yes, I realize.
Look at an existing plugin and start with that. Or use the Maven Plugin
archteype. If you don't know what I'm talking about then read this:
http://www.sonatype.com/products/maven/documentation/book-defguide
On Jun 15, 2010, at 11:04 AM, giuseppe.gr...@b-source.ch
Giuseppe.Greco wrote:
Found... but version 2.6 does not contain class MojoExecution and the
code below does not compile.
I don't really understand what you're trying to do when you *depend* on
the maven-plugin-plugin, usually it's just used to built your plugin's
metadata.
MojoExecution
Finally I was able to compile it... but it does not work. I created a
base class like this:
public abstract class ContextAbstractMojo extends AbstractMojo {
/**
* The execution ID as defined in the POM.
*
* @parameter default-value=${mojoExecution}}
* @readonly
*/
On 15 June 2010 16:31, giuseppe.gr...@b-source.ch wrote:
Finally I was able to compile it... but it does not work. I created a
base class like this:
public abstract class ContextAbstractMojo extends AbstractMojo {
/**
* The execution ID as defined in the POM.
*
*
Guy,
It works! Thank you very much for your help.
Cheers,
Jeff
-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: Tuesday, June 15, 2010 5:36 PM
To: Maven Developers List
Subject: Re: How to get the execution id from a plugin
On 15 June
I looked at this issue, and it seems to me like plexus-utils lost its
1.3 compatibility between 1.5.6 and 1.5.7. Not so long ago someone
declared plexus-utils 1.4, IMO a fairly sensible thing to do given the
state of affairs.
The only practical way I see of solving this stuff is to steal the
Or restore backward compatibility back to plexus-utils?
On Jun 15, 2010, at 12:29 PM, Kristian Rosenvold wrote:
I looked at this issue, and it seems to me like plexus-utils lost its
1.3 compatibility between 1.5.6 and 1.5.7. Not so long ago someone
declared plexus-utils 1.4, IMO a fairly
ti., 15.06.2010 kl. 12.43 -0400, skrev Jason van Zyl:
Or restore backward compatibility back to plexus-utils?
I'll give it a shot, I was a bit intimidated by compatibility having
been broken 2 years ago, but the breach I've seen can be solved
with other means.
Kristian
I started digging deeper into this issue, and it turns out that java 1.3
support last functioned in surefire 2.2. The plexus-utils dependency has
been 1.4-dependant since 18 june 07, and currently has some fairly heavy
1.4 dependencies.
Now 1.3 has been EOL'ed for 5 years. It's not as if the
The Site Plugin should be configured in the build section of the POM,
not in the reporting section.
On 2010-06-14 22:27, Anthony Jurado Jr wrote:
I googled for an answer with no luck, so I posted this to the user list on
June 7 but have had no response. I'm hoping somebody on the dev list
19 matches
Mail list logo
