Review Board 1.7.22


OOZIE-831 POMs cleanup/fixing of hadoop version and to be able to publish oozie JARs to maven repo

Review Request #5082 - Created May 9, 2012 and submitted

Alejandro Abdelnur
trunk
OOZIE-831
Reviewers
oozie
kamrul, virag
oozie
Adding Apache Maven repo URLs to distribution management, both for snapshots and releases

Keeping 2 hadoop versions hadooplibs, hadoop-1 (using hadoop 1.0.1) and hadoop-2 (using hadoop 2.0.0-SNAPSHOT)

Changing the version scheme of hadooplibs to be tied to Oozie release (and to be snapshots/releases based on Oozie version)
clean build and run some test for sanity check.

deployed to an local repo and verified all artifacts make it there.
Posted (May 9, 2012, 10:53 p.m.)

   

  
trunk/pom.xml (Diff revision 1)
 
 
why is this removed?
  1. this is not used and creates a funny dir everytime.
    
    
    PS: if you are using internally, I'd suggest to keep it in your internal repo (i'm doing that for some build tweaks I need)
  2. also note that distribution management is now pointing Apache Maven repo, so if you need an internal repo, you'll have to tweak the poms
Posted (May 10, 2012, 7:25 p.m.)
for trunk. it looks perfect.
For 3.2, can we only change the minimum?
trunk/pom.xml (Diff revision 1)
 
 
We tested with 0.23.1. The code is deployed into sandbox, do we need to change it for 3.2? or we can do this for trunk.
Ship it!
Posted (May 10, 2012, 11:38 p.m.)
+1