It could be better but far from perfect. Few users are reading this file and
are using it to create their own.
I think they are often copying it from the page you pointed.
There are several annoying things about settings from my point of view but
we won't be able to change before a 3.x :
- We
Hi,
M3 complains now if the referenced parent of a POM is not in the parent
directory:
=== % =
$ mvn validate
[INFO] Scanning for projects...
[INFO] snapshot com.scalaris.buildsystem.maven2:master:SNAPSHOT: checking
for updates from scalaris-repo-snapshot
[WARNING]
Hi guys,
it's not the first time I complain about Maven performance, but it seems M3
is heading the right direction. Yet, still not on the 2.0.x level:
% =
$ MAVEN_OPTS=-Xmx768m -XX:MaxPermSize=128m mvn-2.0 eclipse:eclipse
Apache Maven 2.0.11
Java version: 1.6.0_20
Java
Jörg Schaible wrote:
M3 complains now if the referenced parent of a POM is not in the parent
directory:
[WARNING] 'parent.relativePath' of POM com.scalaris.commons:scalaris-
commons-lang:2.2.11-SNAPSHOT (/home/jos/work/internal/commons/lang/pom.xml)
points at com.scalaris.commons:builder
Hi
Do the same test with mvn org.twdata.maven:maven-cli-plugin:execute-phase - A
regular compile with large projects cuts down the time drastically
Hermod
-Original Message-
From: Jörg Schaible [mailto:joerg.schai...@gmx.de]
Sent: Tuesday, April 27, 2010 2:11 PM
To:
On Tue, Apr 27, 2010 at 2:13 PM, Benjamin Bentmann
benjamin.bentm...@udo.edu wrote:
Jörg Schaible wrote:
M3 complains now if the referenced parent of a POM is not in the parent
directory:
[WARNING] 'parent.relativePath' of POM com.scalaris.commons:scalaris-
commons-lang:2.2.11-SNAPSHOT
Hi Benjamin,
Benjamin Bentmann wrote:
Jörg Schaible wrote:
M3 complains now if the referenced parent of a POM is not in the parent
directory:
[WARNING] 'parent.relativePath' of POM com.scalaris.commons:scalaris-
commons-lang:2.2.11-SNAPSHOT
(/home/jos/work/internal/commons/lang/pom.xml)
Milos Kleint wrote:
Can we have this documented in the xsd for the relativePath
element?
Done.
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
I never had results like you.
I always noticed improvements between 2.02.23.0
I'll do some tests.
Where I have problems for now, it is on some OS. While with OSes like
Suse,OpensSolaris,Windows 7 we have good perfs results for the build, on
linux servers like ubuntu, fedora , ... we have results
Jörg,
If you are going to use the maven-eclipse-plugin as your benchmark I think it's
going to be very hard to pin point where the bottleneck is. It's a little
universe unto itself. Could be the shared components, resolution code, the
plugin itself. I see vast improvements in speed in Maven
2010/4/27 Arnaud Héritier aherit...@gmail.com:
It could be better but far from perfect. Few users are reading this file and
are using it to create their own.
I think they are often copying it from the page you pointed.
There are several annoying things about settings from my point of view but
I think mirrors should be able to be defined inside of (settings)
profiles. That would make it easier to deal with moving from location
to location.
+1
If this isn't yet in our backlog for 3.x we can add it.
Hello Maven community, I have written a maven plugin which uses the
2.2.1 api to download artifacts. I see the api's between 2.x and 3.x
have changed for plugins like this.
Actually, it looks like I use 2 parts of the old api.
1) Downloading artifacts using these deprecated classes.
Arnaud, I run into situations where one project demands a complete
different settings.xml than another. Assume you have a book project
that deals with a separate repo manager and set of credentials vs. a
tiny codehaus project with a separate repo man vs. an internal
corporate project with
Harsha Sri-Narayana wrote:
org.apache.maven.artifact.repository.layout.DefaultRepositoryLayout;
This is an implementation class/component, your plugin should not refer
to this directly but rather use something like
/** @component roleHint=default */
private ArtifactRepositoryLayout
I think you can already do what you are asking with a repo manager.
If you need to communicate to 3 different repos, then those repos should all be
controlled through the repo manager. One of the repos could be public (ie: like
an org) and another could be private (like a com).
Your
You can't deploy to different repos via the same repo manager though
On 27 April 2010 15:43, Thiessen, Todd (Todd) tthies...@avaya.com wrote:
I think you can already do what you are asking with a repo manager.
If you need to communicate to 3 different repos, then those repos should
all be
But isn't settings.xml only related to artifacts that are downloaded, not
deployed? Deployment of artifacts to a repo I believe goes in the pom.
-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: Tuesday, April 27, 2010 11:09 AM
To: Maven
server specific setting and proxy details go into settings.xml
you might need to use a different proxy to deploy to a specific repo
you might need to use different server credentials esp if you have two
different projects which have decided to use the same server-id for
different servers
On
I just created a cli tool using code from nexus-archetype-plugin, and
updated the central archetype catalog with latest central index
The nexus-archetype-plugin is open sourced:
http://scm.sonatype.org/repobrowser.svn?path=/trunk/revision=HEADname=Nexus-plugins
I will clean up the cli code and
Ah, I forgot that it's defined in the super pom. I was thinking that it was in
the code somewhere.
I think adding the central repo to the default global settings would be a good
start. Would it even need to be commented out? If it is defined in both
places, I'm assuming that the one in the
Benjamin Bentmann wrote:
Paul Gier wrote:
Would there be any problems if the central repo definition was moved
out of the
Maven internals and into the default settings.xml [1]?
I assume you refer to the global settings file shipped inside the Maven
installation directory. The one issue I
You can deploy to different repos via a single repo manager (and a single URL)
if those repos are hosted on a single server. We're doing that currently with
Nexus where the destination repository is determined by the groupId.
Maybe you meant you can't deploy to different servers via the same
Different server credentials is not a problem since you just associate each cred
with an ID. Unless for some reason you are defining a single repository ID for
multiple deployment URLs.
Multiple proxies would require separate settings, but I wouldn't think this is a
common use case. If it is
Brian Fox wrote:
2010/4/27 Arnaud Héritier aherit...@gmail.com:
It could be better but far from perfect. Few users are reading this file and
are using it to create their own.
I think they are often copying it from the page you pointed.
There are several annoying things about settings from my
On 27 April 2010 19:46, Paul Gier pg...@redhat.com wrote:
Different server credentials is not a problem since you just associate each
cred
with an ID. Unless for some reason you are defining a single repository ID
for
multiple deployment URLs.
or in the case I described where you are
Hi Jason,
Jason van Zyl wrote:
Jörg,
If you are going to use the maven-eclipse-plugin as your benchmark I think
it's going to be very hard to pin point where the bottleneck is. It's a
little universe unto itself. Could be the shared components, resolution
code, the plugin itself. I see
Hi,
I want to release Maven Archetypes parent pom - maven-archetype-bundles
version 4- and some Maven Archetypes:
- maven-archetype-plugin version 1.1
- maven-archetype-plugin-site version 1.1
- maven-archetype-quickstart version 1.1
- maven-archetype-site version 1.1
-
Just a question: will use central catalog, or the catalog got from the
_roor_ of defined reposes?
In other word: will mirrorOf affect from where is catalog pulled?
Asking, since initially when I talked to Raphael wrt nexus-archetype-plugin,
the main reason why this plugin put the catalog in the
29 matches
Mail list logo
