I'm not sure what you mean when you say "moving plugins out". However,
we have to be careful with this. For several reasons. My belief is that
plugin should be hosted where it makes it easier for the plugin "owner"
to work on it.
For example, I wouldn't move the aspectwerkz plugin out just yet bec
> Not Fabrizio's doing at all, I'm just asking that you be
> careful in what you apply because the xdoc plugin is going to
> be one of the first bridges between component land, and with
> it maintainability, and the maven1 plugins.
Yep, will do.
> Who cares if it's spectacular or not, if Arnau
On Mon, 2004-04-19 at 23:54, Brett Porter wrote:
> > Yes, it was the entire change of the plugin I wasn't kosher
> > with as it changed entirely the css and markup and broke the
> > theme work Bob did. I definitely want to maintain what Bob
> > originally had because it is the first plugin I int
> Yes, it was the entire change of the plugin I wasn't kosher
> with as it changed entirely the css and markup and broke the
> theme work Bob did. I definitely want to maintain what Bob
> originally had because it is the first plugin I intend to
> swap out partially for the pure java version, t
On Mon, 2004-04-19 at 23:35, Brett Porter wrote:
> > And the approach building a set of developers for the
> > plugins? If it's akin to what has happened with Arnaud that
> > would be an excellent thing. A track record of producing good
> > quality patches and recognized by someone else trying t
> And the approach building a set of developers for the
> plugins? If it's akin to what has happened with Arnaud that
> would be an excellent thing. A track record of producing good
> quality patches and recognized by someone else trying to take
> care of that plugin. I think Vincent also menti
On Mon, 2004-04-19 at 19:00, Brett Porter wrote:
> There's a few discussions here, so on each point:
>
> Arnaud: +1 to Arnaud (welcome!)
> HOWEVER: my understanding is that 3 x +1 is not enough to jump in - aren't
> we required to wait 24 hours so those on the other side of the planet have a
> cha
Thanks. I've added it to the list of stuff to fix for RC3.
> -Original Message-
> From: Heritier Arnaud [mailto:[EMAIL PROTECTED]
> Sent: Monday, 19 April 2004 6:18 PM
> To: Maven Developers List
> Subject: RE: cvs commit: maven-plugins/multiproject plugin.jelly
>
>
> Hi brett,
>
> It
There's a few discussions here, so on each point:
Arnaud: +1 to Arnaud (welcome!)
HOWEVER: my understanding is that 3 x +1 is not enough to jump in - aren't
we required to wait 24 hours so those on the other side of the planet have a
chance to -1? (Not that this is necessary in this case, I just n
On Mon, 2004-04-19 at 18:18, Fabrizio Giustina wrote:
> > There's nothign stopping you from putting your own stuff in any
> web-enabled location and pointing any build you want at that location.
>
> I know, and I already do that... but you still need to ask people to add your new
> repository loc
> There's nothign stopping you from putting your own stuff in any
web-enabled location and pointing any build you want at that location.
I know, and I already do that... but you still need to ask people to add your new
repository location (http://maven-validator.sourceforge.net/) while the uplo
The following comment has been added to this issue:
Author: Olivier Mengu?
Created: Mon, 19 Apr 2004 6:03 PM
Body:
The JDepend author has applied my patch and published a new JDepend version: 2.7. See
http://www.clarkware.com/software/JDepend.html.
So the solution to this bug is
On Mon, 2004-04-19 at 16:38, Fabrizio Giustina wrote:
> Yes, please... start thinking about opening the doors for new committers on
> maven-plugins or on specific plugins only.
> I agree that cvs access should not be given away for free, but the list of plugins
> is too long to have so few people
Some manipulation error? ;-)
-Vincent
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: 19 April 2004 22:39
> To: [EMAIL PROTECTED]
> Subject: [jira] Assigned: (MPANNOUNCEMENT-2) Maven does not display
> anything when "maven announcement" is called
>
> Mess
Yes, please... start thinking about opening the doors for new committers on
maven-plugins or on specific plugins only.
I agree that cvs access should not be given away for free, but the list of plugins is
too long to have so few people taking the responsibility for all of them. Better
having peo
Message:
The following issue has been closed.
Resolver: Vincent Massol
Date: Mon, 19 Apr 2004 3:21 PM
Done. It would be a good idea to send an announcement to the Maven mailing list. May I
suggest you use the announcement plugin which automatically generates such
announcement. Sim
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVENUPLOAD-96
Here is an overview of the issue:
---
Emmanuel asked me to do it some weeks ago (to not take a risk that my patches were
refused).
I sent my CLA by mail.
Thanks a lot everybody.
Arnaud.
-Message d'origine-
De : Jason van Zyl [mailto:[EMAIL PROTECTED]
Envoyé : lundi 19 avril 2004 19:21
À : Maven Developers List
Objet : RE: [
On Mon, 2004-04-19 at 12:50, Heritier Arnaud wrote:
> Hello guys,
>
> Thanks a lot Emmanuel to suggest doing me a committer.
> I'm totally aggree that you should do the distinction between the two modules.
> In any case, I won't take the liberty to modify the maven core.
You certainly can, but t
On Mon, 2004-04-19 at 12:09, Vincent Massol wrote:
> +1 from me too for both the distinction and for Arnaud as a committer on
> the maven-plugins.
Cool, that's at least enough for commit privs for Arnaud anyway.
> Thanks
> -Vincent
>
> > -Original Message-
> > From: Jason van Zyl [mailto
Hello guys,
Thanks a lot Emmanuel to suggest doing me a committer.
I'm totally aggree that you should do the distinction between the two modules.
In any case, I won't take the liberty to modify the maven core.
I'm not yet an expert in it and I'll prefer to let more competent committers to do it.
+1 from me too for both the distinction and for Arnaud as a committer on
the maven-plugins.
Thanks
-Vincent
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: 19 April 2004 17:56
> To: Maven Developers List
> Subject: Re: [Vote] Arnaud Heritier as a committer
>
On Mon, 2004-04-19 at 11:47, Emmanuel Venisse wrote:
> >
> > I would like to start making a distinction here. A committer for
> > maven-plugins is fine, but not for the core.
>
> I'm +1 too for a distinction.
>
> >
> > If this distinction is fine, which we can control with the cvs avail
> > file
- Original Message -
From: "Jason van Zyl" <[EMAIL PROTECTED]>
To: "Maven Developers List" <[EMAIL PROTECTED]>
Sent: Monday, April 19, 2004 4:20 PM
Subject: Re: [Vote] Arnaud Heritier as a committer
> On Mon, 2004-04-19 at 10:00, Emmanuel Venisse wrote:
> > Howdy,
> >
> > As part of mav
On Mon, 2004-04-19 at 10:00, Emmanuel Venisse wrote:
> Howdy,
>
> As part of maven fixes and evolution, I'd like to add Arnaud as a committer.
> Since few month, he submit a lot of patchs for fix bugs and it's him that
> rewrite the PDF plugin.
>
> Moreover, it often takes part on the mailing lis
evenisse2004/04/19 07:09:33
Removed: maven-core/src/main/java/org/apache/maven/util
HttpUtils.java MimeBase64Encoder.java
Log:
Remove unused old classes
-
To unsubscribe, e-mail: [EMAIL PROTE
Howdy,
As part of maven fixes and evolution, I'd like to add Arnaud as a committer.
Since few month, he submit a lot of patchs for fix bugs and it's him that
rewrite the PDF plugin.
Moreover, it often takes part on the mailing list to help the other users.
My +1.
Emmanuel
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPMULTIPROJECT-26
Here is an overview of the issue:
evenisse2004/04/19 06:34:04
Modified:maven-core project.xml
Log:
Remove duplicate dependency.
Revision ChangesPath
1.9 +0 -5 maven-components/maven-core/project.xml
Index: project.xml
===
On Mon, 2004-04-19 at 09:00, Niclas Hedhman wrote:
> On Monday 19 April 2004 20:40, Jason van Zyl wrote:
> > Huh? You don't want to share dependencies anywhere?
>
> No. Just to say that
> xerces -> 2.4.0
> avalon-logkit -> 1.2
> jakarta-bcel -> 5.2
> log4j -> 1.2.1
>
> and so on.
>
> > > I wan
jvanzyl 2004/04/19 06:04:41
Modified:maven-project/src/test/java/org/apache/maven/project
AbstractProjectTestCase.java
DefaultProjectBuilderTest.java
ProjectReactorTest.java
maven-project/src/test/java
On Monday 19 April 2004 20:40, Jason van Zyl wrote:
> Huh? You don't want to share dependencies anywhere?
No. Just to say that
xerces -> 2.4.0
avalon-logkit -> 1.2
jakarta-bcel -> 5.2
log4j -> 1.2.1
and so on.
> > I want to have ONE place, where I can list the versions to use
> > for each arti
On Mon, 2004-04-19 at 07:57, Niclas Hedhman wrote:
> On Monday 19 April 2004 02:05, Jason van Zyl wrote:
>
> > To help you could give me a little tree description of your build and
> > describe how you would like things shared.
>
> > I would assume that ideally, you would like to a parent POM in
On Mon, 2004-04-19 at 02:50, [EMAIL PROTECTED] wrote:
> Jason van Zyl <[EMAIL PROTECTED]> wrote on 18/04/2004 01:22:36 AM:
>
> > On Sat, 2004-04-17 at 10:15, [EMAIL PROTECTED] wrote:
> > > vmassol 2004/04/17 07:15:57
> > >
> > > Modified:jetty/xdocs changes.xml
> > >jett
On Monday 19 April 2004 20:07, Vincent Massol wrote:
> This defeats the goal of centralizing dependency definitions. We find it
> better to have:
>
> &xml-apis;
This is really good tip... :o)
Niclas
--
+-//---+
| http://www.bali.ac |
| http://niclas.hedhman.or
Niclas Hedhman wrote on Monday, April 19, 2004 2:01 PM:
> On Monday 19 April 2004 04:11, Jörg Schaible wrote:
>
>> So my /myproject/build/entities directory contains the project.ent
>> and all the files that define the real entities like characters.ent,
>> versions.ent, ...
>>
>> project.ent co
> -Original Message-
> From: Niclas Hedhman [mailto:[EMAIL PROTECTED]
> Sent: 19 April 2004 13:50
> To: Maven Developers List
> Subject: Re: XML Catalogs
>
>
> Ok. We understand this pattern, and IMHO it is not applicable at all,
> since
> you can't have everything depend on everything.
On Monday 19 April 2004 04:11, Jörg Schaible wrote:
> So my /myproject/build/entities directory contains the project.ent and all
> the files that define the real entities like characters.ent,
> versions.ent, ...
>
> project.ent contains the lines:
>
> %character-entities;
> %version-entities;
>
On Monday 19 April 2004 02:05, Jason van Zyl wrote:
> To help you could give me a little tree description of your build and
> describe how you would like things shared.
> I would assume that ideally, you would like to a parent POM in very
> top-level directory in order to share as much as possibl
Ok. We understand this pattern, and IMHO it is not applicable at all, since
you can't have everything depend on everything.
However, the modified version is to have only the 'value entities' and use the
spelled-out dependencies for each artifact, like;
%index-of-entities;
&xml-apis-group;
&xm
The following comment has been added to this issue:
Author: Ben Walding
Created: Mon, 19 Apr 2004 5:02 AM
Body:
Indeed... I hadn't noticed this before. I'll take a look into it at some point.
-
View this comment:
Hi brett,
It seems that this commit introduced a bug.
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPMULTIPROJECT-25
You missed to update templates because the new collection is multiprojects instead of
reactorProjects.
Arnaud
-Message d'origine-
De : [EMAIL PROTECTED] [mailto:
42 matches
Mail list logo
