[jira] Subscription: Oozie Patch Available

2015-03-31 Thread jira 
Issue Subscription
Filter: Oozie Patch Available (48 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-2188  Fix typos in twiki documentation
https://issues.apache.org/jira/browse/OOZIE-2188
OOZIE-2170  Oozie should automatically set configs to make Spark jobs show up 
in the Spark History Server
https://issues.apache.org/jira/browse/OOZIE-2170
OOZIE-2168  Oozie flow and action names have 50 char limit 
https://issues.apache.org/jira/browse/OOZIE-2168
OOZIE-2140  Audit Log should be shown in Oozie UI
https://issues.apache.org/jira/browse/OOZIE-2140
OOZIE-2134  Remove references to Services.get().getConf() in code
https://issues.apache.org/jira/browse/OOZIE-2134
OOZIE-2130  Add EL Function for offsetting a date by a timezone amount 
including DST
https://issues.apache.org/jira/browse/OOZIE-2130
OOZIE-2129  Duplicate child jobs per instance
https://issues.apache.org/jira/browse/OOZIE-2129
OOZIE-2106  Make tomcat download url configurable in the pom file
https://issues.apache.org/jira/browse/OOZIE-2106
OOZIE-2105  Make version of submodules configurable with parent version 
https://issues.apache.org/jira/browse/OOZIE-2105
OOZIE-2099  Add test-patch support for patches generated without --no-prefix
https://issues.apache.org/jira/browse/OOZIE-2099
OOZIE-2081  WorkflowJob notification to include coordinator action id 
https://issues.apache.org/jira/browse/OOZIE-2081
OOZIE-2060  Incorrect documentation of Java action config XML filename
https://issues.apache.org/jira/browse/OOZIE-2060
OOZIE-2051  Allows multiple default action configuration files per action
https://issues.apache.org/jira/browse/OOZIE-2051
OOZIE-2044  ssh action succeed with a not exists command which should be fail.
https://issues.apache.org/jira/browse/OOZIE-2044
OOZIE-2030  Configuration properties from global section is not getting set in 
Hadoop job conf when using sub-workflow action in Oozie workflow.xml 
https://issues.apache.org/jira/browse/OOZIE-2030
OOZIE-1980  Sql error should not fail coord job
https://issues.apache.org/jira/browse/OOZIE-1980
OOZIE-1977  Display patch analysis issues
https://issues.apache.org/jira/browse/OOZIE-1977
OOZIE-1963  Create a Hive Server 2 example
https://issues.apache.org/jira/browse/OOZIE-1963
OOZIE-1936  Queuedump command should display queue information for all server.
https://issues.apache.org/jira/browse/OOZIE-1936
OOZIE-1931  Admin command to print all locks held by server(s)
https://issues.apache.org/jira/browse/OOZIE-1931
OOZIE-1927  Use StoreStatusFilter for WorkflowsJobGetJPAExecutor 
https://issues.apache.org/jira/browse/OOZIE-1927
OOZIE-1922  MemoryLocksService fails if lock is acquired multiple times in same 
thread and released
https://issues.apache.org/jira/browse/OOZIE-1922
OOZIE-1918  ActionXCommand refactoring for code reuse
https://issues.apache.org/jira/browse/OOZIE-1918
OOZIE-1884  ZKJobsConcurrencyService.checkJobIdForServer fails if jobs length > 
7
https://issues.apache.org/jira/browse/OOZIE-1884
OOZIE-1860  Oozie job mapper launch fails due to null value returned from 
action file
https://issues.apache.org/jira/browse/OOZIE-1860
OOZIE-1855  TestPriorityDelayQueue#testPoll failed intermittently in Jenkins
https://issues.apache.org/jira/browse/OOZIE-1855
OOZIE-1829  URIHandlerService doesn't support URI schemes with query strings 
but no path segment
https://issues.apache.org/jira/browse/OOZIE-1829
OOZIE-1816  LogInfo uses action name instead of id
https://issues.apache.org/jira/browse/OOZIE-1816
OOZIE-1810  Workflow cannot get into Failed state when kill control node cannot 
resolve variable in message 
https://issues.apache.org/jira/browse/OOZIE-1810
OOZIE-1802  Support workflow action log
https://issues.apache.org/jira/browse/OOZIE-1802
OOZIE-1793  Improve find bugs reporting for Oozie
https://issues.apache.org/jira/browse/OOZIE-1793
OOZIE-1782  Workflow path not found is thrown as SC_UNAUTHORIZED
https://issues.apache.org/jira/browse/OOZIE-1782
OOZIE-1779  Add parent-id as a filter option
https://issues.apache.org/jira/browse/OOZIE-1779
OOZIE-1705  Enable gc logs and print thread id in logs
https://issues.apache.org/jira/browse/OOZIE-1705
OOZIE-1676  Instrumentation and Configuration over the REST API and Web UI 
should include all Oozie servers
https://issues.apache.org/jira/browse/OOZIE-1676
OOZIE-1654  Fix typo (inteval to interval)
https://issues.apache.org/jira/browse/OOZIE-1654
OOZIE-1638  Action retry does not respect default retry max count.
https://issues.apache.org/jira/browse/OOZIE-1638
OOZIE-1636  OOZIE_SYS table engine shou

[jira] [Commented] (OOZIE-1963) Create a Hive Server 2 example

2015-03-31 Thread Robert Kanter (JIRA) 

[ 
https://issues.apache.org/jira/browse/OOZIE-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14390031#comment-14390031
 ] 

Robert Kanter commented on OOZIE-1963:
--

Looks good overall, a few things:
# Can you rename "hive-node" to "hive2-node"?
# Can you rename "hive-wf" to "hive2-wf"?
# Can you update the kill node's message to something like "Hive2 failed..." or 
"Beeline failed..." etc?
# Can you add a README to let users know that they need to have a Hive Server 2 
running?  It can be similar to the HCatalog example, but probably simpler as it 
doesn't need to talk about jars and as much setup.
# Can you add a secure version of the workflow that uses Hive2Credentials, 
similar to the HCatalog example?

> Create a Hive Server 2 example
> --
>
> Key: OOZIE-1963
> URL: https://issues.apache.org/jira/browse/OOZIE-1963
> Project: Oozie
>  Issue Type: Sub-task
>  Components: action
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Harsh J
> Fix For: trunk
>
> Attachments: OOZIE-1963.patch, OOZIE-1963.patch
>
>
> Create an example for the new Hive Server 2 action.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Review Request 32443: OOZIE-2183 provide an option to disable cleanup for output dataset in rerun

2015-03-31 Thread Ryota Egashira 

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

(Updated March 31, 2015, 11:36 p.m.)


Review request for oozie.


Changes
---

fixed comment


Summary (updated)
-

OOZIE-2183 provide an option to disable cleanup for output dataset in rerun 


Repository: oozie-git


Description
---

https://issues.apache.org/jira/browse/OOZIE-2183


Diffs (updated)
-

  client/src/main/resources/oozie-coordinator-0.4.xsd 78205f6 
  core/src/main/java/org/apache/oozie/command/coord/CoordRerunXCommand.java 
050662e 
  core/src/test/java/org/apache/oozie/command/coord/TestCoordRerunXCommand.java 
45457d1 
  core/src/test/resources/coord-rerun-action4.xml PRE-CREATION 
  docs/src/site/twiki/CoordinatorFunctionalSpec.twiki 0812bb8 
  docs/src/site/twiki/DG_CoordinatorRerun.twiki c937da5 

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


Testing
---


Thanks,

Ryota Egashira

[jira] [Updated] (OOZIE-2182) SLA alert commands are not in sync with doc

2015-03-31 Thread Purshotam Shah (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OOZIE-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Purshotam Shah updated OOZIE-2182:
--
Attachment: OOZIE-2182-V1.patch

> SLA alert commands are not in sync with doc
> ---
>
> Key: OOZIE-2182
> URL: https://issues.apache.org/jira/browse/OOZIE-2182
> Project: Oozie
>  Issue Type: Bug
>Reporter: Purshotam Shah
> Attachments: OOZIE-2182-V1.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1624) Exclusion pattern for sharelib.

2015-03-31 Thread Purshotam Shah (JIRA) 

[ 
https://issues.apache.org/jira/browse/OOZIE-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389516#comment-14389516
 ] 

Purshotam Shah commented on OOZIE-1624:
---

{quote}
Even with metafile, the shareliblist command exposes the file paths. hbase. 
*thrift. *. jar would match both cases. It is easy to write a generic regex for 
a file under given directory how many ever levels it is nested.
{quote}
This is what my worry is, full path is exposed to user and he create any regex 
which might break in future release. Not every user will follow best practices.
Ex 1.
Pig_current/Pig can internally point to .../pig.10.0.1.0.xx/lib/jar
Since path is exposed to user, he can create regex as 
.*/pig.10.0.1.0.xx/lib/jar/abc*.jar.
If we move pig_current/pig to next pig release, then all user job at production 
will start failing.

Ex 2.
Currently if thift jar in in hbase dir, habse/lib/thift.jar
By looking at sharelib full path, user can create regex as 
.*/hbase/lib/thift.jar.
This will prohibit ops/admin to change hbase sharelib directory structure.

> Exclusion pattern for sharelib.
> ---
>
> Key: OOZIE-1624
> URL: https://issues.apache.org/jira/browse/OOZIE-1624
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Purshotam Shah
>Assignee: Purshotam Shah
> Attachments: OOZIE-1624-V2.patch, OOZIE-1624-v1.patch
>
>
> Sharelib may bring some jar which might conflict with user jars.
> Ex. Sharelib hive has json-2..jar, where as some of the user use-case 
> need higher version of json jar.
> He should be able to exclude sharelib json jar and bring his own version.
> 
> oozie.action.sharelib.for.hive.exclusion
> json-\*.jar|abc-*.jar
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2157) Oozie job submit calls jobsServlet ( not jobServelt) to submit job

