Well, that's the problem..we don't want to release a new version of
unchanged projects because it will confuse our users, especially for the
api projects...
maybe we did wrong using this kind of layout ?
Thanxs for your answers anyways
Max
On Sat, Dec 10, 2011 at 9:09 PM, Anders Hammar
Hi,
Well, that's the problem..we don't want to release a new version of
unchanged projects because it will confuse our users, especially for the
api projects...
maybe we did wrong using this kind of layout ?
Thanxs for your answers anyways
In this case you should separate out the api module and
We did exactly what you want to do.
We built a learning management system that includes more than 70 jar and
war files.
We started out changing every version with each release but soon reached
a point where most of the modules did not change as we improved the
modularity of the system and as
Yes, indeed that can be a long term solution to this problem if we see that
a few projects don't change too much in the next releases/months.
Regards,
Max
On Mon, Dec 12, 2011 at 11:23 AM, Karl Heinz Marbaise khmarba...@gmx.dewrote:
Hi,
Well, that's the problem..we don't want to release a
Thanxs Ron,
In fact our project is an old mulitple individual jars project (we had like
~40 jars), but eclipse had an hard time compiling/refreshing workspace so
we decided to merge a lot of projects.
Anyways thanxs for your anwser, i think a mix of multi module projects and
individual projects
On 12/12/2011 9:33 AM, Max Carpentier wrote:
Thanxs Ron,
In fact our project is an old mulitple individual jars project (we had like
~40 jars), but eclipse had an hard time compiling/refreshing workspace so
we decided to merge a lot of projects.
There is no need for Eclipse to have any more than
Hi folks,
I'm a bit new to Maven. I have some existing modules. One of them is a
'common' module which has utilities used by the other modules. how do I set
up a build to package all the modules together? I tried finding a way to add
the 'common' jar to the local repository immediately after
On 12/12/2011 11:28 AM, Amit Bhargava wrote:
Hi folks,
I'm a bit new to Maven. I have some existing modules. One of them is a
'common' module which has utilities used by the other modules. how do I set
up a build to package all the modules together? I tried finding a way to add
the 'common' jar
Hello all,
I tried posting this on the codehaus user list but it won't accept my e-mails.
So let's try here:
I'm having an issue with the cobertura plugin. I have a muti-module build that
I invoke like this on a nightly basis:
mvn install site:site findbugs:findbugs cobertura:cobertura
Now
Try to set the version of the plugin to 2.5.1
It is a good practice to always set the version for every plugin.
Maven-3.0.x already warns you about it and it will probably be required one day.
-Robert
ps. why not just run 'mvn install site'? This should already trigger these
plugins
Robert,
Thanks much for the response. I have a parent pom that does just that in its
pluginManagement section. Under the heading of it never hurts to try, I went
ahead and tried putting this in the offending module:
plugin
groupIdorg.codehaus.mojo/groupId
I just looked at the cobertura maven source the other day, so I took another
look. skipMojo() is the first call in the instrument plugin and if skip is
true it should log at INFO level: Skipping cobertura execution
While I don't have a solution to your issue, I can tell you that cobertura is
If you run 'mvn cobertura:cobertura -X' (-X means debug-level logging) you
should see the used configuration.
Can you confirm there's a skip-parameter and that its value is true?
The pluginManagement doesn't work for reporting-plugins, so within the
reporting-section you are required to
I created a small example of the problem and put it here:
http://pastebin.com/QDhx2kVf
Just run that pom.xml (I have tried Maven 2.2.1 and Maven 3.0.3) with this
command:
mvn install cobertura:cobertura
If it is truly skipping the cobertura plugin, you should only see this line
once:
Is it that the skip mojo is skipping the report but not the forked execution?
On 12 December 2011 21:58, Jim McCaskey jim.mccas...@pervasive.com wrote:
I created a small example of the problem and put it here:
http://pastebin.com/QDhx2kVf
Just run that pom.xml (I have tried Maven 2.2.1 and
Exactly my conclusion
-Robert
Date: Mon, 12 Dec 2011 22:09:53 +
Subject: Re: skip cobertura for a module
From: stephen.alan.conno...@gmail.com
To: users@maven.apache.org
Is it that the skip mojo is skipping the report but not the forked execution?
On 12 December 2011 21:58, Jim
Hi,
I am trying to find comparison on Archiva vs Artificatory but i couldn't
find any good discussion URL on these specific 2 repositories.
Can anybody tell me which one is good repository to USE ? and what's the
reason behind that ?
Please help me out on this one.
Thanks,
daivish.
Below link may help you
http://docs.codehaus.org/display/MAVENUSER/Maven+Repository+Manager+Feature+Matrix
Thanks
Pawan
-Original Message-
From: Daivish Shah [mailto:daivish.s...@gmail.com]
Sent: Monday, December 12, 2011 5:23 PM
To: Maven Users List
Subject: Any idea on choosing
Thanks Pawan !! this helps a lot !!
On Mon, Dec 12, 2011 at 2:31 PM, Gandhi, Pawan
gandhi.pa...@pennmutual.comwrote:
Below link may help you
http://docs.codehaus.org/display/MAVENUSER/Maven+Repository+Manager+Feature+Matrix
Thanks
Pawan
-Original Message-
From: Daivish Shah
Keep in mind that this article is mainly written directly by the guys
developing those software and two of them have a commercial version,
meaning that they are pretty focused on making their tool bright and shiny.
Cheers,
Guillaume
Le 13/12/2011 00:17, Daivish Shah a écrit :
Thanks Pawan !!
I think that what he was trying to achieve is to not repeat the same
version in all the pom's but this is totally impossible because of the
way Maven works.
Guillaume
Le 11/12/2011 18:24, Benson Margulies a écrit :
You do this by inheriting the version through the parent element. You
have to
On Tue, Dec 13, 2011 at 9:24 AM, Guillaume Polet
guillaume.po...@gmail.com wrote:
I think that what he was trying to achieve is to not repeat the same version
in all the pom's but this is totally impossible because of the way Maven
works.
Yes, but at least you only need to define it once for
Sure, writing it in the parent definition is the best way to go since
you avoid to write it twice. This is the way I work at least.
Sorry if I made that unclear with my previous e-mail.
Guillaume
Le 13/12/2011 01:07, Barrie Treloar a écrit :
On Tue, Dec 13, 2011 at 9:24 AM, Guillaume Polet
Thanks Ron. It worked.
Another question, if I may :
In my pom, I had already specified the local repository using the
repositories tag as follows
repositories
repository
idlocal1/id
nameMy First Repository/name
On Tue, Dec 13, 2011 at 11:55 AM, Amit Bhargava amit.bhar...@gmail.com wrote:
Thanks Ron. It worked.
Another question, if I may :
In my pom, I had already specified the local repository using the
repositories tag as follows
repositories
repository
Thanks for your reply. Are you suggestting something below.
Parent POM.
groupIdcom.tdsecurities/groupId
artifactIdtest-parent/artifactId
version1.0-SNAPSHOT/version
In all child projects
parent
artifactIdtest-parent/artifactId
groupIdcom.tdsecurities/groupId
On Tue, Dec 13, 2011 at 4:12 PM, Prashant Neginahal
prashu.n...@gmail.com wrote:
Thanks for your reply. Are you suggestting something below.
Parent POM.
groupIdcom.tdsecurities/groupId
artifactIdtest-parent/artifactId
version1.0-SNAPSHOT/version
In all child projects
parent
27 matches
Mail list logo
