Christian Schlichtherle wrote > > (1) Profiles are part of the POM reference specification. >
I think it's important to distinguish between the Maven build file and the (tool independent?) module descriptor. As I see it, the POM reference specification is about the former. I'm looking for a specification for the latter so that we can make Gradle behave exactly like expected when dealing with Maven modules and their dependencies. Does Maven offer a self-contained library that generates a consumption-time view of the POM for the purpose of dependency resolution? Christian Schlichtherle wrote > > (2) Every POM is published somehow - at least to your local repository. > No doubt about that, but does this speak against resolving profiles at publication time? I think there's already some POM transformation going on at publication time. For example, variables might get replaced with their values. I can't find any definitive information on this though. Cheers, Peter -- Peter Niederwieser Principal Engineer, Gradleware http://gradleware.com Creator, Spock Framework http://spockframework.org Twitter: @pniederw -- View this message in context: http://maven.40175.n5.nabble.com/Are-profiles-in-published-POMs-a-supported-feature-tp5469611p5473432.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
