Jason van Zyl-5 wrote: > > This is a bad idea and don't count on Maven 3.x supporting this > because it makes determining what the dependencies are black magic. > The dependency tree and visualization tools won't work. In Maven 3.x > we are likely to make the dependency set immutable post resolution > phase. > > I don't feel there is any valid use case for programatically adding > dependencies and if someone finds one then something is wrong with > Maven itself. >
Use case: Eclipse bundles. They can be simple jars or jars containing jars. Any other ideas for getting the classes inside those inner jars visible for the compiler? eclipse.jar contains whatever.jar. whatever.jar contains classes. I want to compile myjar.jar using the classes in whatever.jar. I do not want (for ease of use, this is a request) to manually add the inside dependencies, I just want to add eclipse.jar (like Eclipse itself does during plugin development). I think this is a legitimate use case, *so*, for my use case, could anyone please point out what I'm doing wrong? -- View this message in context: http://www.nabble.com/Programmatically-adding-dependencies-to-a-MavenProject-tp21173440p21680711.html Sent from the Maven Developers mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
