Ok, I'd prefer to stay away from it then since these kinds of problems are
killer on my development schedule.  I do look forward to when a new version
of Maven comes out though and can't wait to see what it's in 2.1.

On 8/9/07, Eric Redmond <[EMAIL PROTECTED]> wrote:
>
> Well, 2.1 is a lot cooler than 2.0.x - however, I would tend to stay away
> for now unless you want to get involved in the core - it's not THAT
> stable.
> At least wait until the alpha release, which should be coming around in a
> month or so.
>
> --
> Eric Redmond
> http://blog.propellors.net
>
> On 8/8/07, Ryan Moquin <[EMAIL PROTECTED]> wrote:
> >
> > Oh you run 2.1?  Do you build it from source?  I tend to try to stay
> away
> > from non-stable builds unless there is a feature I really need, so that
> I
> > avoid problems like the one I'm describing.  I absolutely love Maven
> > though
> > and am very very tempted to try out the newer stuff early :)
> >
> > On 8/8/07, Eric Redmond <[EMAIL PROTECTED]> wrote:
> > >
> > > Ah, was not aware. Glad it's gotten fixed - I tend to run 2.1 anymore.
> > >
> > > On 8/8/07, Max Bowsher <[EMAIL PROTECTED]> wrote:
> > > >
> > > > Eric Redmond wrote:
> > > > > testResources files get copied to the testOutputDirectory. Using
> > > > surefire,
> > > > > the testOutputDirecotry files should take precedence.
> > > >
> > > > Actually, no. In Maven 2.0.7 and below, the main output directory
> > takes
> > > > precedence. In Maven 2.0.8-SNAPSHOT, this has been fixed.
> > > >
> > > > Compare the getTestClasspathElements method in:
> > > >
> > > >
> > > >
> > >
> >
> http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/maven-project/src/main/java/org/apache/maven/project/MavenProject.java
> > > >
> > > >
> > >
> >
> http://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.x/maven-project/src/main/java/org/apache/maven/project/MavenProject.java
> > > >
> > > > Max.
> > > >
> > >
> > >
> > >
> > > --
> > > Eric Redmond
> > > http://blog.propellors.net
> > >
> >
>

Reply via email to