off the top of my head
how about declaring your plugin to bind to another phase ?
the second option is to
create custom lifecycle
https://community.jboss.org/wiki/CreatingACustomLifecycleInMaven
Get your hip boots on ..custom lifecyles are 'unsupported'
Viel Gluck
Martin
---
I think MojoDecriptor can get me PluginDescriptor. but dont think
${mojo} would give me MojoDescriptor. Null is what I get.
-D
On Sun, Feb 24, 2013 at 2:25 PM, Dan Tran wrote:
> what is the class for ${mojo}?
>
> the closest I can get from within my mojo is
> this.getPluginContext(), but this do
what is the class for ${mojo}?
the closest I can get from within my mojo is
this.getPluginContext(), but this does not lead me to PluginDecriptor
Thanks
-D
On Sun, Feb 24, 2013 at 1:03 PM, Robert Scholte wrote:
> http://maven.apache.org/plugin-tools/maven-plugin-tools-annotations/index.html
>
http://maven.apache.org/plugin-tools/maven-plugin-tools-annotations/index.html
I wasn't aware that this is a M3 only feature, but through ${mojo} you
should be able to find the PluginDescriptor too
Robert
Op Sun, 24 Feb 2013 21:35:09 +0100 schreef Dan Tran :
Strange thing happens,
under m
Strange thing happens,
under maven2 the contents of ${plugin} is empty, ( ie
plugin.getArtifacts() = null ), does it has something to do with me
upgrade to latest mojo-parent?
Thanks
-D
On Sun, Feb 24, 2013 at 10:30 AM, Dan Tran wrote:
> Thanks Robert, this gives me a good start
>
> -D
>
> On
Hello Martin,
thanks for your suggestion. However I think I did not make myself
clear in my description. My problem is not with generated reports but
that during report generation while building the site a bunch of the
reporting mojos are starting a "default" lifecycle phase again hereby
prolongin
Thanks Robert, this gives me a good start
-D
On Sun, Feb 24, 2013 at 2:46 AM, Robert Scholte wrote:
> Hi Dan,
>
> ${plugin} will return the ProjectDescriptor[1]
> From here you can get the artifacts or artifactsMap and maybe you could
> filter on runtime-scoped artifacts.
> That will probably be
-- Forwarded message --
From: Olivier Lamy
Date: Sat, Feb 23, 2013 at 9:59 AM
Subject: [SECURITY] CVE-2013-0253 Apache Maven 3.0.4
To: annou...@apache.org, annou...@maven.apache.org
Cc: Maven Developers List
VE-2013-0253 Apache Maven
Severity: Medium
Vendor: The Apache Softwar
Just wanted to bring this to the users list and ensure that those reading
the release notes see the security alert for 3.0.4:
CVE-2013-0253 Apache Maven
Severity: Medium
Vendor: The Apache Software Foundation
Versions Affected:
- Apache Maven 3.0.4
- Apache Maven Wagon 2.1, 2.2, 2.3
Descripti
Mirko
one way is to customise maven-clean plugin to exclude target folder and only
include reports
for example we can leave target alone and delete surefire with this example
org.apache.maven.plugins
maven-clean-plugin
2.4.1
Matthew and Frederic
properties-maven-plugin has no hardcoded reference to derby.log
If you could identify the ORM maven-plugin groupId,artifactId,version you are
implementing ..we could take a look at where its going fubar
-M
> Date: Sun, 24 Feb 2013 08
Am 24.02.2013 12:39, schrieb Thomas Sundberg:
Hi!
I just wrote a blog on getting started with Maven It might help
someone to get a small example up and running.
http://thomassundberg.wordpress.com/2013/02/24/maven-the-simplest-possible-introduction/
You may want to mark the JUnit dependency as
Hi!
I just wrote a blog on getting started with Maven It might help
someone to get a small example up and running.
http://thomassundberg.wordpress.com/2013/02/24/maven-the-simplest-possible-introduction/
Cheers
Thomas
--
Thomas Sundberg
M. Sc. in Computer Science
Mobile: +46 70 767 33 15
Blog:
The Apache Maven team is pleased to announce the release of the Maven Help
Plugin, version 2.2
This plugin is used to get relative information about a project or the
system. It can be used to get a description of a particular plugin,
including the plugin's mojos with their parameters and co
Hi Dan,
${plugin} will return the ProjectDescriptor[1]
From here you can get the artifacts or artifactsMap and maybe you could
filter on runtime-scoped artifacts.
That will probably be good enough most of the time, but it not really
reliable (you're not sure if you get only the required artif
Am 23.02.2013 21:21, schrieb Baptiste MATHUS:
Hi Joachim,
Could you please tell us the URL of the page(s) you read where you think
this information would have been valuable?
We can improve it.
http://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html#updateReleaseInfo
-
Fail safe has the same config options, and perhaps your ORM's maven plugin
needs an enhancement ;-)
On Sunday, 24 February 2013, Matthew Adams wrote:
> Good suggestion, but I need it for not just that (and besides, you should
> be using failsafe for integration tests, not surefire). But also I n
Hello,
I am trying to fix https://jira.codehaus.org/browse/MOJO-1534 need
advice to how achieve the solution mentioned in to topic.
Very much appreciated.
Thanks
-D
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
18 matches
Mail list logo
