Let me double check first. If we can keep the parent.
-------- Original message -------- From: Zack Shoylev <[email protected]> Date: 07/18/2013 2:48 PM (GMT-06:00) To: jclouds/jclouds-cli <[email protected]> Subject: Re: [jclouds-cli] Fix jclouds-cli inheritance and dependencies (mvn) (#10) I think so. Is that not the right way to do it? Keeping the original parent had some issues I think -------- Original message -------- From: Andrew Phillips <[email protected]> Date: 07/18/2013 2:23 PM (GMT-06:00) To: jclouds/jclouds-cli <[email protected]> Cc: Zack Shoylev <[email protected]> Subject: Re: [jclouds-cli] Fix jclouds-cli inheritance and dependencies (mvn) (#10) Actually, erm, looking at the JIRA issue: which one of these is supposed to be the new "parent" POM? This change basically makes all CLI POM's inherit straight from the jclouds-project POM. Was that the intention after discussion on the JIRA issue? — Reply to this email directly or view it on GitHub<https://github.com/jclouds/jclouds-cli/pull/10#issuecomment-21207287>. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-cli/pull/10#issuecomment-21209332
