You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "sean.chen(陈思淼)" <ch...@gmail.com> on 2008/11/17 03:16:00 UTC
Is this cycle dependency ridiculous?
the dom4j:1.5.2 and jaxen:1.1-beta-4, the two guys depend on each other, Is
that a problem?
<dependency>
<groupId>dom4j</groupId>
<artifactId>dom4j</artifactId>
<version>1.5.2</version>
</dependency>
<dependency>
<groupId>jaxen</groupId>
<artifactId>jaxen</artifactId>
<version>1.1-beta-4</version>
</dependency>
the attachment is a picture describe this relationship.
Re: Is this cycle dependency ridiculous?
Posted by Wayne Fay <wa...@gmail.com>.
> why cant I just use <exclude>*</exclude>, so it will exclude all the
> transitive dependency by jaxen?
That is simply not functionality available in Maven as of now. I don't
think it makes sense to add/use if your poms are good, so I'd prefer
that time is spent to fix poms than add this feature.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Is this cycle dependency ridiculous?
Posted by "sean.chen(陈思淼)" <ch...@gmail.com>.
the <exclude> Tag in the <dependency> Tag is are not friendly,for example, i
want to exclude all the dependency import by jaxen, I must look through the
jaxen pom.xml,and find all the dependencies in that pom,and use <excludes>
Tag,
why cant I just use <exclude>*</exclude>, so it will exclude all the
transitive dependency by jaxen?
2008/11/17 Geoffrey Wiseman <ge...@gmail.com>
> 2008/11/17 sean.chen(陈思淼) <ch...@gmail.com>
>
> > So please use <option> Tag to exclude jaxen out the dependency tree, or,
> it
> > will be include in all the project which depend on dom4j.
> >
>
> Totally agreed - only, I don't control that POM, so in the meantime, all
> you
> can do is 'exclude'.
>
> - Geoffrey
> --
> Geoffrey Wiseman
>
Re: Is this cycle dependency ridiculous?
Posted by Geoffrey Wiseman <ge...@gmail.com>.
2008/11/17 sean.chen(陈思淼) <ch...@gmail.com>
> So please use <option> Tag to exclude jaxen out the dependency tree, or, it
> will be include in all the project which depend on dom4j.
>
Totally agreed - only, I don't control that POM, so in the meantime, all you
can do is 'exclude'.
- Geoffrey
--
Geoffrey Wiseman
Re: Is this cycle dependency ridiculous?
Posted by "sean.chen(陈思淼)" <ch...@gmail.com>.
So please use <option> Tag to exclude jaxen out the dependency tree, or, it
will be include in all the project which depend on dom4j.
2008/11/17 Geoffrey Wiseman <ge...@gmail.com>
> On Sun, Nov 16, 2008 at 9:16 PM, sean.chen(陈思淼) <chensimiao@gmail.com
> >wrote:
>
> > the dom4j:1.5.2 and jaxen:1.1-beta-4, the two guys depend on each other,
> Is
> > that a problem?
> > <dependency>
> > <groupId>dom4j</groupId>
> > <artifactId>dom4j</artifactId>
> > <version>1.5.2</version>
> > </dependency>
> >
> > <dependency>
> > <groupId>jaxen</groupId>
> > <artifactId>jaxen</artifactId>
> > <version>1.1-beta-4</version>
> > </dependency>
> >
>
> Jaxen's dependencies are out of whack:
>
> http://furiouspurpose.blogspot.com/2008/10/xom-and-jaxen-transitive-dependencies.html
>
>
> --
> Geoffrey Wiseman
>
Re: Is this cycle dependency ridiculous?
Posted by Geoffrey Wiseman <ge...@gmail.com>.
On Sun, Nov 16, 2008 at 9:16 PM, sean.chen(陈思淼) <ch...@gmail.com>wrote:
> the dom4j:1.5.2 and jaxen:1.1-beta-4, the two guys depend on each other, Is
> that a problem?
> <dependency>
> <groupId>dom4j</groupId>
> <artifactId>dom4j</artifactId>
> <version>1.5.2</version>
> </dependency>
>
> <dependency>
> <groupId>jaxen</groupId>
> <artifactId>jaxen</artifactId>
> <version>1.1-beta-4</version>
> </dependency>
>
Jaxen's dependencies are out of whack:
http://furiouspurpose.blogspot.com/2008/10/xom-and-jaxen-transitive-dependencies.html
--
Geoffrey Wiseman