You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by Ted Yu <yu...@gmail.com> on 2013/11/13 06:09:15 UTC
scope of jersey-test-framework-grizzly2
Hi,
To answer some question on dev@hbase, I noticed the following dependencies:
[INFO] +- org.apache.hadoop:hadoop-mapreduce-client-core:jar:2.2.0:compile
[INFO] | +- org.apache.hadoop:hadoop-yarn-common:jar:2.2.0:compile
[INFO] | | +- com.google.inject:guice:jar:3.0:compile
[INFO] | | | +- javax.inject:javax.inject:jar:1:compile
[INFO] | | | \- aopalliance:aopalliance:jar:1.0:compile
[INFO] | | +- com.sun.jersey.jersey-test-framework:
*jersey-test-framework-grizzly2*:jar:1.9:compile
[INFO] | | | +-
com.sun.jersey.jersey-test-framework:jersey-test-framework-core:jar:1.9:compile
Should jersey-test-framework-grizzly2 have test scope ?
I tried the following change:
Index: hadoop-yarn-project/hadoop-yarn/pom.xml
===================================================================
--- hadoop-yarn-project/hadoop-yarn/pom.xml (revision 1541341)
+++ hadoop-yarn-project/hadoop-yarn/pom.xml (working copy)
@@ -119,6 +119,7 @@
<dependency>
<groupId>com.sun.jersey.jersey-test-framework</groupId>
<artifactId>jersey-test-framework-grizzly2</artifactId>
+ <scope>test</scope>
</dependency>
<dependency>
<groupId>com.sun.jersey</groupId>
The above change led to addition of
jersey-test-framework-grizzly2 in
hadoop-mapreduce-project/hadoop-mapreduce-client/pom.xml
I want to get some opinion on whether jersey-test-framework-grizzly2 should
have test scope.
Thanks
Re: scope of jersey-test-framework-grizzly2
Posted by Ted Yu <yu...@gmail.com>.
I attached a patch to HADOOP-9991 where scope of jersey-test-framework is
changed to test.
Looking at the bottom of the JIRA, there are several more tasks to be done.
Cheers
On Wed, Nov 13, 2013 at 10:30 AM, Steve Loughran <st...@hortonworks.com>wrote:
> looks accidental, file a patch & link it to HADOOP-9991
>
>
> On 13 November 2013 05:09, Ted Yu <yu...@gmail.com> wrote:
>
> > Hi,
> > To answer some question on dev@hbase, I noticed the following
> > dependencies:
> >
> > [INFO] +-
> org.apache.hadoop:hadoop-mapreduce-client-core:jar:2.2.0:compile
> > [INFO] | +- org.apache.hadoop:hadoop-yarn-common:jar:2.2.0:compile
> > [INFO] | | +- com.google.inject:guice:jar:3.0:compile
> > [INFO] | | | +- javax.inject:javax.inject:jar:1:compile
> > [INFO] | | | \- aopalliance:aopalliance:jar:1.0:compile
> > [INFO] | | +- com.sun.jersey.jersey-test-framework:
> > *jersey-test-framework-grizzly2*:jar:1.9:compile
> > [INFO] | | | +-
> >
> >
> com.sun.jersey.jersey-test-framework:jersey-test-framework-core:jar:1.9:compile
> >
> > Should jersey-test-framework-grizzly2 have test scope ?
> >
> > I tried the following change:
> >
> > Index: hadoop-yarn-project/hadoop-yarn/pom.xml
> > ===================================================================
> > --- hadoop-yarn-project/hadoop-yarn/pom.xml (revision 1541341)
> > +++ hadoop-yarn-project/hadoop-yarn/pom.xml (working copy)
> > @@ -119,6 +119,7 @@
> > <dependency>
> > <groupId>com.sun.jersey.jersey-test-framework</groupId>
> > <artifactId>jersey-test-framework-grizzly2</artifactId>
> > + <scope>test</scope>
> > </dependency>
> > <dependency>
> > <groupId>com.sun.jersey</groupId>
> >
> > The above change led to addition of
> > jersey-test-framework-grizzly2 in
> > hadoop-mapreduce-project/hadoop-mapreduce-client/pom.xml
> >
> > I want to get some opinion on whether jersey-test-framework-grizzly2
> should
> > have test scope.
> >
> > Thanks
> >
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>
Re: scope of jersey-test-framework-grizzly2
Posted by Steve Loughran <st...@hortonworks.com>.
looks accidental, file a patch & link it to HADOOP-9991
On 13 November 2013 05:09, Ted Yu <yu...@gmail.com> wrote:
> Hi,
> To answer some question on dev@hbase, I noticed the following
> dependencies:
>
> [INFO] +- org.apache.hadoop:hadoop-mapreduce-client-core:jar:2.2.0:compile
> [INFO] | +- org.apache.hadoop:hadoop-yarn-common:jar:2.2.0:compile
> [INFO] | | +- com.google.inject:guice:jar:3.0:compile
> [INFO] | | | +- javax.inject:javax.inject:jar:1:compile
> [INFO] | | | \- aopalliance:aopalliance:jar:1.0:compile
> [INFO] | | +- com.sun.jersey.jersey-test-framework:
> *jersey-test-framework-grizzly2*:jar:1.9:compile
> [INFO] | | | +-
>
> com.sun.jersey.jersey-test-framework:jersey-test-framework-core:jar:1.9:compile
>
> Should jersey-test-framework-grizzly2 have test scope ?
>
> I tried the following change:
>
> Index: hadoop-yarn-project/hadoop-yarn/pom.xml
> ===================================================================
> --- hadoop-yarn-project/hadoop-yarn/pom.xml (revision 1541341)
> +++ hadoop-yarn-project/hadoop-yarn/pom.xml (working copy)
> @@ -119,6 +119,7 @@
> <dependency>
> <groupId>com.sun.jersey.jersey-test-framework</groupId>
> <artifactId>jersey-test-framework-grizzly2</artifactId>
> + <scope>test</scope>
> </dependency>
> <dependency>
> <groupId>com.sun.jersey</groupId>
>
> The above change led to addition of
> jersey-test-framework-grizzly2 in
> hadoop-mapreduce-project/hadoop-mapreduce-client/pom.xml
>
> I want to get some opinion on whether jersey-test-framework-grizzly2 should
> have test scope.
>
> Thanks
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.