On Wed, 2003-05-28 at 08:54, Paulo Silveira wrote:
> > It is and I think Paulo even whipped up a patch for it. I
> > explained to him how to fix it in IRC because I don't have
> > time to fix it as I'm about to head off to boston. An
> > absolute path will allow the tests to pass for now or you
> It is and I think Paulo even whipped up a patch for it. I
> explained to him how to fix it in IRC because I don't have
> time to fix it as I'm about to head off to boston. An
> absolute path will allow the tests to pass for now or you can
> fix the interpolation in ArtifactFactory::getMaveRep
On Wed, 2003-05-28 at 06:24, Michal Maczka wrote:
> My repository path does not start with ${maven.home}...so this problem did
> not show up.
>
> I have something like:
>
> /repository
> /maven
>
> It seems like interpolation problem.
It is and I think Paulo even whipped up a patch for it. I ex
Michal Maczka wrote:
> My repository path does not start with ${maven.home}...so this problem did
> not show up.
>
> I have something like:
>
> /repository
> /maven
>
> It seems like interpolation problem.
I have a question: What is the proper way of building maven-new?
It is not self hosting A
My repository path does not start with ${maven.home}...so this problem did
not show up.
I have something like:
/repository
/maven
It seems like interpolation problem.
Michal
> -Original Message-
> From: Rafal Krzewski [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, May 28, 2003 12:05 PM
>
Ben Walding wrote:
> This stuff is in so much flux that I'd expect tests to fail on a regular
> basis. That being said, attaching the output of test results would be a
> good start.
> target/test-reports/whichever ones failed
Ha! Didn't know about that one... (I'm not using Junit in my project
ye
This stuff is in so much flux that I'd expect tests to fail on a regular
basis. That being said, attaching the output of test results would be a
good start.
target/test-reports/whichever ones failed
Rafal Krzewski wrote:
I tried to build maven-new and I got this:
[junit] Running
org.apache
vmassol 2003/05/28 02:41:44
Modified:src/plugins-build/cactus plugin.jelly
Log:
now using the "plain" formatter instead of the "brief" one in order to get list of
tests printed in the console.
Revision ChangesPath
1.17 +1 -1 maven/src/plugins-build/cactus/plugi
vmassol 2003/05/28 02:36:20
Modified:src/plugins-build/cactus/xdocs properties.xml
src/plugins-build/cactus plugin.properties plugin.jelly
Log:
Added maven.cactus.printsummary property (same meaning as the printsummary attribute
of the Ant junit task).
Revision
I tried to build maven-new and I got this:
[junit] Running
org.apache.maven.artifact.factory.DefaultArtifactFactoryTest
maven.repo.local = ${maven.home}/repository
artifact factory : mavenRepoLocal = ${maven.home}/repository
artifact factory : mavenRepoLocal = ${maven.home}/repository
maven.re
vmassol 2003/05/28 02:07:15
Modified:src/plugins-build/checkstyle .cvsignore
Log:
added eclipse project files to ignore list
Revision ChangesPath
1.2 +2 -0 maven/src/plugins-build/checkstyle/.cvsignore
Index: .cvsignore
==
11 matches
Mail list logo
