OoO

2014-07-24 Thread Cinquini, Luca (398J)
Hi all and sorry for the cross-posting,

I will be on vacation from Friday, July 25th, through Saturday August 
9th.

I will probably not be able to check email consistently, so if anything comes 
up please resend in a few weeks.
For anything critical, please try my cell at 818-309-0680.

thanks, Luca






Re: [ANNOUNCE] Tyler Palsulich is now on the PMC too!

2014-07-24 Thread Tyler Palsulich
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 mattm...@apache.org wrote:

 Addressed, a while ago :)

 http://s.apache.org/uI

 https://issues.apache.org/jira/browse/OODT-369




 -Original Message-
 From: ke...@apache.org
 Reply-To: dev@oodt.apache.org
 Date: Wednesday, July 23, 2014 10:20 AM
 To: u...@oodt.apache.org
 Cc: dev dev@oodt.apache.org
 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 tpalsul...@gmail.com 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
 rajithsiriward...@gmail.com wrote:
  Welcome Tyler..!!!
 
 
  Cheers,
  --Rajith
 
 
  On Wed, Jul 23, 2014 at 1:06 AM, Michael Starch starc...@umich.edu
 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 jo...@apache.org wrote:
  Yay! Welcome Tyler!!!
 
 
  -- Joyce
 
 
  On Tue, Jul 22, 2014 at 11:36 AM, Tom Barber tom.bar...@meteorite.bi
 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
 tpalsul...@gmail.com 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
 
 
 
 
 





Build failed in Jenkins: oodt-trunk #1406

2014-07-24 Thread Apache Jenkins Server
See https://builds.apache.org/job/oodt-trunk/1406/changes

Changes:

[lewismc] OODT-685 ix OODT 0.7-SNAPSHOT Jenkins nightly build on Ubuntu 2nd Pass

--
[...truncated 7367 lines...]
at java.io.File$LazyInitialization.temporaryDirectory(File.java:1673)
at java.io.File.createTempFile0(File.java:1719)
at java.io.File.createTempFile(File.java:1838)
at 
org.apache.oodt.cas.filemgr.catalog.TestDataSourceCatalog.init(TestDataSourceCatalog.java:81)
at 
org.apache.oodt.cas.filemgr.catalog.TestOrderedDataSourceCatalog.init(TestOrderedDataSourceCatalog.java:41)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at 
org.junit.runners.BlockJUnit4ClassRunner.createTest(BlockJUnit4ClassRunner.java:202)
at 
org.junit.runners.BlockJUnit4ClassRunner$1.runReflectiveCall(BlockJUnit4ClassRunner.java:251)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at 
org.junit.runners.BlockJUnit4ClassRunner.methodBlock(BlockJUnit4ClassRunner.java:248)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at 
org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:35)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:115)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:97)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103)
at com.sun.proxy.$Proxy14.invoke(Unknown Source)
at 
org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150)
at 
org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91)
at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:105)
at 
org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:619)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at 
hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:182)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at 
org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at hudson.maven.agent.Main.launch(Main.java:205)
at 

Build failed in Jenkins: oodt-trunk » Catalog and Archive File Management Component #1406

2014-07-24 Thread Apache Jenkins Server
See 
https://builds.apache.org/job/oodt-trunk/org.apache.oodt$cas-filemgr/1406/changes

Changes:

[lewismc] OODT-685 ix OODT 0.7-SNAPSHOT Jenkins nightly build on Ubuntu 2nd Pass

--
[...truncated 670 lines...]
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at 
org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:35)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:115)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:97)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103)
at com.sun.proxy.$Proxy14.invoke(Unknown Source)
at 
org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150)
at 
org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91)
at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:105)
at 
org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:619)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at 
hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:182)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at 
org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at hudson.maven.agent.Main.launch(Main.java:205)
at hudson.maven.MavenBuilder.call(MavenBuilder.java:154)
at hudson.maven.Maven2Builder.call(Maven2Builder.java:79)
at hudson.maven.Maven2Builder.call(Maven2Builder.java:55)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:328)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:662)
java.lang.NullPointerException
at java.io.UnixFileSystem.normalize(UnixFileSystem.java:69)
at java.io.File$LazyInitialization.temporaryDirectory(File.java:1673)
at java.io.File.createTempFile0(File.java:1719)
at java.io.File.createTempFile(File.java:1838)
at 
org.apache.oodt.cas.filemgr.catalog.TestDataSourceCatalog.init(TestDataSourceCatalog.java:81)
at 
org.apache.oodt.cas.filemgr.catalog.TestOrderedDataSourceCatalog.init(TestOrderedDataSourceCatalog.java:41)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at 

Build failed in Jenkins: oodt-trunk #1407

2014-07-24 Thread Apache Jenkins Server
See https://builds.apache.org/job/oodt-trunk/1407/

