Le mardi 1 avril 2014 13:25:49 Jason van Zyl a écrit : > No problem, I will write up a little description of the approach in the > README.md file. > > As a user you are familiar with the pom.xml and internally what we use to > parse that is called the ModelBuilder. It handles inheritance, profile > application, property interpolation, dependency management and those sorts > of things. What it gives to you at the end is the fully fleshed out model > or what we call a MavenProject. see http://maven.apache.org/ref/3-LATEST/maven-model-builder/ for some more detailed info with pointers to related code
> A lifecycle participant has the ability to > inspect and potentially mutate MavenProject instances before a build is > executed. A number of systems utilize this to change dependency information > before the build is executed like Tycho. But at this point I surmise it may > be too late. > > Really as a user you probably have a better perspective how the system > should work. The hard part is defining how a mixin would be defined, what > the rules would be for applying the mixin and validating them. At the very > least you should be able to prototype with the hacked up lifecycle > participant and you can see if it's too limiting. I'll try to clean up the > repo tonight and push it to Github so you can take a look. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
