couple of days.
> Paulo
>
>
> >
> > > Michal
> > >
> > > > -Original Message-
> > > > From: Rafal Krzewski [mailto:[EMAIL PROTECTED]
> > > > Sent: Wednesday, May 28, 2003 12:05 PM
> > > > To: Maven Developers
ts run.
Paulo
>
> > Michal
> >
> > > -Original Message-
> > > From: Rafal Krzewski [mailto:[EMAIL PROTECTED]
> > > Sent: Wednesday, May 28, 2003 12:05 PM
> > > To: Maven Developers List
> > > Subject: Re: maven-new tests failing
> &
al
>
> > -Original Message-
> > From: Rafal Krzewski [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, May 28, 2003 12:05 PM
> > To: Maven Developers List
> > Subject: Re: maven-new tests failing
> >
> >
> > Ben Walding wrote:
> > &g
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
12:05 PM
> To: Maven Developers List
> Subject: Re: maven-new tests failing
>
>
> 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
> > goo
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
