brett 2003/09/10 23:27:22
Added: src/plugins-build/scm/xdocs index.xml
src/plugins-build/scm/xdocs/releases/v1.0 index.xml
Log:
Add required index files
Revision ChangesPath
1.1 maven/src/plugins-build/scm/xdocs/index.xml
Index: in
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-808
Here is an overview of the issue:
--
The following comment has been added to this issue:
Author: bmak
Created: Wed, 10 Sep 2003 11:16 PM
Body:
bug was because I added a tag to project.xml file
-
View the issue:
http://jira.codehaus.org/secure/View
Last 500 lines of a clean bootstrap build of maven at 20030910-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
> I'm not planning (and I didn't think the roadmap had) any new
> features
> atm, especially after you moved them :-)
:) I was referring more to any of the changes to the ant project/jelly
context to fix the leak that might screw up other code. Sounds like this is
going to be much less now than
On Wed, 2003-09-10 at 20:33, [EMAIL PROTECTED] wrote:
> I'd rather stick with the roadmap we have. If the memory leak is taking
> too long, lets move it to 1.0-final.
I think what is most important is a release that allows the decoupling
of the plugins.
There are also a lot of fixes that could
Brett Porter <[EMAIL PROTECTED]> wrote on 11/09/2003 11:15:51 AM:
> My concern is calling something RC1 then making changes to the way
things
> work that could break other people's stuff before 1.0.
I'm not planning (and I didn't think the roadmap had) any new features
atm, especially after you
My concern is calling something RC1 then making changes to the way things
work that could break other people's stuff before 1.0.
Also, calling something RC1 before we really consider it worthy of that is
probably not great.
Also, I'm not sure 1.0 is the next jump after RC1. 1.0-final should be
1.0
I'd rather stick with the roadmap we have. If the memory leak is taking
too long, lets move it to 1.0-final.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Brett Porter <[EMAIL PROTECTED]> wrote on 11/09/2003 09:27:31 AM:
> I'm wondering whether we shoul
I'm wondering whether we should release a final beta from what is in CVS
now.
Reasoning:
- has plugin dependencies & downloading
- has some reasonably frequently asked Q's already fixed (like multiproject
bugs)
- RC1 seems a little while off still, and the last big change has a large
risk of introd
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-807
Here is an overview of the issue:
--
Tabs
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
[EMAIL PROTECTED] wrote on 11/09/2003 12:19:42 AM:
> evenisse2003/09/10 07:19:42
>
> Modified:src/plugins-build/tjdo plugin.jelly project.xml
>src/plugins-build/tjdo/xdocs
Thanks.
- Original Message -
From: <[EMAIL PROTECTED]>
To: "Maven Developers List" <[EMAIL PROTECTED]>
Sent: Wednesday, September 10, 2003 4:10 PM
Subject: Re: cvs commit: maven/src/plugins-build/xdoc plugin.jelly
> I'm happy for us to add it back in once we work out why 'maven site' is
evenisse2003/09/10 08:09:45
Added: src/plugins-build/tjdo/announcements 1.0.ann
Log:
Release the plugin
Revision ChangesPath
1.1 maven/src/plugins-build/tjdo/announcements/1.0.ann
Index: 1.0.ann
===
evenisse2003/09/10 08:09:06
maven/src/plugins-build/tjdo/announcements - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Message:
The following issue has been closed.
Resolver: Emmanuel Venisse
Date: Wed, 10 Sep 2003 9:35 AM
Done
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-736
Here is an overview of
Message:
The following issue has been closed.
Resolver: Emmanuel Venisse
Date: Wed, 10 Sep 2003 9:35 AM
Done
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-778
Here is an overview of
evenisse2003/09/10 07:19:42
Modified:src/plugins-build/tjdo plugin.jelly project.xml
src/plugins-build/tjdo/xdocs changes.xml goals.xml index.xml
Log:
Apply MAVEN-736
Revision ChangesPath
1.4 +85 -65maven/src/plugins-build/tjdo/plugin.jelly
I
I'm happy for us to add it back in once we work out why 'maven site' is
interfering with it.
p.s. I really like the output!
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
[EMAIL PROTECTED] wrote on 10/09/2003 11:26:08 PM:
> evenisse2003/09/10 06:26:
evenisse2003/09/10 06:26:07
Modified:src/plugins-build/xdoc plugin.jelly
Log:
Remove jcoverage report from default reports.
Revision ChangesPath
1.47 +0 -1 maven/src/plugins-build/xdoc/plugin.jelly
Index: plugin.jelly
=
On Wed, 2003-09-10 at 03:54, Rademacher Tobias wrote:
> Hi James,
>
> > We are moving away from accepting every and all plugins for
> > distribution
> > with Maven. Some changes have taken place in the core that will allow
> > the distribution of plugins apart from Maven.
> >
> > Even right now
That's not my point.
Other projects may use the default set and it may not work for them as it
doesn't for Maven.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
"Emmanuel Venisse" <[EMAIL PROTECTED]> wrote on 10/09/2003 06:57:06 PM:
> I add jcoverage re
Message:
The following issue has been closed.
Resolver: Emmanuel Venisse
Date: Wed, 10 Sep 2003 6:02 AM
Done
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-639
Here is an overview of
evenisse2003/09/10 03:47:44
Modified:src/plugins-build/javadoc plugin.jelly
src/plugins-build/javadoc/xdocs changes.xml properties.xml
Log:
MAVEN-639. Add maven.javadoc.overview property.
Revision ChangesPath
1.22 +4 -0 maven/src/plugins-build/jav
Hi Thiago,
I'd really like to have a J2ME plugin. Sourceforge's maven-plugins might
be a distribution channel. Tell me how you're getting on. As I said, I'm
keen on testing your plugin.
Dominik
On Mon, 2003-09-08 at 21:02, Thiago Leão Moreira wrote:
> Hi,
>
> I am a Maven's user and I
Sorry for the late reply, and thanks for looking into this,
It seems that this has been fixed - the jar plugin uses
${pom.specificationVersion} for the Specification-Version attribute
(when I last looked it was using ${pom.version}.
-Opprinnelig melding-
Fra: Ben Walding [mailto:[EMAIL
Message:
The following issue has been closed.
Resolver: Emmanuel Venisse
Date: Wed, 10 Sep 2003 5:09 AM
Done.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-805
Here is an overview o
evenisse2003/09/10 02:54:22
Modified:src/plugins-build/javadoc plugin.jelly plugin.properties
src/plugins-build/javadoc/xdocs changes.xml properties.xml
Log:
MAVEN-805. Add maven.javadoc.useexternalfile property.
Revision ChangesPath
1.21 +2 -1 ma
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-806
Here is an overview of the issue:
--
I add jcoverage report in default reports, but maven site doesn't use
default.
- Original Message -
From: <[EMAIL PROTECTED]>
To: "Maven Developers List" <[EMAIL PROTECTED]>
Sent: Tuesday, September 09, 2003 5:44 PM
Subject: Re: cvs commit: maven/src/plugins-build/xdoc plugin.jelly
> Sh
The following issue has been updated:
Updater: Simone Zorzetti (mailto:[EMAIL PROTECTED])
Date: Wed, 10 Sep 2003 4:08 AM
Comment:
Patch to src\plugins-build\javadoc\plugin.jelly
Changes:
Attachment changed to path.txt
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-805
Here is an overview of the issue:
--
Message:
The following issue has been closed.
Resolver: Emmanuel Venisse
Date: Wed, 10 Sep 2003 3:54 AM
Done.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-803
Here is an overview o
evenisse2003/09/10 01:39:47
Modified:src/java/org/apache/maven/project Repository.java
Log:
Fix MAVEN-803.
Revision ChangesPath
1.17 +2 -2 maven/src/java/org/apache/maven/project/Repository.java
Index: Repository.java
=
Hi James,
> We are moving away from accepting every and all plugins for
> distribution
> with Maven. Some changes have taken place in the core that will allow
> the distribution of plugins apart from Maven.
>
> Even right now it is not that hard to package up plugins for
> your users
> and the
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-804
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-803
Here is an overview of the issue:
--
Thiago Leão Moreira wrote:
>I am a Maven's user and I work with J2ME plataform. I wrote plugins
> to improve the process of development of J2ME software. So I would like
> to add these plugins in Maven distribution. How can do this
Maven wiki has some helpful infomration:
http://wiki.code
38 matches
Mail list logo