2015-03-31 Thread Jacob Tolar (JIRA) 

[ 
https://issues.apache.org/jira/browse/OOZIE-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389424#comment-14389424
 ] 

Jacob Tolar commented on OOZIE-2157:


i think that's a pretty typical RESTful convention - adding a new job to the 
jobs collection would be a POST to /jobs.

that said, i do think it's confusing that there are 2 separate endpoints. as 
far as i can tell, there's no real reason /jobs and /job can't be combined into 
a single /jobs endpoint (except that you'd need to bump the api version to v3 
to avoid compatibility issues).

POST /jobs - unchanged
GET /jobs - unchanged
GET /jobs/ - same behavior as /job/

> Oozie job submit calls jobsServlet ( not jobServelt) to submit job
> --
>
> Key: OOZIE-2157
> URL: https://issues.apache.org/jira/browse/OOZIE-2157
> Project: Oozie
>  Issue Type: Bug
>Reporter: Purshotam Shah
>
> {code}
> JobSubmit(Properties conf, boolean start) {
> super("POST", RestConstants.JOBS, "", (start) ? 
> prepareParams(RestConstants.ACTION_PARAM,
> RestConstants.JOB_ACTION_START) : prepareParams());
> this.conf = notNull(conf, "conf");
> }
> {code}
> Where other job operation  goes to jobServelt.
> Does anyone know reason behind this?
> In-fact jobServlet doesn't have any method to accept job submission.
> It confusion for people who uses web-service to interact with Oozie.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2190) Fix conflicts between generated filenames and user filenames in actions