--
[...truncated 7383 lines...]
at java.io.File$LazyInitialization.temporaryDirectory(File.java:1673)
at java.io.File.createTempFile0(File.java:1719)
at java.io.File.createTempFile(File.java:1838)
at 
org.apache.oodt.cas.filemgr.catalog.TestDataSourceCatalog.init(TestDataSourceCatalog.java:81)
at 
org.apache.oodt.cas.filemgr.catalog.TestOrderedDataSourceCatalog.init(TestOrderedDataSourceCatalog.java:41)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at 
org.junit.runners.BlockJUnit4ClassRunner.createTest(BlockJUnit4ClassRunner.java:202)
at 
org.junit.runners.BlockJUnit4ClassRunner$1.runReflectiveCall(BlockJUnit4ClassRunner.java:251)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at 
org.junit.runners.BlockJUnit4ClassRunner.methodBlock(BlockJUnit4ClassRunner.java:248)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at 
org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:35)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:115)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:97)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103)
at com.sun.proxy.$Proxy14.invoke(Unknown Source)
at 
org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150)
at 
org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91)
at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:105)
at 
org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:619)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at 
hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:182)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at 
org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at hudson.maven.agent.Main.launch(Main.java:205)
at hudson.maven.MavenBuilder.call(MavenBuilder.java:154)
at hudson.maven.Maven2Builder.call(Maven2Builder.java:79)

Build failed in Jenkins: oodt-trunk » Catalog and Archive File Management Component #1407

2014-07-24 Thread Apache Jenkins Server
See https://builds.apache.org/job/oodt-trunk/org.apache.oodt$cas-filemgr/1407/

--
[...truncated 670 lines...]
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at 
org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:35)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:115)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:97)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103)
at com.sun.proxy.$Proxy14.invoke(Unknown Source)
at 
org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150)
at 
org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91)
at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:105)
at 
org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:619)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at 
hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:182)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at 
org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at hudson.maven.agent.Main.launch(Main.java:205)
at hudson.maven.MavenBuilder.call(MavenBuilder.java:154)
at hudson.maven.Maven2Builder.call(Maven2Builder.java:79)
at hudson.maven.Maven2Builder.call(Maven2Builder.java:55)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:328)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:662)
java.lang.NullPointerException
at java.io.UnixFileSystem.normalize(UnixFileSystem.java:69)
at java.io.File$LazyInitialization.temporaryDirectory(File.java:1673)
at java.io.File.createTempFile0(File.java:1719)
at java.io.File.createTempFile(File.java:1838)
at 
org.apache.oodt.cas.filemgr.catalog.TestDataSourceCatalog.init(TestDataSourceCatalog.java:81)
at 
org.apache.oodt.cas.filemgr.catalog.TestOrderedDataSourceCatalog.init(TestOrderedDataSourceCatalog.java:41)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at 

Jenkins build became unstable: oodt-trunk » CAS Protocol SFTP Implementation #1408

2014-07-24 Thread Apache Jenkins Server
See 
https://builds.apache.org/job/oodt-trunk/org.apache.oodt$cas-protocol-sftp/1408/



Jenkins build is unstable: oodt-trunk » Catalog and Archive File Management Component #1408

2014-07-24 Thread Apache Jenkins Server
See 
https://builds.apache.org/job/oodt-trunk/org.apache.oodt$cas-filemgr/1408/changes



Jenkins build is unstable: oodt-trunk #1408

2014-07-24 Thread Apache Jenkins Server
See https://builds.apache.org/job/oodt-trunk/1408/changes



Re: Review Request 23878: Successor to rlaidlaw reviewboard #23870 for OODT-685

2014-07-24 Thread Tyler Palsulich

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23878/#review48677
---


I'm getting the same result as with Ross' patch. Not sure why... I don't have 
any environment variables set for OODT.

Tests run: 190, Failures: 64, Errors: 28, Skipped: 0

- Tyler Palsulich


On July 24, 2014, 5:52 a.m., Lewis McGibbney wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/23878/
 ---
 
 (Updated July 24, 2014, 5:52 a.m.)
 
 
 Review request for oodt, Tom Barber, Chris Mattmann, Sean Kelly, Paul 
 Ramirez, Rishi Verma, Ross Laidlaw, and Tyler Palsulich.
 
 
 Bugs: OODT-685
 https://issues.apache.org/jira/browse/OODT-685
 
 
 Repository: oodt
 
 
 Description
 ---
 
 Hi Folks,
 OK in the name of staying sane, I am fully behind the decision to just get 
 filemgr back stable. 
 This review board is somewhat of a successor to @rlaidlaw's patch attached to 
 review board request - https://reviews.apache.org/r/23870/
 Bascially, there is now one failing test (as below) which I cannot debug as 
 it passes for me locally within my IDE!!!
 What is more is that from the command line it actually DOES fail!!! 
 
 Results :
 
 Failed tests:
   
 testGetElements(org.apache.oodt.cas.filemgr.validation.TestXMLValidationLayer):
  There aren't exactly 4 elements in the test samples! expected:4 but 
 was:11
 
 Tests run: 190, Failures: 1, Errors: 0, Skipped: 0
 
 From within my IDE the failing test is located at 
 org.apache.oodt.cas.filemgr.validation.TestXMLValidationLayer#testModifyElement,
  which DOES NOT fail when I load it from the command line.
 
 I think we should commit these improvements to the filemgr test suite before 
 moving on to work on maybe upgrading to JUnit 4.11 as per 
 https://issues.apache.org/jira/browse/OODT-687
 
 
 Diffs
 -
 
   
 http://svn.apache.org/repos/asf/oodt/trunk/commons/src/main/java/org/apache/oodt/commons/xml/XMLUtils.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/java/org/apache/oodt/cas/filemgr/validation/XMLValidationLayer.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/catalog/TestDataSourceCatalog.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/catalog/TestMappedDataSourceCatalog.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/catalog/TestOrderedDataSourceCatalog.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/cli/TestFileManagerCli.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/datatransfer/TestLocalDataTransferer.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestCachedIngester.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestLocalCache.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestRmiCache.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestStdIngester.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/repository/TestXMLRepositoryManager.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/structs/type/TestTypeHandler.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/system/TestXmlRpcFileManager.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/system/TestXmlRpcFileManagerClient.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/tools/TestExpImpCatalog.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/tools/TestMetadataBasedProductMover.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/util/TestXmlRpcStructFactory.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/validation/TestXMLValidationLayer.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/versioning/TestBasicVersioner.java
  1612972 
   
 

