Although not terribly useful, occasionally looking to see how many of
your tests are running can be elucidating. If the tests aren't running
/ logic in them isn't running, why is it there? Are you not testing
logic paths that you thought you were testing? (i.e. test code isn't
running, hence
The following comment has been added to this issue:
Author: Chad Woolley
Created: Wed, 3 Dec 2003 7:29 PM
Body:
I rolled back to 1.0 beta 9 and everything worked again. This is definitely a bug in
RC1
-
View the
> On Wed, 2003-12-03 at 19:39, Brett Porter wrote:
> > 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-branch, but
brett 2003/12/03 17:19:13
Modified:.Tag: MAVEN-1_0-BRANCH project.properties
Log:
exclude simian for now - it's not working with the changes
Revision ChangesPath
No revision
No revision
1.51.2.2 +3 -1 maven/project.p
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPXDOC-73
Here is an overview of the issue:
--
jvanzyl 2003/12/03 17:09:53
Modified:maven-model maven-model.iws project.xml
maven-model/src/java/org/apache/maven/model Build.java
Resource.java
Log:
o just adding more tests
Revision ChangesPath
1.3 +56 -24maven-component
jvanzyl 2003/12/03 17:09:42
Modified:maven-model/src/java/org/apache/maven/model Model.java
Log:
o ids can be created in the project. we want to stick with the model here.
Revision ChangesPath
1.11 +9 -20
maven-components/maven-model/src/java/org/apache/maven/mo
jvanzyl 2003/12/03 17:08:12
Modified:maven-model/src/java/org/apache/maven/model Model.java
Log:
o file reference should not be stored here and belongs in the project. might
not be a file anyway.
Revision ChangesPath
1.10 +1 -25
maven-components/maven-model/
On Wed, 2003-12-03 at 19:58, Ben Walding wrote:
> This can be useful behaviour. It should be optional though.
How so? Just never thought about it myself really. But it should be off
by default. If you want to check the integrity of your tests we could
use something like jester.
> Jason van Zyl wr
jvanzyl 2003/12/03 17:01:19
Modified:maven-model/src/java/org/apache/maven/model Model.java
Log:
o gump descriptor can be gleaned from the repo information now.
Revision ChangesPath
1.9 +1 -24
maven-components/maven-model/src/java/org/apache/maven/model/Model.j
jvanzyl 2003/12/03 16:58:46
Modified:maven-model/src/java/org/apache/maven/model Model.java
Log:
o modelVersion not pomVersion
this is not to say that these might both exist i.e. the model might stay
the same but the transformation that creates the project might be
dif
This can be useful behaviour. It should be optional though.
Jason van Zyl wrote:
Vincent,
It looks like you were the last to modify the clover plugin and it seems
to be instrumenting and reporting on test cases as well. Is this
intentional?
jvanzyl 2003/12/03 16:52:40
Modified:maven-model/src/java/org/apache/maven/model Model.java
Log:
o use version not currentVersion
Revision ChangesPath
1.7 +9 -9
maven-components/maven-model/src/java/org/apache/maven/model/Model.java
Index: Model.java
==
On Wed, 2003-12-03 at 19:39, Brett Porter wrote:
> 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-branch, but I suspect it wil
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-branch, but I suspect it will be fine too now.
- Brett
> -Original Message-
>
brett 2003/12/03 16:36:14
Removed: changelog/src/test/org/apache/maven/cvslib
CvsConnectionTest.java
Log:
remove dud test. Fails offline/behind firewall on one test, and the other is a false
positive. Testing actual connections is beyond the scope of a unit
jvanzyl 2003/12/03 16:33:48
Modified:maven-model/src/java/org/apache/maven/model Dependency.java
Log:
o return the kind not the type.
Revision ChangesPath
1.6 +3 -15
maven-components/maven-model/src/java/org/apache/maven/model/Dependency.java
Index: Depend
Vincent,
It looks like you were the last to modify the clover plugin and it seems
to be instrumenting and reporting on test cases as well. Is this
intentional?
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org
In short, man creates for himself a new religion of a rational
and
On Wed, 2003-12-03 at 18:16, Brett Porter wrote:
> Confirmed problem for 1.1-SNAPSHOT. The vast majority of the plugins don't
> get put in $MAVEN_HOME/plugins for some reason. Investigating.
I just did a fresh co of HEAD, bootstrapped and then built and ran
clover. You can't bootstrap?
> - Brett
Vincent, are you offline/behind a firewall? There's a bug in the changelog
plugin unit tests (been in JIRA for a while) that causes them to fail and is
probably the cause.
I think I'll just remove the test class as behind a firewall one is a false
positive and the other fails, and unit tests shoul
Confirmed problem for 1.1-SNAPSHOT. The vast majority of the plugins don't
get put in $MAVEN_HOME/plugins for some reason. Investigating.
- Brett
> -Original Message-
> From: Brett Porter
> Sent: Thursday, 4 December 2003 9:07 AM
> To: 'Maven Developers List'
> Subject: RE: Using maven H
The following comment has been added to this issue:
Author: Matthew Hawthorne
Created: Wed, 3 Dec 2003 4:57 PM
Body:
here's the URL --
http://apache.org/~matth/dist/commons-sql-1.0-dev.jar
thanks!
-
View the issue
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVENUPLOAD-42
Here is an overview of the issue:
-
On Wed, 2003-12-03 at 17:07, Brett Porter wrote:
> No, this isn't the case. HEAD is 1.1-SNAPSHOT, and doesn't incude the branch
> changes until they are stable (which is very close). Then the branch will be
> merged regularly.
Ah, ok.
> Both the branch and HEAD should bootstrap and be functional
No, this isn't the case. HEAD is 1.1-SNAPSHOT, and doesn't incude the branch
changes until they are stable (which is very close). Then the branch will be
merged regularly.
Both the branch and HEAD should bootstrap and be functional afterwards - and
have as far as my testing has gone. However, I'm
The site is online at http://www.mvdb.org/maven/plugins/svg and the
plugin kind-of finished (some debug stuff is left behind, but it is a
start).
I cannot release it yet, since the batik1.5 jars aren't on ibiblio yet..
Directions on where to get the source are on the site too, so you can
have peek
bwalding2003/12/03 13:10:16
Modified:xdocsrepository-upload.xml
Log:
Updated details for requesting uploads to ibiblio
Revision ChangesPath
1.8 +1 -2 maven/xdocs/repository-upload.xml
Index: repository-upload.xml
=
Hi,
I think things are relatively under control now. There are still 50
"core" issues that should probably be funnelled out and be assigned to a
more descriptive component and there are still 29 "No component" issues.
I think I have had enough of JIRA for a fews days but if anyone else
wants to l
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1067
Here is an overview of the issue:
-
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: 03 December 2003 17:47
> To: Maven Developers List
> Subject: Re: Using maven HEAD
>
> On Wed, 2003-12-03 at 11:38, Vincent Massol wrote:
> > Hi,
> >
> > Has anyone tried to build a clean HEAD and then to manual
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVENUPLOAD-40
Here is an overview of the issue:
-
On Wed, 2003-12-03 at 11:38, Vincent Massol wrote:
> Hi,
>
> Has anyone tried to build a clean HEAD and then to manually build a
> plugin project?
You realize HEAD is now the RC2_UNSTABLE code? You sure you're not
meaning to build the 1.0 branch?
> Thanks
> -Vincent
>
>
> -
Hi,
Has anyone tried to build a clean HEAD and then to manually build a
plugin project?
Thanks
-Vincent
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
* [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]> [2003
Hi,
I'm trying MAVEN HEAD (i.e. 1.1-SNAPSHOT, we need to change the version
BTW) and I'm having some issues. It build and installs fine. However
when I try to build any plugin, I get the following error:
E:\Dev\maven-plugins\dashboard>maven clean plugin:install
__ __
| \/ |__ _Apache__ ___
|
vmassol 2003/12/03 03:10:45
Modified:dashboard/src/plugin-resources/templates legend.jsl
Log:
Binary --> Ascii
Revision ChangesPath
1.2 +41 -41
maven-plugins/dashboard/src/plugin-resources/templates/legend.jsl
Index: legend.jsl
===
vmassol 2003/12/03 03:10:09
Modified:dashboard/xdocs changes.xml authoring.xml
dashboard/src/plugin-resources/templates dashboard.jsl
dashboard plugin.properties plugin.jelly
Added: dashboard/src/plugin-resources/templates legend.jsl
Log:
Added c
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVENUPLOAD-39
Here is an overview of the issue:
-
The following comment has been added to this issue:
Author: Jörg Schaible
Created: Wed, 3 Dec 2003 3:45 AM
Body:
JUst becasue of the comments: This fixes my environment Windows/Cygwin!
-
View the issue:
http://j
The following issue has been updated:
Updater: Jörg Schaible (mailto:[EMAIL PROTECTED])
Date: Wed, 3 Dec 2003 3:43 AM
Comment:
Please reapply as target for this issue the 1.0-BRANCH. This bug already caused me to
create a wrong bug report (MAVEN-1058). Attached a patch against the
Brett Porter wrote on Tuesday, December 02, 2003 10:59 PM:
> Do you have a clean update? This was the problem before yesterday's
> commits.
Did a clean checkout, have the same errors!
Regards,
Jörg
-
To unsubscribe, e-mail: [E
41 matches
Mail list logo
