error resolving commons-io

[Craig Swing <cs...@gmail.com>]

When I try to resolve with this dependency:

<dependency org="org.apache.directory.server" name="apacheds-core"
rev="1.5.4" />

I get the following error

inconsistent module descriptor file found in '
http://repo1.maven.org/maven2/org/apache/commons/commons-io/1.3.2/commons-io-1.3.2.pom':
bad organisation: expected='org.apache.commons' found='commons-io';

Looking at the org.apache.commons directory, the poms refer to the
organization as commons-io, thus the error.

Is there something I can do to work around this?

One solution to move the directory server files into a local repository and
modify the dependency to use commons-io as the organization.  This seems
more of a hack to me and I'd prefer to avoid doing this.

ivy-settings.xml
<ivysettings>
  <settings defaultResolver="maven.maven2"/>
  <resolvers>
<ibiblio name="maven.maven2" root="http://repo1.maven.org/maven2/"
m2compatible="true" />
  </resolvers>
</ivysettings>



Craig

Re: error resolving commons-io

[Emmanuel Lecharny <el...@apache.org>]

Craig Swing wrote:
> When I try to resolve with this dependency:
>
> <dependency org="org.apache.directory.server" name="apacheds-core"
> rev="1.5.4" />
>
> I get the following error
>
> inconsistent module descriptor file found in '
> http://repo1.maven.org/maven2/org/apache/commons/commons-io/1.3.2/commons-io-1.3.2.pom':
> bad organisation: expected='org.apache.commons' found='commons-io';
>
> Looking at the org.apache.commons directory, the poms refer to the
> organization as commons-io, thus the error.
>
> Is there something I can do to work around this?
>   
The problem is that commons-io is defined in two places in the maven 
repository (probably a mistake).

We have changed the dependency in trunk to point to commons-io instead 
of org.apache.commons-io.

Now, I guess that you are trying to build your application including 
Apacheds, and you use commons-io somewhere else in your dependencies.
> One solution to move the directory server files into a local repository and
> modify the dependency to use commons-io as the organization.  This seems
> more of a hack to me and I'd prefer to avoid doing this.
>   
atm, I'm not sure you have another workaround. It will probably be 
solved in 1.5.5

-- 
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org