On 02/11/10 03:17, Nan Zhu wrote:
> Hi, all
>
> I'm trapping in a strange problem in this evening,
>
> I have been working on hadoop for several months, including modify the
> source code and re-compile it, I have never met any problem, but when I
> re-compile the hadoop this evening, it shows that the ivy cannot resolve the
> dependencies, the messages are following:
>
> [ivy:resolve] :: problems summary ::
>   [ivy:resolve] :::: WARNINGS
>   [ivy:resolve]         [FAILED     ] javax.jms#jms;1.1!jms.jar:  (0ms)
>   [ivy:resolve]     ==== apache-snapshot: tried
>   [ivy:resolve]
> https://repository.apache.org/content/repositories/snapshots/javax/jms/jms/1.1/jms-1.1.jar
>   [ivy:resolve]     ==== maven2: tried
>   [ivy:resolve]
> http://repo1.maven.org/maven2/javax/jms/jms/1.1/jms-1.1.jar
>   [ivy:resolve]         [FAILED     ]
> com.sun.jdmk#jmxtools;1.2.1!jmxtools.jar:  (0ms)
>   [ivy:resolve]     ==== apache-snapshot: tried
>   [ivy:resolve]
> https://repository.apache.org/content/repositories/snapshots/com/sun/jdmk/jmxtools/1.2.1/jmxtools-1.2.1.jar
>   [ivy:resolve]     ==== maven2: tried
>   [ivy:resolve]
> http://repo1.maven.org/maven2/com/sun/jdmk/jmxtools/1.2.1/jmxtools-1.2.1.jar
>   [ivy:resolve]         [FAILED     ] com.sun.jmx#jmxri;1.2.1!jmxri.jar:
> (0ms)
>   [ivy:resolve]     ==== apache-snapshot: tried
>   [ivy:resolve]
> https://repository.apache.org/content/repositories/snapshots/com/sun/jmx/jmxri/1.2.1/jmxri-1.2.1.jar
>   [ivy:resolve]     ==== maven2: tried
>   [ivy:resolve]
> http://repo1.maven.org/maven2/com/sun/jmx/jmxri/1.2.1/jmxri-1.2.1.jar
>   [ivy:resolve]         ::::::::::::::::::::::::::::::::::::::::::::::
>   [ivy:resolve]         ::              FAILED DOWNLOADS            ::
>   [ivy:resolve]         :: ^ see resolution messages for details  ^ ::
>   [ivy:resolve]         ::::::::::::::::::::::::::::::::::::::::::::::
>   [ivy:resolve]         :: javax.jms#jms;1.1!jms.jar
>   [ivy:resolve]         :: com.sun.jdmk#jmxtools;1.2.1!jmxtools.jar
>   [ivy:resolve]         :: com.sun.jmx#jmxri;1.2.1!jmxri.jar
>   [ivy:resolve]         ::::::::::::::::::::::::::::::::::::::::::::::
>
>
> I don't know why it happens and how to solve it, anyone can give some ideas?
> thank you

I know the problem here, which is that jms and jmx aren't in the main
repository as oracle/sun require click-through licenses. The metadata
files are in the repository, but not the JARS

http://mvnrepository.com/artifact/com.sun.jdmk/jmxtools/1.2.1
http://mvnrepository.com/artifact/jms/jms

What I don't know is why a hadoop build needs it -have you added them?
If not, what library have you recenty added? It may have an accidental
dependency (log4j says it needs jmxtools), which the ivy files need to
exclude explicitly.

-steve

Hi, Steve

I haven't added jms and jmxtools, but I added a jxl library to generate some
statistical result with excel format, but it seems not to be the reason,
because I have worked with it for several days,

I guess it's caused by log4j, I wrote a class and add a logger in it, but
it's same with other original classes in hadoop, I don't know why it will
need these two files, when I explicitly exclude them, the building process
will failed on the problem of "cannot find symbols"

it's strange...

Nan

