The Maven team is pleased to announce the release of the Maven Invoker
Plugin, version 1.7
The Invoker Plugin is used to run a set of Maven projects. The plugin
can determine whether each project execution is successful, and
optionally can verify the output generated from a given project
execution
The Maven team is pleased to announce the release of the Maven
Script Interpreter, version 1.1
This component provides some utilities to interpret/execute some
scripts for various implementations: groovy or beanshell.
http://maven.apache.org/shared/maven-script-interpreter/
You should specify th
The Maven team is pleased to announce the release of the Maven
Filtering, version 1.1
These Plexus components have been built from the filtering process/code
in Maven Resources Plugin. The goal is to provide a shared component for
all plugins that needs to filter resources.
http://maven.apache.or
Hi Martin,
Plugin A has several executions defined with different configurations.
Here's an example of such a configuration (from the -part):
aspectJ-weaving-execution
compile
executePlugin
If we ever fix test-jar packaging the optional will make sense ;-)
On Tuesday, 14 August 2012, Laird Nelson wrote:
> One other "I've spent too much time on this" question.
>
> I've been working with Maven for years, so understand it pretty well. But
> this particular combination of options has a
Filed as:
http://jira.codehaus.org/browse/MSITE-648
Ian
On Aug 12, 2012, at 12:39 PM, Ian Brandt wrote:
>
> Greetings,
>
> When I update from 3.0 to 3.1 I get the error below. I've reproduced it on a
> couple projects, but here is a relatively simple POM that manifests the issue
> when u
One other "I've spent too much time on this" question.
I've been working with Maven for years, so understand it pretty well. But
this particular combination of options has always stumped me.
I've read
http://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies
I have spent a fair amount of time trying to parse this message in the
dependency:tree output.
I think that it is trying to tell me that a entry, declared as
part of a stanza somewhere--and thus a description
of constraints that should apply throughout the project for dependencies of
this kind,
On Tue, Aug 14, 2012 at 8:53 AM, Wright, Omari wrote:
> Is this possible? If so, how can I do it?
>
You might be asking:
"I depend on an artifact. It has a properties file in it that gets read or
is otherwise present on the classpath. This interferes with my system. I
would like to continue d
> Is this possible? If so, how can I do it?
Please spell out what you are thinking for those of us who are unable
to interpret what you are asking about.
Wayne
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For add
Richard
"I want plugin A to be executed always and plugin A to decide whether plugin B
(defined in
pluginManagement) should be executed"what criteria are you using to trigger the
execution of plugin B by plugin A?
Martin
__
Verzicht und Vertraulich
Some additional info on the last thread :
Plugin A is defined in the part, plugin B is defined in the
-part.
It appears that injection as specified in the configuration is not properly
executed when the plugin is defined in the pluginManagement part (while this
worked fine in Maven 2).
If I add
Hi All,
Thank you for your response.
I think I need a little bit more help. Maybe you guys can be somewhat more
specific as to which classes I can use as an example.
I have downloaded the sources for both the maven-site-plugin and the
maven-executor-plugin but so far have not found an example of
13 matches
Mail list logo
