stephenconnolly wrote > 1. Congratulations on successfully posting XML from Nabble. Until now, I > genuinely did not think it was possible (as evidenced by the many many > posts via Nabble where the xml is stripped). I take your success as an > indication that you are a smart guy with some technical savvy
Yeah, nothing special there. Copy/paste/worky. stephenconnolly wrote > 2. Maven is an opinionated build tool. It really loves to build > environment > agnostic artifacts, and it thinks its job is finished when those > environment agnostic artifacts have been "deployed" into a Maven > Repository. ACK stephenconnolly wrote > 3. You are building something SaaS-like, so your application requires > configuration for the environment into which it will be deployed. Maven > does not really have a good story for these stages in the application life > cycle (since they take place after the environment agnostic artifact has > been deployed to a maven repository). I think you misunderstand my intent. My build contains integration tests which must execute successfully against various ORM, database, and jdbc driver combinations. The artifacts that are built are indeed environmentally agnostic. For example, my domain artifact, which contains my persistent JPA entities, has a Spring context file that simply requires an EntityManagerFactory; where that comes from doesn't matter to my entities. As long as its present in the Spring configuration, the domain component is good to go. stephenconnolly wrote > The closest to a good story is to > create a separate module for each destination environment and repackage > the > environment agnostic artifact in those modules... Better is to use DevOps > toolchains to handle this DevOps style task (think chef/puppet) > > Please read my answer to a similar question on stack overflow: > http://stackoverflow.com/questions/14650468/whats-a-practicable-way-for-automated-configuration-versioning-and-deployment/14661186#14661186 Yeah, that may be true in some cases, but not mine. stephenconnolly wrote > The TL;DR is that profiles are not really aimed for use in your use case. > Yes you can use them, but you probably shouldn't and you will fight maven > the whole way. > > Please read the above carefully, if you still are 100% certain that > profiles are the only solution to your problem, then maybe we can take a > look at where things are going wrong... > > But my earnest belief is that you are heading down a path towards hating > maven, and I'd rather try and help you off that path rather than find the > obscure tweak needed to help you further down the path you are on > > -Stephen Maven profiles suit this task just fine, IMHO. I could have created a generic/contrived/artificial foobar-style example to demonstrate the crux of the issue, but I was too lazy. Please don't let my particulars & intent cloud the issue at hand, which is why all executions of a plugin, defined in the pom parent, are being executed when only certain execution ids are being specified in the child pom. I'm not a maven newbie. I'm just using it in a sophisticated way as a responsible adult, aware of the tradeoffs. I appreciate your concern. Now, on to the issue at hand. Can anyone tell me why all executions from the parent pom plugin are being executed in the child pom, even though the child is only referencing some of the parent's executions? Thanks, Matthew -- View this message in context: http://maven.40175.n5.nabble.com/Problem-reusing-specific-plugin-executions-with-profiles-tp5746276p5746373.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]