2015-03-31 Thread Rohini Palaniswamy (JIRA) 

[ 
https://issues.apache.org/jira/browse/OOZIE-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389282#comment-14389282
 ] 

Rohini Palaniswamy commented on OOZIE-2190:
---

This is good instead of having to painfully add them to job xml. We added 
getShareLibFilesForActionConf to methods to get files that will have conflict 
(currently only hive-site.xml) and add them directly to action xml if they were 
part of sharelib (Previously hive-site.xml in sharelib was not possible). But 
it does not address cases where user has specified hive-site.xml. 
Please rename that method to give a more common name and reuse it for this jira 
for hive and sqoop.

> Fix conflicts between generated filenames and user filenames in actions
> ---
>
> Key: OOZIE-2190
> URL: https://issues.apache.org/jira/browse/OOZIE-2190
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Reporter: Robert Kanter
>
> We've seen issues where if you have a hive-site.xml with the Hive action or a 
> sqoop-site.xml with the Sqoop action, it fails because of a name conflict 
> (the action wants to write a file with the same name).  We should go through 
> all of the actions and look for any filenames that go into the working 
> directory and try to fix these name conflicts.  Here are some ideas on how to 
> fix this:
> # Generate a subdir in the working directory named "oozie-" and 
> put all files generated by the action in there; it would be extremely 
> unlikely for the user to have a directory named that.
> # Before creating any files in the action, we check if that file already 
> exists and if so, rename it
> # Add "-" to the filenames generated by actions
> I think option 1 is the easiest and best for maintainability.  We can make 
> some helper method that all of the actions can use that returns the directory 
> that's created and just make sure to put any created files in there.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2150) Shell launcher should print shell script

