Hello!
I'm having trouble getting scm with perforce working. I've set up a
simple project (archetype:create), and then modified my pom.xml to
contain this:
...
scm
connectionscm:perforce:p4bck:1666://my-app/connection
Hi,
If you want to see the list of dependencies and their scope for a POM, you
could try mvn dependency:tree
For further information on how to use the dependency plugin, have a look a
this link ;
Hi,
I am wondering if it's possible to do the following:
My application context uses some beans from a different application context
which is located in one of its dependencies.
I am now writing unit tests for this project and the dependency as well.
So I have my test application context in
I want to deploy my parent module to the remote repository but not its child
modules. How can I do this?
--
View this message in context:
http://www.nabble.com/How-can-I-deploy-parent-module-without-deploying-sub-modules--tp17881951p17881951.html
Sent from the Maven - Users mailing list archive
Hi there;
Am Tue, 17 Jun 2008 03:13:02 -0700 (PDT)
schrieb Papapara Tudu [EMAIL PROTECTED]:
My application context uses some beans from a different application
context which is located in one of its dependencies.
Looking at your terminologies and file snippets: Are you using Spring
in your
Looking at your terminologies and file snippets: Are you using Spring
in your projects?
Yes
If (I assume so) Spring is involved, this should work, at least I do
have libraries (jar artifacts) wired up with web applications (war
artifacts) right this way. Where is your
** nudge **
On Mon, Jun 16, 2008 at 12:42 PM, Karan Malhi [EMAIL PROTECTED] wrote:
Hi,
I have a requirement to configure the eclipse plugin within the pom so that
I can replace the following
mvn eclipse:eclipse -DdownloadSources=true -DdownloadJavadocs=true
-DsomeProperty
with something
I will give those steps a shot today and let you all know if I run into any
problems. It sounds like a pretty logical thing to do actually, and
fortunately I do not require cross-platform compilation and support at this
point.
One quick question though, when you say that I should use the
Have you tried with the command mvn -N deploy ?
Giancarlo
2008/6/17, youhaodeyi [EMAIL PROTECTED]:
I want to deploy my parent module to the remote repository but not its child
modules. How can I do this?
--
View this message in context:
I want to checkout my project according to tagname.Can anyone helpme out with
the command?
--
View this message in context:
http://www.nabble.com/help-regarding-checkout-according-to-tagname-using-mvn-scm-plugin-tp17885847p17885847.html
Sent from the Maven - Users mailing list archive at
Hi all
My prj_home_dir/src/main/java has about 1642 classes. When Maven executes
the compile life cycle, all tha 1642 classes are compiled at once and i
always get a out of memory error. Is there a way that i can instruct maven
to compile in steps. e.g web layer first, then the business layer etc.
Oh, it works. thanks a lot.
Giancarlo Degani wrote:
Have you tried with the command mvn -N deploy ?
Giancarlo
2008/6/17, youhaodeyi [EMAIL PROTECTED]:
I want to deploy my parent module to the remote repository but not its
child
modules. How can I do this?
--
View this message
Am Tue, 17 Jun 2008 03:39:19 -0700 (PDT)
schrieb Papapara Tudu [EMAIL PROTECTED]:
The test application context in the dependency is located in the
/src/test/resources folder in its project
(in the project I'm writing the tests for, my app context is in
/src/test/resources also).
I see...
Actually, I can think of seperate module inside the main root project and a
seperate pom.xml for each one. Then you can build those one by one.
Else, try increasing the memory with the compiler plugin (I think, you have
atleast 1.5 GB RAM)
plugin
groupIdorg.apache.maven.plugins/groupId
On Tue, Jun 17, 2008 at 12:00:51PM +, Kristian Rink wrote:
Am Tue, 17 Jun 2008 03:39:19 -0700 (PDT)
schrieb Papapara Tudu [EMAIL PROTECTED]:
The test application context in the dependency is located in the
/src/test/resources folder in its project
(in the project I'm writing the
I tried increasing the memory using the maxmem and memintial, initial=512mb
and mac=2048m. still the same error. my 1642 files have been distributed
accross four packages. src/main/java/com/abc/xyz/pkg1
pkg2
So I take it that the beta 3's are targeted at Maven 2.1? Is there not
a way in Maven to prevent plug ins that are targeted at different
versions of maven from being installed?
Thanks,
Chris
Brian E. Fox wrote:
Those wagons are not compatible with maven 2.0.9 or less.
-Original
Hi All,
From the maven command line help :
-U,--update-snapshots Forces a check for updated releases and
snapshots on remote repositories
Does this actually work with released artifacts ? I don't seem to be
able to force an update of a released artefact.
Thanks in advance
The general concept with Maven would be that you should divide your
code up into modules along whatever lines that make sense to you (1
module per pkg may be reasonable for your specific implementation, I
suppose).
Then you set up dependencies between the modules via each one's
pom.xml file, and
The easiest way is to split your sources into separate maven modules.
If you have 1600 classes, this imho makes sense anyway!
I (personally) mean, if a project is _that_ fat, then a modularisation would
help to better understand the whole application. Each modules should have their
own unit
Released artifacts are never updated. If you are pushing updates to
released artifacts, you will break your Maven builds in horrible,
ugly, nasty, indeterminate ways.
Unless you are talking about a new VERSION of a released artifact.
Which is it?
Wayne
On 6/17/08, SlinnHawkins, Jon (ELS-CAM)
Unfortunately - its updates to released versions.
-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED]
Sent: 17 June 2008 14:56
To: Maven Users List
Subject: Re: -U
Released artifacts are never updated. If you are pushing updates to
released artifacts, you will break your Maven
Unless we are talking about snapshots, that will never, ever work and
it is a very poor practice.
But I am using xyz-1.2.jar! Why is yours working and mine isn't?
Wayne
On 6/17/08, SlinnHawkins, Jon (ELS-CAM) [EMAIL PROTECTED] wrote:
Unfortunately - its updates to released versions.
On Tue, Jun 17, 2008 at 6:28 AM, SlinnHawkins, Jon (ELS-CAM)
[EMAIL PROTECTED] wrote:
From the maven command line help :
-U,--update-snapshots Forces a check for updated releases and
snapshots on remote repositories
Does this actually work with released artifacts ? I don't seem to be
Hi,
I am unable to generate PMD/CPD metrics for a test suite as part of a
multi-module build.
The parent pom pulls version 2.3 of the PMD plugin and sets the
includeTests setting to true. The PMD and CPD reports are generated but
do not include the test metrics.
However if I generate a site from
On Tue, Jun 17, 2008 at 9:59 AM, SlinnHawkins, Jon (ELS-CAM)
[EMAIL PROTECTED] wrote:
Unfortunately - its updates to released versions.
Well, as long as you recognize this isn't a particularly good idea and may
have all sorts of unintended side effects, the simplest action is to clear
the old
Hi,
We have a multiproject which contains both war and jar projects. I would
like (in a profile) to disable the war projects from building their wars -
as it takes ages and we only need them now and then.
Is this possible?
So I want to run
mvn install -PnoWars
At the parent and get all the jars
Hi,
I have defined a parent tag within my pom which, because no root pom is
being pulled into org/jboss/seam/root in my repository, is throwing a
'Badly formed maven project' error, using Netbeans 6.1, in relation to
the groupId and unspecified versions in the defined dependencies. What
is
Paul Spencer wrote:
The URL's in the banner tags of site.xml are the maven-site-plugin is
the hostname is not found by nslookup. In my case the hostname only
exists in my hosts files on a the Windows machine running mvn site.
The above should be:
Absolute URL's in the banner tags of
Greetings,
In a POM, I'm displaying the value of the env variable:
project
.
build
plugins
...
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
executions
execution
I would probably set that up as follows:
Default profile (in parent pom) only specifies modules which are jars
War profile specifies all modules, jars and wars
When you want a jar-only build, you just execute mvn install at the parent.
When you want wars too, you execute mvn install -Dpluswars at
there are indeed seperate test classes for all those packages.
but what i m not understanding is how do i write seperate poms for each
pakage. and where do i kep that pom? and how do i call it?
right now I am using one pom in the prj_home dir.
On 6/17/08, Mark Struberg [EMAIL PROTECTED] wrote:
Hi,
actually we have 2 ClearCase VOBs (databases) - one for the test-team, the
other for developement.
Both maven builds should use the same company-parent pom.xml:
parent
groupIdcom.mycompany/groupId
artifactIdglobal-parent/artifactId
I want to use the javadoc goal of the maven-javadoc-plugin. But I want to
run it in three different ways
1. generate a .properties file from a source java file, using a custom
doclet. My doclet expects 3 command line parameters.
2. generate javadoc for all other java files (excluding the java
Hi Torsten,
I have faced a similar situation and unfortunately have not come up with
a silver bullet solution. I too would be interested if anyone else
has one. Fortunately for us, so far all of our projects that use maven
are small enough that we can put all modules in a single
I have added the two elements to the pom (downloadSources and
downloadJavadocs), the eclipse:eclipse goal does not run to completion and
errors out after 6 minutes or so. It says there are too many open files. I
knew I had seen this error before and it is because there is a limit of
total number
You have to restructure your project.
Like:
module-name-pkg1/src/main/java/com/abc/xyz/pkg1
module-name-pkg1/src/test/java/com/abc/xyz/pkg1
module-name-pkg1/pom.xml
module-name-pkg2/src/main/java/com/abc/xyz/pkg2
module-name-pkg2/src/test/java/com/abc/xyz/pkg2
module-name-pkg2/pom.xml
Is this a good time to bring up a potential name conflict between maven
convention and ant's use of 'env'?
eg: property environment=env/
provides all environment variables as Ant properties prefixed by env.
-Original Message-
From: nicolas.duminil [mailto:[EMAIL PROTECTED]
Sent:
I have followed the steps, and I am now getting the following error message
when I try to package my project:
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO]
I'm guessing you didn't install the dll with the packaging type dll (use
-Dpackaging=dll, the default is jar -
http://maven.apache.org/plugins/maven-deploy-plugin/usage.html). Check your
local repository and the pom for the dll. Regarding your earlier question,
you sure can package it into a jar
Kalle,
I have made sure to carefully deploy the dll's to my repository, with the
appropriate packaging parameters and all. Initially I was using mvn
install:install-file, I now use mvn deploy:deploy-file, and when I look
inside the repository, it all seems to be there, and it looks to be correct.
A nice, thanks.. didn't even realize I could do that with that plugin.
Thank! Hopefully that will tell me what is being excluded.. must be
something indirect since I wouldn't exclude my own core dependencies. :)
(or at least not intentionally).
On Tue, Jun 17, 2008 at 4:45 AM, Julien Simon
getting long hangs on both codehaus repos:
http://snapshots.repository.codehaus.org/
http://repository.codehaus.org
does anyone know of any mirror for these?
tia,
-Russ
-
To unsubscribe, e-mail: [EMAIL
At 12:25 PM -0700 6/17/08, Russ Tremain wrote:
getting long hangs on both codehaus repos:
http://snapshots.repository.codehaus.org/
http://repository.codehaus.org
does anyone know of any mirror for these?
tia,
-Russ
as a temporary work-around, assuming you don't need to update
Hi,
It's back now. (http://jira.codehaus.org/browse/HAUS-1700).
--
Olivier
2008/6/17 Russ Tremain [EMAIL PROTECTED]:
At 12:25 PM -0700 6/17/08, Russ Tremain wrote:
getting long hangs on both codehaus repos:
http://snapshots.repository.codehaus.org/
http://repository.codehaus.org
Thanks for your help Brian. I'm afriad I'm not quite following your
suggestion though.
If I add the narUnArchiver dependency to the maven-dependency-plugin like
so:
plugin
groupIdorg.freehep/groupId
artifactIdfreehep-nar-plugin/artifactId
executions
execution
Hi,
I'm having a problem where a project using the assembly plugin is
copying two versions of the jaxb-api jar (1.0.5 2.0) to the
WEB-INF/lib directory of a webapp the assembly is creating.
I tried using dependency management to explicitly specify to use version
2.0 like this:
On Tue, Jun 17, 2008 at 8:15 PM, Matias Otero
[EMAIL PROTECTED] wrote:
I'm having a problem where a project using the assembly plugin is copying
two versions of the jaxb-api jar (1.0.5 2.0) to the WEB-INF/lib directory
of a webapp the assembly is creating.
My guess is that you're picking up
Yes, I had a suspicion that was the problem when I saw the jaxb jars in
multiple group Ids in the maven repository.
I have fixed the problem now by adding exclusions in the assembly
dep.xml file using the groupId javax.xml as that's where all the jaxb
1.x jars live.
Thanks very much for your
This seems like a common/obvious request but a bit of googling didn't turn
it up. At my work we're using the Dependency Convergence report to detect
dependency conflicts. We'd like to fail the build if we don't have 100%
dependency convergence on that report.
I had hoped that I'd be able
I'm not sure when you put META-INF\application.xml.
Does it go under src\main\resources or src\main\application?
mvn eclipse:eclipse generates a source dir reference to
src\main\application, and that is what it appears to need to be able to
run the test app in the environment.
However,
51 matches
Mail list logo