+1
On 11/29/06, John Tolentino <[EMAIL PROTECTED]> wrote:
+1
On 11/30/06, Jesse McConnell <[EMAIL PROTECTED]> wrote:
> I like it, nice way to solve the problem I think. I notice the
> javadoc plugin also addresses a problem I had with it a couple of
> months ago so I am all for releasing it.
>
+1
On 11/30/06, Jesse McConnell <[EMAIL PROTECTED]> wrote:
I like it, nice way to solve the problem I think. I notice the
javadoc plugin also addresses a problem I had with it a couple of
months ago so I am all for releasing it.
+1
jesse
On 11/29/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
From what I can tell this mail is talking about putting the assemble
in the top-level pom, not in the maven-cli pom.
In Geronimo we hook up assembly:attached to be executed by default
when `mvn install` is run with no problems. The result is, there is
one command to build modules and gener
All of these are meant to indicate programming errors - the RT
exceptions should be guarded by checking the validity of the POM used
to create the artifacts. As for the illegalstateexception - how is
the reports module getting handed a file that doesn't exist to report
on?
- Brett
On 30/
But we should be able to use the :single goal like we do for
maven-2.0.x until the other lifecycle things are sorted out.
- Brett
On 30/11/2006, at 2:41 PM, Wendy Smoak wrote:
On 11/28/06, Jason Dillon <[EMAIL PROTECTED]> wrote:
Why is this step needed:
cd maven-cli
mvn assembly:assembly
On 11/28/06, Jason Dillon <[EMAIL PROTECTED]> wrote:
Why is this step needed:
cd maven-cli
mvn assembly:assembly
Why not hook up assembly to the be performed with just `mvn install` ?
Possibly because of what John Casey describes here:
http://www.nabble.com/Re%3A-building-assemblies-from-th
Issue Subscription
Filter: Outstanding Repository Maintenance: Uploads (15 issues)
Subscriber: mavendevlist
Key Summary
MAVENUPLOAD-1257Please upload EZMorph-0.9.1
http://jira.codehaus.org/browse/MAVENUPLOAD-1257
MAVENUPLOAD-1250Upload org.hibernate:hibernate:jar:3.2.1.ga to i
Issue Subscription
Filter: Outstanding Repository Maintenance: Evangelism (34 issues)
Subscriber: mavendevlist
Key Summary
MEV-461 Missing pom for commons-logging-api-1.1
http://jira.codehaus.org/browse/MEV-461
MEV-459 Velocity should not depend on Velocity-dep
I like it, nice way to solve the problem I think. I notice the
javadoc plugin also addresses a problem I had with it a couple of
months ago so I am all for releasing it.
+1
jesse
On 11/29/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
I have fixed all the headers and checked them in.
jason.
O
I am abstaining from this vote. +0
- Joakim
Brett Porter wrote:
> Hi,
>
> There seemed to be no major objections to the logos presented, so I'll
> turn this into a formal vote.
>
> Please vote [1] for the one you would like and [2] for your second
> preference, if you have one, and so on.
>
> Id
Now that thing are working I suggest we start new threads for all the
votes.
Jason.
On 29 Nov 06, at 7:29 PM 29 Nov 06, Jason van Zyl wrote:
Hi,
The license insertion in to JAR, Source, and JavaDoc bundles is
working fine now and I have updated the headers to their correct
form for all
Hi,
The license insertion in to JAR, Source, and JavaDoc bundles is
working fine now and I have updated the headers to their correct form
for all resoures for the following Plugins:
Dependency
Checkstyle
JavaDoc
PMD
RAR
RAR
Release
Remote Resources
Source
Surefire
WAR
Anyone who has been w
I have fixed all the headers and checked them in.
jason.
On 29 Nov 06, at 6:54 PM 29 Nov 06, Joakim Erdfelt wrote:
Once the headers are fixed, +1
- Joakim
Daniel Kulp wrote:
Jason,
The files still don't have the proper Apache header on them. You
added
the old style (with the copyright
Once the headers are fixed, +1
- Joakim
Daniel Kulp wrote:
> Jason,
>
> The files still don't have the proper Apache header on them. You added
> the old style (with the copyright date) instead of the new style
> documented at:
> http://www.apache.org/legal/src-headers.html
> Those need to chan
Yep, I know Jason did the change today
On 11/29/06, Jukka Zitting <[EMAIL PROTECTED]> wrote:
Hi,
On 11/30/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
> You should be able to use a mirror while this gets fixed
> http://maven.apache.org/guides/mini/guide-mirror-settings.html
Yeah, I had no tro
Hi,
On 11/30/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
You should be able to use a mirror while this gets fixed
http://maven.apache.org/guides/mini/guide-mirror-settings.html
Yeah, I had no trouble setting myself up. I just wanted to let you
know that the mirrors.ibiblio.org redirect proba
You should be able to use a mirror while this gets fixed
http://maven.apache.org/guides/mini/guide-mirror-settings.html
On 11/29/06, Jukka Zitting <[EMAIL PROTECTED]> wrote:
Hi,
On 11/30/06, Jukka Zitting <[EMAIL PROTECTED]> wrote:
> It seems that the mirrors.ibiblio.org redirect doesn't work
Hi,
On 11/30/06, Jukka Zitting <[EMAIL PROTECTED]> wrote:
It seems that the mirrors.ibiblio.org redirect doesn't work well with
Maven 1.0.2. I just tried to download a new dependency from the
repository using 1.0.2, but apparently the 301 redirect is treated as
an error code.
Note that the pro
Hi,
It seems that the mirrors.ibiblio.org redirect doesn't work well with
Maven 1.0.2. I just tried to download a new dependency from the
repository using 1.0.2, but apparently the 301 redirect is treated as
an error code. See below:
__ __
| \/ |__ _Apache__ ___
| |\/| /
On 30/11/2006, at 1:11 AM, Jason van Zyl wrote:
On 29 Nov 06, at 1:35 AM 29 Nov 06, Brett Porter wrote:
You're oversimplifying it. There is no cycle when you run mvn
install, Maven is misdetecting it.
I cannot even run "mvn clean" in the plugins directory so I'm not
sure what you're t
Hi,
I am cooperating with Frank Seidinger on the J2ME plugin, and we need to
set the bootclasspath of the compiler plugin. This can be done in the
POM like this:
...
However, I want to use the Unified Emulator Interface to determine the
bootclasspath automatically and
On 29 Nov 06, at 11:22 AM 29 Nov 06, Don Sizemore wrote:
|Is mirrors.ibiblio.org balancing the load on the mirrors? Will you
leave
|www.ibiblio.org/maven and www.ibiblio.org/maven2 as redirects to
the new
|location? We need to check for maven1 users that still point
there, but
|for mave
[1] Top Left
[2] Lower Right
On 11/7/06, Brett Porter <[EMAIL PROTECTED]> wrote:
Hi,
There seemed to be no major objections to the logos presented, so
I'll turn this into a formal vote.
Please vote [1] for the one you would like and [2] for your second
preference, if you have one, and so on.
Hi,
LL: 1
LR: 2
UR: 3
Vincent Siveton wrote:
[1] for Top Right and [2] for Lower Left
Cheers,
Vincent
On 08/11/2006, at 12:43 PM, Brett Porter wrote:
Hi,
There seemed to be no major objections to the logos presented, so I'll
turn
this into a formal vote.
Please vote [1] for the one y
|Is mirrors.ibiblio.org balancing the load on the mirrors? Will you leave
|www.ibiblio.org/maven and www.ibiblio.org/maven2 as redirects to the new
|location? We need to check for maven1 users that still point there, but
|for maven2 is fine as they already use repo1.maven.org as central
Hi C
Jason,
The files still don't have the proper Apache header on them. You added
the old style (with the copyright date) instead of the new style
documented at:
http://www.apache.org/legal/src-headers.html
Those need to change.
Also, the pom.xml files need to have the header as well. Note: the
Hi,
This is a group release to attempt to deal with the licensing
resources that need to be packaged up in all the archives we
distribute. This is, in particular, and attempt to deal with the JARs
we release. Namely the binary, source, and javadoc JARs we create
with the JAR, Source, and
Nice!
On 29 Nov 06, at 9:16 AM 29 Nov 06, Mark Hobson wrote:
On 07/07/06, Mik Kersten <[EMAIL PROTECTED]> wrote:
There should be no problem. Just file a Mylar bug report with the
structure
you want and we can iterate from there. If the easiest way to do
that is
for us to build those JARs
On 07/07/06, Mik Kersten <[EMAIL PROTECTED]> wrote:
There should be no problem. Just file a Mylar bug report with the structure
you want and we can iterate from there. If the easiest way to do that is
for us to build those JARs via Maven instead of plain Ant I'm happy to do
that too.
Finally
On 29 Nov 06, at 1:35 AM 29 Nov 06, Brett Porter wrote:
You're oversimplifying it. There is no cycle when you run mvn
install, Maven is misdetecting it.
I cannot even run "mvn clean" in the plugins directory so I'm not
sure what you're talking about. Try it.
When you generate a site, i
Hi Raphael,
> -Original Message-
> From: leahpar [mailto:[EMAIL PROTECTED]
> Sent: mercredi 29 novembre 2006 14:14
> To: dev@maven.apache.org
> Subject: Re: How to handle different tool versions in Maven plugins?
>
>
> hello,
>
> option 1 will be a good solution with the drawback that s
hello,
option 1 will be a good solution with the drawback that some people will
fall into trouble because they are "not allowed" to change anything and
cannot upgrade (belong to theses...)
option 3 is the best world to me
I think that a naming convention to express the version of the underlying
On 29 Nov 06, at 1:36 AM 29 Nov 06, Brett Porter wrote:
Is this documented anywhere? I don't quite understand what it means.
Just like the remote resources plugin I'll finish the doco and run it
through docck.
On 29/11/2006, at 5:29 PM, [EMAIL PROTECTED] wrote:
Author: jvanzyl
Date: Tu
[EMAIL PROTECTED] a écrit :
Emmanuel Hugonnet <[EMAIL PROTECTED]> schrieb am 28.11.2006
15:54:34:
I have to edit the pom.xml of
maven-plugin-tools-java to set the version of qdox to 1.6.1 and then
all
is fine.
Hi,
This is a temporary solution I use with a proximity
Emmanuel Hugonnet <[EMAIL PROTECTED]> schrieb am 28.11.2006
15:54:34:
> >> I have to edit the pom.xml of
> >> maven-plugin-tools-java to set the version of qdox to 1.6.1 and then
all
> >> is fine.
> Hi,
> This is a temporary solution I use with a proximity proxy and an
> overriding pom.xml bu
Hi guys,
I'm rather curious about that construction mentioned below, but
couldn't get any responses on the user-list. would you mind, providing
me a pointer to some information or if it's supposed to work at all?
sorry for hesitating,
-Stefan
-- Forwarded message --
From: Stefan
Sounds weird. Why do you want to do that?
Anyway, once maven has loaded the pom, the dependencies are resolved. The
only thing I see is to put a variable in your version(s) and switch the
parameter on command line.
But I won't certainly find this a best practice.
Cheers,
Stéphane
On 11/29/06,
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: mardi 28 novembre 2006 23:36
> To: Maven Developers List
> Subject: Re: How to handle different tool versions in Maven plugins?
>
> I'd actually go with (1), creating a branch for bugfixes on the old
> one. (3) s
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
> Carlos Sanchez
> Sent: mardi 28 novembre 2006 23:20
> To: Maven Developers List
> Subject: Re: How to handle different tool versions in Maven plugins?
>
> waht about having 2.x branch for clover 1 and
39 matches
Mail list logo
