dion2004/02/04 21:50:23
Modified:was40/xdocs navigation.xml changes.xml
was40project.xml plugin.jelly project.properties
plugin.properties
Log:
Start work on v1.1
Revision ChangesPath
1.2 +3 -6 maven-plugins/was40/
The following comment has been added to this issue:
Author: John Casey
Created: Thu, 5 Feb 2004 12:43 AM
Body:
The source and destination directory will be recursively scanned for Java source files
to compile. Only Java files that have no corresponding .class file or where the cl
Hi Jason,
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: 03 February 2004 22:12
> To: Maven Developers List
> Subject: RE: RC2
>
> On Tue, 2004-02-03 at 15:35, Vincent Massol wrote:
> > > -Original Message-
> > > From: [EMAIL PROTECTED] [mailto:[EMAIL
The following comment has been added to this issue:
Author: Tim Anderson
Created: Wed, 4 Feb 2004 8:12 PM
Body:
It may need to be:
exit /B %ERRORLEVEL%
to avoid terminating cmd.exe if maven.bat was invoked from
the command line.
--
The following comment has been added to this issue:
Author: dion gillard
Created: Wed, 4 Feb 2004 7:58 PM
Body:
Seems harmless to add this in
-
View this comment:
http://jira.codehaus.org/secure/ViewIssue.js
The following comment has been added to this issue:
Author: dion gillard
Created: Wed, 4 Feb 2004 7:56 PM
Body:
I still don't get it. If the source file is changed (since we're not using depend), it
will be recompiled...
The following comment has been added to this issue:
Author: John Casey
Created: Wed, 4 Feb 2004 7:33 PM
Body:
I remember exactly this issue being brought up on the Ant lists a couple of years ago.
It has to do with Ant detecting which files actually need to be recompiled, and then
The following issue has been updated:
Updater: Brett Porter (mailto:[EMAIL PROTECTED])
Date: Wed, 4 Feb 2004 7:26 PM
Comment:
appears it is not working, and still needed (eg for clover plugin when run
independantly)
Changes:
assignee changed to Brett Porter
There's already an issue filed - I thought it was working alternatively, but
I'll bump it back to RC2.
- Brett
> -Original Message-
> From: Sean Timm [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 5 February 2004 10:51 AM
> To: Maven Developers List
> Subject: RC2 - Clover?
>
>
> Is anyon
Is anyone successfully using Clover with the RC2 bits? I'm getting the
following error when I try and do a "maven clover:report":
Reference maven.test.compile.src.set not found.
Also, some tags are getting echoed out when the task starts, so I assume
they're not being recognized. I'm seeing the
The following comment has been added to this issue:
Author: dion gillard
Created: Wed, 4 Feb 2004 5:32 PM
Body:
Can you be more specific.
What does this have to do with Maven? If you change source code, it gets recompiled,
right??
-
The following comment has been added to this issue:
Author: Brett Porter
Created: Wed, 4 Feb 2004 5:27 PM
Body:
can do, but I'm wondering if you know of a way to fix it by changing the way the ant
task is called. Getting rid of the root classloader hack is really something we need
The following issue has been updated:
Updater: Leif Nelson (mailto:[EMAIL PROTECTED])
Date: Wed, 4 Feb 2004 5:25 PM
Comment:
1.21 version of plugin.jelly patched.
Changes:
Attachment changed to plugin.jelly
---
The following comment has been added to this issue:
Author: dion gillard
Created: Wed, 4 Feb 2004 5:24 PM
Body:
I'm happy for them to go back.
-
View this comment:
http://jira.codehaus.org/secure/ViewIssue.jspa?
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPJNLP-6
Here is an overview of the issue:
-
The following issue has been updated:
Updater: Leif Nelson (mailto:[EMAIL PROTECTED])
Date: Wed, 4 Feb 2004 5:24 PM
Comment:
the patch file
Changes:
Attachment changed to plugin.jelly.patch
-
Fo
The following comment has been added to this issue:
Author: Brett Porter
Created: Wed, 4 Feb 2004 5:09 PM
Body:
apparently putting back:
root
fixes it. I believe dion took these out some time ago. Is there another solution than
this?
-
The following issue has been updated:
Updater: Sean Timm (mailto:[EMAIL PROTECTED])
Date: Wed, 4 Feb 2004 4:53 PM
Comment:
Here's the attachment demonstrating the problem.
Changes:
Attachment changed to inheritance.zip
---
This is correct behaviour. Linkcheck should not fail because it can't
resolve a link - it reports it. It probably should not spit exceptions to
the build though...
- Brett
> -Original Message-
> From: Jörg Schaible [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, 4 February 2004 6:46 PM
> To
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1150
Here is an overview of the issue:
---
jvanzyl 2004/02/04 11:20:13
Modified:maven-project/src/meta-inf components.xml
maven-project/src/test/org/apache/maven/project
DefaultProjectBuilderTest.xml
Log:
o fixing component descriptor, removing duplication from test configuration.
R
Hold that thought...I'm an idiot...built the wrong branch. Let me build
anew before bothering you again with my trivial stupidities... ;)
> -Original Message-
> From: Sean Timm
> Sent: Wednesday, February 04, 2004 12:05 PM
> To: [EMAIL PROTECTED]
> Subject: RC2 - Inheritance Question
>
jvanzyl 2004/02/04 11:14:25
Modified:maven-model-xpp3/src/test/org/apache/maven/model
DefaultModelMarshallingTest.xml
Log:
o don't need to configure tests manually anymore, the descripts get discovered
by plexus.
Revision ChangesPath
1.4
jvanzyl 2004/02/04 11:09:51
Modified:maven-model-xpp3 project.xml
Added: maven-model-xpp3/src/meta-inf components.xml
Log:
o packing up component descriptor in the JAR so plexus can find it.
Revision ChangesPath
1.13 +10 -16maven-components/maven-model-xp
jvanzyl 2004/02/04 11:06:50
maven-components/maven-model-xpp3/src/meta-inf - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
jvanzyl 2004/02/04 11:05:47
Modified:maven-project project.xml
maven-project/src/java/org/apache/maven/project
MavenProject.java
Log:
o packaging component descriptor in JAR so plexus can find it.
Revision ChangesPath
1.13 +13 -
I've got a project-base.xml file that sets up my basic, generic
information (including build/SourceDirectory). I've got a
project-component.xml that extends this but does not contain the build
node at all. I then have a component-specific project.xml that extends
project-component.xml. My expect
jvanzyl 2004/02/04 11:00:24
Added: maven-project/src/meta-inf components.xml
Log:
o let the component tell plexus about itself.
Revision ChangesPath
1.1 maven-components/maven-project/src/meta-inf/components.xml
Index: components.xml
jvanzyl 2004/02/04 10:56:09
maven-components/maven-project/src/meta-inf - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1149
Here is an overview of the issue:
---
jvanzyl 2004/02/04 07:10:57
Modified:maven-mboot TODO.txt
Log:
Revision ChangesPath
1.2 +1 -0 maven-components/maven-mboot/TODO.txt
Index: TODO.txt
===
RCS file: /home/cvs/maven-component
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPECLIPSE-17
Here is an overview of the issue:
-
The following comment has been added to this issue:
Author: Stephen McConnell
Created: Wed, 4 Feb 2004 7:34 AM
Body:
Yes - "merlin:site" has been renamed to the goal "avalon:site"
-
View this comment:
http://jir
The following comment has been added to this issue:
Author: Rafal Krzewski
Created: Wed, 4 Feb 2004 4:41 AM
Body:
Indeed, the super project pom needs to be installed locally, or deployed to some
available repository before sub projects may be built, but I think it is a fair
requi
The following comment has been added to this issue:
Author: Steffen Dingel
Created: Wed, 4 Feb 2004 3:54 AM
Body:
does not allow adding JARs to the classpath. It works when we
unpack the JARs and add the directories to , but that is not a
very convenient solution.
--
Hello again,
I recognized, that Aspectwerkz is currently excluded, but now I have an exception
testing the xdoc-plugin. From the log I believe that not the test itself fails, but
the link validation mechanism. It seems that a request done with httpunit fails and
httpunit will alway throw an exc
vmassol 2004/02/03 23:24:23
Modified:aspectwerkz/src/plugin-test/child maven.xml project.xml
aspectwerkz/src/plugin-test/child/src/main/org/apache/maven/aspectwerkz
Target.java
Log:
Added goal to run the test application and verify (manually for
jvanzyl 2004/02/03 23:19:38
Added: maven-mboot TODO.txt
Log:
Revision ChangesPath
1.1 maven-components/maven-mboot/TODO.txt
Index: TODO.txt
===
o obey jar overrides
38 matches
Mail list logo