Re: Review Request 23878: Successor to rlaidlaw reviewboard #23870 for OODT-685

2014-07-24 Thread Chris Mattmann

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23878/#review48676
---

Ship it!


Ship It!

- Chris Mattmann


On July 24, 2014, 5:52 a.m., Lewis McGibbney wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/23878/
 ---
 
 (Updated July 24, 2014, 5:52 a.m.)
 
 
 Review request for oodt, Tom Barber, Chris Mattmann, Sean Kelly, Paul 
 Ramirez, Rishi Verma, Ross Laidlaw, and Tyler Palsulich.
 
 
 Bugs: OODT-685
 https://issues.apache.org/jira/browse/OODT-685
 
 
 Repository: oodt
 
 
 Description
 ---
 
 Hi Folks,
 OK in the name of staying sane, I am fully behind the decision to just get 
 filemgr back stable. 
 This review board is somewhat of a successor to @rlaidlaw's patch attached to 
 review board request - https://reviews.apache.org/r/23870/
 Bascially, there is now one failing test (as below) which I cannot debug as 
 it passes for me locally within my IDE!!!
 What is more is that from the command line it actually DOES fail!!! 
 
 Results :
 
 Failed tests:
   
 testGetElements(org.apache.oodt.cas.filemgr.validation.TestXMLValidationLayer):
  There aren't exactly 4 elements in the test samples! expected:4 but 
 was:11
 
 Tests run: 190, Failures: 1, Errors: 0, Skipped: 0
 
 From within my IDE the failing test is located at 
 org.apache.oodt.cas.filemgr.validation.TestXMLValidationLayer#testModifyElement,
  which DOES NOT fail when I load it from the command line.
 
 I think we should commit these improvements to the filemgr test suite before 
 moving on to work on maybe upgrading to JUnit 4.11 as per 
 https://issues.apache.org/jira/browse/OODT-687
 
 
 Diffs
 -
 
   
 http://svn.apache.org/repos/asf/oodt/trunk/commons/src/main/java/org/apache/oodt/commons/xml/XMLUtils.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/java/org/apache/oodt/cas/filemgr/validation/XMLValidationLayer.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/catalog/TestDataSourceCatalog.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/catalog/TestMappedDataSourceCatalog.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/catalog/TestOrderedDataSourceCatalog.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/cli/TestFileManagerCli.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/datatransfer/TestLocalDataTransferer.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestCachedIngester.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestLocalCache.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestRmiCache.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestStdIngester.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/repository/TestXMLRepositoryManager.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/structs/type/TestTypeHandler.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/system/TestXmlRpcFileManager.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/system/TestXmlRpcFileManagerClient.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/tools/TestExpImpCatalog.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/tools/TestMetadataBasedProductMover.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/util/TestXmlRpcStructFactory.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/validation/TestXMLValidationLayer.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/versioning/TestBasicVersioner.java
  1612972 
   
 http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/versioning/TestDateTimeVersioner.java
  1612972 
   
 

Re: Review Request 23870: OODT-685: update the file manager unit tests to reflect changes in the project directory structure

2014-07-24 Thread Lewis McGibbney

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23870/#review48678
---


Ultimately committed @revision 1613264 in trunk via 
https://reviews.apache.org/r/23878/
Nice work rlaidlaw... REALLY nice work.

- Lewis McGibbney


On July 23, 2014, 11:33 p.m., Ross Laidlaw wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/23870/
 ---
 
 (Updated July 23, 2014, 11:33 p.m.)
 
 
 Review request for oodt, Lewis McGibbney, Chris Mattmann, and Paul Ramirez.
 
 
 Bugs: OODT-685
 https://issues.apache.org/jira/browse/OODT-685
 
 
 Repository: oodt
 
 
 Description
 ---
 
 After changes in the file manager directory structure for OODT-685, some of 
 the file manager unit tests required updating to point to the new location 
 for test resources (src/testdata moved to src/test/resources).
 
 This patch updates several of the file manager unit tests that referred to 
 src/testdata to point to src/test/resources instead.
 
 It also removes duplicate XML from the following test resources in 
 src/test/resources: cmd-line-actions.xml, cmd-line-options.xml and 
 product-types.xml.
 
 After applying the patch, there are still some issues when running file 
 manager tests (one test error and one test failure), see below for details.
 
 
 Diffs
 -
 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/catalog/TestDataSourceCatalog.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/catalog/TestMappedDataSourceCatalog.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/catalog/TestOrderedDataSourceCatalog.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/cli/TestFileManagerCli.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/datatransfer/TestLocalDataTransferer.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestCachedIngester.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestLocalCache.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestRmiCache.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestStdIngester.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/repository/TestXMLRepositoryManager.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/structs/type/TestTypeHandler.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/system/TestXmlRpcFileManager.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/system/TestXmlRpcFileManagerClient.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/tools/TestExpImpCatalog.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/tools/TestMetadataBasedProductMover.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/util/TestXmlRpcStructFactory.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/validation/TestXMLValidationLayer.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/versioning/TestBasicVersioner.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/versioning/TestDateTimeVersioner.java
  1612886 
   /trunk/filemgr/src/test/resources/cmd-line-actions.xml 1612886 
   /trunk/filemgr/src/test/resources/cmd-line-options.xml 1612886 
   /trunk/filemgr/src/test/resources/xmlrpc-struct-factory/product-types.xml 
 1612886 
 
 Diff: https://reviews.apache.org/r/23870/diff/
 
 
 Testing
 ---
 
 Before applying the patch, the majority of file manager tests fail, as shown 
 by the results below:
 
   Tests run: 189, Failures: 74, Errors: 30, Skipped: 0
 
 
 After applying the patch, the majority of file manager tests pass, except for 
 the following (1 failure, 1 error):
 
   Results :
 
   Failed tests: 
 
 testGetElements(org.apache.oodt.cas.filemgr.validation.TestXMLValidationLayer):
  There aren't exactly 4 elements in the test samples! expected:4 but 
 was:11
 
   Tests in error: 
 testAddProductType(org.apache.oodt.cas.filemgr.cli.TestFileManagerCli): 
 org.apache.oodt.cas.cli.exception.CmdLineConstructionException: Invalid 
 option: 'typeName'
 
 
 Thanks,
 
 Ross Laidlaw
 




