But using the option -X doesn't tell me to move the dependency/ into the
plugin/ section, right? :-/
--- Wayne Fay wayne...@gmail.com schrieb am Do, 8.9.2011:
Von: Wayne Fay wayne...@gmail.com
Betreff: Re: Get java.lang.NoClassDefFoundError though the class is in the
classpath
An: Maven
Hi Thomas,
I've been following this thread across from the m2e users list.
As you appear to be using Java 7, you had a long list of dependencies in your
pom that are not needed, as they are provided by the JDK (since about 1.6.03 or
thereabouts). So, be sure to get rid of the all of the jax-ws
I everyone,
I am using Maven Ant Tasks to call Maven to compile my code.
When I compile it with Maven directly from command line, it works
perfectly well. My version of Maven is: Apache Maven 3.0.3
(rNON-CANONICAL_2011-06-28_15-20_mockbuild; 2011-06-28 17:20:31+0200)
But when I use Maven Ant
Hello Maven users,
Can prepare-mojo of maven-release-plugin be configured which files
and/or directories to include and/or exclude from the (svn) tag? Just
like with -N submodules can be excluded from the release build, I'd
like to exclude them from the tag as well, or in other words include
only
You are absolutellly right!
The pom.xml is used since a long time from JDK 1.5. I am too lazy to update it.
:-/
--- Stephen Coy st...@resolvesw.com schrieb am Fr, 9.9.2011:
Von: Stephen Coy st...@resolvesw.com
Betreff: Re: Get java.lang.NoClassDefFoundError though the class is in the
no.
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 9 Sep 2011 04:15, Stevo Slavić ssla...@gmail.com wrote:
Hello Maven users,
Can prepare-mojo of maven-release-plugin
Hi Wayne,
thx for claryfing my concept...it's quite what I meant... :-)
Cheers
--
Daniele
On Thu, Sep 8, 2011 at 11:53 PM, Wayne Fay wayne...@gmail.com wrote:
Can you please tell me which tag is that *(for default folder inclusion,
which in turn exists )*
This tag/feature does not
try turning on fork.
2011/9/9 Benoît Thiébault thieba...@artenum.com:
I everyone,
I am using Maven Ant Tasks to call Maven to compile my code.
When I compile it with Maven directly from command line, it works
perfectly well. My version of Maven is: Apache Maven 3.0.3
Thank you for your answer,
I tried that and the compilation worked.
I however have plenty of warnings about invalid pom files (see below).
Should I worry?
[artifact:mvn] [WARNING] POM for
'org.osgi:org.osgi.core:pom:4.3.0:compile' is invalid. It will be
ignored for artifact resolution. Reason:
I started getting this error in a project. So I switched to
mave-site-plugin:3.0, but I still get the error (except it reports the
Plugin Realm for 3.0
Using Maven 2.2.1 I can't find anything consistent .. the error appears to
happen to other people for a variety of reasons. I purged my local
OK, thanks! Just wanted to check if I'm missing something without
going into plugin code.
I'm aware of Maven philosophy and release assumptions (
http://www.sonatype.com/people/2011/01/using-the-maven-release-plugin-things-to-know/
) and it works for me really well. But now I'm practically
Has anyone successfully used release:stage?
I'm assuming that release:stage should be used
after release:prepare, in place of release:perform.
I tried using it like this:
mvn
-DstagingRepository=http://internal-mvn-server.mycompany.net/repositories/o
ur.staging.area release:stage
But maven
Take a look at the output of mvn help:effective-pom and
http://maven.apache.org/pom.html#Distribution_Management
You should use something like mvn
Thank you, Mirko, for your response.
The output from help:effective-pom doesn't include staging.
We don't have repo ids for the staging repository in
any of POMs or settings.xml. I thought that is why
we specify -DstagingRepository on the command line.
Do I need to pre-set the staging repo
AFAIK you overwrite your regular release repository with this.
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/
https://bitbucket.org/mfriedenhagen/
On Fri, Sep 9, 2011 at 21:29, Teruhiko Kurosaka k...@basistech.com wrote:
Thank you, Mirko, for
Suppose I have a plugin parameter like this:
/**
* @parameter *default-value=hoopy* property=disposition
*/
private String disposition;
...and a getter/setter pair like this:
public String getDisposition() {
return this.disposition;
}
public void setDisposition(final String disposition) {
On Fri, Sep 9, 2011 at 6:32 PM, Laird Nelson ljnel...@gmail.com wrote:
I am observing in my plugin tests (based on the
maven-plugin-testing-harnesshttp://maven.apache.org/plugin-testing/maven-plugin-testing-harness/machinery,
using
AIUI, both build/plugins and build/pluginManagement are inherited by
child projects, the difference being that plugiManagement entries are
only used if the child project references the plugin in its
build/plugins section.
That being the case, if a plugin is defined in build/plugins, is there
any
Is it possible to reference Maven properties in APT documents? or
environment variables?
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
http://maven.apache.org/plugins/maven-site-plugin/examples/creating-content.html#Filtering
HTH,
-Lukas
sebb wrote:
Is it possible to reference Maven properties in APT documents? or
environment variables?
-
To unsubscribe,
It all depends on what you want to accomplish.
Configuration in pluginMgmt will be used if you execute the plugin
goal specifically from CLI (like mvn plugin:goal).
So one use case to have move the configuration to the pluginMgmt
section would be if you want to have some config for the build AND
21 matches
Mail list logo
