fer-maven-plugin on CLI without updating pom.xml
> > >
> > > the only issue I'm facing is how to write the -D properties to
> populate a
> > > few fields from Objects required in plugin configuration:
> > >
> > > - signature groupId/artifactId/vers
1, Hervé Boutemy wrote:
> >
> > my use case: I want sometimes to execute maven-toolchain-plugin or animal-
> > sniffer-maven-plugin on CLI without updating pom.xml
> >
> > the only issue I'm facing is how to write the -D properties to populate a
> > few f
rvé Boutemy wrote:
>
> my use case: I want sometimes to execute maven-toolchain-plugin or animal-
> sniffer-maven-plugin on CLI without updating pom.xml
>
> the only issue I'm facing is how to write the -D properties to populate a few
> fields from Objects requir
my use case: I want sometimes to execute maven-toolchain-plugin or animal-
sniffer-maven-plugin on CLI without updating pom.xml
the only issue I'm facing is how to write the -D properties to populate a few
fields from Objects required in plugin configuration:
- signature groupId/artif
Hello,
Currently one can use
@org.apache.maven.plugins.annotations.Parameter
private LinkedHashMap keyValues = new LinkedHashMap<>();
to read a plugin configuration that looks like
value1
value2
My question is if it is possible to somehow read a configuratio
merged to master
thank you
Hervé
Le dimanche 19 mars 2017, 16:35:14 CET Stephen Connolly a écrit :
> +1
>
> On Sun 19 Mar 2017 at 16:21, Hervé BOUTEMY wrote:
> > see https://issues.apache.org/jira/browse/MNG-6189 for more details on the
> > logic behind this warning.
> >
> > It's only a warni
+1
On Sun 19 Mar 2017 at 16:21, Hervé BOUTEMY wrote:
> see https://issues.apache.org/jira/browse/MNG-6189 for more details on the
> logic behind this warning.
>
> It's only a warning, and there is an IT to check the result
>
> I think it is safe and will help us continue cleaning users poms for
see https://issues.apache.org/jira/browse/MNG-6189 for more details on the
logic behind this warning.
It's only a warning, and there is an IT to check the result
I think it is safe and will help us continue cleaning users poms for people
lost in stopped migration from to
In addition, this wi
approach to get this configuration is to read the pom using injected
> > MavenProject and get an Xpp3Dom [1]. This approach is very hacky since we
> > have to manually take care of all possible ways to configure a plugin:
> > - configuration can be in build/plugins or in build/plug
Xpp3Dom [1]. This approach is very hacky since we
> > have to manually take care of all possible ways to configure a plugin:
> > - configuration can be in build/plugins or in build/pluginsManagement
> or
> > even in reporting section
> > - I'm not sure we are s
e to manually take care of all possible ways to configure a plugin:
> - configuration can be in build/plugins or in build/pluginsManagement or
> even in reporting section
> - I'm not sure we are supporting configuration "per execution"
> - we are not supporti
configuration is to read the pom using injected
MavenProject and get an Xpp3Dom [1]. This approach is very hacky since we have
to manually take care of all possible ways to configure a plugin:
- configuration can be in build/plugins or in build/pluginsManagement or even
in reporting section
- I&#
When you don't specify the value in the POM you are *effectively*[1]
specifying ${demoName}
So what you have done is disabled configuration via the CLI.
[1] I say *effectively* because if you did configure that and the property
was undefined then that explicit configuration would evaluate to the
Github user ctrueden closed the pull request at:
https://github.com/apache/maven-plugins/pull/52
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
GitHub user ctrueden opened a pull request:
https://github.com/apache/maven-plugins/pull/52
Move plugin configuration outside executions
As described by Ron Wheeler at:
http://mail-archives.apache.org/mod_mbox/maven-users/201505.mbox/%3C554C33D1.3000502%40artifact-software.com
Thank You @Stuart McCulloch (and others that helped me in this topic)! Your
explanation is very valuable and resolved my problems :)
Regards,
animator.
--
View this message in context:
http://maven.40175.n5.nabble.com/Problem-while-getting-injected-parameters-from-plugin-configuration
75.n5.nabble.com/Problem-while-getting-injected-parameters-from-plugin-configuration-tp5805894p5806136.html
> Sent from the Maven Developers mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: dev-unsubscr..
o
arg constructor and @Requirement annotation but still I get the same
exceptions.
Thanks for answers.
--
View this message in context:
http://maven.40175.n5.nabble.com/Problem-while-getting-injected-parameters-from-plugin-configuration-tp5805894p5806136.html
Sent from the Maven Developers mailing
-parameters-from-plugin-configuration-tp5805894p5806136.html
Sent from the Maven Developers mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h
7e0a4ed748bc54
>
>
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Problem-while-getting-injected-parameters-from-plugin-configuration-tp5805894p5805996.html
> Sent from the Maven Developers mailing list archive at Nabble.com.
>
>
a
*2
https://github.com/lgadawski/cloverage-maven-plugin/commit/0f99966fbb965be8c4d79845617e0a4ed748bc54
--
View this message in context:
http://maven.40175.n5.nabble.com/Problem-while-getting-injected-parameters-from-plugin-configuration-tp5805894p5805996.html
Sent from the Maven Developers mailing list
a/com/gadawski/maven/plugins/cloverage/goals/InstrumentMojo.java I
> >> declared there 4 parameter, those declared with property attirubutes
> >> work fine, but those without, that reffers to configuration don't.
> >>
> >>
> >>
> >> --
&
gins/cloverage/goals/InstrumentMojo.java I declared
there 4 parameter, those declared with property attirubutes work fine, but
those without, that reffers to configuration don't.
--
View this message in context:
http://maven.40175.n5.nabble.com/Problem-while-getting-injected-parameters->
onfiguration don't.
>
>
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Problem-while-getting-injected-parameters->
> from-plugin-configuration-tp5805894p5805910.html Sent from the Maven
> Developers mailing list archive at Nabble.com.
&g
/InstrumentMojo.java
I declared there 4 parameter, those declared with property attirubutes work
fine, but those without, that reffers to configuration don't.
--
View this message in context:
http://maven.40175.n5.nabble.com/Problem-while-getting-injected-parameters-from-plugin-configuration-tp5805894p58
I use Java 7,
Maven 3.1. I have a problem with getting injected parameters from plugin
configuration. In Mojo class I've field like:
@Parameter
private String srcDirClj;
and in different project that I want to execute on this plugin I have
following con
Hi,
I'm developing custom reporting plugin for my own needs. I use Java 7,
Maven 3.1. I have a problem with getting injected parameters from plugin
configuration. In Mojo class I've field like:
@Parameter
private String srcDirClj;
and in different project that I want to execu
Hi,
i'm working on a maven-plugin
(https://github.com/khmarbaise/maven-iterator-invoker-plugin/blob/master/src/main/java/com/soebes/maven/plugins/IteratorInvokerMojo.java)
which gets a configuration snippet from the following (from an
integration test):
com.soebes.maven.plugins
rom: Hervé BOUTEMY
> To: Maven Developers List
> Cc:
> Sent: Sunday, November 18, 2012 11:14 AM
> Subject: Re: Preserve whitespace in Maven plugin configuration?
>
> fair enough: I'll have to do the work :/
> at least I'm now convinced it is useful :)
>
> I
> > From: Olivier Lamy
> > To: Maven Developers List
> > Cc:
> > Sent: Sunday, November 18, 2012 9:10 AM
> > Subject: Re: Preserve whitespace in Maven plugin configuration?
> >
> > 2012/11/18 Hervé BOUTEMY :
> >> I just implemented MODELLO-256,
xml:space="preserve" is found?
> >
> > WDYT?
>
> +1 for xml:space="preserve".
> Using real norm sounds good for me.
so, you like the complex scenario :(
(which is, yes, exciting since we're at least using a standard attribute)
the basic scenario where whi
strub
- Original Message -
> From: Olivier Lamy
> To: Maven Developers List
> Cc:
> Sent: Sunday, November 18, 2012 9:10 AM
> Subject: Re: Preserve whitespace in Maven plugin configuration?
>
> 2012/11/18 Hervé BOUTEMY :
>> I just implemented MODELLO-25
2012/11/18 Hervé BOUTEMY :
> I just implemented MODELLO-256, which will permit to preserve whitespace in
> Maven plugins configuration: see MNG-5380 [1].
>
> The question is: should we change the overall behaviour (plugins can trim when
> they need, and usually, there is no extra space in plugin co
I just implemented MODELLO-256, which will permit to preserve whitespace in
Maven plugins configuration: see MNG-5380 [1].
The question is: should we change the overall behaviour (plugins can trim when
they need, and usually, there is no extra space in plugin configurations so
nothing will brea
I'm writing a plugin with rather complex configuration, and I haven't
found any documentation on how to get annotations looked at in custom
classes representing parts of the configuration. Maven (actually
Plexus, I suppose, under the covers) is finding my classes and
injecting values, but doesn't
The ability to run multiple providers within a single execution is a
fairly new feature, and
I'm not surprised that works as expected.
There are hundreds of blog posts out there that explain how to run
testng/junit using multiple executions of surefire,
which was the best available method at the t
Tue, 2 Aug 2011 10:57:16 -0600
> Subject: Re: Maven 2/3 and Cobetura plugin with both TestNG and JUnit tests
> (with Surefire plugin configuration)
> From: lar...@gmail.com
> To: dev@maven.apache.org
>
> On Mon, Aug 1, 2011 at 9:56 AM, Larry Shatzer, Jr. wrote:
> > I want to
One last update. If I remove the sections that tell
Surefire to run both TestNG and Junit, and put dependencies on the
Surefire Plugin like so:
org.apache.maven.surefire
surefire-junit4
${surefire.version}
o
On Mon, Aug 1, 2011 at 9:56 AM, Larry Shatzer, Jr. wrote:
> I want to run with both JUnit and TestNG. By removing JUnit (and the
> tests that JUnit run), it ran just fine, as do the inverse, just JUnit
> and no TestNG. It is the combination of both of them.
>
> To help, instead of having gists, I
On Thu, Jul 28, 2011 at 6:04 AM, Martin Gainty wrote:
>
> Larry-
>
> try loading both dependencies in your local repository and running offline
> with mvn -o (at least your dependencies will be found)
>
> did you check cobertura for errors?
>
> mvn -e -X cobertura:cobertura -Dquiet=true
I did no
gin with both TestNG and JUnit tests (with
> Surefire plugin configuration)
> From: lar...@gmail.com
> To: dev@maven.apache.org
>
> I did send this to the users list, but got no response in over a week.
> I know dev lists are not a magical escalation path, but this might be
>
sts to run.
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
So it appears to try to run both tests, but fails to actually run any
tests, and gets 0% coverage.
It appears there is something odd between Maven 2.2.1 and Maven 3.0.3
when the cobertura plugin runs, and its reading of
Thanks for pointing me in the right direction. 10-RC2 doesn't fix it, but
this patch on the head of
http://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.x
does:
Index: maven-project/src/main/java/org/apache/maven/project/ModelUtils.java
The users list is the right place... give it a bit more time, it
hasn't even been 24 hours yet. :)
You can also search JIRA to see if this problem has already been
reported. Is this it? http://jira.codehaus.org/browse/MNG-1999
(Reporting inheritance does not work properly)
If so, it's marked fi
s up. If it is, please let me
know where to go.
Thanks so much,
--Nik
-- Forwarded message --
From: Nikolas Everett <[EMAIL PROTECTED]>
Date: Thu, Oct 30, 2008 at 12:49 PM
Subject: Reporting plugin configuration no inheriting
To: [EMAIL PROTECTED]
I'm trying
and configure the compiler accordingly. I am
able to access the UEI from my Mojo, but I do not know how to access the
compiler plugin configuration programmatically. I think I need the
current container and an evaluator to do this, at least that is how the
test harness configures plugins
I need to configure my plugin like this
...
How can I make this?
Thanks in advance.
--
View this message in context:
http://www.nabble.com/Plugin-configuration-tf1980099.html#a5433174
Sent from the Apache Maven Developers List forum at Nabble.com
Population problem when ${project.organization.name} is used in pom, e.g. in
plugin configuration.
--
Key: MNG-2134
URL: http://jira.codehaus.org/browse/MNG-2134
Project: Maven
[ http://jira.codehaus.org/browse/MNG-1546?page=all ]
John Casey updated MNG-1546:
Fix Version: (was: 2.0.3)
2.0.4
> no way to retrieve/change plugin configuration in the POM or globa
[ http://jira.codehaus.org/browse/MNG-2064?page=all ]
Brett Porter updated MNG-2064:
--
Fix Version: 2.1
> automatic plugin configuration from system properties
> -
>
> Key: MNG-2064
&g
automatic plugin configuration from system properties
-
Key: MNG-2064
URL: http://jira.codehaus.org/browse/MNG-2064
Project: Maven 2
Type: New Feature
Components: Plugins and Lifecycle
Reporter: Brett
[ http://jira.codehaus.org/browse/MPWAR-56?page=all ]
Kris Nuttycombe closed MPWAR-56:
Resolution: Duplicate
Moved this to Maven 2.x War Plugin project.
> [PATCH] Add ability to specify context.xml file in plugin configurat
[PATCH] Add ability to specify context.xml file in plugin configuration
---
Key: MWAR-24
URL: http://jira.codehaus.org/browse/MWAR-24
Project: Maven 2.x War Plugin
Type: New Feature
Versions
Add ability to specify context.xml file in plugin configuration
> ---
>
> Key: MPWAR-57
> URL: http://jira.codehaus.org/browse/MPWAR-57
> Project: maven-war-plugin
> Type: New Feature
[PATCH] Add ability to specify context.xml file in plugin configuration
---
Key: MPWAR-57
URL: http://jira.codehaus.org/browse/MPWAR-57
Project: maven-war-plugin
Type: New Feature
Environment
this.
> [PATCH] Add ability to specify context.xml file in plugin configuration
> ---
>
> Key: MPWAR-56
> URL: http://jira.codehaus.org/browse/MPWAR-56
> Project: maven-war-plugin
>
[PATCH] Add ability to specify context.xml file in plugin configuration
---
Key: MPWAR-56
URL: http://jira.codehaus.org/browse/MPWAR-56
Project: maven-war-plugin
Type: New Feature
Environment
[ http://jira.codehaus.org/browse/MPLUGIN-11?page=all ]
Hervé BOUTEMY updated MPLUGIN-11:
-
Attachment: MPLUGIN-intro2.patch
PluginXdocGenerator.java
> add an introduction to plugin configuration in plugin rep
[ http://jira.codehaus.org/browse/MPLUGIN-11?page=comments#action_56499 ]
Brett Porter commented on MPLUGIN-11:
-
oh, I see. My mistake.
> add an introduction to plugin configuration in plugin rep
revision where this code would have
changed : am I looking at a wrong place ?
> add an introduction to plugin configuration in plugin report
>
>
> Key: MPLUGIN-11
> URL: http://jira.codehaus.org/browse/M
[ http://jira.codehaus.org/browse/MPLUGIN-11?page=comments#action_56418 ]
Brett Porter commented on MPLUGIN-11:
-
Herve, the plugin xdoc generator is no longer used. Look for the report in the
plugin-plugin.
> add an introduction to plugin configurat
[ http://jira.codehaus.org/browse/MNG-1121?page=all ]
John Casey updated MNG-1121:
Fix Version: documentation
> document standard location for plugin configuration files
> -
>
> K
Plugin-configuration editor for POM editor
--
Key: MNGECLIPSE-40
URL: http://jira.codehaus.org/browse/MNGECLIPSE-40
Project: Maven 2.x Plug-in for Eclipse
Type: New Feature
Components: POM Editor
Reporter: Eugene
here, I have problems with multi page reports
(see MPLUGIN-7 comments).
> add an introduction to plugin configuration in plugin report
>
>
> Key: MPLUGIN-11
> URL: http://jira.codehaus.org/br
have the same
content. Can you add this?
> add an introduction to plugin configuration in plugin report
>
>
> Key: MPLUGIN-11
> URL: http://jira.codehaus.org/browse/MPLUGIN-11
> Project: Maven
of configuring this in
2.1).
> Ability to have different plugin configuration per goal
> ---
>
> Key: MJAVADOC-44
> URL: http://jira.codehaus.org/browse/MJAVADOC-44
> Project: Maven 2.x Javadoc Plugin
&
: Improvement)
Key: MJAVADOC-44 (was: MNG-1951)
Project: Maven 2.x Javadoc Plugin (was: Maven 2)
> Ability to have different plugin configuration per goal
> ---
>
> Key: MJAVADOC-44
>
Ability to have different plugin configuration per goal
---
Key: MNG-1951
URL: http://jira.codehaus.org/browse/MNG-1951
Project: Maven 2
Type: Improvement
Components: Plugins and Lifecycle
Versions: 2.0.1
[ http://jira.codehaus.org/browse/MNG-1941?page=all ]
Jason van Zyl updated MNG-1941:
---
Fix Version: (was: 2.0.2)
> add an introduction to plugin configuration (patch inclu
add an introduction to plugin configuration (patch included)
Key: MNG-1941
URL: http://jira.codehaus.org/browse/MNG-1941
Project: Maven 2
Type: Improvement
Components: Plugin Creation Tools
[ http://jira.codehaus.org/browse/MPLUGIN-11?page=all ]
Hervé BOUTEMY updated MPLUGIN-11:
-
Attachment: plugin-info.html
> add an introduction to plugin configuration in plugin rep
add an introduction to plugin configuration in plugin report
Key: MPLUGIN-11
URL: http://jira.codehaus.org/browse/MPLUGIN-11
Project: Maven 2.x Plugin Plugin
Type: Improvement
Reporter: Hervé BOUTEMY
t-ejb
name-without-version.ejb3
notice the ejbModule -> ejb3Module
> Plugin configuration doesn't support .ejb3 and .par EJB modules
> ---
>
> Key: ME
ely I could not find how the modules are initialized if
the element is present in the pom file.
> Plugin configuration doesn't support .ejb3 and .par EJB modules
> ---
>
> Key: MEAR-1
> URL: http://jira.cod
[ http://jira.codehaus.org/browse/MEAR-1?page=all ]
Stephane Nicoll closed MEAR-1:
--
Resolution: Fixed
Fix Version: 2.1
> Plugin configuration doesn't support .ejb3 and .par EJB
[ http://jira.codehaus.org/browse/MEAR-1?page=all ]
Stephane Nicoll reopened MEAR-1:
> Plugin configuration doesn't support .ejb3 and .par EJB modules
> ---
>
>
: jira (was: Maven)
Key: MECLIPSE-41 (was: MNG-956)
Project: Maven 2.x Eclipse Plugin (was: Maven 2)
> There sould be possible to add additional classpath entry in plugin
> configu
)
Key: MEAR-1 (was: MNG-1723)
Project: Maven 2.x Ear Plugin (was: Maven 2)
> Plugin configuration doesn't support .ejb3 and .par EJB modules
> ---
>
> Key: MEAR-1
> URL: http://jira.codeha
[ http://jira.codehaus.org/browse/MNG-1723?page=all ]
Stephane Nicoll closed MNG-1723:
Resolution: Fixed
Fix Version: 2.0.1
Got access to SVN finally. Applied and fixed.
> Plugin configuration doesn't support .ejb3 and .par EJB
[ http://jira.codehaus.org/browse/MNG-1723?page=all ]
Stephane Nicoll updated MNG-1723:
-
Attachment: MNG-1723.patch
Patch. John, could you please apply it, I have issue with SVN on my local box.
> Plugin configuration doesn't support .ejb3 and
[ http://jira.codehaus.org/browse/MNG-1723?page=all ]
Stephane Nicoll updated MNG-1723:
-
Version: 2.0
Component: maven-ear-plugin
> Plugin configuration doesn't support .ejb3 and .par EJB
-plugin)
> Plugin configuration doesn't support .ejb3 and .par EJB modules
> ---
>
> Key: MNG-1723
> URL: http://jira.codehaus.org/browse/MNG-1723
> Project: Maven 2
> Type: Bug
&
Plugin configuration doesn't support .ejb3 and .par EJB modules
---
Key: MPEAR-43
URL: http://jira.codehaus.org/browse/MPEAR-43
Project: maven-ear-plugin
Type: Bug
Reporter: Tim Kettler
Pri
[ http://jira.codehaus.org/browse/MNG-1546?page=all ]
John Casey updated MNG-1546:
Priority: Major (was: Critical)
Version: 2.0
Fix Version: (was: 2.0.1)
2.0.2
> no way to retrieve/change plugin configuration in the
[ http://jira.codehaus.org/browse/MNG-1546?page=all ]
John Casey updated MNG-1546:
Fix Version: 2.0.1
May not be able to handle the second use case until we have explicit export
parameters for mojos implemented.
> no way to retrieve/change plu
no way to retrieve/change plugin configuration in the POM or globally
-
Key: MNG-1546
URL: http://jira.codehaus.org/browse/MNG-1546
Project: Maven 2
Type: Bug
Components: maven-embedder
[ http://jira.codehaus.org/browse/MNG-1121?page=comments#action_49451 ]
Brett Porter commented on MNG-1121:
---
you need to paste the whole URL instead of clicking the link...
> document standard location for plugin configuration fi
[ http://jira.codehaus.org/browse/MNG-1121?page=comments#action_49341 ]
Jason van Zyl commented on MNG-1121:
Neither of those links work. What was the gist of theissue?
> document standard location for plugin configuration fi
document standard location for plugin configuration files
-
Key: MNG-1121
URL: http://jira.codehaus.org/browse/MNG-1121
Project: Maven 2
Type: Task
Components: documentation
Reporter: Brett Porter
[ http://jira.codehaus.org/browse/MNG-956?page=all ]
Brett Porter closed MNG-956:
Resolution: Fixed
> There sould be possible to add additional classpath entry in plugin
> configu
ssues:
...
...
> There sould be possible to add additional classpath entry in plugin
> configuration
> -
>
> Key: MNG-956
> URL: http://jira.codehaus.org/browse/MNG-956
[ http://jira.codehaus.org/browse/MNG-956?page=all ]
Brett Porter updated MNG-956:
-
Remaining Estimate: 2 hours
Original Estimate: 7200
> There sould be possible to add additional classpath entry in plugin
> configu
[ http://jira.codehaus.org/browse/MNG-1033?page=all ]
John Casey closed MNG-1033:
---
Resolution: Fixed
> plugin configuration errors are only shown with -X
> --
>
> Key: MNG-1033
>
(incomplete), which can also be used to create a documentation page on the
website.
also, fixed the problem with triggering the plugin configuration diagnoser.
Finally, added it1016 to express a couple of the more tricky plugin param
scenarios.
> plugin configuration errors are only shown with
gered in these
cases, and maybe improve the error diagnoser to catch plexus-level
plugin-parameter errors.
> plugin configuration errors are only shown with -X
> --
>
> Key: MNG-1033
> URL: http://jira.codehaus
plugin configuration errors are only shown with -X
--
Key: MNG-1033
URL: http://jira.codehaus.org/browse/MNG-1033
Project: Maven 2
Type: Bug
Components: maven-core
Reporter: Brett Porter
Fix For: 2.0-beta-3
[ http://jira.codehaus.org/browse/MNG-956?page=all ]
Brett Porter updated MNG-956:
-
Fix Version: 2.0-beta-3
> There sould be possible to add additional classpath entry in plugin
> configu
[ http://jira.codehaus.org/browse/MNG-781?page=all ]
John Casey closed MNG-781:
--
Resolution: Fixed
marking as "Fixed" since it looks like kenney fixed the problem.
> Plugin configuration reset to null when configuration specifi
on of simply verifying the fix.
> Plugin configuration reset to null when configuration specified in
> tag
> --
>
> Key: MNG-781
> URL: http://jira.codehaus.org/browse/MNG-781
[ http://jira.codehaus.org/browse/MNG-781?page=all ]
John Casey updated MNG-781:
---
Remaining Estimate: 3 hours
Original Estimate: 10800
> Plugin configuration reset to null when configuration specified in
>
1 - 100 of 133 matches
Mail list logo