Re: Review Request 23870: OODT-685: update the file manager unit tests to reflect changes in the project directory structure

2014-07-24 Thread Tyler Palsulich

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23870/#review48675
---


No joy for me. svn co, patch, mvn install led to:

...
Tests run: 190, Failures: 64, Errors: 28, Skipped: 0
...
Catalog and Archive File Management Component . FAILURE [6.742s]
...


- Tyler Palsulich


On July 23, 2014, 11:33 p.m., Ross Laidlaw wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/23870/
 ---
 
 (Updated July 23, 2014, 11:33 p.m.)
 
 
 Review request for oodt, Lewis McGibbney, Chris Mattmann, and Paul Ramirez.
 
 
 Bugs: OODT-685
 https://issues.apache.org/jira/browse/OODT-685
 
 
 Repository: oodt
 
 
 Description
 ---
 
 After changes in the file manager directory structure for OODT-685, some of 
 the file manager unit tests required updating to point to the new location 
 for test resources (src/testdata moved to src/test/resources).
 
 This patch updates several of the file manager unit tests that referred to 
 src/testdata to point to src/test/resources instead.
 
 It also removes duplicate XML from the following test resources in 
 src/test/resources: cmd-line-actions.xml, cmd-line-options.xml and 
 product-types.xml.
 
 After applying the patch, there are still some issues when running file 
 manager tests (one test error and one test failure), see below for details.
 
 
 Diffs
 -
 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/catalog/TestDataSourceCatalog.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/catalog/TestMappedDataSourceCatalog.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/catalog/TestOrderedDataSourceCatalog.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/cli/TestFileManagerCli.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/datatransfer/TestLocalDataTransferer.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestCachedIngester.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestLocalCache.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestRmiCache.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestStdIngester.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/repository/TestXMLRepositoryManager.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/structs/type/TestTypeHandler.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/system/TestXmlRpcFileManager.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/system/TestXmlRpcFileManagerClient.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/tools/TestExpImpCatalog.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/tools/TestMetadataBasedProductMover.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/util/TestXmlRpcStructFactory.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/validation/TestXMLValidationLayer.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/versioning/TestBasicVersioner.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/versioning/TestDateTimeVersioner.java
  1612886 
   /trunk/filemgr/src/test/resources/cmd-line-actions.xml 1612886 
   /trunk/filemgr/src/test/resources/cmd-line-options.xml 1612886 
   /trunk/filemgr/src/test/resources/xmlrpc-struct-factory/product-types.xml 
 1612886 
 
 Diff: https://reviews.apache.org/r/23870/diff/
 
 
 Testing
 ---
 
 Before applying the patch, the majority of file manager tests fail, as shown 
 by the results below:
 
   Tests run: 189, Failures: 74, Errors: 30, Skipped: 0
 
 
 After applying the patch, the majority of file manager tests pass, except for 
 the following (1 failure, 1 error):
 
   Results :
 
   Failed tests: 
 
 testGetElements(org.apache.oodt.cas.filemgr.validation.TestXMLValidationLayer):
  There aren't exactly 4 elements in the test samples! expected:4 but 
 was:11
 
   Tests in error: 
 testAddProductType(org.apache.oodt.cas.filemgr.cli.TestFileManagerCli): 
 org.apache.oodt.cas.cli.exception.CmdLineConstructionException: Invalid 
 option: 'typeName'
 
 
 Thanks,
 
 Ross Laidlaw
 




Re: [ANNOUNCE] Tyler Palsulich is now on the PMC too!

2014-07-24 Thread Michael Starch
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 jo...@apache.org wrote:

 Yay! Welcome Tyler!!!


 -- Joyce


 On Tue, Jul 22, 2014 at 11:36 AM, Tom Barber tom.bar...@meteorite.bi
 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 tpalsul...@gmail.com
 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






Re: [ANNOUNCE] Tyler Palsulich is now on the PMC too!

2014-07-24 Thread Tom Barber

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 
tpalsul...@gmail.com mailto:tpalsul...@gmail.com 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





Re: Filemgr Tests

2014-07-24 Thread Tom Barber