On Tue, Nov 2, 2010 at 6:26 PM, Steve Loughran <[EMAIL PROTECTED]> wrote:

> On 02/11/10 03:17, Nan Zhu wrote:
>
>> Hi, all
>>
>> I'm trapping in a strange problem in this evening,
>>
>> I have been working on hadoop for several months, including modify the
>> source code and re-compile it, I have never met any problem, but when I
>> re-compile the hadoop this evening, it shows that the ivy cannot resolve
>> the
>> dependencies, the messages are following:
>>
>> [ivy:resolve] :: problems summary ::
>>  [ivy:resolve] :::: WARNINGS
>>  [ivy:resolve]         [FAILED     ] javax.jms#jms;1.1!jms.jar:  (0ms)
>>  [ivy:resolve]     ==== apache-snapshot: tried
>>  [ivy:resolve]
>>
>> https://repository.apache.org/content/repositories/snapshots/javax/jms/jms/1.1/jms-1.1.jar
>>  [ivy:resolve]     ==== maven2: tried
>>  [ivy:resolve]
>> http://repo1.maven.org/maven2/javax/jms/jms/1.1/jms-1.1.jar
>>  [ivy:resolve]         [FAILED     ]
>> com.sun.jdmk#jmxtools;1.2.1!jmxtools.jar:  (0ms)
>>  [ivy:resolve]     ==== apache-snapshot: tried
>>  [ivy:resolve]
>>
>> https://repository.apache.org/content/repositories/snapshots/com/sun/jdmk/jmxtools/1.2.1/jmxtools-1.2.1.jar
>>  [ivy:resolve]     ==== maven2: tried
>>  [ivy:resolve]
>>
>> http://repo1.maven.org/maven2/com/sun/jdmk/jmxtools/1.2.1/jmxtools-1.2.1.jar
>>  [ivy:resolve]         [FAILED     ] com.sun.jmx#jmxri;1.2.1!jmxri.jar:
>> (0ms)
>>  [ivy:resolve]     ==== apache-snapshot: tried
>>  [ivy:resolve]
>>
>> https://repository.apache.org/content/repositories/snapshots/com/sun/jmx/jmxri/1.2.1/jmxri-1.2.1.jar
>>  [ivy:resolve]     ==== maven2: tried
>>  [ivy:resolve]
>> http://repo1.maven.org/maven2/com/sun/jmx/jmxri/1.2.1/jmxri-1.2.1.jar
>>  [ivy:resolve]         ::::::::::::::::::::::::::::::::::::::::::::::
>>  [ivy:resolve]         ::              FAILED DOWNLOADS            ::
>>  [ivy:resolve]         :: ^ see resolution messages for details  ^ ::
>>  [ivy:resolve]         ::::::::::::::::::::::::::::::::::::::::::::::
>>  [ivy:resolve]         :: javax.jms#jms;1.1!jms.jar
>>  [ivy:resolve]         :: com.sun.jdmk#jmxtools;1.2.1!jmxtools.jar
>>  [ivy:resolve]         :: com.sun.jmx#jmxri;1.2.1!jmxri.jar
>>  [ivy:resolve]         ::::::::::::::::::::::::::::::::::::::::::::::
>>
>>
>> I don't know why it happens and how to solve it, anyone can give some
>> ideas?
>> thank you
>>
>
> I know the problem here, which is that jms and jmx aren't in the main
> repository as oracle/sun require click-through licenses. The metadata files
> are in the repository, but not the JARS
>
> http://mvnrepository.com/artifact/com.sun.jdmk/jmxtools/1.2.1
> http://mvnrepository.com/artifact/jms/jms
>
> What I don't know is why a hadoop build needs it -have you added them? If
> not, what library have you recenty added? It may have an accidental
> dependency (log4j says it needs jmxtools), which the ivy files need to
> exclude explicitly.
>
> -steve
>

