Hi Martin, Actually I want to use the aggregation pattern as it is used with Maven. Aggregation has modules which are child artifacts and child artifact have parent which is the aggregation pom file.
The mixin will include the plugin and dependency sections that are typically used by the artifact type. E.g. a model artifact would include the model plugins and model dependencies and the test artifact would include the test plugins and test dependencies from the service creation framework. Regards Richard -----Original Message----- From: ext Martin Gainty [mailto:[email protected]] Sent: Wednesday, April 13, 2011 4:00 AM To: [email protected] Subject: RE: Expected implementation date for Maven MIXIN Feature given these pom elements which are inherited from parent to child dependenciesdevelopers and contributorsplugin listsreports listsplugin executions with matching idsplugin configuration where 'aggregation' as defined in maven as any pom which supports multiple modules the 2008 discussion which i think you are allusing to ..defines mixin as an aggregatation of model properties (using an unknown algorithm) http://www.sonatype.com/people/2008/11/maven-project-model/ which features are you envisioning to support your concept of 'aggregation'? gruss Martin ______________________________________________ Jogi és Bizalmassági kinyilatkoztatás/Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Ez az üzenet bizalmas. Ha nem ön az akinek szánva volt, akkor kérjük, hogy jelentse azt nekünk vissza. Semmiféle továbbítása vagy másolatának készítése nem megengedett. Ez az üzenet csak ismeret cserét szolgál és semmiféle jogi alkalmazhatósága sincs. Mivel az electronikus üzenetek könnyen megváltoztathatóak, ezért minket semmi felelöség nem terhelhet ezen üzenet tartalma miatt. Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. > Subject: Expected implementation date for Maven MIXIN Feature > Date: Wed, 13 Apr 2011 01:24:06 +0200 > From: [email protected] > To: [email protected] > > I am using maven as the backend for a service creation environment. > There are types of artifacts that always require the same plugin > configurations or dependencies. Therefore we have defined some base > artifacts which an artifact can inherit as parent. > > Usually we have multi project artifacts where three to six artifacts are > an aggregation. > > Using base aritfacts as parents instead of the aggregation pom has some > severe side effects that make life very difficult. E.g. common > properties of the aggregation cannot be shared with the child artifacts > as the parent is already used for the base artifact. > > The only solution out of this problem I understood when reading the > Internet is the MIXIN feature. You can find in the Internet references > from 2008 until 2011. It was promised for Maven 3.0 but then shifted > from Maven 3.0 to Maven 3.1. > > The important questions are, when will Maven 3.1 be release as there is > not even a date for a planned release? > Do you consider to include the MIXIN feature into Maven 3.0 as an > important update? > > If I am taking the time Maven 3.0 was release and add that to Maven 3.1 > it will be years? It would be really of much help to get some statements > on this from the Maven core team member. > > Best regards > > Richard > > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