Hows the stew? ;)

On 19/07/14 00:33, Lewis John Mcgibbney wrote:

I'm going to let this stew over the weekend and come up with some comments
of my own Tom.
There is a LOT for discussion.


On Fri, Jul 18, 2014 at 5:21 PM, Tom Barber tom.bar...@meteorite.bi wrote:


Hello OODT Development Team

I was wondering if
a) it would make sense for us to either have a call at some point, or just
get a thread/jira started that allows us to get a rough idea of what
aspects of OODT people are working on, what they need etc as currently I
don't think many of us have a real clue
b) On the new website, would it be worth publishing a roadmap cause, I
have no clue where the project is going
c) Are there any better ways of sorting out, planning, roadmaps, meetings,
community stuff, and collaboration on tasks, that we can take from other
Apache projects, because, whilst I enjoy OODT, and the ideas behind it (and
I appreciate within the NASA bunch there is probably more cohesion), it
seems a little rudderless in terms of direction. Feel free to flame me at
this point lovely community people.

Regards

Tom







--
*Tom Barber* | Technical Director

meteorite bi
*T:* +44 20 8133 3730
*W:* www.meteorite.bi | *Skype:* meteorite.consulting
*A:* Surrey Technology Centre, Surrey Research Park, Guildford, GU2 7YG, UK


Re: Review Request 23870: OODT-685: update the file manager unit tests to reflect changes in the project directory structure

2014-07-24 Thread Ross Laidlaw

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23870/
---

(Updated July 23, 2014, 11:33 p.m.)


Review request for oodt, Lewis McGibbney, Chris Mattmann, and Paul Ramirez.


Bugs: OODT-685
https://issues.apache.org/jira/browse/OODT-685


Repository: oodt


Description (updated)
---

After changes in the file manager directory structure for OODT-685, some of the 
file manager unit tests required updating to point to the new location for test 
resources (src/testdata moved to src/test/resources).

This patch updates several of the file manager unit tests that referred to 
src/testdata to point to src/test/resources instead.

It also removes duplicate XML from the following test resources in 
src/test/resources: cmd-line-actions.xml, cmd-line-options.xml and 
product-types.xml.

After applying the patch, there are still some issues when running file manager 
tests (one test error and one test failure), see below for details.


Diffs
-

  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/catalog/TestDataSourceCatalog.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/catalog/TestMappedDataSourceCatalog.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/catalog/TestOrderedDataSourceCatalog.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/cli/TestFileManagerCli.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/datatransfer/TestLocalDataTransferer.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestCachedIngester.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestLocalCache.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestRmiCache.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestStdIngester.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/repository/TestXMLRepositoryManager.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/structs/type/TestTypeHandler.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/system/TestXmlRpcFileManager.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/system/TestXmlRpcFileManagerClient.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/tools/TestExpImpCatalog.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/tools/TestMetadataBasedProductMover.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/util/TestXmlRpcStructFactory.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/validation/TestXMLValidationLayer.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/versioning/TestBasicVersioner.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/versioning/TestDateTimeVersioner.java
 1612886 
  /trunk/filemgr/src/test/resources/cmd-line-actions.xml 1612886 
  /trunk/filemgr/src/test/resources/cmd-line-options.xml 1612886 
  /trunk/filemgr/src/test/resources/xmlrpc-struct-factory/product-types.xml 
1612886 

Diff: https://reviews.apache.org/r/23870/diff/


Testing
---

Before applying the patch, the majority of file manager tests fail, as shown by 
the results below:

  Tests run: 189, Failures: 74, Errors: 30, Skipped: 0


After applying the patch, the majority of file manager tests pass, except for 
the following (1 failure, 1 error):

  Results :

  Failed tests: 

testGetElements(org.apache.oodt.cas.filemgr.validation.TestXMLValidationLayer): 
There aren't exactly 4 elements in the test samples! expected:4 but was:11

  Tests in error: 
testAddProductType(org.apache.oodt.cas.filemgr.cli.TestFileManagerCli): 
org.apache.oodt.cas.cli.exception.CmdLineConstructionException: Invalid option: 
'typeName'


Thanks,

Ross Laidlaw



Review Request 23870: OODT-685: update the file manager unit tests to reflect changes in the project directory structure

2014-07-24 Thread Ross Laidlaw

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23870/
---

Review request for oodt, Lewis McGibbney, Chris Mattmann, and Paul Ramirez.


Bugs: OODT-685
https://issues.apache.org/jira/browse/OODT-685


Repository: oodt


Description
---

After some changes in the file manager directory structure for OODT-685, some 
of the file manager unit tests required updating to point to the new location 
for some test resources (src/testdata moved to src/test/resources).

This patch updates some of the file manager unit tests that referred to 
src/testdata to point to src/test/resources instead.

It also removes some duplicate XML from the following test resources in 
src/test/resources: cmd-line-actions.xml, cmd-line-options.xml and 
product-types.xml.

After applying the patch, there are still some issues when running file manager 
tests (one test error and one test failure), see below for details.


