Hi Michael, thanks a lot for your answer. This is how we are currently doing it. In reality our scenario is a bit more complicated than the given database example. We have many artifacts (like A and B), and a whole lot of "connection" parts (like A2B), that would be better placed in their own artifacts, provided that they are used when both artifacts are in the classpath, and we don't want to have the user bother with these connection artifacts. Also because A and B could arrive in the classpath via transiitive dependencies, so the user have no idea (if not doing a dependency:tree) that they are there and the connection part A2B is missing.
As a last resort, do you think a plugin can handle these "dynamic" dependencies? Can a plugin add dependencies to the project, and then have them resolved and used in the rest of the build lifecycle? Maybe binding to one of the early phases? Simone Michael McCallum wrote: > wrap the dependency for the db driver in a pom project that also depends upon > the dialect > > e.g. > > example.company.db.posgresql > -> postgresql jdc driver > -> postgresql database dialect > > then > > example.company.applicationwithdb > -> example.company.db.postgresql > > profiles should not be used to munge up dependencies, it just makes it > confusing for people to have side effects. > > On Mon, 06 Oct 2008 05:47:16 Simone Gianni wrote: > >> Has anybody ever done something >> like this? Has anybody had the same need and investigated a way to solve >> it? >> > > > > -- Simone Gianni CEO Semeru s.r.l. Apache Committer MALE human being programming a computer http://www.simonegianni.it/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
