Is there a proper way to install an artifact during the build process
based upon a path? There is a proprietary set of artifacts that I would
like to define in the a parent pom that will install the artifacts based
upon a path defined in the child project pom.
Once you have deleted the directory from disk you will have to update the
database (admin: database update database now) and scan your repository
(admin: repositories scan repository now).
-Original Message-
From: Michael Hüttermann [mailto:mich...@huettermann.net]
Sent: Monday,
We had similar issues with archiva. These type of issues were resolved when we
went to http://nexus.sonatype.org/
-Original Message-
From: Michael Hüttermann [mailto:mich...@huettermann.net]
Sent: Monday, February 02, 2009 11:45 AM
To: users@maven.apache.org
Subject: Archiva and Maven
Is there a way to Exclude a plugin dependency declared in a parent pom?
We have an enterprise level pom that turns WTP capabilities by default:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-eclipse-plugin/artifactId
configuration
Addendum: I know that we can turn WTP off by overriding the
configuration. I was just wondering if there is a way to exclude the
plugin in the child pom to prevent any other compatibility issues that
may arise.
-Original Message-
From: Hoover, William [mailto:whoo...@nemours.org]
Sent
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
-Original Message-
From: Trevor Harmon [mailto:[EMAIL PROTECTED]
Sent:
${org.eclipse.jdt.core.version}/version
/dependency
/dependencies
/plugin
Regards,
Rice
On Tue, Nov 11, 2008 at 2:17 AM, Rice Yeh [EMAIL PROTECTED] wrote:
Thanks, it works.
On Tue, Nov 11, 2008 at 1:38 AM, Hoover, William
[EMAIL PROTECTED]wrote:
http
http://article.gmane.org/gmane.comp.jakarta.turbine.maven.user/91072
-Original Message-
From: Rice Yeh [mailto:[EMAIL PROTECTED]
Sent: Monday, November 10, 2008 12:30 PM
To: users@maven.apache.org
Subject: Use eclipse to compile
Hi,
I am following the instructions on
org.eclipse.jdt.core.version3.4.2.v_883_R34x/org.eclipse.jdt.version
/properties
...
-Original Message-
From: Hoover, William [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 23, 2008 2:49 PM
To: users@maven.apache.org
Subject: maven-compiler-plugin using eclipse
In maven version 2.0.8 we
In maven version 2.0.8 we originally tried the following, but it did not
resolve the generics issue that the plexus compiler has related to
http://jira.codehaus.org/browse/PLXCOMP-100:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
+1
-Original Message-
From: Manos Batsis [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 06, 2008 6:16 AM
To: Maven Users List
Subject: Re: [POLL] Default Value for Reports Output Encoding
[a] Use UTF-8
Cheers,
Manos
for me as well.
Arne.
-Opprinnelig melding-
Fra: Hoover, William [mailto:[EMAIL PROTECTED]
Sendt: 18. mars 2008 19:33
Til: Maven Users List
Emne: RE: [ANN] Maven Eclipse Plugin 2.5 Released
I found that replacing...
localRepository/path/to/repo/localRepository
with...
localRepositoryC
Using mvn eclipse:clean eclipse:eclipse with version 2.5. For example, if
M2_REPO = /path/to/repo executing the command renders build paths for
dependencies for project as
M2_REPO/path/to/repo/commons-collections/commons-collections/3.2/commons-collections-3.2.jar
If I use version 2.4 M2_REPO
Released
+1. Same problem here. Just saw the behaviour some minutes ago.
Precision: I'm not using the default repository location, this might a cause of
this problem.
Do you want someone to log a bug in the tracker, Arnaud?
Cheers.
-Message d'origine-
De : Hoover, William [mailto
, 2008 at 1:56 PM, Hoover, William [EMAIL PROTECTED]
wrote:
I'm not using the default repository location either. I think you may be
right- it may have something to do with that.
-Original Message-
From: MATHUS Baptiste [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 18, 2008
switching to 2.5, but so far only in
when packaging are war, not jar or ejb.
I'm using wtpversion 2.0.
I'm using windows XP, Maven 2.0.8
Arne.
-Opprinnelig melding-
Fra: Hoover, William [mailto:[EMAIL PROTECTED]
Sendt: 18. mars 2008 17:36
Til: Maven Users List
Emne: RE: [ANN] Maven Eclipse
anyone else verify that this fixes their issues as well?
-Original Message-
From: Hoover, William [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 18, 2008 12:57 PM
To: Maven Users List
Subject: RE: [ANN] Maven Eclipse Plugin 2.5 Released
I tested with packaging as jar or war and still have
Does anyone know a way to include test classes (src/test/java) in the
checkstyle report? I am only recieving results for packaged classes
(src/main/java)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands,
] Including test classes in report?
I see you can only give one sourcedirectory, but you can add the
parameter includeTestSourceDirectory [1].
Hth,
Nick Stolwijk
[1]
http://maven.apache.org/plugins/maven-checkstyle-plugin/checkstyle-mojo.html#includeTestSourceDirectory
Hoover, William wrote
19 matches
Mail list logo