There's no maven error, only Java compile errors which would be meaningless without the context of the code (which I can't give).
But I figured it out already! The thing was that ONE of the dependencies had it's "scope" set to "provided" and it seems that either those dependencies don't get inherited by design or maven gets confused somehow and doesn't include them. Either changing the "scope" to "compile" (which isn't an option because now it will be included in the packaging process) or taking that one dependency out and moving it to the project itself fixed the problem. Thanks for the help! -Tako On Tue, Aug 18, 2009 at 12:32, Anders Hammar<[email protected]> wrote: > Including the pom project to which you moved all the dependencies? > > Could you please provide the error output? > > /Anders > > On Tue, Aug 18, 2009 at 12:18, Tako Schotanus <[email protected]> wrote: > >> Yes, did an "mvn clean install" on all related projects just to be sure. >> >> -Tako >> >> >> >> On Tue, Aug 18, 2009 at 11:43, Jeff Johnston<[email protected]> >> wrote: >> > Is your dependencies pom installed in your repository? >> > >> > 2009/8/18 Tako Schotanus <[email protected]> >> > >> >> I tried that, but it doesn't seem to work? I just get long lists of >> >> compile errors saying "can't find symbol". >> >> >> >> Basically what I did was take a (compiling, working) project with a >> >> list of dependencies and copy them all to a new project of type POM >> >> like you suggested as well and then I added a single dependency to the >> >> original project >> >> >> >> <dependency> >> >> <groupId>test.group</groupId> >> >> <artifactId>dependencies</artifactId> >> >> <version>0.0.1-SNAPSHOT</version> >> >> <scope>compile</scope> >> >> <type>pom</type> >> >> </dependency> >> >> >> >> But now the compiler doesn't seem to "see" any of the dependencies- >> >> >> >> -Tako >> >> >> >> >> >> >> >> On Tue, Aug 18, 2009 at 10:46, Jeff Johnston<[email protected]> >> >> wrote: >> >> > For 2, this can be achieved by adding the group of dependencies to a >> >> project >> >> > of type pom and then including this group project as a dependency >> >> whenever >> >> > you need to include the whole group of dependencies. You mark the >> >> > dependency as of type pom and it just pulls in all the transitive >> >> > dependencies. >> >> > >> >> > 2009/8/18 Tako Schotanus <[email protected]> >> >> > >> >> >> Yes, that is an option but one that will only work if ALL subprojects >> >> >> need those dependencies, something that isn't the case in our >> >> >> situation. And we don't want to subdivide our hierarchy even more >> just >> >> >> to to be able to define dependencies. Ah well, that's just the way it >> >> >> is then :) >> >> >> >> >> >> -Tako >> >> >> >> >> >> >> >> >> >> >> >> On Tue, Aug 18, 2009 at 10:26, Anders Hammar<[email protected]> >> wrote: >> >> >> > 2) I believe inclusion like this is planned for Maven 3.0, but for >> M2 >> >> you >> >> >> > have to settle with using a parent where you define common >> >> dependencies. >> >> >> > >> >> >> > /Anders >> >> >> > >> >> >> > On Tue, Aug 18, 2009 at 09:43, Tako Schotanus <[email protected]> >> >> wrote: >> >> >> > >> >> >> >> Hi, >> >> >> >> I've got 2 questions that I haven't been able to find an answer >> to: >> >> >> >> >> >> >> >> 1. For maven projects of type WAR is there a way to still have it >> >> >> include >> >> >> >> the contents of WEB-INF/lib in the class path during >> >> >> compilation/packaging? >> >> >> >> For a project we're doing we have a large list of 3rd party JARs >> that >> >> we >> >> >> >> need to include and I don't want to set up a central repository >> and >> >> add >> >> >> >> them >> >> >> >> there or have every developer add them to their local repository. >> >> >> >> >> >> >> >> 2. If you have several projects which all share a certain largish >> set >> >> of >> >> >> >> dependencies, is it possible to define those dependencies >> somewhere >> >> and >> >> >> >> "include" them? >> >> >> >> >> >> >> >> Cheers, >> >> >> >> -Tako >> >> >> >> >> >> >> > >> >> >> >> >> >> --------------------------------------------------------------------- >> >> >> 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] >> >> >> >> >> > >> >> --------------------------------------------------------------------- >> 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]
