Hi Phillip,
Phillip Hellewell wrote:
> I'm thinking about moving all our version management into the parent
> pom in a dependencyManagement section, but I'm trying to figure out if
> it will really make things easier or not.
>
> Of course each version number would only be in one place instead of
On 1 March 2011 05:29, Fuke, Amol wrote:
> Thanks Hilco for the reply.
>
> We are using war plugin also;
>
>
> org.apache.maven.plugins
> maven-war-plugin
>
> conf/
> Are there any specific tags or properties that would tell maven to convert
> from
> one file type to another when moving it to the local repository?
Nothing that I can think of off the top of my head. You should just
look at the effective-pom output and, if you can't figure out where
its coming
Are there any specific tags or properties that would tell maven to convert from
one file type to another when moving it to the local repository?
jf
-Original Message-
From: Wayne Fay [mailto:wayne...@gmail.com]
Sent: Monday, February 28, 2011 9:00 PM
To: Maven Users List
Subject: Re: wh
Well, I figured out the problem. My code was using System.exit(n>0) which
killed the surefire plugin, because this termination method is apparently is
too much for testFailureIgnore>true.
Please close the issue.
From: Morgovsky, Alexander (US - Glen Mills)
Sent: Monday, February 28, 2011 2:21
The simple answer is you can't.
This is because you are deleting a file but those remaining files have not
been modified.
It is always a good idea to have a clean build once you delete a source
file.
So that obsolete class is not polluted you build.
On Tue, Mar 1, 2011 at 11:15 AM, jy hu wrote:
Hi everyone,
I met a problem in maven. for example , there is a project including 7 java
files. I will gain 7 class files after executing the Mvn compile in cmd. and
then I deleted or removed a java file of all, the rest 6 java files had
not been changed in the project. I executed Mvn compile agai
> I've got a weird one on a project that I've inherited that I can't come
> up with the correct search terms to find out there. When copying the
> created jar files to my local repository, 1 gets converted to a zip file
> and I can't figure out where something like this is even configured.
Check
I've got a weird one on a project that I've inherited that I can't come
up with the correct search terms to find out there. When copying the
created jar files to my local repository, 1 gets converted to a zip file
and I can't figure out where something like this is even configured.
Here's the outp
On Mon, Feb 28, 2011 at 8:07 AM, Marc Rohlfs wrote:
>> I would guess that this is the expected behavior, as otherwise it would
>> not be possible to remove reports defined in the parent. You will have
>> to add all the reports again if you want them to run in this module.
>
> No, it's a bug. Inher
Maven 3.0.2, maven-site-plugin 3.0-beta-3.
We've solved it by removing one entry in entries, bit
mysterious. So the exception is not available anymore. Anyway, I could try
to recreate it tomorrow.
Best,
Jakub
--
View this message in context:
http://maven.40175.n5.nabble.com/Require-site-descr
On 28/02/2011 2:39 PM, Phillip Hellewell wrote:
Interesting ideas, thanks. By "aggregation jars" I assume you mean
like intermediate components with no actual code but that serve to
manage versions. I think that is a neat idea.
As much I Iove being associated with a neat idea, I have to point o
Interesting ideas, thanks. By "aggregation jars" I assume you mean
like intermediate components with no actual code but that serve to
manage versions. I think that is a neat idea.
Phillip
On Mon, Feb 28, 2011 at 10:23 AM, Ron Wheeler
wrote:
> Our move to aggregation jars was our solution of th
Hi
Please specify which versions of Maven and Site Plugin you are using.
Also give us the full error message that you get.
On 2011-02-28 11:56, kefik wrote:
> Hi!
>
> This issue is troubling me too. Suddenly out of nowhere our site goals are
> failing due to missing "site_en" artifact.
>
> Do
Hi all.
I have tried using Maven 2.0.5, 2.0.6, etc. all the way up to 2.1.0. I have
also tried versions of maven-surefire plugin, from 2.2 all the way to 2.6. I
have also tried all versions of forkmode, including always, once, pretest and
configuring true.
I even tried passing maven.test.fai
Of course there are a lot of Q&A that are not just about the Maven
core and plugins under org.apache.maven.plugins. And it is always
acceptable to ask questions here and hope that maybe someone will be
able to help you.
But it seemed like your email was more of a complaint about poor
documentation
Thank you for your help. I am running mvn site. I have also found a solution
to my issue. Basically, I run the plugin during the "package" phase. This
link is where I got my information
http://hedemark.net/blog/?cat=4
Russell Collins
Sr. Software Engineer
CoreLogic Spatial Solutions
"Do o
Of course the base maven project is not going to do anything about the third
party documentation. However, based on what I have scene, there are a lot of
questions and answers that are not just base maven. There are announcements
about third party tools along with questions that involve third
Our move to aggregation jars was our solution of this problem.
We wanted central control over versions without a lot places to manage
version numbers.
For each application release, we decide what third versions of third
party libraries will be used.
If any of the libraries need changing we crea
Our move to aggregation jars was our solution of this problem.
We wanted central control over versions without a lot places to manage
version numbers.
For each application release, we decide what third versions of third
party libraries will be used.
If any of the libraries need changing we crea
Thank you.
Russell Collins
Sr. Software Engineer
CoreLogic Spatial Solutions
"Do or do not, there is no try." - Yoda
-Original Message-
From: Ryan Connolly [mailto:ryn...@gmail.com]
Sent: Monday, February 28, 2011 11:22 AM
To: Maven Users List
Subject: Re: [Cobertura] Cobertura Report
> -Original Message-
> From: Wayne Fay [mailto:wayne...@gmail.com]
> Sent: Friday, February 25, 2011 8:26 PM
> To: Maven Users List
> Subject: Re: [Cobertura] Cobertura Report Not Showing
>
>> I am not able to get this plugin to work properly. The online documentation
>> is terrible.
> ..
On 25 February 2011 22:58, Collins, Russell wrote:
>
> I am not able to get this plugin to work properly. The online documentation
> is terrible. When I run the plugin, I can get the results from the clean and
> check goals. However, it seems as though the cobertura goal isn't even
> running
I think what Wayne was trying to say is that there is a separate list for
help with individual plugins. In this case you may get more specific help
here: http://mojo.codehaus.org/cobertura-maven-plugin/mail-lists.html
On Mon, Feb 28, 2011 at 9:16 AM, Collins, Russell wrote:
> ...and one more
On Mon, Feb 28, 2011 at 9:49 AM, Phillip Hellewell wrote:
> The problem I see with using a snapshot for the parent is it doesn't
> allow you to make changes in a safe way. I could update the version #
> of a lower component, and then a much higher component could build
> against that before all t
On 28 February 2011 06:53, Fuke, Amol wrote:
> I am using below snippet to copy dependant jars from lib to war. But this
> also copying some unwanted jars like rt.jar and tools.jar.
>
> Is there any way I exclude them from getting copied into my war.
>
>
> maven-dependency-plugin
>
>
> i
On 28/02/2011 8:56 AM, Greg Akins wrote:
I would like some advice for structuring "config" files in a Maven
Project. Could someone give me some suggestions, or pointers to more
information?
The project needs different config files for each environment (dev,
qa, stage, production1, production2).
I'm thinking about moving all our version management into the parent
pom in a dependencyManagement section, but I'm trying to figure out if
it will really make things easier or not.
Of course each version number would only be in one place instead of N
places, where N is the avg # of reverse depend
Both compile and link are hooked into maven compile phase. Normally
the native compile should get by very quickly since no code changes.
The link phase still have to rebuild. Currently there is no work
around.
-Dan
On Mon, Feb 28, 2011 at 5:53 AM, sintetik wrote:
> Hi,
>
> I'm trying to migrate
Thanks Anders..
On Mon, Feb 28, 2011 at 9:34 AM, Anders Hammar wrote:
>
> This has been the discussion several times before, so you should find lots
> of info in the archive. You shouldn't need to go back more than a few
> months.
> Search for keywords like "properties jndi config environment" et
Hi,
I've two short questions regarding the release.properties that can be used
for the maven-release-plugin.
1) Can I specify the location of the property file as command line
parameter?
2) How does the release plugin behave, when the
project.dev.\. property is the current version in the
pom?
--
Hi,
I'm trying to migrate my cpp project to native-maven-plugin.
I've got buld succefull but there's a problem with repatable build. The
problem is that both compilation and linking is repeated even is there was
no changes in source code.
All in all, i have total time for the first build (single m
No, he does not! Using profiles to create different result based on
environment is an anti-pattern. In Maven specifically, but also in general
for builds.
Your CM is right. Your artifact (war or what ever) should be environment
generic. Keep the configs outside.
This has been the discussion severa
Thank you Ondřej
> This tutorial should give you all information you need:
>
> http://www.manydesigns.com/documentation/tutorials/using-maven-profiles-and-resource-filtering.html
That's a bit better than what I'm currently doing (which is using
profiles, but keeping multiple copies instead of usi
...and one more thing. If you are not going to help, please don’t respond.
Russell Collins
Sr. Software Engineer
CoreLogic Spatial Solutions
"Do or do not, there is no try." - Yoda
-Original Message-
From: Collins, Russell
Sent: Monday, February 28, 2011 8:16 AM
To: 'Maven Users List'
Well, if you feel that way, then announcing third party plugins should not be
allowed on this mailing list as well.
Russell Collins
Sr. Software Engineer
CoreLogic Spatial Solutions
"Do or do not, there is no try." - Yoda
-Original Message-
From: Wayne Fay [mailto:wayne...@gmail.com]
S
Dne 28.2.2011 14:56, Greg Akins napsal(a):
I would like some advice for structuring "config" files in a Maven
Project. Could someone give me some suggestions, or pointers to more
information?
The project needs different config files for each environment (dev,
qa, stage, production1, production2
Dne 28.2.2011 14:56, Greg Akins napsal(a):
I would like some advice for structuring "config" files in a Maven
Project. Could someone give me some suggestions, or pointers to more
information?
The project needs different config files for each environment (dev,
qa, stage, production1, production2
I would guess that this is the expected behavior, as otherwise it would
not be possible to remove reports defined in the parent. You will have
to add all the reports again if you want them to run in this module.
No, it's a bug. Inheritance of report plugin configuration worked with
Maven 2 and
I would like some advice for structuring "config" files in a Maven
Project. Could someone give me some suggestions, or pointers to more
information?
The project needs different config files for each environment (dev,
qa, stage, production1, production2). Right now, in another Mavenized
project,
Jeff Jensen wrote:
With Maven 3, how do I configure the site plugin to have a module's
defined site reports added to the parent's defined site reports (and
parent doesn't have the child report defined) instead of replacing the
parent's report config? Is this expected to work/possible (I'm hopi
Thanks for the hint!
Fredy
-Ursprüngliche Nachricht-
Von: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] Im Auftrag
von Anders Hammar
Gesendet: Montag, 28. Februar 2011 11:14
An: Maven Users List
Betreff: Re: maven jetty plugin - running two jetty's with different ports
A
Hi!
This issue is troubling me too. Suddenly out of nowhere our site goals are
failing due to missing "site_en" artifact.
Do you have a solution for the case where:
1) have a parent pom ... this parent pom neither has site generated nor have
any kind of site.xml therefore it can't deploy any site
As that's a specific question for that plugin, you should probably ask on a
mailing list specific for that plugin.
I believe these are the appropriate ones:
http://jetty.codehaus.org/jetty/maven-plugin/mail-lists.html
/Anders
On Mon, Feb 28, 2011 at 10:59, Hauschel Fred Robert <
fredrobert.hausc.
Hi List,
is it possible to run two jetty instances one on port 8080 and one on
port 8090?
Both jetty's should start several webApps.
"Running Multiple Webapps" is decribed in
http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin I hope this
works.
Thanks Fredy
---
On 28 February 2011 02:17, Peter Niederwieser wrote:
> According to (1), every POM must have elements like , and
> . So far I've always put such information into the parent only.
>
Are the inherited values correct?
specifically are the inherited scm url's correct?
mvn help:effective-pom | sed
46 matches
Mail list logo
