Hi,
My question is similar to this one:
http://mail-archives.apache.org/mod_mbox/maven-users/200512.mbox/browser
but for maven 2.0.9 - 2.2.1.
I have two projects A and B. B is dependent upon A. A produces
A-1.0-SNAPSHOT.jar.
When a change is introduced into A and the new snapshot is
I'm currently working with the book Better Builds with Maven and doing
some custom maven plugin development. I have a plugin I've created with the
following POM info.
groupIdcom.exist.mvnbook.plugins/groupId
artifactIdmaven-buildinfo-plugin/artifactId
packagingmaven-plugin/packaging
You know
2009/9/25 Daniel Bell daniel.b...@nec.com.au
Hi,
My question is similar to this one:
http://mail-archives.apache.org/mod_mbox/maven-users/200512.mbox/browser
but for maven 2.0.9 - 2.2.1.
I have two projects A and B. B is dependent upon A. A produces
A-1.0-SNAPSHOT.jar.
When a change
The way I know of is through the pluginGroups element of settings.xml.
/Anders
On Fri, Sep 25, 2009 at 03:12, Tristan Rouse tjcro...@gmail.com wrote:
I'm currently working with the book Better Builds with Maven and doing
some custom maven plugin development. I have a plugin I've created with
On Fri, 25 Sep 2009 11:37:40 +1000
Brett Porter br...@apache.org wrote:
Would you mind submitting these to JIRA?
http://jira.codehaus.org/browse/MDOAP
If you can attach patches to correct them they can be applied and
released relatively easily.
- Brett
Hey,
I did not find any
Hi Brett,
Yes, Resource1.xsd is part of Proj1. And there is a dependency between Proj3
and Proj1.
Maybe i should explain it differently:
I need to run wsdl2java (i use the cxf plugin for that) which needs the
Resource1.xsd to be able to run correctly. Additionally some namespaces have to
The Maven team is pleased to announce the release of the Maven Invoker,
version 2.0.11.
This component allows to programmatically invoke Maven. See the
component's site for more details:
http://maven.apache.org/shared/maven-invoker/
To use this component in your projects, add the
Hi,
I am using the release plugin with CVS. Is there a way to remove the CVS user
name and password from the pom.xml? I am setting up a maven project for 20+
developers and it would be bad if every one of them needs to keep a modified
pom.xml in their machine with their user name. I tried the
The Maven team is pleased to announce the release of the Maven Invoker
Plugin, version 1.4.
This plugin allows to run Maven on a collection of projects and is
especially useful for integration testing of other Maven plugins. See
the plugin's site for more details:
That was my first idea. And I couldn't find a way to do it. All I find are
discussions on how people want not to have this in their settings.xml but in an
external properties file. How to put arbitrary properties in the settings.xml
remains a mistery to me.
Anders Hammar wrote:
Why not have
Hmm, I pretty sure I've seen an example of this somewhere. I'll have a
look
/A
On Fri, Sep 25, 2009 at 11:06, Todor Boev t.b...@prosyst.bg wrote:
That was my first idea. And I couldn't find a way to do it. All I find are
discussions on how people want not to have this in their
Ok. I think I found the example, and it uses environment properties. Should
work.
Or, define a profile in your settings.xml that defines these properties. The
benefit of this approach is that they can easily be defined (or overridden)
through the command line as well.
/Anders
On Fri, Sep 25,
THis is my project structure:
parent
client
server
src
main
java
cn
wps
01.java
02.java
resources
cn
Why not have two pre-define properties for this, which everyone needs to set
up in their settings.xml?
/Anders
On Fri, Sep 25, 2009 at 10:48, Todor Boev t.b...@prosyst.bg wrote:
Hi,
I am using the release plugin with CVS. Is there a way to remove the CVS
user name and password from the
The Maven team is pleased to announce the release of the Maven Invoker
Plugin, version 1.4.
This plugin allows to run Maven on a collection of projects and is
especially useful for integration testing of other Maven plugins. See
the plugin's site for more details:
Yup. This worked. Thanks :)
Anders Hammar wrote:
Ok. I think I found the example, and it uses environment properties. Should
work.
Or, define a profile in your settings.xml that defines these properties. The
benefit of this approach is that they can easily be defined (or overridden)
through the
I tried using Mvn 2.2.1 and got the same error from the wagon plugin:
[INFO] [site:deploy {execution: default-deploy}]
WAGON_VERSION: 1.0-beta-2
http://ci1.xxx/test - Session: Opened
Uploading: ./css/maven-base.css to http://ci1.xxx/test
# Transfer error:
2009/9/25 David Hoffer dhoff...@gmail.com:
Hum,
Can you restate/finish the last point 'better still is to switch reporting
plugins to report, and not to do, and use the build lifecycle for doing'?
At the moment, reporting plugins do stuff rather than just generate a
report of stuff that has
Also if you have the plugin configured in your pom (even in
pluginManagement) and the goalPrefix
(http://maven.apache.org/plugins/maven-plugin-plugin/descriptor-mojo.html#goalPrefix)
was correctly configured or auto-detected for your plugin, then you
can just use goalPrefix:goal when running maven
Hi,
I have created a small Maven plugin which uses the Eclipse code formatter to
format my code.
I would like to release it but the available librairies of Eclipse are quite
old and I don't want my users to have Eclipse installed (that's the whole
point of the plugin). Is there a repository with
Can you post the output of mvn help:effective-pom at parent level?
With regards,
Nick Stolwijk
~Java Developer~
IPROFS BV.
Claus Sluterweg 125
2012 WS Haarlem
http://www.iprofs.nl
On Fri, Sep 25, 2009 at 11:25 AM, maven apache apachemav...@gmail.com wrote:
THis is my project structure:
Yes I did and I am still getting the same error. Any ideas what I could do?
Anders Hammar wrote:
Did you have a look at the doc link I provided?
/Anders
On Sat, Sep 19, 2009 at 23:31, nnocerino
nicandro.nocer...@cigna.comwrote:
Anders
I tried v2.1.2 and after downloading all
Paste your pom snippet here would allow us to check it.
/A
On Fri, Sep 25, 2009 at 14:18, nnocerino nicandro.nocer...@cigna.comwrote:
Yes I did and I am still getting the same error. Any ideas what I could
do?
Anders Hammar wrote:
Did you have a look at the doc link I provided?
Thanks for the explanation that makes sense. I'm surprised maven reporting
is designed so poorly, I agree your approach in the invoker makes more
sense.
BTW, when you say 'fork a build', is this done in the current VM? Is there
a way to force all these in separate VMs?
The problem we have is
Hi,
Since maven 2.1.0, I use in a mojo the
org.sonatype.plexus.components.sec.dispatcher.SecDispatcher
from the artifact org.sonatype.plexus:plexus-sec-dispatcher:1.3.1
to decrypt password in my settings.xml
I recently change to maven 2.2.1, but my mojo does not anylonger works fine
(same
We just need a high-quality POM, correct metadata, javadocs, sources,
and signatures.
It is debatable is what you mean on high quality.
For me (totally a Maven fan!) what makes the POM high quality?
Its ability to build the project!
I don't really care if it is full of maven-antrun-plugin, but
As I was pasting the snippet of code, I noticed where the issue was, I had
placed the dependency under the wrong plugin. Problem when you multitask!
Well thanks for all your help and support, I am sure I will be asking other
questions.
Nick
Anders Hammar wrote:
Paste your pom snippet
It looks like your server pom file configures the compiler plugin:
plugin
artifactIdmaven-compiler-plugin/artifactId
version2.0.2/version
configuration
includes
includeorg/n52/wps/server/**/include
2009/9/25 Nick Stolwijk nick.stolw...@gmail.com
It looks like your server pom file configures the compiler plugin:
plugin
artifactIdmaven-compiler-plugin/artifactId
version2.0.2/version
configuration
includes
2009/9/25 maven apache apachemav...@gmail.com
2009/9/25 Nick Stolwijk nick.stolw...@gmail.com
It looks like your server pom file configures the compiler plugin:
plugin
artifactIdmaven-compiler-plugin/artifactId
version2.0.2/version
configuration
Dear all,
I have been browsing the Maven Book online recently (available on
http://www.sonatype.com/books/maven-book/reference/public-book.html),
and I have found something interesting about the profiles used in Maven
in one example:
Could it be that you IDE already put those classes in target/classes?
The jar packaging just takes everything under target/classes and put
that into a jar file.
And why did you configure the compiler plugin with includes. Normally
you would just want to compile everything under src/main/java.
Just a couple more ideas/questions.
Currently we specify our reports at the top level only. Is there a way to
exclude some reports on child modules? Or should we be specifying our
reports at each child module level where we need the report and not at the
top level? I.e. what's the best way to
2009/9/25 Nick Stolwijk nick.stolw...@gmail.com
Could it be that you IDE already put those classes in target/classes?
The jar packaging just takes everything under target/classes and put
that into a jar file.
Maybe.
And why did you configure the compiler plugin with includes. Normally
you
Any suggestions anyone? This is only happening when building via Hudson
and multiple executors running at once.
-Original Message-
From: EJ Ciramella [mailto:ecirame...@upromise.com]
Sent: Thursday, September 24, 2009 4:57 PM
To: users@maven.apache.org
Subject: RE: Random can't find
I think this issue is related:
https://issues.sonatype.org/browse/MVNDEF-261
On Fri, Sep 25, 2009 at 9:58 PM, Reynald Borer reynald.bo...@elca.chwrote:
Dear all,
I have been browsing the Maven Book online recently (available on
Hello,
I have a multimodules project (ProjectParent) with each module has a super
pom's parent .
See the figure:
http://www.nabble.com/file/p25614127/Screen03.jpg
(red : parent, blue : module)
My problem is very simple. I can't manage the version of my modules from my
multimodules
I am trying to convert a project to Maven and it is going reasonably well.
However the project uses Pellet (http://clarkparsia.com/pellet). And no
resent version of Pellet is available in any mvn repository I can find, so I
will need to build one my self.
I was wondering if there are any tools or
Hi,
i want to use the maven plugin appc to compile my .ear files in our
project. I use Bea Weblogic 10.0 as Webserver and Apache Maven in the
version 2.1.0 as configuration tool. Java is used in version 1.5.0_20.
The pom.xml where the plugin is mapped looks like:
.
Hi All,
I was just wondering about the following situation
I'm using maven 2.2.1 which requires jdk 1.5 to run, but my modules will
compile only with 1.4, so i used the 1.4 executable in my compiler plugin.
In this case if i create profile with the activation rule for jdk1.4/jdk
when this
If you don't need the report on every module I would only specify the
report on the modules that require it.
In this respect the reporting section is badly let down by the lack
of a pluginManagement section... but that would require a schema
change... and I am not sure I see that happening any
For me,
High quality is that:
/project/(?parent/)(groupId|artifactId|version) are valid and do not
reference properties
/project/dependencies is valid and if there are any properties defined
they are defined within the pom or it's parents
/project/name
/project/description
/project/url
Bonus
The pure Maven repo should say:
We honestly don't care which Maven plugin the people build with, as
long as that plugin is already checked into here.
And why people would prefer to use libraries from the pure Maven repo?
Quality.
Being build-able has always been the target of OSS developments.
2009/9/25 Albert Kurucz albert.kur...@gmail.com:
The pure Maven repo should say:
We honestly don't care which Maven plugin the people build with, as
long as that plugin is already checked into here.
And why people would prefer to use libraries from the pure Maven repo?
Quality.
Being
Le vendredi 25 septembre 2009, Stephen Connolly a écrit :
For me,
High quality is that:
/project/(?parent/)(groupId|artifactId|version) are valid and do not
reference properties
/project/dependencies is valid and if there are any properties defined
they are defined within the pom or it's
Le vendredi 25 septembre 2009, Stephen Connolly a écrit :
2009/9/25 Albert Kurucz albert.kur...@gmail.com:
The pure Maven repo should say:
We honestly don't care which Maven plugin the people build with, as
long as that plugin is already checked into here.
And why people would prefer to
On Fri September 25 2009 12:07:09 pm Stephen Connolly wrote:
For me,
High quality is that:
/project/(?parent/)(groupId|artifactId|version) are valid and do not
reference properties
/project/dependencies is valid and if there are any properties defined
they are defined within the pom or
2009/9/25 Hervé BOUTEMY herve.bout...@free.fr:
Le vendredi 25 septembre 2009, Stephen Connolly a écrit :
For me,
High quality is that:
/project/(?parent/)(groupId|artifactId|version) are valid and do not
reference properties
/project/dependencies is valid and if there are any properties
2009/9/25 Hervé BOUTEMY herve.bout...@free.fr:
Le vendredi 25 septembre 2009, Stephen Connolly a écrit :
2009/9/25 Albert Kurucz albert.kur...@gmail.com:
The pure Maven repo should say:
We honestly don't care which Maven plugin the people build with, as
long as that plugin is already
Le Fri, 25 Sep 2009 15:17:04 +0200,
Tony Chemit che...@codelutin.com a écrit :
Hi,
Since maven 2.1.0, I use in a mojo the
org.sonatype.plexus.components.sec.dispatcher.SecDispatcher
from the artifact org.sonatype.plexus:plexus-sec-dispatcher:1.3.1
to decrypt password in my
there are some jars already there from an attempt long time ago to
have eclipse in the repository, under org.eclipse
On Fri, Sep 25, 2009 at 2:00 AM, Emmanuel Hugonnet ehsavoi...@gmail.com wrote:
Hi,
I have created a small Maven plugin which uses the Eclipse code formatter to
format my code.
Brian Fox-3 wrote:
In theory this would be possible, but the paths probably need to be
rooted in the same location.
I think it can not be a path problem.
When I change the url of the distributionManagement to
file:///home/thomas/test-repo
It all works. The maven-metadata is created.
Technically it is possible to manage 3 different OSS Maven repos.
1. The good enough
This is the current Maven Central
No rules, only recommendations:
http://maven.apache.org/guides/mini/guide-central-repository-upload.html
Note: it is not a rule what is not enforced!
2. The good
This would be
Hi Jan,
Jan wrote:
Hi All,
I was just wondering about the following situation
I'm using maven 2.2.1 which requires jdk 1.5 to run, but my modules will
compile only with 1.4, so i used the 1.4 executable in my compiler plugin.
In this case if i create profile with the activation rule
When performing [clean] install on multi-module projects, where is maven
supposed to look for (child) dependencies? Does it look in target/classes
or does it look at the jar previously installed in the local repo?
We have two systems where one seems to be looking in the local repo for all
On Fri, Sep 25, 2009 at 12:44 PM, Albert Kurucz albert.kur...@gmail.com wrote:
Technically it is possible to manage 3 different OSS Maven repos.
1. The good enough
This is the current Maven Central
No rules, only recommendations:
For the additional requirement, getting into the pure Maven repo (The
best), I really meant: build-able.
Me too, I don't really care what tool you use to build it as long as
the tool is already checked in and you only use the attached metadata
and the attached sources.
But a tool like this, in
57 matches
Mail list logo