On 02/11/10 14:47, Nan Zhu wrote:
> Hi, Steve
>
> I haven't added jms and jmxtools, but I added a jxl library to generate some
> statistical result with excel format, but it seems not to be the reason,
> because I have worked with it for several days,
>
> I guess it's caused by log4j, I wrote a class and add a logger in it, but
> it's same with other original classes in hadoop, I don't know why it will
> need these two files, when I explicitly exclude them, the building process
> will failed on the problem of "cannot find symbols"
>

It'll be log4J. Try making the dependency on log4j be on the base
artifact (via a  ->master  dependency declaration), rather than
->default, which gives you everything the people who wrote the JAR felt
you needed, which is often what they needed to compile it, rather than
what you need to use it.

Here is what my ivy.xml file looks like from a different project -all
other modules which use any of the logging libraries depend on this
module, which sets up all the dependencies correct by only asking for
the master artifacts (and having separate configurations for log4j,
commons-logging and slf4j)

     <!--it is essential that only the master JAR of commons logging
     is pulled in, as its dependencies are usually a mess, including things
     like a version of JMX that isn't in the repository
     -->
     <dependency org="log4j"
       name="log4j"
       rev="${log4j.version}"
       conf="log4j->master"
       />
     <!--it is essential that only the master JAR of commons logging
     is pulled in, as its dependencies are usually a mess, including things
     like out of date servlet APIs, bits of Avalon, etc.
     -->
     <dependency org="commons-logging"
       name="commons-logging"
       rev="${commons-logging.version}"
       conf="commons-logging->master"/>

     <dependency org="org.slf4j"
       name="slf4j-api"
       rev="${slf4j.version}"
       conf="slf4j->master"/>

     <dependency org="org.slf4j"
       name="slf4j-jcl"
       rev="${slf4j.version}"
       conf="slf4j->master"/>

I see...

Thank you very much, Steve
Nan

On Wed, Nov 3, 2010 at 1:08 AM, Steve Loughran <[EMAIL PROTECTED]> wrote:

> On 02/11/10 14:47, Nan Zhu wrote:
>
>> Hi, Steve
>>
>> I haven't added jms and jmxtools, but I added a jxl library to generate
>> some
>> statistical result with excel format, but it seems not to be the reason,
>> because I have worked with it for several days,
>>
>> I guess it's caused by log4j, I wrote a class and add a logger in it, but
>> it's same with other original classes in hadoop, I don't know why it will
>> need these two files, when I explicitly exclude them, the building process
>> will failed on the problem of "cannot find symbols"
>>
>>
> It'll be log4J. Try making the dependency on log4j be on the base artifact
> (via a  ->master  dependency declaration), rather than ->default, which
> gives you everything the people who wrote the JAR felt you needed, which is
> often what they needed to compile it, rather than what you need to use it.
>
> Here is what my ivy.xml file looks like from a different project -all other
> modules which use any of the logging libraries depend on this module, which
> sets up all the dependencies correct by only asking for the master artifacts
> (and having separate configurations for log4j, commons-logging and slf4j)
>
>    <!--it is essential that only the master JAR of commons logging
>    is pulled in, as its dependencies are usually a mess, including things
>    like a version of JMX that isn't in the repository
>    -->
>    <dependency org="log4j"
>      name="log4j"
>      rev="${log4j.version}"
>      conf="log4j->master"
>      />
>    <!--it is essential that only the master JAR of commons logging
>    is pulled in, as its dependencies are usually a mess, including things
>    like out of date servlet APIs, bits of Avalon, etc.
>    -->
>    <dependency org="commons-logging"
>      name="commons-logging"
>      rev="${commons-logging.version}"
>      conf="commons-logging->master"/>
>
>    <dependency org="org.slf4j"
>      name="slf4j-api"
>      rev="${slf4j.version}"
>      conf="slf4j->master"/>
>
>    <dependency org="org.slf4j"
>      name="slf4j-jcl"
>      rev="${slf4j.version}"
>      conf="slf4j->master"/>
>