No, you need to remove poms under commons-attributes in your local
repo. They had wrong dependencies

On 11/1/05, Chris Wilkes <[EMAIL PROTECTED]> wrote:
> Edson Yanaga <yanaga <at> insula.com.br> writes:
> > I'm trying to migrate my projects from Maven 1.1b2 to 2, but when I
> > insert the following dependency:
> >
> >                 <dependency>
> >                         <groupId>springframework</groupId>
> >                         <artifactId>spring-mock</artifactId>
> >                         <version>1.2.5</version>
> >                         <scope>test</scope>
> >                 </dependency>
> >
> > My build fails. It requests javadoc-1.4.jar, but it does not exist. How
> > can I get this file, or is it a problema with the springframework
> > pom.xml?
>
> I have the exact same problem with my spring project, at first I thought it 
> was
> due to being on Windows and having a space in my CLASSPATH but I also tried 
> this
> out on a linux machine and the same error came up
>
> > Downloading:
> > http://repo1.maven.org/maven2/javadoc/javadoc/1.4/javadoc-1.4.jar
> > [WARNING] Unable to get resource from repository central
> > (http://repo1.maven.org/maven2)
>
> Looking on that site there's a javadoc for 1.3 but not for 1.4.  I take it 
> maven
> should look under $JAVA_HOME and find the javadoc executable, correct?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to