Jenkins build became unstable: oodt-trunk #1822

2015-04-28 Thread Apache Jenkins Server
See https://builds.apache.org/job/oodt-trunk/1822/



[GitHub] oodt pull request: Moved scala plugin from core pom to streaming p...

2015-04-28 Thread r4space
GitHub user r4space opened a pull request:

https://github.com/apache/oodt/pull/20

Moved scala plugin from core pom to streaming pom only



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/r4space/oodt trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/oodt/pull/20.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #20


commit 01afbe89953ef621379f906bb4e186a5eccf1e8e
Author: Jane Wyngaard wynga...@jpl.nasa.gov
Date:   2015-04-28T16:14:45Z

Moved scala plugin from core pom to streaming pom only




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


Re: [GitHub] oodt pull request: Moved scala plugin from core pom to streaming p...

2015-04-28 Thread Michael Starch
Yeah I noticed.  Thanks!

On Tue, Apr 28, 2015 at 10:22 AM, Chris Mattmann chris.mattm...@gmail.com
wrote:

 Done already! :)

 
 Chris Mattmann
 chris.mattm...@gmail.com




 -Original Message-
 From: Michael Starch starc...@umich.edu
 Reply-To: dev@oodt.apache.org
 Date: Tuesday, April 28, 2015 at 10:21 AM
 To: dev@oodt.apache.org
 Subject: Re: [GitHub] oodt pull request: Moved scala plugin from core pom
 to streaming p...

 All,
 
 I will check this in.
 
 -Michael
 
 On Tue, Apr 28, 2015 at 9:18 AM, r4space g...@git.apache.org wrote:
 
  GitHub user r4space opened a pull request:
 
  https://github.com/apache/oodt/pull/20
 
  Moved scala plugin from core pom to streaming pom only
 
 
 
  You can merge this pull request into a Git repository by running:
 
  $ git pull https://github.com/r4space/oodt trunk
 
  Alternatively you can review and apply these changes as the patch at:
 
  https://github.com/apache/oodt/pull/20.patch
 
  To close this pull request, make a commit to your master/trunk branch
  with (at least) the following in the commit message:
 
  This closes #20
 
  
  commit 01afbe89953ef621379f906bb4e186a5eccf1e8e
  Author: Jane Wyngaard wynga...@jpl.nasa.gov
  Date:   2015-04-28T16:14:45Z
 
  Moved scala plugin from core pom to streaming pom only
 
  
 
 
  ---
  If your project is set up for it, you can reply to this email and have
 your
  reply appear on GitHub as well. If your project does not have this
 feature
  enabled and wishes so, or if the feature is enabled but not working,
 please
  contact infrastructure at infrastruct...@apache.org or file a JIRA
 ticket
  with INFRA.
  ---
 





Re: [GitHub] oodt pull request: Moved scala plugin from core pom to streaming p...

2015-04-28 Thread Chris Mattmann
Done already! :)


Chris Mattmann
chris.mattm...@gmail.com




-Original Message-
From: Michael Starch starc...@umich.edu
Reply-To: dev@oodt.apache.org
Date: Tuesday, April 28, 2015 at 10:21 AM
To: dev@oodt.apache.org
Subject: Re: [GitHub] oodt pull request: Moved scala plugin from core pom
to streaming p...

All,

I will check this in.

-Michael

On Tue, Apr 28, 2015 at 9:18 AM, r4space g...@git.apache.org wrote:

 GitHub user r4space opened a pull request:

 https://github.com/apache/oodt/pull/20

 Moved scala plugin from core pom to streaming pom only



 You can merge this pull request into a Git repository by running:

 $ git pull https://github.com/r4space/oodt trunk

 Alternatively you can review and apply these changes as the patch at:

 https://github.com/apache/oodt/pull/20.patch

 To close this pull request, make a commit to your master/trunk branch
 with (at least) the following in the commit message:

 This closes #20

 
 commit 01afbe89953ef621379f906bb4e186a5eccf1e8e
 Author: Jane Wyngaard wynga...@jpl.nasa.gov
 Date:   2015-04-28T16:14:45Z

 Moved scala plugin from core pom to streaming pom only

 


 ---
 If your project is set up for it, you can reply to this email and have
your
 reply appear on GitHub as well. If your project does not have this
feature
 enabled and wishes so, or if the feature is enabled but not working,
please
 contact infrastructure at infrastruct...@apache.org or file a JIRA
ticket
 with INFRA.
 ---





Re: [GitHub] oodt pull request: Moved scala plugin from core pom to streaming p...

2015-04-28 Thread Michael Starch
All,

I will check this in.

-Michael

On Tue, Apr 28, 2015 at 9:18 AM, r4space g...@git.apache.org wrote:

 GitHub user r4space opened a pull request:

 https://github.com/apache/oodt/pull/20

 Moved scala plugin from core pom to streaming pom only



 You can merge this pull request into a Git repository by running:

 $ git pull https://github.com/r4space/oodt trunk

 Alternatively you can review and apply these changes as the patch at:

 https://github.com/apache/oodt/pull/20.patch

 To close this pull request, make a commit to your master/trunk branch
 with (at least) the following in the commit message:

 This closes #20

 
 commit 01afbe89953ef621379f906bb4e186a5eccf1e8e
 Author: Jane Wyngaard wynga...@jpl.nasa.gov
 Date:   2015-04-28T16:14:45Z

 Moved scala plugin from core pom to streaming pom only

 


 ---
 If your project is set up for it, you can reply to this email and have your
 reply appear on GitHub as well. If your project does not have this feature
 enabled and wishes so, or if the feature is enabled but not working, please
 contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
 with INFRA.
 ---



[GitHub] oodt pull request: Moved scala plugin from core pom to streaming p...

2015-04-28 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/oodt/pull/20


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---