2015-03-31 Thread Purshotam Shah (JIRA) 

[ 
https://issues.apache.org/jira/browse/OOZIE-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389227#comment-14389227
 ] 

Purshotam Shah commented on OOZIE-2150:
---

[~jacobtolar] I have assigned JIRA to you.

> Shell launcher should print shell script
> 
>
> Key: OOZIE-2150
> URL: https://issues.apache.org/jira/browse/OOZIE-2150
> Project: Oozie
>  Issue Type: Bug
>Reporter: Purshotam Shah
>Assignee: Jacob Tolar
>Priority: Minor
>
> Pig and Hive does this. It will be helpful in debugging.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OOZIE-2150) Shell launcher should print shell script

2015-03-31 Thread Purshotam Shah (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OOZIE-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Purshotam Shah reassigned OOZIE-2150:
-

Assignee: Purshotam Shah

> Shell launcher should print shell script
> 
>
> Key: OOZIE-2150
> URL: https://issues.apache.org/jira/browse/OOZIE-2150
> Project: Oozie
>  Issue Type: Bug
>Reporter: Purshotam Shah
>Assignee: Purshotam Shah
>Priority: Minor
>
> Pig and Hive does this. It will be helpful in debugging.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2150) Shell launcher should print shell script

2015-03-31 Thread Purshotam Shah (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OOZIE-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Purshotam Shah updated OOZIE-2150:
--
Assignee: Jacob Tolar  (was: Purshotam Shah)

> Shell launcher should print shell script
> 
>
> Key: OOZIE-2150
> URL: https://issues.apache.org/jira/browse/OOZIE-2150
> Project: Oozie
>  Issue Type: Bug
>Reporter: Purshotam Shah
>Assignee: Jacob Tolar
>Priority: Minor
>
> Pig and Hive does this. It will be helpful in debugging.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2150) Shell launcher should print shell script

2015-03-31 Thread Jacob Tolar (JIRA) 

[ 
https://issues.apache.org/jira/browse/OOZIE-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389179#comment-14389179
 ] 

Jacob Tolar commented on OOZIE-2150:


I agree that this would be a nice feature, but it won't work nicely all the 
time - a shell action isn't necessarily running a script (you can ship and run 
a binary, or use an interpreter in  and a a script as an argument). 

I imagine you could catch many/most cases if you use a library (e.g. 
http://tika.apache.org/ ) to guess the type of file in , and print it if 
it doesn't look like an executable.

if this approach makes sense, I could work on this.

> Shell launcher should print shell script
> 
>
> Key: OOZIE-2150
> URL: https://issues.apache.org/jira/browse/OOZIE-2150
> Project: Oozie
>  Issue Type: Bug
>Reporter: Purshotam Shah
>Priority: Minor
>
> Pig and Hive does this. It will be helpful in debugging.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OOZIE-2190) Fix filename conflicts in actions

2015-03-31 Thread Robert Kanter (JIRA) 
Robert Kanter created OOZIE-2190:


 Summary: Fix filename conflicts in actions
 Key: OOZIE-2190
 URL: https://issues.apache.org/jira/browse/OOZIE-2190
 Project: Oozie
  Issue Type: Bug
  Components: action
Reporter: Robert Kanter


We've seen issues where if you have a hive-site.xml with the Hive action or a 
sqoop-site.xml with the Sqoop action, it fails because of a name conflict (the 
action wants to write a file with the same name).  We should go through all of 
the actions and look for any filenames that go into the working directory and 
try to fix these name conflicts.  Here are some ideas on how to fix this:
# Generate a subdir in the working directory named "oozie-" and put 
all files generated by the action in there; it would be extremely unlikely for 
the user to have a directory named that.
# Before creating any files in the action, we check if that file already exists 
and if so, rename it
# Add "-" to the filenames generated by actions

I think option 1 is the easiest and best for maintainability.  We can make some 
helper method that all of the actions can use that returns the directory that's 
created and just make sure to put any created files in there.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2190) Fix conflicts between generated filenames and user filenames in actions

