On 11/09/2006, at 3:05 AM, Jimisola Laursen wrote:
It would be nice if we could decide on a working name for the APIs.
maven-issue is fine for now (ie, Maven Issue).
For projects:
1. Maven Project API
2. Maven Projects API
3. Maven Project Management API
4. Maven Projects Management A
On 9/12/06, Brett Porter <[EMAIL PROTECTED]> wrote:
The first one doesn't exist (POM only):
http://www.ibiblio.org/maven2/acegisecurity/acegi-security/1.0.0/
acegi is now under org.acegisecurity groupId
The second one doesn't exist in the m2 repo (the version is actually
2.0-m4, which is in
The first one doesn't exist (POM only):
http://www.ibiblio.org/maven2/acegisecurity/acegi-security/1.0.0/
The second one doesn't exist in the m2 repo (the version is actually
2.0-m4, which is in the m1 repo):
http://www.ibiblio.org/maven/org.springframework/jars/spring-2.0-m4.jar
The third on
Still going with the maven-dependency-plugin testing, I have the
following setup using 1.0-SNAPSHOT of the testing-harness:
plugin-config.xml:
maven-dependency-plugin
org.apache.maven
maven-artifact
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 12, 2006 10:35 PM
To: Maven Developers List
Subject: Re: plugin resolution
It seems the search order is back to front, we had the same problem with
Jetty.
- Brett
On 13/09/2006, at 12:26 PM, Bria
It seems the search order is back to front, we had the same problem
with Jetty.
- Brett
On 13/09/2006, at 12:26 PM, Brian E. Fox wrote:
I'm trying to test the new version of maven-dependency-plugin by
executing a simpler CLI invocation like: mvn dependency:resolve. For
some reason, mvn keeps
I'm trying to test the new version of maven-dependency-plugin by
executing a simpler CLI invocation like: mvn dependency:resolve. For
some reason, mvn keeps finding the mojo version dependency-maven-plugin
and executing that. Any idea why it's not picking up the correct one in
my local repo?
Than
Done.
-Original Message-
From: dan tran [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 06, 2006 12:59 PM
To: Maven Developers List
Subject: Re: 775 for maven-dependency-plugin's snapshot
It turns out I have permission to rename maven-dependency-plugin
directory to another name. A
I suggest using '3' for the release (which has the problem), then
republishing the site with the new version.
See my separate thread on moving the plugin tools for fixing this
properly.
On 13/09/2006, at 2:22 AM, Dennis Lundberg wrote:
Vincent, I can confirm this on my setup as well.
The
On Sep 12, 2006, at 3:49 PM, dan tran wrote:
2 scenarios:
1 - user uses version 1, then he/she will need to fix up lots of
configurations in order to use 1.1
Yes, I don't see this as a major problem. If a user wants to use the
new functionality they need to upgrade their configuration
Hi Stephane,
Maybe have a look to javadoc plugin.
HTH
Cheers,
Vincent
2006/9/12, Stephane Nicoll <[EMAIL PROTECTED]>:
Anyone?
On 9/4/06, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I am trying to write a complete test suite for the EAR plugin and I am
> wondering if there is a docu
Anyone?
On 9/4/06, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
Hi,
I am trying to write a complete test suite for the EAR plugin and I am
wondering if there is a documentation somewhere about available tools
/ techniques.
My needs are the following:
- Ability to define test projects with the a
Vincent, I can confirm this on my setup as well.
The reason for bumping the version of the parent was to prepare for a
release (see separate vote thread). From what I understand a release
cannot be made if there are any SNAPSHOT-dependencies.
Let's see I get this... When I fixed (updated to a
I tried the latest build of 2.0.5-SNAPSHOT from 09-10-2006. It is not
fixed. Is this bug in the maven core or is it part of the "plugin" plugin?
Where would I look to begin fixing this?
Thanks,
Todd
On 9/11/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
You can test a build generated by our
Hi guys,
The following artifacts are available for m2 (I found them in
mvnrepository) but not for m1.
Attempting to download
acegi-security-1.0.0.jar[groupid:acegisecurity,artifactid:acegi-security,version:
1.0.0].
Searching in repository : http://www.ibiblio.org/maven
WARNING: Failed to downlo
An user answer woukld be :
release a 2.0.5 version to publicise the bubfixes :)
Raphaël
2006/9/12, Brett Porter <[EMAIL PROTECTED]>:
Hi,
I'd like to propose moving the plugin-tools and reporting-impl to
shared, to decouple plugin releases from the maven core releases.
Right now, building the
16 matches
Mail list logo