Diffs
-

  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/catalog/TestDataSourceCatalog.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/catalog/TestMappedDataSourceCatalog.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/catalog/TestOrderedDataSourceCatalog.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/cli/TestFileManagerCli.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/datatransfer/TestLocalDataTransferer.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestCachedIngester.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestLocalCache.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestRmiCache.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestStdIngester.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/repository/TestXMLRepositoryManager.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/structs/type/TestTypeHandler.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/system/TestXmlRpcFileManager.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/system/TestXmlRpcFileManagerClient.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/tools/TestExpImpCatalog.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/tools/TestMetadataBasedProductMover.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/util/TestXmlRpcStructFactory.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/validation/TestXMLValidationLayer.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/versioning/TestBasicVersioner.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/versioning/TestDateTimeVersioner.java
 1612886 
  /trunk/filemgr/src/test/resources/cmd-line-actions.xml 1612886 
  /trunk/filemgr/src/test/resources/cmd-line-options.xml 1612886 
  /trunk/filemgr/src/test/resources/xmlrpc-struct-factory/product-types.xml 
1612886 

Diff: https://reviews.apache.org/r/23870/diff/


Testing
---

Before applying the patch, the majority of file manager tests fail, as shown by 
the results below:

  Tests run: 189, Failures: 74, Errors: 30, Skipped: 0


After applying the patch, the majority of file manager tests pass, except for 
the following (1 failure, 1 error):

  Results :

  Failed tests: 

testGetElements(org.apache.oodt.cas.filemgr.validation.TestXMLValidationLayer): 
There aren't exactly 4 elements in the test samples! expected:4 but was:11

  Tests in error: 
testAddProductType(org.apache.oodt.cas.filemgr.cli.TestFileManagerCli): 
org.apache.oodt.cas.cli.exception.CmdLineConstructionException: Invalid option: 
'typeName'


Thanks,

Ross Laidlaw



Re: Review Request 23870: OODT-685: update the file manager unit tests to reflect changes in the project directory structure

2014-07-24 Thread Ross Laidlaw

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23870/
---

(Updated July 23, 2014, 11:31 p.m.)


Review request for oodt, Lewis McGibbney, Chris Mattmann, and Paul Ramirez.


Bugs: OODT-685
https://issues.apache.org/jira/browse/OODT-685


Repository: oodt


Description (updated)
---

After changes in the file manager directory structure for OODT-685, some of the 
file manager unit tests required updating to point to the new location for some 
test resources (src/testdata moved to src/test/resources).

This patch updates several of the file manager unit tests that referred to 
src/testdata to point to src/test/resources instead.

It also removes duplicate XML from the following test resources in 
src/test/resources: cmd-line-actions.xml, cmd-line-options.xml and 
product-types.xml.

After applying the patch, there are still some issues when running file manager 
tests (one test error and one test failure), see below for details.


Diffs
-

  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/catalog/TestDataSourceCatalog.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/catalog/TestMappedDataSourceCatalog.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/catalog/TestOrderedDataSourceCatalog.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/cli/TestFileManagerCli.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/datatransfer/TestLocalDataTransferer.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestCachedIngester.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestLocalCache.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestRmiCache.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestStdIngester.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/repository/TestXMLRepositoryManager.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/structs/type/TestTypeHandler.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/system/TestXmlRpcFileManager.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/system/TestXmlRpcFileManagerClient.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/tools/TestExpImpCatalog.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/tools/TestMetadataBasedProductMover.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/util/TestXmlRpcStructFactory.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/validation/TestXMLValidationLayer.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/versioning/TestBasicVersioner.java
 1612886 
  
/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/versioning/TestDateTimeVersioner.java
 1612886 
  /trunk/filemgr/src/test/resources/cmd-line-actions.xml 1612886 
  /trunk/filemgr/src/test/resources/cmd-line-options.xml 1612886 
  /trunk/filemgr/src/test/resources/xmlrpc-struct-factory/product-types.xml 
1612886 

Diff: https://reviews.apache.org/r/23870/diff/


Testing
---

Before applying the patch, the majority of file manager tests fail, as shown by 
the results below:

  Tests run: 189, Failures: 74, Errors: 30, Skipped: 0


After applying the patch, the majority of file manager tests pass, except for 
the following (1 failure, 1 error):

  Results :

  Failed tests: 

testGetElements(org.apache.oodt.cas.filemgr.validation.TestXMLValidationLayer): 
There aren't exactly 4 elements in the test samples! expected:4 but was:11

  Tests in error: 
testAddProductType(org.apache.oodt.cas.filemgr.cli.TestFileManagerCli): 
org.apache.oodt.cas.cli.exception.CmdLineConstructionException: Invalid option: 
'typeName'


Thanks,

Ross Laidlaw



Re: Review Request 23878: Successor to rlaidlaw reviewboard #23870 for OODT-685

2014-07-24 Thread Lewis McGibbney

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23878/
---

(Updated July 24, 2014, 5:52 a.m.)


Review request for oodt, Tom Barber, Chris Mattmann, Sean Kelly, Paul Ramirez, 
Rishi Verma, Ross Laidlaw, and Tyler Palsulich.


Bugs: OODT-685
https://issues.apache.org/jira/browse/OODT-685


Repository: oodt


Description
---

Hi Folks,
OK in the name of staying sane, I am fully behind the decision to just get 
filemgr back stable. 
This review board is somewhat of a successor to @rlaidlaw's patch attached to 
review board request - https://reviews.apache.org/r/23870/
Bascially, there is now one failing test (as below) which I cannot debug as it 
passes for me locally within my IDE!!!
What is more is that from the command line it actually DOES fail!!! 

Results :

Failed tests:
  
testGetElements(org.apache.oodt.cas.filemgr.validation.TestXMLValidationLayer): 
There aren't exactly 4 elements in the test samples! expected:4 but was:11

