Last 500 lines of a clean bootstrap build of maven at 20031024-2200
[exec] +
[exec] build:
[exec] [echo] D succeeds on purpose
[exec] [echo] failure-1 failed correctly
[exec] [echo] failure-2 failed correctly
[exec
* Javier del Gesu <[EMAIL PROTECTED]> [2003-10-24 21:03]:
> * Javier del Gesu <[EMAIL PROTECTED]> [2003-10-24 20:12]:
> > I want to be able to trace into Xerces/Xalan/Xindice/Cocoon/Avalon
> > when debugging my application. It doesn't seem that the dependencies
> > downloaded from ibiblio will perm
On Fri, 2003-10-24 at 16:39, Erdfelt, Joakim wrote:
> > -Original Message-
> > From: Shatzer, Larry [mailto:[EMAIL PROTECTED]
> > Sent: Friday, October 24, 2003 4:21 PM
> > To: 'Maven Developers List'
> > Subject: RE: Use Java based CVS library instead of command line
> > executable
> >
> >
I thought that jCVS would not be useful because of that (I think I saw a
post about that). I looked at Eclipse
(http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.team.cv
s.core/about.html) and apparently it used the CPL (Common Public License)
which looks compatible at first glan
* Javier del Gesu <[EMAIL PROTECTED]> [2003-10-24 20:12]:
> I want to be able to trace into Xerces/Xalan/Xindice/Cocoon/Avalon
> when debugging my application. It doesn't seem that the dependencies
> downloaded from ibiblio will permit this, I don't see any source
> files. Is there a standard strat
> -Original Message-
> From: Shatzer, Larry [mailto:[EMAIL PROTECTED]
> Sent: Friday, October 24, 2003 4:21 PM
> To: 'Maven Developers List'
> Subject: RE: Use Java based CVS library instead of command line
> executable
>
> > I think this is what ant strives for. a 100% java solution
> >
> -Original Message-
> From: Erdfelt, Joakim [mailto:[EMAIL PROTECTED]
> Sent: Friday, October 24, 2003 1:05 PM
> To: 'Maven Developers List'
> Subject: RE: Use Java based CVS library instead of command line
> executable
>
>
> I think this is what ant strives for. a 100% java solution
>
I want to be able to trace into Xerces/Xalan/Xindice/Cocoon/Avalon
when debugging my application. It doesn't seem that the dependencies
downloaded from ibiblio will permit this, I don't see any source
files. Is there a standard strategy for building debug dependencies
and setting a debug classpath?
On Fri, 2003-10-24 at 15:50, Jason van Zel wrote:
>On Fri, 2003-10-24 at 13:37, Eric Pugh wrote:
>> Hi all,
>>
>> Something that I find quite annoying is that every box that I want to
>> generate the various CVS related reports, I need to have the cvs
commandline
>> tool installed. Since I am an
On Fri, 2003-10-24 at 13:37, Eric Pugh wrote:
> Hi all,
>
> Something that I find quite annoying is that every box that I want to
> generate the various CVS related reports, I need to have the cvs commandline
> tool installed. Since I am an Eclipse user, I don't typically have the
> command line
Hi all,
Something that I find quite annoying is that every box that I want to
generate the various CVS related reports, I need to have the cvs commandline
tool installed. Since I am an Eclipse user, I don't typically have the
command line client available. Anyone done any work on supplying a jav
evenisse2003/10/24 09:14:21
Modified:simian/xdocs properties.xml
Log:
Fix properties documentation
Revision ChangesPath
1.3 +2 -2 maven-plugins/simian/xdocs/properties.xml
Index: properties.xml
Done.
-Message d'origine-
De: [EMAIL PROTECTED]
A: [EMAIL PROTECTED]
Date: 24/10/03
Objet: Little error in simian plugin doc
Hi
In simian plugin properties doc page
(http://maven.apache.org/reference/plugins/simian/properties.html)
maven.simian.includeTests optional is "true" and should
Message:
The following issue has been closed.
Resolver: Emmanuel Venisse
Date: Fri, 24 Oct 2003 11:34 AM
Applied
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-967
Here is an overvie
evenisse2003/10/24 08:26:20
Modified:jcoverage project.xml
jcoverage/src/main/org/apache/maven/jcoveragereport
CoverageReport.java
jcoverage/xdocs changes.xml
Log:
Apply MAVEN-967
Revision ChangesPath
1.6 +2 -2
Noel J. Bergman wrote:
Jira seems like it could use additional administrative features. Pruning
tools, for example. We will have over 25K users after importing bugzilla.
Ideally, we would like to be able to purge users who aren't associated with
any issues, who don't have any special permissions,
The following issue has been updated:
Updater: Emmanuel Venisse (mailto:[EMAIL PROTECTED])
Date: Fri, 24 Oct 2003 9:55 AM
Comment:
We must respect the RFC.
DependencyVerifier and SnashotResolver must use the same mecanism for download a file.
Changes:
Component chan
Hi
In simian plugin properties doc page
(http://maven.apache.org/reference/plugins/simian/properties.html)
maven.simian.includeTests optional is "true" and should be "Yes (default
= true)" (I think)
Should i open an issue in Jira for this ?
If yes, in which component ? (i don't see plugin-simian
The following issue has been updated:
Updater: Jeff Brekke (mailto:[EMAIL PROTECTED])
Date: Fri, 24 Oct 2003 9:50 AM
Comment:
Quick patch to catch the exception and set the percentage to 0. ?% is shown sometimes
as the string. This seems to work, but maybe there's a better way?
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-967
Here is an overview of the issue:
--
The following issue has been updated:
Updater: Chris Rauschuber (mailto:[EMAIL PROTECTED])
Date: Fri, 24 Oct 2003 8:34 AM
Comment:
Sorry, the last patch only fixed source. This one fixes both source and test.
Changes:
Attachment changed to maven_eclipse_jira_899.t
On Thu, Oct 23, 2003 at 10:08:35PM -0400, Noel J. Bergman wrote:
> > bugzilla import is completely broken in 2.4.1,
> > whereas it works quite well in the 2.5 beta :)
>
> Aha! I was wondering about that problem. :-)
FYI, Brett found another smaller bug [1], which we've fixed.
> > But regarding
22 matches
Mail list logo
