Yeah. I tried on another computer with Maven 3 (mvn --version below) and it
passed the commons tests (but failed on filemgr).

I talked to Lewis about it some yesterday. Maybe I have an improperly set
environment variable?

➜  oodt.trunk  mvn --version
Apache Maven 3.0.4
Maven home: /usr/share/maven
Java version: 1.7.0_40, vendor: Oracle Corporation
Java home: /usr/lib/jvm/jdk1.7.0/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.11.0-19-generic", arch: "i386", family: "unix"

Tyler


On Wed, Jul 23, 2014 at 8:09 PM, Chris Mattmann <[email protected]> wrote:

> Addressed, a while ago :)
>
> http://s.apache.org/uI
>
> https://issues.apache.org/jira/browse/OODT-369
>
>
>
>
> -----Original Message-----
> From: <[email protected]>
> Reply-To: <[email protected]>
> Date: Wednesday, July 23, 2014 10:20 AM
> To: <[email protected]>
> Cc: dev <[email protected]>
> Subject: Re: [ANNOUNCE] Tyler Palsulich is now on the PMC too!
>
> >Give it a shot with Maven-2.2.1.  (I don't think we're ready for Maven 3,
> >which itself is another issue that needs addressing.)
> >
> >--k
> >
> >On 2014-07-23, at 10:49 AM, Tyler Palsulich <[email protected]> wrote:
> >
> >> Thanks all! I'm looking forward to the roadmap call.
> >>
> >> Before then, I'm having issues even passing the Commons tests on a
> >>clean install... Here is the output of `mvn test -X`:
> >>https://paste.apache.org/75u9.
> >>
> >> ?  mvn --version
> >> Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9;
> >>2014-02-14T09:37:52-08:00)
> >> Maven home: /usr/local/Cellar/maven/3.2.1/libexec
> >> Java version: 1.7.0_60, vendor: Oracle Corporation
> >> Java home:
> >>/Library/Java/JavaVirtualMachines/jdk1.7.0_60.jdk/Contents/Home/jre
> >> Default locale: en_US, platform encoding: UTF-8
> >> OS name: "mac os x", version: "10.9.3", arch: "x86_64", family: "mac"
> >>
> >> TL;DR: I don't see any failed tests. -DfailIfNoTests=false doesn't
> >>help. My surefire directory doesn't have any failures.
> >>
> >> Is there any config that needs to be set up before install? Or, am I
> >>missing something in the output above?
> >>
> >> Thank for any help,
> >> Tyler
> >>
> >>
> >> On Tue, Jul 22, 2014 at 8:43 PM, Rajith Siriwardana
> >><[email protected]> wrote:
> >> Welcome Tyler..!!!
> >>
> >>
> >> Cheers,
> >> --Rajith
> >>
> >>
> >> On Wed, Jul 23, 2014 at 1:06 AM, Michael Starch <[email protected]>
> >>wrote:
> >> Great!  Welcome, Tyler.
> >>
> >> As another new PMC I aggree that we should discuss a roadmap.
> >>
> >> -Michael
> >>
> >> On Jul 22, 2014 11:58 AM, "Michael Joyce" <[email protected]> wrote:
> >> Yay! Welcome Tyler!!!
> >>
> >>
> >> -- Joyce
> >>
> >>
> >> On Tue, Jul 22, 2014 at 11:36 AM, Tom Barber <[email protected]>
> >>wrote:
> >> Aye I'll +1 that, and move this over to dev@
> >>
> >> We have an ever expanding PMC, so lets do some Project Managing! ;)
> >>
> >> I think we need to come up with some roadmap goals, both regarding
> >>features, and also the existing code base, build systems and delivery.
> >>
> >> Personally I think it would be benificial to get a bunch of us on the
> >>phone and discuss it in real time (I'm GMT based which does make it a
> >>little tricker) rather than hash it out over a 6 month chain of emails.
> >>Like I said the other day, I don't really know how other projects manage
> >>this type of thing so those with more experience may want to chime in
> >>here.
> >>
> >> Regards
> >>
> >> Tom
> >>
> >>
> >>
> >> On 22/07/14 18:33, Lewis John Mcgibbney wrote:
> >>> Hi Tyler,
> >>> Please see Tom's thread from before the weekend.
> >>> I say we have a full on discussion on establishing a roadmap.
> >>> For us to establish and agree on this will be extremely beneficial for
> >>>the project.
> >>> Lewis
> >>>
> >>>
> >>> On Tue, Jul 22, 2014 at 10:29 AM, Tyler Palsulich
> >>><[email protected]> wrote:
> >>> Hi All,
> >>>
> >>> Thanks for inviting me to join as a committer and PMC member! I'm
> >>>happy to be part of the project. Any tips on where to dive in?
> >>>
> >>> Tyler
> >>
> >>
> >>
> >>
> >
>
>
>

Reply via email to