[Hadoop-common-dev] [jira] Created: (HADOOP-3676) Remove Hadoop's dependance on the cli 2 snapshot

[ https://issues.apache.org/jira/browse/HADOOP-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609911#action_12609911 ]

Steve Loughran commented on HADOOP-3676:
----------------------------------------

+1

this complicates downstream applications, and as there is no sign of a cli-2.0 coming out, would be a blocker when hadoop got round to a 1.0 release, as ASF rules say "Dont release with unreleased versions of other bits of apache code"

[ https://issues.apache.org/jira/browse/HADOOP-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609948#action_12609948 ]

Owen O'Malley commented on HADOOP-3676:
---------------------------------------

which means this should really be a blocker, since we *have* been making releases with it. *sigh* Unfortunately, this means I have to re-write the cli handling for both streaming and pipes, so I think putting this into 0.18 would be a very bad idea from a reliability point of view.

[ https://issues.apache.org/jira/browse/HADOOP-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12612499#action_12612499 ]

Steve Loughran commented on HADOOP-3676:
----------------------------------------

well lets target a later version; or push the commons 2 team to roll out a stable 2.0 release.

[ https://issues.apache.org/jira/browse/HADOOP-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643411#action_12643411 ]

Frederick Haebin Na commented on HADOOP-3676:
---------------------------------------------

Add following scripts in the pom.

<repositories>
<repository>
<id>apache snapshot</id>
<url>http://people.apache.org/repo/m2-snapshot-repository</url>
</repository>
</repositories>

...

<dependencies>
...
<!--CLI is needed to scan the command line, but only the 1.0 branch is released -->
<dependency>
<groupId>commons-cli</groupId>
<artifactId>commons-cli</artifactId>
<version>1.1</version>
</dependency>
<dependency>
<groupId>org.apache.commons</groupId>
<artifactId>commons-cli</artifactId>
<version>2.0-SNAPSHOT</version>
</dependency>
...
</dependencies>



Then, you will be able to use the both versions of commons-cli.

[ https://issues.apache.org/jira/browse/HADOOP-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643413#action_12643413 ]

Edward J. Yoon commented on HADOOP-3676:
----------------------------------------

+1, and I also agree with steve loughran.

frederick, thanks for your good tip, but there is no pom.xml file and that matter is of no significance on this issue.

[ https://issues.apache.org/jira/browse/HADOOP-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643411#action_12643411 ]

haebin edited comment on HADOOP-3676 at 10/28/08 10:05 PM:
------------------------------------------------------------------------

Oops,
what I was trying to say was that you could use snapshot release.
You can depend on the both versions since they use different package name. (I tested with my pom file)



-------------------------------------------------------------------------------------------------------------------------------
Add following scripts in the pom.

<repositories>
<repository>
<id>apache snapshot</id>
<url>http://people.apache.org/repo/m2-snapshot-repository</url>
</repository>
</repositories>

...

<dependencies>
...
<!--CLI is needed to scan the command line, but only the 1.0 branch is released -->
<dependency>
<groupId>commons-cli</groupId>
<artifactId>commons-cli</artifactId>
<version>1.1</version>
</dependency>
<dependency>
<groupId>org.apache.commons</groupId>
<artifactId>commons-cli</artifactId>
<version>2.0-SNAPSHOT</version>
</dependency>
...
</dependencies>



Then, you will be able to use the both versions of commons-cli.

was (Author: haebin):
Add following scripts in the pom.

<repositories>
<repository>
<id>apache snapshot</id>
<url>http://people.apache.org/repo/m2-snapshot-repository</url>
</repository>
</repositories>

...

<dependencies>
...
<!--CLI is needed to scan the command line, but only the 1.0 branch is released -->
<dependency>
<groupId>commons-cli</groupId>
<artifactId>commons-cli</artifactId>
<version>1.1</version>
</dependency>
<dependency>
<groupId>org.apache.commons</groupId>
<artifactId>commons-cli</artifactId>
<version>2.0-SNAPSHOT</version>
</dependency>
...
</dependencies>



Then, you will be able to use the both versions of commons-cli.

[ https://issues.apache.org/jira/browse/HADOOP-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643411#action_12643411 ]

haebin edited comment on HADOOP-3676 at 10/28/08 10:17 PM:
------------------------------------------------------------------------

Oops again,
0.20.0 already using it.

why don't you close this issue.
this is not a blocker anymore rite?

------------------------------------------------------------------------------------------------------------------------------
Oops,
what I was trying to say was that you could use snapshot release.
You can depend on the both versions since they use different package name. (I tested with my pom file)



-------------------------------------------------------------------------------------------------------------------------------
Add following scripts in the pom.

<repositories>
<repository>
<id>apache snapshot</id>
<url>http://people.apache.org/repo/m2-snapshot-repository</url>
</repository>
</repositories>

...

<dependencies>
...
<!--CLI is needed to scan the command line, but only the 1.0 branch is released -->
<dependency>
<groupId>commons-cli</groupId>
<artifactId>commons-cli</artifactId>
<version>1.1</version>
</dependency>
<dependency>
<groupId>org.apache.commons</groupId>
<artifactId>commons-cli</artifactId>
<version>2.0-SNAPSHOT</version>
</dependency>
...
</dependencies>



Then, you will be able to use the both versions of commons-cli.

was (Author: haebin):
Oops,
what I was trying to say was that you could use snapshot release.
You can depend on the both versions since they use different package name. (I tested with my pom file)



-------------------------------------------------------------------------------------------------------------------------------
Add following scripts in the pom.

<repositories>
<repository>
<id>apache snapshot</id>
<url>http://people.apache.org/repo/m2-snapshot-repository</url>
</repository>
</repositories>

...

<dependencies>
...
<!--CLI is needed to scan the command line, but only the 1.0 branch is released -->
<dependency>
<groupId>commons-cli</groupId>
<artifactId>commons-cli</artifactId>
<version>1.1</version>
</dependency>
<dependency>
<groupId>org.apache.commons</groupId>
<artifactId>commons-cli</artifactId>
<version>2.0-SNAPSHOT</version>
</dependency>
...
</dependencies>



Then, you will be able to use the both versions of commons-cli.

[ https://issues.apache.org/jira/browse/HADOOP-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643466#action_12643466 ]

Steve Loughran commented on HADOOP-3676:
----------------------------------------

Frederick,
The issue is not that we can't get hold of a CLI snapshot (we have one checked in), but that apache rules say "don't release snapshort artifacts as they haven't been through the full legally backed release process". to put it differently: SNAPSHOTS are nightly builds, not releases, don't depend on them.

That holds for the SNAPSHOT repository, which is an interesting area, and not anything that anyone who wants a replicable build should be including in their dependency graph, as it becomes impossible to build a previous version of your application if that artifact changes.