Tests run: 190, Failures: 1, Errors: 0, Skipped: 0

From within my IDE the failing test is located at 
org.apache.oodt.cas.filemgr.validation.TestXMLValidationLayer#testModifyElement,
 which DOES NOT fail when I load it from the command line.

I think we should commit these improvements to the filemgr test suite before 
moving on to work on maybe upgrading to JUnit 4.11 as per 
https://issues.apache.org/jira/browse/OODT-687


Diffs
-

  
http://svn.apache.org/repos/asf/oodt/trunk/commons/src/main/java/org/apache/oodt/commons/xml/XMLUtils.java
 1612972 
  
http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/java/org/apache/oodt/cas/filemgr/validation/XMLValidationLayer.java
 1612972 
  
http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/catalog/TestDataSourceCatalog.java
 1612972 
  
http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/catalog/TestMappedDataSourceCatalog.java
 1612972 
  
http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/catalog/TestOrderedDataSourceCatalog.java
 1612972 
  
http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/cli/TestFileManagerCli.java
 1612972 
  
http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/datatransfer/TestLocalDataTransferer.java
 1612972 
  
http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestCachedIngester.java
 1612972 
  
http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestLocalCache.java
 1612972 
  
http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestRmiCache.java
 1612972 
  
http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestStdIngester.java
 1612972 
  
http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/repository/TestXMLRepositoryManager.java
 1612972 
  
http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/structs/type/TestTypeHandler.java
 1612972 
  
http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/system/TestXmlRpcFileManager.java
 1612972 
  
http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/system/TestXmlRpcFileManagerClient.java
 1612972 
  
http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/tools/TestExpImpCatalog.java
 1612972 
  
http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/tools/TestMetadataBasedProductMover.java
 1612972 
  
http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/util/TestXmlRpcStructFactory.java
 1612972 
  
http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/validation/TestXMLValidationLayer.java
 1612972 
  
http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/versioning/TestBasicVersioner.java
 1612972 
  
http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/versioning/TestDateTimeVersioner.java
 1612972 
  
http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/resources/cmd-line-actions.xml
 1612972 
  
http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/resources/cmd-line-options.xml
 1612972 
  
http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/test/resources/xmlrpc-struct-factory/product-types.xml
 1612972 

Diff: https://reviews.apache.org/r/23878/diff/


Testing
---

via command line with following environment variables I get obe failing test as 
described above.
Running 

Re: Review Request 23870: OODT-685: update the file manager unit tests to reflect changes in the project directory structure

2014-07-24 Thread Lewis McGibbney


 On July 23, 2014, 11:50 p.m., Lewis McGibbney wrote:
  Checked out fresh copy of trunk, applied patch
  mvn install
  
  Results :
  
  Failed tests:

  testGetElements(org.apache.oodt.cas.filemgr.validation.TestXMLValidationLayer):
   There aren't exactly 4 elements in the test samples! expected:4 but 
  was:11
  
  Tests in error:
testAddProductType(org.apache.oodt.cas.filemgr.cli.TestFileManagerCli): 
  org.apache.oodt.cas.cli.exception.CmdLineConstructionException: Invalid 
  option: 'typeName'
  
  Tests run: 190, Failures: 1, Errors: 1, Skipped: 0
  
  I seriously think that we should commit this patch as a solution to 
  stabalizing trunk codebase in filemgr

Additionally, this patch avoid changing too much as it does not pick up test 
resources from the /target/test-classes/ directory, it also still loads 
resources into System calls as oppose to piping resources to a 
'java.util.Property' object however this means that we can change this at a 
later stage.
Stabalizing trunk build is the priority here as it is a blocker for releasing 
0.7, Ross' patch here is a good short term solution to fixing this.


- Lewis


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23870/#review48576
---


On July 23, 2014, 11:33 p.m., Ross Laidlaw wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/23870/
 ---
 
 (Updated July 23, 2014, 11:33 p.m.)
 
 
 Review request for oodt, Lewis McGibbney, Chris Mattmann, and Paul Ramirez.
 
 
 Bugs: OODT-685
 https://issues.apache.org/jira/browse/OODT-685
 
 
 Repository: oodt
 
 
 Description
 ---
 
 After changes in the file manager directory structure for OODT-685, some of 
 the file manager unit tests required updating to point to the new location 
 for test resources (src/testdata moved to src/test/resources).
 
 This patch updates several of the file manager unit tests that referred to 
 src/testdata to point to src/test/resources instead.
 
 It also removes duplicate XML from the following test resources in 
 src/test/resources: cmd-line-actions.xml, cmd-line-options.xml and 
 product-types.xml.
 
 After applying the patch, there are still some issues when running file 
 manager tests (one test error and one test failure), see below for details.
 
 
 Diffs
 -
 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/catalog/TestDataSourceCatalog.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/catalog/TestMappedDataSourceCatalog.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/catalog/TestOrderedDataSourceCatalog.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/cli/TestFileManagerCli.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/datatransfer/TestLocalDataTransferer.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestCachedIngester.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestLocalCache.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestRmiCache.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestStdIngester.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/repository/TestXMLRepositoryManager.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/structs/type/TestTypeHandler.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/system/TestXmlRpcFileManager.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/system/TestXmlRpcFileManagerClient.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/tools/TestExpImpCatalog.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/tools/TestMetadataBasedProductMover.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/util/TestXmlRpcStructFactory.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/validation/TestXMLValidationLayer.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/versioning/TestBasicVersioner.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/versioning/TestDateTimeVersioner.java
  1612886 
   /trunk/filemgr/src/test/resources/cmd-line-actions.xml 1612886 
   /trunk/filemgr/src/test/resources/cmd-line-options.xml 1612886 
   /trunk/filemgr/src/test/resources/xmlrpc-struct-factory/product-types.xml 
 1612886 
 
 Diff: https://reviews.apache.org/r/23870/diff/
 
 
 Testing
 ---
 
 Before applying the patch, the majority of file manager tests fail, as 

