[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [m2e-users] Dependencies with classifiers not working
|
Benson, I was surprised too, but I learnt a few weeks ago you can actually add dependencies to a pom artifact, then make your project depend on that pom and you'll get its dependencies transitively. Always thought pom dependencies were supposed to be dealt with a scope=import in the dependencyManagement section.
Now I dunno if depending on a pom can be considered a best practice or not.
Regards
Fred Bricon
2011/10/11 Benson Margulies
<bimargulies@xxxxxxxxx>
Eric,
Why type=pom? How would that ever result in a dependency in Eclipse?
On Tue, Oct 11, 2011 at 9:17 AM, Eric Kolotyluk
<
eric.kolotyluk@xxxxxxxxx> wrote:
> I recently added some dependencies with classifiers, for example,
>
> <dependency>
> <groupId>info.collide</groupId>
> <artifactId>sqlspaces-commons</artifactId>
> <version>3.10.0</version>
> <type>pom</type>
> <classifier>jdk15</classifier>
> </dependency>
>
> But my Eclipse build is broken now because this does not show up properly in
> "Maven Dependencies"
>
> If I build from the command line things are OK, but I cannot seem to
> configure Eclipse to work with classifiers.
>
> Does anyone have any suggestions?
>
> Cheers, Eric
> _______________________________________________
> m2e-users mailing list
>
m2e-users@xxxxxxxxxxx
>
https://dev.eclipse.org/mailman/listinfo/m2e-users
>
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
--
"Have you tried turning it off and on again" - The IT Crowd