brett 2003/09/11 22:49:52
Modified:src/test/java/org/apache/maven/project
ProjectInheritanceTest.java
Log:
CanonicalPath continues to wreak havoc on assertEquals
Revision ChangesPath
1.39 +1 -3
maven/src/test/java/org/apache/maven/proj
The extracted ones - I think downloaded stuff goes to MAVEN_HOME.
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Friday, 12 September 2003 3:13 PM
> To: Maven Developers List
> Subject: RE: Core plugins?
>
>
> Sounds good. That's where they go now, righ
Sounds good. That's where they go now, right? $MAVEN_HOME_LOCAL/plugins.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Brett Porter <[EMAIL PROTECTED]> wrote on 12/09/2003 02:25:38 PM:
> > We could remove the installation into MAVEN_HOME as part of
> >
dion2003/09/11 21:57:31
Modified:src/plugins-build/jellydoc/src/main/org/apache/maven/jellydoc
XMLDoclet.java
Log:
Remove .* imports
Revision ChangesPath
1.2 +33 -13
maven/src/plugins-build/jellydoc/src/main/org/apache/maven/jellydoc/
Message:
The following issue has been closed.
Resolver: dion gillard
Date: Fri, 12 Sep 2003 12:12 AM
Applied today
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-756
Here is an overv
dion2003/09/11 21:42:17
Modified:src/plugins-build/xdoc/xdocs changes.xml
src/plugins-build/xdoc/src/plugin-resources/templates
cvs-usage.xml
Log:
Applied MAVEN-756: cvs-usage.xml breaks on non-cvs scm URL
Revision ChangesPath
1.
dion2003/09/11 21:41:21
Modified:src/java/org/apache/maven/project Repository.java
Log:
Applied MAVEN-756: cvs-usage.xml breaks on non-cvs scm URL
Revision ChangesPath
1.18 +12 -1 maven/src/java/org/apache/maven/project/Repository.java
Index: Repository.
The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Thu, 11 Sep 2003 11:53 PM
Changes:
Fix Version changed to 1.0-final
Fix Version changed from 1.0-rc1
---
The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Thu, 11 Sep 2003 11:52 PM
Changes:
Fix Version changed to 1.1
Fix Version changed from 1.0-rc1
-
> We could remove the installation into MAVEN_HOME as part of
> the plugin
> processing. No big deal there.
I think that is where plugin:download is targetted to as well. If it is not
installed to the central plugin dir, then that will be out of sync with the
expanded plugins dir.
> What about
dion2003/09/11 21:22:58
Modified:src/plugins-build/multiproject plugin.jelly
Log:
Change banner to something more sensible
Revision ChangesPath
1.29 +1 -1 maven/src/plugins-build/multiproject/plugin.jelly
Index: plugin.jelly
==
Last 500 lines of a clean bootstrap build of maven at 20030911-2200
[exec] Copying 1 file to
/usr/local/builds/maven/src/maven/src/plugins-build/webserver/target/classes/plugin-resources
[exec] Copying 4 files to
/usr/local/builds/maven/src/maven/src/plugins-build/webserver/target
Brett Porter <[EMAIL PROTECTED]> wrote on 12/09/2003 09:07:04 AM:
[snip]
> To obtain a plugin, you can give a dependency, or use the
plugin:download
> goal. Either way, it gets installed into MAVEN_HOME (this is a problem
at
> the moment - we're back to the beta-9 and before days of not having a
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? :-) ;-)
>
> http://www.picocontainer.org/
>
> Aslak
Religious Wars
-
This is underway, but needs someone to finish it off.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Norbert Pabiś <[EMAIL PROTECTED]> wrote on 12/09/2003 01:05:51 AM:
> Vincent Massol wrote:
> > What we seem to need is a way to prevent folks having to en
"Vincent Massol" <[EMAIL PROTECTED]> wrote on 12/09/2003 01:19:36 AM:
> Hi Norbert,
>
> 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
dion2003/09/11 18:45:56
Modified:src/plugins-build/eclipse/src/plugin-resources/templates
launch.jelly
Log:
Use resource name, not resource location
Revision ChangesPath
1.3 +1 -1
maven/src/plugins-build/eclipse/src/plugin-resources
The following comment has been added to this issue:
Author: Aslak Hellesoy
Created: Thu, 11 Sep 2003 8:12 PM
Body:
It would be even better to be able to specify in project.xml's to specify
whether a particula jar should go into the Class-Path
Aslak
--
Message:
The following issue has been closed.
Resolver: dion gillard
Date: Thu, 11 Sep 2003 7:24 PM
Already fixed in CVS
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-810
Here is an
Martin Skopp <[EMAIL PROTECTED]> wrote on 11/09/2003 08:25:30 PM:
> To be honest, I don't really care how the next release is named, as soon
> as it comes in a few weeks ;-)
I hear ya.
> IMHO the essential questions are:
>
> 1) which will be the first rel with the memory leak be fixed ?
There'
"Vincent Massol" <[EMAIL PROTECTED]> wrote on 11/09/2003 05:44:52 PM:
> Hi,
>
> Brett mentioned in a an earlier email today that the idea of RC1 would
> be a maven core containing core plugins and other plugins which would
> not be part of the main maven distribution.
That's not what I thought h
I should clarify what I was getting at.
The reason to select and bundle "core" plugins is because they are
frequently used, and will be downloaded first run anyway. We want to save
the user some time. The analogy with Ant would be the regular tasks vs. the
optional tasks - however they often do di
There are a few cases like this. There is also a repository tag.
However, I still use deploy because SSH1 works.
Ideally, artifact could handle the tasks of deploy and repository, and
things like dist and *:deploy should use it. At the moment, war uses
artifact and jar uses deploy, and it's a pai
On Thu, 11 Sep 2003, [ISO-8859-2] Aslak Helles?y wrote:
> Jason van Zyl wrote:
>
> >
> >Yes, things will be much further with components. I promise :-)
> >
> >
> Hmmm. Components. Have you chosen a container yet? :-) ;-)
>
> http://www.picocontainer.org/
I believe that http://plexus.codehaus.org/
Jason van Zyl wrote:
Yes, things will be much further with components. I promise :-)
Hmmm. Components. Have you chosen a container yet? :-) ;-)
http://www.picocontainer.org/
Aslak
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
On Thu, 2003-09-11 at 13:49, Rafal Krzewski wrote:
> Norbert Pabiś wrote:
>
> > Yes.
> > You said you don't want users to have 20 dependencies in project.xml.
> > I do not want to have any. If there will default project.xml with
> > preferred versions
> > with a possibility to change it - that sou
Norbert Pabiś wrote:
> Yes.
> You said you don't want users to have 20 dependencies in project.xml.
> I do not want to have any. If there will default project.xml with
> preferred versions
> with a possibility to change it - that sounds good to me.
Sounds interesting, but it's rather hard to achi
Hi all,
Not sure, but the deploy plugin looks like it may have gotton stale.. Should it use
the artifact tags? It seems like there needs to be a plugin to wrap the basic
artifact tags..?
Eric
-
To unsubscribe, e-mail: [EMAIL
Vincent Massol wrote:
My view is that effectively whenever Maven is released it will provide
a default list of core plugins in their most recent released version.
Of course, this default project.xml file can be changed at any time by a user.
Actually, if you wish you could keep it from one versio
> -Original Message-
> From: Norbert Pabiœ [mailto:[EMAIL PROTECTED]
> Sent: 11 September 2003 18:28
> To: Maven Developers List
> Subject: Re: Core plugins?
>
> Vincent Massol wrote:
> > How do you tell a given project to use such version of the plugin?
> This is good point. Of course y
Vincent Massol wrote:
How do you tell a given project to use such version of the plugin?
This is good point. Of course you can add -D's but that would be ugly
and inconvenient. are better here.
But what about such a case.
You have maven-site-plugin-1.2, maven-site-plugin-1.3, maven-site-beta2
Do I
> -Original Message-
> From: Norbert Pabiœ [mailto:[EMAIL PROTECTED]
> Sent: 11 September 2003 17:41
> To: Maven Developers List
> Subject: Re: Core plugins?
>
> Vincent Massol wrote:
> > Hi Norbert,
> >
> > First my mail wasn't about discussing the way plugins are
referenced.
> > I tho
Vincent Massol wrote:
Hi Norbert,
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 ).
I don't want to change that. All I wanted is to share that idea about
plugin independence from project.
T
Hi Norbert,
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 ).
Then your solution doesn't handle plugin versions. One project may want to use such
plugin in version 1.0 and another may want to
Vincent Massol wrote:
What we seem to need is a way to prevent folks having to enter 20 plugin
dependencies in all their project.xml. These are the "core plugin". But
these plugins do not have to be located in Maven nor do they need to be
distributed with Maven.
This is a little weird.
project.xml
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-810
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-809
Here is an overview of the issue:
--
Ok. Cool. We are saying the same thing. Just a matter of time. I'm fine
with having a transition period where we keep some "core plugin" stuff
in Maven core.
Thanks
-Vincent
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: 11 September 2003 15:38
> To: Maven De
On Thu, 2003-09-11 at 09:19, Vincent Massol wrote:
> > -Original Message-
> > From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> > Sent: 11 September 2003 15:01
> > To: Maven Developers List
> > Subject: Re: Core plugins?
> >
> > On Thu, 2003-09-11 at 03:44, Vincent Massol wrote:
> > > Hi,
>
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: 11 September 2003 15:01
> To: Maven Developers List
> Subject: Re: Core plugins?
>
> On Thu, 2003-09-11 at 03:44, Vincent Massol wrote:
> > Hi,
> >
> > Brett mentioned in a an earlier email today that the idea o
evenisse2003/09/11 06:03:56
Modified:src/java/org/apache/maven/plugin PluginCacheManager.java
src/java/org/apache/maven/project ArtifactType.java
Dependency.java Resource.java
Log:
detab
Revision ChangesPath
1.16 +1 -1 mave
On Thu, 2003-09-11 at 03:44, Vincent Massol wrote:
> Hi,
>
> Brett mentioned in a an earlier email today that the idea of RC1 would
> be a maven core containing core plugins and other plugins which would
> not be part of the main maven distribution.
>
> What I don't understand is the concept of "
evenisse2003/09/11 05:57:10
Modified:src/plugins-build/tjdo plugin.jelly plugin.properties
src/plugins-build/tjdo/xdocs changes.xml index.xml
properties.xml
Log:
detab
Revision ChangesPath
1.5 +80 -80maven/src/plugins-build
vmassol 2003/09/11 05:14:10
Modified:src/plugins-build/cactus/xdocs changes.xml goals.xml
src/plugins-build/cactus plugin.jelly
Log:
New cactus:jar-install goal to install the Cactus jar in the local
Maven repository. This is useful if you wish to put Cactus test clas
vmassol 2003/09/11 05:04:01
Modified:src/plugins-build/cactus/xdocs changes.xml goals.xml
src/plugins-build/cactus plugin.jelly
Log:
New cactus:jar goal to generate a jar containing the Cactus test
classes. This is useful if you wish to put Cactus test classes in one
vmassol 2003/09/11 04:58:02
Modified:src/plugins-build/cactus/sample project.xml
Log:
Keep the cactus sample project at version 1.0 to simplify version management.
Revision ChangesPath
1.4 +2 -2 maven/src/plugins-build/cactus/sample/project.xml
Index: proj
On Thu, 2003-09-11 at 01:27, Brett Porter wrote:
> I'm wondering whether we should release a final beta from what is in CVS
> now.
To be honest, I don't really care how the next release is named, as soon
as it comes in a few weeks ;-)
IMHO the essential questions are:
1) which will be the first
Hi,
Brett mentioned in a an earlier email today that the idea of RC1 would
be a maven core containing core plugins and other plugins which would
not be part of the main maven distribution.
What I don't understand is the concept of "code plugins". For me a
plugin is a plugin and they should all be
48 matches
Mail list logo