Re: [ANNOUNCE] Tyler Palsulich is now on the PMC too!

2014-07-24 Thread Tom Barber

Hey Tyler,

I've seen some failures but not this one before, can you dig out the 
failure message from the surefire test? You could always just munge it 
and try -DskipTests


On 23/07/14 16:49, Tyler Palsulich 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 
rajithsiriward...@gmail.com wrote:


Welcome Tyler..!!!


Cheers,
--Rajith


On Wed, Jul 23, 2014 at 1:06 AM, Michael Starch starc...@umich.edu
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 jo...@apache.org wrote:


Yay! Welcome Tyler!!!


-- Joyce


On Tue, Jul 22, 2014 at 11:36 AM, Tom Barber tom.bar...@meteorite.bi
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 tpalsul...@gmail.com

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






--
*Tom Barber* | Technical Director

meteorite bi
*T:* +44 20 8133 3730
*W:* www.meteorite.bi | *Skype:* meteorite.consulting
*A:* Surrey Technology Centre, Surrey Research Park, Guildford, GU2 7YG, UK


Re: Review Request 23870: OODT-685: update the file manager unit tests to reflect changes in the project directory structure

2014-07-24 Thread Lewis McGibbney

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23870/#review48576
---


Checked out fresh copy of trunk, applied patch
mvn install

Results :

Failed tests:
  
testGetElements(org.apache.oodt.cas.filemgr.validation.TestXMLValidationLayer): 
There aren't exactly 4 elements in the test samples! expected:4 but was:11

Tests in error:
  testAddProductType(org.apache.oodt.cas.filemgr.cli.TestFileManagerCli): 
org.apache.oodt.cas.cli.exception.CmdLineConstructionException: Invalid option: 
'typeName'

Tests run: 190, Failures: 1, Errors: 1, Skipped: 0

I seriously think that we should commit this patch as a solution to stabalizing 
trunk codebase in filemgr

- Lewis McGibbney


On July 23, 2014, 11:33 p.m., Ross Laidlaw wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/23870/
 ---
 
 (Updated July 23, 2014, 11:33 p.m.)
 
 
 Review request for oodt, Lewis McGibbney, Chris Mattmann, and Paul Ramirez.
 
 
 Bugs: OODT-685
 https://issues.apache.org/jira/browse/OODT-685
 
 
 Repository: oodt
 
 
 Description
 ---
 
 After changes in the file manager directory structure for OODT-685, some of 
 the file manager unit tests required updating to point to the new location 
 for test resources (src/testdata moved to src/test/resources).
 
 This patch updates several of the file manager unit tests that referred to 
 src/testdata to point to src/test/resources instead.
 
 It also removes duplicate XML from the following test resources in 
 src/test/resources: cmd-line-actions.xml, cmd-line-options.xml and 
 product-types.xml.
 
 After applying the patch, there are still some issues when running file 
 manager tests (one test error and one test failure), see below for details.
 
 
 Diffs
 -
 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/catalog/TestDataSourceCatalog.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/catalog/TestMappedDataSourceCatalog.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/catalog/TestOrderedDataSourceCatalog.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/cli/TestFileManagerCli.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/datatransfer/TestLocalDataTransferer.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestCachedIngester.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestLocalCache.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestRmiCache.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/ingest/TestStdIngester.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/repository/TestXMLRepositoryManager.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/structs/type/TestTypeHandler.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/system/TestXmlRpcFileManager.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/system/TestXmlRpcFileManagerClient.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/tools/TestExpImpCatalog.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/tools/TestMetadataBasedProductMover.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/util/TestXmlRpcStructFactory.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/validation/TestXMLValidationLayer.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/versioning/TestBasicVersioner.java
  1612886 
   
 /trunk/filemgr/src/test/java/org/apache/oodt/cas/filemgr/versioning/TestDateTimeVersioner.java
  1612886 
   /trunk/filemgr/src/test/resources/cmd-line-actions.xml 1612886 
   /trunk/filemgr/src/test/resources/cmd-line-options.xml 1612886 
   /trunk/filemgr/src/test/resources/xmlrpc-struct-factory/product-types.xml 
 1612886 
 
 Diff: https://reviews.apache.org/r/23870/diff/
 
 
 Testing
 ---
 
 Before applying the patch, the majority of file manager tests fail, as shown 
 by the results below:
 
   Tests run: 189, Failures: 74, Errors: 30, Skipped: 0
 
 
 After applying the patch, the majority of file manager tests pass, except for 
 the following (1 failure, 1 error):
 
   Results :
 
   Failed tests: 
 
 testGetElements(org.apache.oodt.cas.filemgr.validation.TestXMLValidationLayer):
  There aren't exactly 4 elements in the test samples! expected:4 but 
 was:11
 
   Tests in error: 
 testAddProductType(org.apache.oodt.cas.filemgr.cli.TestFileManagerCli):