They should be fine. Just to be clear, they are in the
maven-version-plugin-1.0.0.pom, in the local repository?
On 11/10/2010, at 4:07 PM, Jason Chaffee wrote:
I should add that the version on all of these is 2.2.1
-Original Message-
From: Jason Chaffee
Yes.
The 2.2.1 is configured in the parent pom dependencyMangement.
I remember Jason saying talking about the Artifact refactoring about a year ago
and saying it would not be backwards compatible with 2.0 and that if you had
plugins using Artifact resolution you would need to rewrite them
Hi,
i'm using the maven-changes-plugin to get a list of issues from our
jira-instance.
The plugin configuration in my pom.xml looks like this:
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
On 11/10/2010, at 5:42 PM, Jason Chaffee wrote:
Yes.
The 2.2.1 is configured in the parent pom dependencyMangement.
I remember Jason saying talking about the Artifact refactoring about a year
ago and saying it would not be backwards compatible with 2.0 and that if you
had plugins
Looks the maven dependencies are being excluded in the class realm. I am
noticing this for all the plugins executed. All of the org.apache.maven jars
are Excluded.
[INFO] --- maven-version-plugin:1.0.0:version (default) @ cbsp ---
[DEBUG]
Ok sorry, I wasn't looking closely enough at the error message.
ArtifactTransformation has been hidden to avoid it being used going forward. So
the options are to seek an alternative higher level API to obtain the
information, or file a bug request to restore the interface.
What's the reason
Hi
I configured a integration test only project, in a way that every
module uses a configuration that is stored in the parent folder.
I implemented this way:
In the parent pom (in the root of the tree):
properties
envTypelocal/envType !-- Default Environment value --
On 6 October 2010 15:34, Hilco Wijbenga hilco.wijbe...@gmail.com wrote:
On 5 October 2010 09:48, Hilco Wijbenga hilco.wijbe...@gmail.com wrote:
On 5 October 2010 04:09, Benjamin Bentmann benjamin.bentm...@udo.edu wrote:
Hilco Wijbenga wrote:
repositories
repository
Hi All,
I have following configuration in war plugin:
(parent pom)
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.1/version
configuration
excludes
Try this:
excludes.gitignore,**/.gitignore/excludes
If you don't see the property as a ListString in the source, it must
be a comma-separated or space-separated value.
Paul
On Mon, Oct 11, 2010 at 10:38 AM, Dmitry Sklyut dmi...@dsklyut.com wrote:
Hi All,
I have following configuration in war
The Maven team is pleased to announce the release of the Maven Assembly
Plugin, version 2.2
This plugin allows the user to create customized archives based on their
project and its dependencies. For example, the assembly plugin is
commonly used to create distribution archives for projects.
Help! My dependencies only ever get written to the default
${basedir}/target/dependency dir.
Usage:
mvn dependency:copy-dependencies
Pom.xml segment:
-
profiles
profile
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
The closest plugin would be
https://project.smartics.de/maven-buildmetadata-plugin/. I might see if
I can use that one.
My plugin was written a few years in advance of that one and has some
nicer features, but I might just make do with that so I don't have to
maintain it anymore.
Jason
Hi,
Your execution is attached to the lifecycle. You'll get the expected
behaviour if you type mvn package, not by calling directly the mojo from
command line.
2010/10/11 Steve Francolla sfranco...@gmail.com
Help! My dependencies only ever get written to the default
I actually want to run it outside the lifecycle. I've removed the phase
binding and run it with the same usage. It runs but the output gets written
to the default ${basedir}/target/dependency dir instead of the
outputDirectory I've overridden it with in the configuration. Seems clearly
broken
The problem is that the configuration you have is written within the
execution. That execution is NOT for your CLI usage.
You have two options:
1. You need to use the somewhat magic id of default-cli:
http://maven.apache.org/guides/mini/guide-default-execution-ids.html
2. Move the configuration
I'm using the site plugin with distributionManagement set to a
scm:svn:https://... url. This commits the generated site files to a
special place in Subversion where they are then visible as part of the
project's website.
But... there is a pre-commit hook that requires every commit to be
Hi,
I have installed the maven eclipse plug-in from:
http://m2eclipse.sonatype.org/
Now I have more projects in my eclipse workspace. I have run mvn
eclipse:eclipse and imported
the projects in eclipse. I have removed projects references and each
project will use jar in the
maven local
Anders --
That did it. Thanks very much.
Solution summary:
- remove plugin from life-cycle,
- apply execution id default-cli
- contain plugin def by promoting it to build.pluginManagement element.
Working segment:
--
build
pluginManagement
plugins
plugin
Don't use mvn eclipse:eclipse if you want to use the m2eclipse plugin. Use
Import Existing Maven project.
2010/10/11 Davide d...@vide.bz
Hi,
I have installed the maven eclipse plug-in from:
http://m2eclipse.sonatype.org/
Now I have more projects in my eclipse workspace. I have run mvn
In regards to this section of Maven 3 compatibility notes:
https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-DependencyResolution
Will dependency:tree continue to use the old resolution code
indefinitely, or are there plans to fix it to use the new
Hi all,
I just tested the brand new Release Plugin 2.1 and I found that the label
created by the perforce scm provider has an empty file set.
Looking at the generated perforce label, I can see that the perforce view
specification is wrongly all lowercase.
I then found that the
It's currently hardcoded in line 282 of
org/apache/maven/wagon/providers/scm/ScmWagon.java in wagon-scm.
It would be possible to move that up to wagon-level configuration, which would
allow it to be set in settings.xml in the servers section - but that only gives
you one value to replace it
This was to avoid case-comparison issues where c:\something looked different to
C:\something (MRELEASE-536). It seems like it shouldn't be persisting that
change then.
Can you file a new issue?
On 12/10/2010, at 9:11 AM, Thiebaud, Christophe wrote:
Hi all,
I just tested the brand new
The Maven team is pleased to announce the release of the Maven Antrun
Plugin, version 1.6
This plugin provides the ability to run Ant tasks in a Maven build. See
the plugin's site for more details:
http://maven.apache.org/plugins/maven-antrun-plugin/
You should specify the version in your
I tried, but get the following error. I use Maven 3.0 and jdk1.6.0_21.
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-antrun-plugin:1.6:
run (update-env) on project devEnv-build-pom: Execution update-env of
goal org.a
pache.maven.plugins:maven-antrun-plugin:1.6:run failed: An API
Hello,
I am working with the dependency:go-offline plugin goal. I am trying to make a
project COMPLETELY portable. However, when I run this plugin, it often leaves
out certain transitive dependencies. Typically this happens when there is a
conflict. For example, I declare two dependencies, A
Hi all,
I could have sworn I've used ${localRepository} before but it doesn't
seem to work. I've also tried ${settings.localRepository} and
${maven.repo.local}. How do I refer to the location of the local
repository in a portable way? Is there a difference between Maven2 and
Maven3?
Cheers,
28 matches
Mail list logo
