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 release schedule (e.g. a rough date estimate
for version 4). Should I assume that it's done when it's done?
- Is v4 being worked on already or is in the conceptual stage?
- If I want to offer help testing mixin prototypes/betas, how
do I learn when/how to contribute?
Regards
--
Alexander Kriegisch
Anders Hammar schrieb am 01.04.2014 10:53:
> 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,
>> 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 across
>> projects. This is something I (and probably many others) have been waiting
>> for desperately because via inheritance you can only have one aspect
>> covered, but not multiple ones. Comparing to single inheritance in OOP, in
>> order to cleanly encapsulate secondary (even cross-cutting) concerns there
>> are powerful concepts like AOP (I love to use AspectJ for that matter) or
>> simpler ones like mixins. I think mixins would suffice for Maven and
>> massively support DRY (don't repeat yourself), thus making it much easier
>> to keep Maven configurations cleaner and more maintainable.
>>
>> Having said that, I know it is always easier to ask for something than to
>> just implement it by myself (which I am uncapable of because I have never
>> touched or even seen the Maven code base). So, humbly and with all due
>> respect to you as a newbie on this list, I am asking if mixins are still on
>> the development agenda and if the feature has a rather low or high priority.
>>
>> With kind regards
>> --
>> Alexander Kriegisch
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
