Hi Stephen, Am 28.02.2014 23:59, schrieb Stephen Connolly:
On 28 February 2014 22:48, Jörg Hohwiller <jo...@j-hohwiller.de <mailto:jo...@j-hohwiller.de>> wrote:I do not really get what you mean. Maybe you have great thoughts in mind that I can not follow from your statements. First of all, I was having a discussion about some problems with maintenance of large maven projects where IMHO no real solution is available yet. My idea was to install and deploy a POM that is decoupled from the parent POMs and could also be "minified". Robert Scholte said that this is somewhat what is called a consumer POM and pointed me to the discsussion about model 5.0.0. We exchanged some ideas and I wanted to make progress and started with consumer-maven-plugin.Am 27.02.2014 22:12, schrieb Robert Scholte: Hi Jörg, Hi Robert, I think I found the solution without the Interpolator. I've written several IT's to confirm this. If there's a case which isn't coeverd, let me know. There are cases where your approach does not work. You can also use variables in groupId and artifactId.That is not what the consumer pom is about. Plus you will then play havock with the reactor being unable to resolve coordinates that only exist after the consumer pom is instantiated.The idea of a consumer pom is that it is a stripped down pom with the same coordinates... you can;t have the consumer pom idea pre-model version 5... what you are attempting is just a fancier version of shade...
1. if the name is odd, because the plugin is trying something other than what the majority calls a consumer POM, we could just rename the plugin.
2. I can not see what the plugin has to do with maven-shade-plugin3. If there is any other solution yet available for maven to solve my problem in a solid way without consumer-maven-plugin, please let me know and I will just drop it.
However, I do not want to wait for maven 4 or maven 5 or whatever. I am having a real pain with maven for years that can be perfectly solved with consumer-maven-plugin. There are various JIRA issues about the maintenance of module versions in large maven projects that could as a workaround be solved with consumer-maven-plugin. So far I thought that this is a subset of the idea that will come with later maven versions and we can put our ideas together to get consumer-maven-plugin in the right direction and have it as a reduced and intermediate solution for what is to come in the future. If that is not the case, then it is just a workaround for some guys that may like it and can be ignored by all others.
Best regards Jörg
smime.p7s
Description: S/MIME Cryptographic Signature