2015-03-31 Thread Robert Kanter (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OOZIE-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Kanter updated OOZIE-2190:
-
Summary: Fix conflicts between generated filenames and user filenames in 
actions  (was: Fix filename conflicts in actions)

> Fix conflicts between generated filenames and user filenames in actions
> ---
>
> Key: OOZIE-2190
> URL: https://issues.apache.org/jira/browse/OOZIE-2190
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Reporter: Robert Kanter
>
> We've seen issues where if you have a hive-site.xml with the Hive action or a 
> sqoop-site.xml with the Sqoop action, it fails because of a name conflict 
> (the action wants to write a file with the same name).  We should go through 
> all of the actions and look for any filenames that go into the working 
> directory and try to fix these name conflicts.  Here are some ideas on how to 
> fix this:
> # Generate a subdir in the working directory named "oozie-" and 
> put all files generated by the action in there; it would be extremely 
> unlikely for the user to have a directory named that.
> # Before creating any files in the action, we check if that file already 
> exists and if so, rename it
> # Add "-" to the filenames generated by actions
> I think option 1 is the easiest and best for maintainability.  We can make 
> some helper method that all of the actions can use that returns the directory 
> that's created and just make sure to put any created files in there.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2174) Add missing admin commands to OozieClient and OozieCLI

2015-03-31 Thread Hadoop QA (JIRA) 

[ 
https://issues.apache.org/jira/browse/OOZIE-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388166#comment-14388166
 ] 

Hadoop QA commented on OOZIE-2174:
--

Testing JIRA OOZIE-2174

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:red}-1{color} the patch contains 74 line(s) with tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:red}-1{color} the patch contains 2 line(s) longer than 132 
characters
.{color:green}+1{color} the patch does adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1635
.Tests failed: 1
.Tests errors: 0

.The patch failed the following testcases:

.  
testCoordRerunDateNeg(org.apache.oozie.command.coord.TestCoordRerunXCommand)

{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


The full output of the test-patch run is available at

.   https://builds.apache.org/job/oozie-trunk-precommit-build/2283/

> Add missing admin commands to OozieClient and OozieCLI
> --
>
> Key: OOZIE-2174
> URL: https://issues.apache.org/jira/browse/OOZIE-2174
> Project: Oozie
>  Issue Type: Improvement
>  Components: client
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Robert Kanter
> Attachments: OOZIE-2174.patch, OOZIE-2174.patch, OOZIE-2174.patch
>
>
> {{OozieClient}} and {{OozieCLI}} are missing some of the admin commands that 
> have been available over the REST API for a long time.  We should add them:
> - Get Configuration
> - Get OS Env
> - Get Java System Properties
> - Get Instrumentation/Metrics
> -- For this one, we can either make them separate commands or one command 
> that tries one endpoint then the other.  I'll see what works best.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Build failed in Jenkins: oozie-trunk-precommit-build #2283

2015-03-31 Thread Apache Jenkins Server 
See 

Changes:

[rkanter] OOZIE-2181 JsonToBean has some missing and incorrect mappings 
(rkanter)

--
[...truncated 8576 lines...]
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-tools ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-tools ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-tools ---
[INFO] Reading assembly descriptor: ../src/main/assemblies/tools.xml
[WARNING] The following patterns were never triggered in this artifact 
exclusion filter:
o  '*:*:pom:*'

[INFO] Copying files to 

[WARNING] Assembly file: 

 is not a regular file (it may be a directory). It cannot be attached to the 
project build for installation or deployment.
[INFO] 
[INFO] 
[INFO] Building Apache Oozie MiniOozie 4.2.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-mini ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-mini 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-mini ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-mini ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-mini ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-mini ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-mini ---
[INFO] Reading assembly descriptor: src/main/assemblies/empty.xml
[INFO] 
[INFO] 
[INFO] Building Apache Oozie Distro 4.2.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-distro 
---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-distro 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-distro ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-distro ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-distro ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-distro ---
[INFO] 
[INFO] --- maven-antrun-plugin:1.6:run (default) @ oozie-distro ---
[INFO] Executing tasks

main:
  [get] Getting: 
http://archive.apache.org/dist/tomcat/tomcat-6/v6.0.41/bin