Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-816
Here is an overview of the issue:
--
On Fri, 2003-09-12 at 12:04, Norbert Pabiś wrote:
> Jason van Zyl wrote:
> > I don't think so, Aslak likes his container and I like mine :-) But
> > there's no reason Plexus can't support Pico components. It has other
> > factories. If people write components for Picocontainer we can use them.
> >
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-815
Here is an overview of the issue:
--
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-814
Here is an overview of the issue:
--
The following issue has been updated:
Updater: Samuel Mulube (mailto:[EMAIL PROTECTED])
Date: Fri, 12 Sep 2003 12:01 PM
Comment:
This patch seemed to solve the problem for me, but I don't really know why. How the
Java classloader works always seems a little bit like voodoo to me, s
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-813
Here is an overview of the issue:
--
> -Original Message-
> From: Norbert Pabiś [mailto:[EMAIL PROTECTED]
> Sent: Friday, September 12, 2003 6:05 PM
> To: Maven Developers List
> Subject: [offtopic] Re: Core plugins?
>
>
> Jason van Zyl wrote:
> > I don't think so, Aslak likes his container and I like mine :-) But
> > there'
Jason van Zyl wrote:
I don't think so, Aslak likes his container and I like mine :-) But
there's no reason Plexus can't support Pico components. It has other
factories. If people write components for Picocontainer we can use them.
Not a problem. As for Picocontainer itself, I'm really not sold on t
On Thu, 2003-09-11 at 22:36, [EMAIL PROTECTED] wrote:
> Aslak Helles?y <[EMAIL PROTECTED]> wrote on 12/09/2003 08:18:12 AM:
>
> > Jason van Zyl wrote:
> >
> > >
> > >Yes, things will be much further with components. I promise :-)
> > >
> > >
> > Hmmm. Components. Have you chosen a container yet?
Vincent Massol wrote:
> Why? You're making the assumption that the plugins are part of Maven
> core! However, if you consider that Maven core is not about the plugins,
> then, you don't care if the plugins come in binary form. Same as you
> don't want to build jelly from the source, right?
I thin
> -Original Message-
> From: Rafal Krzewski [mailto:[EMAIL PROTECTED]
> Sent: 12 September 2003 14:29
> To: Maven Developers List
> Subject: Re: Core plugins?
>
> Vincent Massol wrote:
> > I'd like to understand (I guess I should read the build script
code).
> > Could you please describe
Vincent Massol wrote:
> I'd like to understand (I guess I should read the build script code).
> Could you please describe in more details why we would shoot ourselves
> in the foot?
First off, you should watch closely the messages that show up during the
bootstrap. The last phase is "Building Mave
Rafal,
I'd like to understand (I guess I should read the build script code).
Could you please describe in more details why we would shoot ourselves
in the foot?
The way I understand things is that we have an Ant build file that
generates the maven jar and a minimal maven directory structure. Why
The following comment has been added to this issue:
Author: Simone Zorzetti
Created: Fri, 12 Sep 2003 3:32 AM
Body:
Yuo're right, sorry for the mess! I'll patch it.
-
View the issue:
http://jira.codehaus.org/se
Vincent Massol wrote:
> However, as Jason pointed out, I agree that we can do it in 2 steps.
> Step 1, keep the core plugins in Maven core while moving others out.
> Step 2, separate all plugins from Maven core.
I don't think we should ever go to step 2. Some of the plugins are
*required* to buil
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: 12 September 2003 01:07
> To: 'Maven Developers List'
> Subject: RE: Core plugins?
>
> I should clarify what I was getting at.
>
> The reason to select and bundle "core" plugins is because they are
> frequently
The following comment has been added to this issue:
Author: dion gillard
Created: Fri, 12 Sep 2003 3:02 AM
Body:
There's a lot wrong with this patch.
a) It uses ant:property outside the
b) It uses !(pom.build.resources != null), which means if the resources are null is
the only
The following issue has been updated:
Updater: Simone Zorzetti (mailto:[EMAIL PROTECTED])
Date: Fri, 12 Sep 2003 2:40 AM
Changes:
Attachment changed to patch.txt
-
For a full history of the issue, s
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-812
Here is an overview of the issue:
--
[EMAIL PROTECTED] wrote:
First my mail wasn't about discussing the way plugins are
referenced. I thought this had already been discussed and agreed (i.
e. using project.xml and ).
This is only one solution, and not one we want to enforce on users.
The plugin plugin has a partially completed goal
The following issue has been updated:
Updater: Simone Zorzetti (mailto:[EMAIL PROTECTED])
Date: Fri, 12 Sep 2003 2:30 AM
Comment:
This is the java package needed.
Changes:
Attachment changed to cleracselib.zip
--
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-811
Here is an overview of the issue:
--
22 matches
Mail list logo
