You might have a good reason for that, but why are you trying to add a pom in the classpath? Do you need to parse it at runtime?
Cheers. 2009/12/23 TomerL <shaoli...@gmail.com> > > Hi all, > > I have a a project with several modules, all with the same version and > groupId. One of the modules is a pom project contains several other > projects > which are jars projects. I managed to build this module and the repository > contains the required artifacts. > > When I try to add a dependency for this module: > > <dependencies> > <dependency> > <groupId>abc</groupId> > <artifactId>language</artifactId> > <version>1.0</version> > <type>pom</type> > </dependency> > </dependencies> > > The artifact is found but the jars within are not in the classpath and i > get > a compilation error. > > Is there some limitation on using the pom type dependency within the same > project? I have used it with scala so maybe there is some incompatibility > with the scala compiler. > > Thanks, > Tomer > -- > View this message in context: > http://old.nabble.com/%3Ctype%3Epom%3C-type%3E-not-working-tp26902026p26902026.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
