Thanks for the speedy reply Igor. It builds fine on the command line under mvn 3.0.3. It appears that it is in fact using pax:compile as the compiler, which would explain the behaviour given your comment. Nice pick. Is there anything that can be done from outside m2e (plugins, or changes to maven-pax-compiler), to help this?
Lindsay Date: Mon, 25 Jul 2011 08:04:26 +0400 From: Igor Fedorenko <[email protected]> To: [email protected] Subject: Re: [m2e-users] Packaging type 'bundle' prevents 'Maven Dependencies' from being created Message-ID: <[email protected]> Content-Type: text/plain; charset=windows-1252; format=flowed Does the project build successfully on command line using maven 3.0.2? What compiler does the project use (pax:compile, for example, is NOT supported by m2e at the moment). Generally, m2e is expected to resolve project dependencies and setup Maven Dependencies classpath container for all projects that use maven-compiler-plugin with compilerId=javac. -- Regards, Igor On 11-07-25 7:31 AM, Lindsay Smith wrote: > Hi there, > > I?m experimenting with a clean eclipse 3.7 installation, and I?ve > installed m2e from the eclipse update site. On the whole it looks > slick, very nice. > > However I have an issue ? my projects have packaging type ?bundle?. It > should be treated like a Java project, but when the project is set up > I don?t the ?Maven Dependencies?. I?ve seen some comments around this > area, such as this bug: > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=337010 > > However this problem is still happening for these ?bundle? projects. > They have, naturally, plugins configured in the pom that handle this > packaging type. > > If I switch the packaging type to ?jar? and update the project > configuration, I get the correct dependency group. I can then switch > it back and it stays around, so that?s my workaround at this stage. > > Thanks > > Lindsay _______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
