dion2003/12/04 20:50:12
Modified:javadoc/xdocs changes.xml
Log:
Default to useexternalfile = yes
Revision ChangesPath
1.13 +1 -0 maven-plugins/javadoc/xdocs/changes.xml
Index: changes.xml
===
dion2003/12/04 20:33:49
Modified:javadoc plugin.properties
Log:
Default to useexternalfile = yes
Revision ChangesPath
1.9 +1 -1 maven-plugins/javadoc/plugin.properties
Index: plugin.properties
Jason van Zyl <[EMAIL PROTECTED]> wrote on 05/12/2003 01:35:05 PM:
> Dion,
>
> You mind if I add the maven archive building stuff to the repository
> plugin?
Sounds fine, but which archive?
> I figure a tag to build the archive and then the repository plugin can
> have some logic for unpacking
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPCLOVER-13
Here is an overview of the issue:
Dion,
You mind if I add the maven archive building stuff to the repository
plugin?
I figure a tag to build the archive and then the repository plugin can
have some logic for unpacking and verifying and then uploading the stuff
to ibiblio.
I'd like to make it a bunch of beans so that we can manua
On Thu, 2003-12-04 at 18:18, Brett Porter wrote:
> > This is not directed at you exclusively. It is directed at my
> > first attempt, Dion's subsequent attempt and your attempt.
> > The problem with the attempts is that the core is so gory
> > that collaboration is difficult at best.
>
> I unde
> This is not directed at you exclusively. It is directed at my
> first attempt, Dion's subsequent attempt and your attempt.
> The problem with the attempts is that the core is so gory
> that collaboration is difficult at best.
I understand - I really meant to explain why it is currently stalle
On Thu, 2003-12-04 at 17:52, Brett Porter wrote:
> > > Except that there are two setup steps now instead of one.
> >
> > Sorry I'm missing something, what are the two setups?
>
> Need to checkout maven, then maven-plugins, then set the properties
> appropriately if you didn't use the defaults.
Y
> > Except that there are two setup steps now instead of one.
>
> Sorry I'm missing something, what are the two setups?
Need to checkout maven, then maven-plugins, then set the properties
appropriately if you didn't use the defaults.
> No, as part of the bootstrap you have to check out modules.
On Thu, 2003-12-04 at 17:27, Brett Porter wrote:
> > All the plugins are in ../maven-plugins and the location
> > specified is control in the project.properties in the core
> > Maven build.
>
> I know - I'm trying to find out where Jorg has something screwy because it
> works for everyone else.
On Thu, 2003-12-04 at 17:23, Brett Porter wrote:
> We need to stop changing the roadmap and decide now. I thought we'd already
> done that, but here goes again...
>
> The 3 options:
> 1) release MAVEN 1.0 RC1 as Maven 1.0 final with any non-plugin-context
> related bugs backported off the branch.
> All the plugins are in ../maven-plugins and the location
> specified is control in the project.properties in the core
> Maven build.
I know - I'm trying to find out where Jorg has something screwy because it
works for everyone else.
>
> > You are only attempting to build with these plugins:
We need to stop changing the roadmap and decide now. I thought we'd already
done that, but here goes again...
The 3 options:
1) release MAVEN 1.0 RC1 as Maven 1.0 final with any non-plugin-context
related bugs backported off the branch. Kill the branch and start 1.1 with
the new model.
2) start in
On Thu, 2003-12-04 at 17:07, Brett Porter wrote:
> IS everything in ../maven-plugins? Is there a build.properties file
> overriding some property?
All the plugins are in ../maven-plugins and the location specified is
control in the project.properties in the core Maven build.
> You are only attemp
IS everything in ../maven-plugins? Is there a build.properties file
overriding some property?
You are only attempting to build with these plugins:
[exec] Maven Eclipse Plug-in
[exec] Maven Genapp Plugin
[exec] Maven JBuilder Plug-in
[exec] Maven WAR Plugin
Looks like moving the b
vmassol 2003/12/04 13:46:36
Modified:clover plugin.jelly plugin.properties
clover/xdocs properties.xml changes.xml
Log:
Conditionally instrument test classes too. To instrument test classes set the
maven.clover.instrument.tests to true.
Note: This feature is st
On Thu, 2003-12-04 at 12:58, Alain Javier Guarnieri del Gesu wrote:
> How does one specify the the bootclasspath to the java task? I don't
> see it in the java plugin code. I've hard coded my custom
> bootclasspath into a copy of the plugin.
Stop cross-posting between the dev and user list.
> Eve
On Thu, 2003-12-04 at 13:06, Vincent Massol wrote:
> Why not simply release Maven 1.0 now (from the 1.0 branch)? There are
> some limitations sure but they will be addressed in Maven 1.1.
That's what I recommended about a month ago and you were one of the
people who advised against that :-) I'm fi
Why not simply release Maven 1.0 now (from the 1.0 branch)? There are
some limitations sure but they will be addressed in Maven 1.1.
I think it's much less work (and less risky) than trying to create
something new altogether. I'm really worried by introducing completely
new code when we should act
How does one specify the the bootclasspath to the java task? I don't
see it in the java plugin code. I've hard coded my custom
bootclasspath into a copy of the plugin.
Even better than setting a bootclasspath would be the ability to
prepend jars to the bootclasspath specified by javac. I'm on OS
The following issue has been updated:
Updater: Alain Javier Guarnieri del Gesu (mailto:[EMAIL PROTECTED])
Date: Thu, 4 Dec 2003 11:57 AM
Comment:
This patch first copies the source files to a temporary directory, applying includes
and excludes, and specifies the temporary directory
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPJAVADOC-16
Here is an overview of the issue:
---
Howdy,
Just wanted to share a few ideas about some things I would like to do
over the next couple of weeks.
I think it is apparent that we are in a bit of deadlock wrt to a release
so I would like to do the following to try and get a stable release out
in the next little while.
1. Get maven-mode
The following comment has been added to this issue:
Author: Alain Javier Guarnieri del Gesu
Created: Thu, 4 Dec 2003 11:49 AM
Body:
Indeed, Micheal Kay now makes the project available via CVS due to my broaching the
subject of CVS on the saxon mailing list in regards to this issue
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [2003-12-02 08:10]:
> Alain Javier Guarnieri del Gesu <[EMAIL PROTECTED]> wrote on 30/11/2003
> 06:42:35 PM:
>
> > * Alain Javier Guarnieri del Gesu <[EMAIL PROTECTED]> [2003-11-28
> 23:55]:
> > > * Alain Javier Guarnieri del Gesu <[EMAIL PROTECTED]> [200
The following comment has been added to this issue:
Author: Janne Kario
Created: Thu, 4 Dec 2003 11:23 AM
Body:
I was about to suggest something similar. Further elaboration. jboss:configure would
copy automatically all dependencies marked with to
${maven.jboss.build.dir}/${mave
The following comment has been added to this issue:
Author: Norbert Pabis
Created: Thu, 4 Dec 2003 10:51 AM
Body:
Please make it a groupId=batik with following jars within:
batik-awt-util-1.5.jar
batik-bridge-1.5.jar
batik-css-1.5.jar
batik-dom-1.5.jar
batik-ext-1.5.jar
batik-exten
evenisse2003/12/04 07:05:50
Modified:jxr/src/main/org/apache/maven/jxr/pacman JavaFileImpl.java
jxr/xdocs changes.xml
Log:
Apply patch from Nicolas De Loof for reduce open files during jxr process.
Revision ChangesPath
1.3 +58 -48
maven-plugins/jx
On Thu, 2003-12-04 at 04:04, Vincent Massol wrote:
> > No problem, but in this case you might want to consider making the
> > clover plugin work the way it did. The clover plugin came before the
> > dashboard plugin. But it's not really a big deal, I just used the old
> > plugin.
>
> Yes, I will w
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: 04 December 2003 09:16
> To: Maven Developers List
> Subject: RE: Clover plugin glitches
>
> On Thu, 2003-12-04 at 03:07, Vincent Massol wrote:
> > Argh! Yes it was me. This was not intentional. I was discussing
Hi Brett,
Brett Porter wrote on Thursday, December 04, 2003 1:40 AM:
> It works now. Your changes reintroduced changelog to the
> bootstrap, and it has been broken offline/behind firewalls
> for a while. I removed the offending test for reasons given
> in the commit.
>
> I'm now testing 1_0-branc
On Thu, 2003-12-04 at 03:07, Vincent Massol wrote:
> Argh! Yes it was me. This was not intentional. I was discussing with Bob
> the reason for his on java:compile. We couldn't find the
> reason at that time... Now I understand, it was to prevent the tests
> from being instrumented :-)
>
> Hmm...
Argh! Yes it was me. This was not intentional. I was discussing with Bob
the reason for his on java:compile. We couldn't find the
reason at that time... Now I understand, it was to prevent the tests
from being instrumented :-)
Hmm... That's going to be hard to fix because if we put back the preGo
jvanzyl 2003/12/04 00:13:41
Added: maven-model/src/test/org/apache/maven/model BranchTest.java
BuildTest.java ContributorTest.java
DependencyTest.java DeveloperTest.java
LicenseTest.java MailingListTest.java
jvanzyl 2003/12/04 00:07:27
Modified:maven-model maven-model.iws
Log:
o adding tests to bring the coverage up to 100%
now we can change as desired in safety as i am going to switch to using
xstream+xpp3.
Revision ChangesPath
1.4 +14 -6 maven-component
jvanzyl 2003/12/04 00:04:12
Modified:maven-model/src/java/org/apache/maven/model Model.java
Log:
o remove determination of the presence of the repository. we'll put it in the
project.
Revision ChangesPath
1.14 +1 -49
maven-components/maven-model/src/java/org/ap
Brett,
I've just tried again CVS HEAD and it works fine now.
Thanks
-Vincent
> -Original Message-
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> Sent: 04 December 2003 08:19
> To: 'Maven Developers List'
> Subject: RE: Using maven HEAD
>
>
>
> > -Original Message-
> > Fro
vmassol 2003/12/03 23:58:37
Modified:dashboard/xdocs changes.xml navigation.xml
dashboard project.xml
Log:
Preparing for 1.2 release
Revision ChangesPath
1.12 +1 -1 maven-plugins/dashboard/xdocs/changes.xml
Index: changes.xml
==
jvanzyl 2003/12/03 23:45:36
Modified:maven-model/src/java/org/apache/maven/model Model.java
Log:
o artifacts are generated from the dependencies by the project builder.
Revision ChangesPath
1.13 +1 -50
maven-components/maven-model/src/java/org/apache/maven/model
jvanzyl 2003/12/03 23:43:32
Modified:maven-model/src/java/org/apache/maven/model Model.java
Log:
o remove more notions of inheritance. they don't belong here.
Revision ChangesPath
1.12 +1 -9
maven-components/maven-model/src/java/org/apache/maven/model/Model.jav
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: 04 December 2003 00:32
> To: 'Maven Developers List'
> Subject: RE: Using maven HEAD
>
> Vincent, are you offline/behind a firewall? There's a bug in the
changelog
> plugin unit tests (been in JIRA for a while) t
41 matches
Mail list logo
