Hi Andrus Thank you, exclude solved the problem. :-)
Those jars are listed as dependencies in the pom, but with the 'provided' scope. Ivy translates the scope into a configuration, so I could probably use that somehow, but I couldn't get that to work. As I understand it, the 'provided' scope usually means that the artifact is provided by the JDK or container at runtime, not that it is provided by this artifact. Also it is used for the compile and test classpaths, not runtime. So it seems wrong that these artifacts are listed as dependencies in the published pom. -Erlend 2012/2/27 Andrus Adamchik <[email protected]> > Hi, > > Odd.. cayenne-server.jar should not have a dependency on > cayenne-jdk1.5-unpublished or cayenne-legal-unpublished. In fact it is an > aggregated jar that *contains* the contents of those 2 jars. I never had > this problem with Maven. Not sure how Ivy calculates the dependency tree, > but if there's a way to add an "exclude", try it out, as these 2 jars are > not needed... > > Another guess... Do you have cgen class generator in your Ivy config? > Could it be that cgen is the culprit here? > > Andrus > > > On Feb 23, 2012, at 11:03 PM, Erlend Birkenes wrote: > > Hi > > > > I'm trying to add Cayenne to a project using Ivy. > > > > I've added these dependencies: > > <dependency org="org.apache.cayenne" name="cayenne-server" > > rev="3.0.2"></dependency> > > <dependency org="org.apache.cayenne" name="cayenne-client" > > rev="3.0.2"></dependency> > > > > But it fails because it can't find > > > > org.apache.cayenne.unpublished#cayenne-jdk1.5-unpublished;3.0.2 and > > org.apache.cayenne.unpublished#cayenne-legal-unpublished;3.0.2 > > > > Do anyone know how I can avoid that? Do I really need those files? > > > > > > Best regards, > > > > Erlend Birkenes > > Dataloy Systems AS > > Phone: +47 98 81 41 57 > >
