Re: Mixins as an aspect-oriented DRY tool

2014-04-01 Thread Hervé BOUTEMY
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

Re: maven-enforcer rule Problem - http://jira.codehaus.org/browse/MENFORCER-189

2014-04-01 Thread Robert Scholte
Hi Karl-Heinz, Let's make a clear separation between the plugin, the enforcer-api and the standard rules. Only the first one can be restricted to a specific Maven version by specifying the prerequisite for Maven. Although the standard rules are included by default, there's no real relations

Re: Mixins as an aspect-oriented DRY tool

2014-04-01 Thread Jason van Zyl
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

Re: Mixins as an aspect-oriented DRY tool

2014-04-01 Thread Alexander Kriegisch
Jason, I guess I am going to accept your generous offer even though as a fairly average Maven user I have not understood half of what you explained about the limitations and implications of your current prototype and a projected final solution. Feel free to send me private messages whenever yo

Re: Mixins as an aspect-oriented DRY tool

2014-04-01 Thread Jason van Zyl
Alexander, I have a repository with a prototype if you want to take a look. I just need to remove some crap and you're welcome to run with it if you want to do something with it. The method employed works by mutating the model once it has been read with a lifecycle participant. You can get pret

Re: maven-project artifact version

2014-04-01 Thread Tamás Cservenák
Howdy, module "maven-project" was removed as part of Maven3 changes/refactoring (but as you noted, was still present in some early alphas). Just compare the two diagrams, and you will see that "project" module is gone: http://maven.apache.org/ref/2.2.1/ http://maven.apache.org/ref/3.2.1/ It's mo

maven-project artifact version

2014-04-01 Thread Karl Heinz Marbaise
Hi, i have just a small question concerning the above artifact. I can find artifacts of maven things like maven-core etc. with an appropriate version like maven-core:3.1.1, 3.0.5 or 3.2.1 but i can't find an artifact of maven-project with version like 3.1.1, 3.0.5 etc. but only maven-project

Re: maven-enforcer rule Problem - http://jira.codehaus.org/browse/MENFORCER-189

2014-04-01 Thread Karl Heinz Marbaise
Hi Robert, first of all thanks for your answer > For Maven2 all arguments are immediately processed, you can't trace back the values of -pl or -amd. I think you should go for the easy and solid solution by requiring specific Maven versions. For instance: In the rule, read the version value

Re: Mixins as an aspect-oriented DRY tool

2014-04-01 Thread Anders Hammar
It's discussion right now and I don't think there has been any actaul work (other than possibly some private PoC). And it will be done when it's done. :-) /Anders On Tue, Apr 1, 2014 at 11:51 AM, Alexander Kriegisch < alexan...@kriegisch.name> wrote: > Thanks Anders, > > so part of my question

Re: Mixins as an aspect-oriented DRY tool

2014-04-01 Thread Alexander Kriegisch
Yes, I found that via Google (maybe someone can fix the wiki anyway), but there is a technical issue (sorry to bother this list with it): I just wanted to comment on the corresponding ticket https://jira.codehaus.org/browse/MNG-5102, but I do not have a user account for the wiki yet. Direct sig

Re: Mixins as an aspect-oriented DRY tool

2014-04-01 Thread Tamás Cservenák
Re MNG issue links... they are in codehaus Jira. Just prepend the " http://jira.codehaus.org/browse"; to them. Like http://jira.codehaus.org/browse/MNG-5102 On Tue, Apr 1, 2014 at 11:51 AM, Alexander Kriegisch < alexan...@kriegisch.name> wrote: > Thanks Anders, > > so part of my question is ans

Re: Mixins as an aspect-oriented DRY tool

2014-04-01 Thread Alexander Kriegisch
Thanks Anders, so part of my question is answered: prio is major (like most other tickets on that target version) and there is a ticket for it. I have a few remaining issues though: - All links to related tickets are broken, they just point back to the wiki page itself. - There is no rel

Re: Mixins as an aspect-oriented DRY tool

2014-04-01 Thread Anders Hammar
Here's the wiki page covering Maven 4: https://cwiki.apache.org/confluence/display/MAVEN/Maven+4.0.0 /Anders On Tue, Apr 1, 2014 at 10:42 AM, Alexander Kriegisch < alexan...@kriegisch.name> wrote: > Dear developers, > > I guess at least since 2008 Jason had the idea to implement Maven mixins, >

Mixins as an aspect-oriented DRY tool

2014-04-01 Thread Alexander Kriegisch
Dear developers, I guess at least since 2008 Jason had the idea to implement Maven mixins, i.e. a kind of include mechanism in order for users to be able to encapsulate sets of dependencies (not just their version numbers as with import-scoped BoMs) and re-use them throughout modules or even ac