You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "Bock, Richard (NSN - DE/Munich)" <ri...@nsn.com> on 2011/04/13 01:24:06 UTC

Expected implementation date for Maven MIXIN Feature

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








RE: Expected implementation date for Maven MIXIN Feature

Posted by "Bock, Richard (NSN - DE/Munich)" <ri...@nsn.com>.
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:mgainty@hotmail.com] 
Sent: Wednesday, April 13, 2011 4:00 AM
To: users@maven.apache.org
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: richard.bock@nsn.com
> To: users@maven.apache.org
> 
> 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


RE: Expected implementation date for Maven MIXIN Feature

Posted by Martin Gainty <mg...@hotmail.com>.
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: richard.bock@nsn.com
> To: users@maven.apache.org
> 
> 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
> 
> 
> 
> 
> 
> 
> 
 		 	   		  

Re: Expected implementation date for Maven MIXIN Feature

Posted by Stephen Connolly <st...@gmail.com>.
If the plugins are orthogonal to the module types then just bung it
all in the root pluginManagement and be done with it.

I am assuming that you have a non-orthogonal case though. In the
non-orthogonal case you could stop having inheritance follow
aggregation. it would mean some duplication in the child poms (need to
specify /project/version, /project/url, /project/scm,
/project/distributionManagement/site) and you'd probably want to add
to /project/dependencyManagement/dependencies

<dependency>
  <groupId>aggregation-parent-groupId</groupId>
  <artifactId>aggregation-parent-artifactId</artifactId>
  <version>${project.version}</version> <!-- you have specified it
explicitly so using this will help break the build if things get out
of sync -->
  <type>pom</type>
  <scope>import</scope>
</dependency>

So that the aggregation can enforce dependency management on all its
child modules.

That's about the closest you can get to the MIXIN proposal today.

-Stephen

On 14 April 2011 10:50, Bock, Richard (NSN - DE/Munich)
<ri...@nsn.com> wrote:
> Hi Anders,
>
> Thanks for your clarifications. I try get the wordings right. But what
> are you actually suggesting? I mean stay away from profiles. Yeah. But
> what to use instead? Modules will not work as I am actually already
> using them. I need modules that have an aggregation parent and still get
> some model type specific configuration (plugins e.g. that are always
> same for a certain module type).
>
> Currently using profiles and <activation><file><exists> is only a
> workaround. I am still curious to get a reply from some Maven
> contributor on whether this problem can be solved with MIXIN and when
> MIXIN will be available.
>
> Using profiles in this manner has the advantage that all module pom
> files are using the traditional aggregation parent but do not contain
> any redundant plugin configurations that are related to the module type
> (e.g. modeling project, java implementation project, web service project
> and so on)
>
> /Richard
>
>
> -----Original Message-----
> From: anders.g.hammar@gmail.com [mailto:anders.g.hammar@gmail.com] On
> Behalf Of ext Anders Hammar
> Sent: Thursday, April 14, 2011 11:09 AM
> To: Maven Users List
> Subject: Re: Expected implementation date for Maven MIXIN Feature
>
> Please, don't call it a super-pom. There is only one (and will only be
> just
> one) super-POM and it lives in Maven core. What you are talking about is
> a
> parent-pom and should be called that.
>
> Also, you're talking about archetypes which is something completely
> different from "artifacts" which I believe you're referring to. Please
> pay
> attention to the wording as it makes it easier for other people to
> understand what you're explaining.
>
> As you've noticed, the actual profile isn't inherited but rather the
> effect
> of the profile. One of those tricky things with profiles but that's by
> design. The simplest thing is to try staying away from profiles all
> together
> as they very often trick you into doing something which isn't the Maven
> Way..
>
> /Anders
>
> On Wed, Apr 13, 2011 at 20:32, Bock, Richard (NSN - DE/Munich) <
> richard.bock@nsn.com> wrote:
>
>> Today I found a workaround which is somehow not optional but keeps me
>> alive.
>>
>> All the base artifact types of a certain platform type will be put
> into a
>> super-pom for that platform type. E.g. jee-super-pom. Each artifact
> base
>> type plugin and properties is encapsulated into a Profile. The profile
> is
>> activated by a file that exists in the child project.
>>
>> Now the aggregator project myapp-pom can inherit from the
> jee-super.pom.
>>
>> Each module module-pom will have a file e.g. javalib-architype,
>> groovylib-architype, basemodel-architype, testimpl-architype. This
> will
>> activate the base architype profiles.
>>
>> Drawback is that this leaves the module-pom projects with funny empty
>> marker files in the project folder and the files cannot be looked up
> in the
>> repository as they are no architypes.
>>
>> What I find rather annoying is that even the activiation condition
> based on
>> properties will not work as the parent profiles will only be triggered
> by
>> parent properties and not by properties defined in the module-pom.
>>
>> So I just hope someday or earlier then later someone will add a
> feature to
>> Maven to resolved the parent properties, then the child properties and
> then
>> start resolving the profiles only.
>>
>> Or let us keep the hope up some one delivers the MIXIN feature.
>>
>> /Richard
>>
>>
>> -----Original Message-----
>> From: ext Wayne Fay [mailto:waynefay@gmail.com]
>> Sent: Wednesday, April 13, 2011 8:19 PM
>> To: Maven Users List
>> Subject: Re: Expected implementation date for Maven MIXIN Feature
>>
>> > AM gets the version from A through the parent relationship.
>> > AM gets the plugin sce.model from the MIXIN relationship to M.
>> >
>> > AI gets the version from A through the parent relationship.
>> > AI gets the plugin sce.compile from the MIXIN relationship to I.
>>
>> Sounds roughly like composition of objects/projects in the POM, is
>> that about right? I haven't really been following any discussion of
>> Mixins previously.
>>
>> Wayne
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Expected implementation date for Maven MIXIN Feature

Posted by Anders Hammar <an...@hammar.net>.
No, it will not.

As you've already seen, adding dependencies through a profile is a very bad
thing to do. You must understand that using Maven isn't just about making
your build work but also making sure that dependency management for those
using (consuming) your artifact works. When you add dependencies in a
profile this most often gets screwed up.

/Anders

On Fri, Apr 15, 2011 at 00:29, Bock, Richard (NSN - DE/Munich) <
richard.bock@nsn.com> wrote:

> Hi Stephen and Martin
>
> Thanks for your constructive contribution :-)
>
> As we implement a framework it is important to leave the user pom files as
> clean as possible to avoid tedious upgrades when we change the
> implementation.
>
> Currently I inject the following stuff using profiles with file exists
> condition:
>
> 1.) dependencies (type compile and provided)
> ...
>                <dependency>
>                        <groupId>javax.servlet</groupId>
>                        <artifactId>servlet-api</artifactId>
>                        <version>2.3</version>
>                        <scope>provided</scope>
>                </dependency>
>                <dependency>
>
>  <groupId>com.nsn.see.sce.container.sipservlet</groupId>
>                        <artifactId>container-sipservlet-api</artifactId>
>                        <version>${sceVersion}</version>
>                        <scope>compile</scope>
>                </dependency>
> ...
>
> 2.) plugin configuration e.g.
>
> <build>
>                <plugins>
>                        <plugin>
>                                <groupId>org.apache.maven.plugins</groupId>
>                                <artifactId>maven-war-plugin</artifactId>
>                                <version>2.1.1</version>
>                                <configuration>
>
>  <webXml>${project.basedir}/WebContent/WEB-INF/web.xml</webXml>
>                                        <webResources>
>                                                <resource>
>
>  <directory>${project.basedir}/WebContent/WEB-INF</directory>
>
>  <targetPath>WEB-INF</targetPath>
>                                                        <includes>
>
>  <include>weblogic.xml</include>
>
>  <include>sip.xml</include>
>                                                        </includes>
>
>  <filtering>false</filtering>
>                                                </resource>
>                                        </webResources>
>                                </configuration>
>                        </plugin>
>                </plugins>
>        </build>
>
> 3.) plugin management configurations
>
> 4.) properties
>
> The only negative sideeffect the profile workaround currently has is that
> the dependencies cannot be used transitively as the file marker is not in
> repository. I just wonder if I could replace the dependencies with the
> import feature. Will import also add the provided dependencies?
>
> /Richard
>
>
>
> -----Original Message-----
> From: ext Stephen Connolly [mailto:stephen.alan.connolly@gmail.com]
> Sent: Thursday, April 14, 2011 2:23 PM
> To: Maven Users List
> Cc: Martin Gainty
> Subject: Re: Expected implementation date for Maven MIXIN Feature
>
> http://www.mail-archive.com/dev@maven.apache.org/msg85145.html
>
> On 14 April 2011 13:16, Martin Gainty <mg...@hotmail.com> wrote:
> >
> > you may want to consider aggregating your plugins into a
> dependency-management block
> > then further down have your poms pull in that dependency-management block
> of plugins with <scope>import</scope>
> > in the calling poms dependency-management dependency
> >
> >
> http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
> >
> > if this doesnt suit your need we could provide a better solution if
> > you could provide specifics on what you are attempting to accomplish
> >
> > gruss
> > Martin
> > ______________________________________________
> > Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
> >
> > 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: RE: Expected implementation date for Maven MIXIN Feature
> >> Date: Thu, 14 Apr 2011 11:50:06 +0200
> >> From: richard.bock@nsn.com
> >> To: users@maven.apache.org
> >>
> >> Hi Anders,
> >>
> >> Thanks for your clarifications. I try get the wordings right. But what
> >> are you actually suggesting? I mean stay away from profiles. Yeah. But
> >> what to use instead? Modules will not work as I am actually already
> >> using them. I need modules that have an aggregation parent and still get
> >> some model type specific configuration (plugins e.g. that are always
> >> same for a certain module type).
> >>
> >> Currently using profiles and <activation><file><exists> is only a
> >> workaround. I am still curious to get a reply from some Maven
> >> contributor on whether this problem can be solved with MIXIN and when
> >> MIXIN will be available.
> >>
> >> Using profiles in this manner has the advantage that all module pom
> >> files are using the traditional aggregation parent but do not contain
> >> any redundant plugin configurations that are related to the module type
> >> (e.g. modeling project, java implementation project, web service project
> >> and so on)
> >>
> >> /Richard
> >>
> >>
> >> -----Original Message-----
> >> From: anders.g.hammar@gmail.com [mailto:anders.g.hammar@gmail.com] On
> >> Behalf Of ext Anders Hammar
> >> Sent: Thursday, April 14, 2011 11:09 AM
> >> To: Maven Users List
> >> Subject: Re: Expected implementation date for Maven MIXIN Feature
> >>
> >> Please, don't call it a super-pom. There is only one (and will only be
> >> just
> >> one) super-POM and it lives in Maven core. What you are talking about is
> >> a
> >> parent-pom and should be called that.
> >>
> >> Also, you're talking about archetypes which is something completely
> >> different from "artifacts" which I believe you're referring to. Please
> >> pay
> >> attention to the wording as it makes it easier for other people to
> >> understand what you're explaining.
> >>
> >> As you've noticed, the actual profile isn't inherited but rather the
> >> effect
> >> of the profile. One of those tricky things with profiles but that's by
> >> design. The simplest thing is to try staying away from profiles all
> >> together
> >> as they very often trick you into doing something which isn't the Maven
> >> Way..
> >>
> >> /Anders
> >>
> >> On Wed, Apr 13, 2011 at 20:32, Bock, Richard (NSN - DE/Munich) <
> >> richard.bock@nsn.com> wrote:
> >>
> >> > Today I found a workaround which is somehow not optional but keeps me
> >> > alive.
> >> >
> >> > All the base artifact types of a certain platform type will be put
> >> into a
> >> > super-pom for that platform type. E.g. jee-super-pom. Each artifact
> >> base
> >> > type plugin and properties is encapsulated into a Profile. The profile
> >> is
> >> > activated by a file that exists in the child project.
> >> >
> >> > Now the aggregator project myapp-pom can inherit from the
> >> jee-super.pom.
> >> >
> >> > Each module module-pom will have a file e.g. javalib-architype,
> >> > groovylib-architype, basemodel-architype, testimpl-architype. This
> >> will
> >> > activate the base architype profiles.
> >> >
> >> > Drawback is that this leaves the module-pom projects with funny empty
> >> > marker files in the project folder and the files cannot be looked up
> >> in the
> >> > repository as they are no architypes.
> >> >
> >> > What I find rather annoying is that even the activiation condition
> >> based on
> >> > properties will not work as the parent profiles will only be triggered
> >> by
> >> > parent properties and not by properties defined in the module-pom.
> >> >
> >> > So I just hope someday or earlier then later someone will add a
> >> feature to
> >> > Maven to resolved the parent properties, then the child properties and
> >> then
> >> > start resolving the profiles only.
> >> >
> >> > Or let us keep the hope up some one delivers the MIXIN feature.
> >> >
> >> > /Richard
> >> >
> >> >
> >> > -----Original Message-----
> >> > From: ext Wayne Fay [mailto:waynefay@gmail.com]
> >> > Sent: Wednesday, April 13, 2011 8:19 PM
> >> > To: Maven Users List
> >> > Subject: Re: Expected implementation date for Maven MIXIN Feature
> >> >
> >> > > AM gets the version from A through the parent relationship.
> >> > > AM gets the plugin sce.model from the MIXIN relationship to M.
> >> > >
> >> > > AI gets the version from A through the parent relationship.
> >> > > AI gets the plugin sce.compile from the MIXIN relationship to I.
> >> >
> >> > Sounds roughly like composition of objects/projects in the POM, is
> >> > that about right? I haven't really been following any discussion of
> >> > Mixins previously.
> >> >
> >> > Wayne
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> > For additional commands, e-mail: users-help@maven.apache.org
> >> >
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

RE: Expected implementation date for Maven MIXIN Feature

Posted by "Bock, Richard (NSN - DE/Munich)" <ri...@nsn.com>.
Hi Stephen and Martin

Thanks for your constructive contribution :-)

As we implement a framework it is important to leave the user pom files as clean as possible to avoid tedious upgrades when we change the implementation.

Currently I inject the following stuff using profiles with file exists condition:

1.) dependencies (type compile and provided)
...
		<dependency>
			<groupId>javax.servlet</groupId>
			<artifactId>servlet-api</artifactId>
			<version>2.3</version>
			<scope>provided</scope>
		</dependency>
		<dependency>
			<groupId>com.nsn.see.sce.container.sipservlet</groupId>
			<artifactId>container-sipservlet-api</artifactId>
			<version>${sceVersion}</version>
			<scope>compile</scope>
		</dependency>
...

2.) plugin configuration e.g.

<build>
		<plugins>
			<plugin>
				<groupId>org.apache.maven.plugins</groupId>
				<artifactId>maven-war-plugin</artifactId>
				<version>2.1.1</version>
				<configuration>
					<webXml>${project.basedir}/WebContent/WEB-INF/web.xml</webXml>
					<webResources>
						<resource>
							<directory>${project.basedir}/WebContent/WEB-INF</directory>
							<targetPath>WEB-INF</targetPath>
							<includes>
								<include>weblogic.xml</include>
								<include>sip.xml</include>
							</includes>
							<filtering>false</filtering>
						</resource>
					</webResources>
				</configuration>
			</plugin>
		</plugins>
	</build>		

3.) plugin management configurations

4.) properties

The only negative sideeffect the profile workaround currently has is that the dependencies cannot be used transitively as the file marker is not in repository. I just wonder if I could replace the dependencies with the import feature. Will import also add the provided dependencies?

/Richard



-----Original Message-----
From: ext Stephen Connolly [mailto:stephen.alan.connolly@gmail.com] 
Sent: Thursday, April 14, 2011 2:23 PM
To: Maven Users List
Cc: Martin Gainty
Subject: Re: Expected implementation date for Maven MIXIN Feature

http://www.mail-archive.com/dev@maven.apache.org/msg85145.html

On 14 April 2011 13:16, Martin Gainty <mg...@hotmail.com> wrote:
>
> you may want to consider aggregating your plugins into a dependency-management block
> then further down have your poms pull in that dependency-management block of plugins with <scope>import</scope>
> in the calling poms dependency-management dependency
>
> http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
>
> if this doesnt suit your need we could provide a better solution if
> you could provide specifics on what you are attempting to accomplish
>
> gruss
> Martin
> ______________________________________________
> Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
>
> 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: RE: Expected implementation date for Maven MIXIN Feature
>> Date: Thu, 14 Apr 2011 11:50:06 +0200
>> From: richard.bock@nsn.com
>> To: users@maven.apache.org
>>
>> Hi Anders,
>>
>> Thanks for your clarifications. I try get the wordings right. But what
>> are you actually suggesting? I mean stay away from profiles. Yeah. But
>> what to use instead? Modules will not work as I am actually already
>> using them. I need modules that have an aggregation parent and still get
>> some model type specific configuration (plugins e.g. that are always
>> same for a certain module type).
>>
>> Currently using profiles and <activation><file><exists> is only a
>> workaround. I am still curious to get a reply from some Maven
>> contributor on whether this problem can be solved with MIXIN and when
>> MIXIN will be available.
>>
>> Using profiles in this manner has the advantage that all module pom
>> files are using the traditional aggregation parent but do not contain
>> any redundant plugin configurations that are related to the module type
>> (e.g. modeling project, java implementation project, web service project
>> and so on)
>>
>> /Richard
>>
>>
>> -----Original Message-----
>> From: anders.g.hammar@gmail.com [mailto:anders.g.hammar@gmail.com] On
>> Behalf Of ext Anders Hammar
>> Sent: Thursday, April 14, 2011 11:09 AM
>> To: Maven Users List
>> Subject: Re: Expected implementation date for Maven MIXIN Feature
>>
>> Please, don't call it a super-pom. There is only one (and will only be
>> just
>> one) super-POM and it lives in Maven core. What you are talking about is
>> a
>> parent-pom and should be called that.
>>
>> Also, you're talking about archetypes which is something completely
>> different from "artifacts" which I believe you're referring to. Please
>> pay
>> attention to the wording as it makes it easier for other people to
>> understand what you're explaining.
>>
>> As you've noticed, the actual profile isn't inherited but rather the
>> effect
>> of the profile. One of those tricky things with profiles but that's by
>> design. The simplest thing is to try staying away from profiles all
>> together
>> as they very often trick you into doing something which isn't the Maven
>> Way..
>>
>> /Anders
>>
>> On Wed, Apr 13, 2011 at 20:32, Bock, Richard (NSN - DE/Munich) <
>> richard.bock@nsn.com> wrote:
>>
>> > Today I found a workaround which is somehow not optional but keeps me
>> > alive.
>> >
>> > All the base artifact types of a certain platform type will be put
>> into a
>> > super-pom for that platform type. E.g. jee-super-pom. Each artifact
>> base
>> > type plugin and properties is encapsulated into a Profile. The profile
>> is
>> > activated by a file that exists in the child project.
>> >
>> > Now the aggregator project myapp-pom can inherit from the
>> jee-super.pom.
>> >
>> > Each module module-pom will have a file e.g. javalib-architype,
>> > groovylib-architype, basemodel-architype, testimpl-architype. This
>> will
>> > activate the base architype profiles.
>> >
>> > Drawback is that this leaves the module-pom projects with funny empty
>> > marker files in the project folder and the files cannot be looked up
>> in the
>> > repository as they are no architypes.
>> >
>> > What I find rather annoying is that even the activiation condition
>> based on
>> > properties will not work as the parent profiles will only be triggered
>> by
>> > parent properties and not by properties defined in the module-pom.
>> >
>> > So I just hope someday or earlier then later someone will add a
>> feature to
>> > Maven to resolved the parent properties, then the child properties and
>> then
>> > start resolving the profiles only.
>> >
>> > Or let us keep the hope up some one delivers the MIXIN feature.
>> >
>> > /Richard
>> >
>> >
>> > -----Original Message-----
>> > From: ext Wayne Fay [mailto:waynefay@gmail.com]
>> > Sent: Wednesday, April 13, 2011 8:19 PM
>> > To: Maven Users List
>> > Subject: Re: Expected implementation date for Maven MIXIN Feature
>> >
>> > > AM gets the version from A through the parent relationship.
>> > > AM gets the plugin sce.model from the MIXIN relationship to M.
>> > >
>> > > AI gets the version from A through the parent relationship.
>> > > AI gets the plugin sce.compile from the MIXIN relationship to I.
>> >
>> > Sounds roughly like composition of objects/projects in the POM, is
>> > that about right? I haven't really been following any discussion of
>> > Mixins previously.
>> >
>> > Wayne
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> > For additional commands, e-mail: users-help@maven.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Expected implementation date for Maven MIXIN Feature

Posted by Stephen Connolly <st...@gmail.com>.
http://www.mail-archive.com/dev@maven.apache.org/msg85145.html

On 14 April 2011 13:16, Martin Gainty <mg...@hotmail.com> wrote:
>
> you may want to consider aggregating your plugins into a dependency-management block
> then further down have your poms pull in that dependency-management block of plugins with <scope>import</scope>
> in the calling poms dependency-management dependency
>
> http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
>
> if this doesnt suit your need we could provide a better solution if
> you could provide specifics on what you are attempting to accomplish
>
> gruss
> Martin
> ______________________________________________
> Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
>
> 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: RE: Expected implementation date for Maven MIXIN Feature
>> Date: Thu, 14 Apr 2011 11:50:06 +0200
>> From: richard.bock@nsn.com
>> To: users@maven.apache.org
>>
>> Hi Anders,
>>
>> Thanks for your clarifications. I try get the wordings right. But what
>> are you actually suggesting? I mean stay away from profiles. Yeah. But
>> what to use instead? Modules will not work as I am actually already
>> using them. I need modules that have an aggregation parent and still get
>> some model type specific configuration (plugins e.g. that are always
>> same for a certain module type).
>>
>> Currently using profiles and <activation><file><exists> is only a
>> workaround. I am still curious to get a reply from some Maven
>> contributor on whether this problem can be solved with MIXIN and when
>> MIXIN will be available.
>>
>> Using profiles in this manner has the advantage that all module pom
>> files are using the traditional aggregation parent but do not contain
>> any redundant plugin configurations that are related to the module type
>> (e.g. modeling project, java implementation project, web service project
>> and so on)
>>
>> /Richard
>>
>>
>> -----Original Message-----
>> From: anders.g.hammar@gmail.com [mailto:anders.g.hammar@gmail.com] On
>> Behalf Of ext Anders Hammar
>> Sent: Thursday, April 14, 2011 11:09 AM
>> To: Maven Users List
>> Subject: Re: Expected implementation date for Maven MIXIN Feature
>>
>> Please, don't call it a super-pom. There is only one (and will only be
>> just
>> one) super-POM and it lives in Maven core. What you are talking about is
>> a
>> parent-pom and should be called that.
>>
>> Also, you're talking about archetypes which is something completely
>> different from "artifacts" which I believe you're referring to. Please
>> pay
>> attention to the wording as it makes it easier for other people to
>> understand what you're explaining.
>>
>> As you've noticed, the actual profile isn't inherited but rather the
>> effect
>> of the profile. One of those tricky things with profiles but that's by
>> design. The simplest thing is to try staying away from profiles all
>> together
>> as they very often trick you into doing something which isn't the Maven
>> Way..
>>
>> /Anders
>>
>> On Wed, Apr 13, 2011 at 20:32, Bock, Richard (NSN - DE/Munich) <
>> richard.bock@nsn.com> wrote:
>>
>> > Today I found a workaround which is somehow not optional but keeps me
>> > alive.
>> >
>> > All the base artifact types of a certain platform type will be put
>> into a
>> > super-pom for that platform type. E.g. jee-super-pom. Each artifact
>> base
>> > type plugin and properties is encapsulated into a Profile. The profile
>> is
>> > activated by a file that exists in the child project.
>> >
>> > Now the aggregator project myapp-pom can inherit from the
>> jee-super.pom.
>> >
>> > Each module module-pom will have a file e.g. javalib-architype,
>> > groovylib-architype, basemodel-architype, testimpl-architype. This
>> will
>> > activate the base architype profiles.
>> >
>> > Drawback is that this leaves the module-pom projects with funny empty
>> > marker files in the project folder and the files cannot be looked up
>> in the
>> > repository as they are no architypes.
>> >
>> > What I find rather annoying is that even the activiation condition
>> based on
>> > properties will not work as the parent profiles will only be triggered
>> by
>> > parent properties and not by properties defined in the module-pom.
>> >
>> > So I just hope someday or earlier then later someone will add a
>> feature to
>> > Maven to resolved the parent properties, then the child properties and
>> then
>> > start resolving the profiles only.
>> >
>> > Or let us keep the hope up some one delivers the MIXIN feature.
>> >
>> > /Richard
>> >
>> >
>> > -----Original Message-----
>> > From: ext Wayne Fay [mailto:waynefay@gmail.com]
>> > Sent: Wednesday, April 13, 2011 8:19 PM
>> > To: Maven Users List
>> > Subject: Re: Expected implementation date for Maven MIXIN Feature
>> >
>> > > AM gets the version from A through the parent relationship.
>> > > AM gets the plugin sce.model from the MIXIN relationship to M.
>> > >
>> > > AI gets the version from A through the parent relationship.
>> > > AI gets the plugin sce.compile from the MIXIN relationship to I.
>> >
>> > Sounds roughly like composition of objects/projects in the POM, is
>> > that about right? I haven't really been following any discussion of
>> > Mixins previously.
>> >
>> > Wayne
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> > For additional commands, e-mail: users-help@maven.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


RE: Expected implementation date for Maven MIXIN Feature

Posted by Martin Gainty <mg...@hotmail.com>.
you may want to consider aggregating your plugins into a dependency-management block
then further down have your poms pull in that dependency-management block of plugins with <scope>import</scope>
in the calling poms dependency-management dependency

http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html

if this doesnt suit your need we could provide a better solution if 
you could provide specifics on what you are attempting to accomplish

gruss 
Martin 
______________________________________________ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
 
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: RE: Expected implementation date for Maven MIXIN Feature
> Date: Thu, 14 Apr 2011 11:50:06 +0200
> From: richard.bock@nsn.com
> To: users@maven.apache.org
> 
> Hi Anders,
> 
> Thanks for your clarifications. I try get the wordings right. But what
> are you actually suggesting? I mean stay away from profiles. Yeah. But
> what to use instead? Modules will not work as I am actually already
> using them. I need modules that have an aggregation parent and still get
> some model type specific configuration (plugins e.g. that are always
> same for a certain module type).
> 
> Currently using profiles and <activation><file><exists> is only a
> workaround. I am still curious to get a reply from some Maven
> contributor on whether this problem can be solved with MIXIN and when
> MIXIN will be available.
> 
> Using profiles in this manner has the advantage that all module pom
> files are using the traditional aggregation parent but do not contain
> any redundant plugin configurations that are related to the module type
> (e.g. modeling project, java implementation project, web service project
> and so on)
> 
> /Richard
> 
> 
> -----Original Message-----
> From: anders.g.hammar@gmail.com [mailto:anders.g.hammar@gmail.com] On
> Behalf Of ext Anders Hammar
> Sent: Thursday, April 14, 2011 11:09 AM
> To: Maven Users List
> Subject: Re: Expected implementation date for Maven MIXIN Feature
> 
> Please, don't call it a super-pom. There is only one (and will only be
> just
> one) super-POM and it lives in Maven core. What you are talking about is
> a
> parent-pom and should be called that.
> 
> Also, you're talking about archetypes which is something completely
> different from "artifacts" which I believe you're referring to. Please
> pay
> attention to the wording as it makes it easier for other people to
> understand what you're explaining.
> 
> As you've noticed, the actual profile isn't inherited but rather the
> effect
> of the profile. One of those tricky things with profiles but that's by
> design. The simplest thing is to try staying away from profiles all
> together
> as they very often trick you into doing something which isn't the Maven
> Way..
> 
> /Anders
> 
> On Wed, Apr 13, 2011 at 20:32, Bock, Richard (NSN - DE/Munich) <
> richard.bock@nsn.com> wrote:
> 
> > Today I found a workaround which is somehow not optional but keeps me
> > alive.
> >
> > All the base artifact types of a certain platform type will be put
> into a
> > super-pom for that platform type. E.g. jee-super-pom. Each artifact
> base
> > type plugin and properties is encapsulated into a Profile. The profile
> is
> > activated by a file that exists in the child project.
> >
> > Now the aggregator project myapp-pom can inherit from the
> jee-super.pom.
> >
> > Each module module-pom will have a file e.g. javalib-architype,
> > groovylib-architype, basemodel-architype, testimpl-architype. This
> will
> > activate the base architype profiles.
> >
> > Drawback is that this leaves the module-pom projects with funny empty
> > marker files in the project folder and the files cannot be looked up
> in the
> > repository as they are no architypes.
> >
> > What I find rather annoying is that even the activiation condition
> based on
> > properties will not work as the parent profiles will only be triggered
> by
> > parent properties and not by properties defined in the module-pom.
> >
> > So I just hope someday or earlier then later someone will add a
> feature to
> > Maven to resolved the parent properties, then the child properties and
> then
> > start resolving the profiles only.
> >
> > Or let us keep the hope up some one delivers the MIXIN feature.
> >
> > /Richard
> >
> >
> > -----Original Message-----
> > From: ext Wayne Fay [mailto:waynefay@gmail.com]
> > Sent: Wednesday, April 13, 2011 8:19 PM
> > To: Maven Users List
> > Subject: Re: Expected implementation date for Maven MIXIN Feature
> >
> > > AM gets the version from A through the parent relationship.
> > > AM gets the plugin sce.model from the MIXIN relationship to M.
> > >
> > > AI gets the version from A through the parent relationship.
> > > AI gets the plugin sce.compile from the MIXIN relationship to I.
> >
> > Sounds roughly like composition of objects/projects in the POM, is
> > that about right? I haven't really been following any discussion of
> > Mixins previously.
> >
> > Wayne
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
 		 	   		  

RE: Expected implementation date for Maven MIXIN Feature

Posted by "Bock, Richard (NSN - DE/Munich)" <ri...@nsn.com>.
Hi Anders,

Thanks for your clarifications. I try get the wordings right. But what
are you actually suggesting? I mean stay away from profiles. Yeah. But
what to use instead? Modules will not work as I am actually already
using them. I need modules that have an aggregation parent and still get
some model type specific configuration (plugins e.g. that are always
same for a certain module type).

Currently using profiles and <activation><file><exists> is only a
workaround. I am still curious to get a reply from some Maven
contributor on whether this problem can be solved with MIXIN and when
MIXIN will be available.

Using profiles in this manner has the advantage that all module pom
files are using the traditional aggregation parent but do not contain
any redundant plugin configurations that are related to the module type
(e.g. modeling project, java implementation project, web service project
and so on)

/Richard


-----Original Message-----
From: anders.g.hammar@gmail.com [mailto:anders.g.hammar@gmail.com] On
Behalf Of ext Anders Hammar
Sent: Thursday, April 14, 2011 11:09 AM
To: Maven Users List
Subject: Re: Expected implementation date for Maven MIXIN Feature

Please, don't call it a super-pom. There is only one (and will only be
just
one) super-POM and it lives in Maven core. What you are talking about is
a
parent-pom and should be called that.

Also, you're talking about archetypes which is something completely
different from "artifacts" which I believe you're referring to. Please
pay
attention to the wording as it makes it easier for other people to
understand what you're explaining.

As you've noticed, the actual profile isn't inherited but rather the
effect
of the profile. One of those tricky things with profiles but that's by
design. The simplest thing is to try staying away from profiles all
together
as they very often trick you into doing something which isn't the Maven
Way..

/Anders

On Wed, Apr 13, 2011 at 20:32, Bock, Richard (NSN - DE/Munich) <
richard.bock@nsn.com> wrote:

> Today I found a workaround which is somehow not optional but keeps me
> alive.
>
> All the base artifact types of a certain platform type will be put
into a
> super-pom for that platform type. E.g. jee-super-pom. Each artifact
base
> type plugin and properties is encapsulated into a Profile. The profile
is
> activated by a file that exists in the child project.
>
> Now the aggregator project myapp-pom can inherit from the
jee-super.pom.
>
> Each module module-pom will have a file e.g. javalib-architype,
> groovylib-architype, basemodel-architype, testimpl-architype. This
will
> activate the base architype profiles.
>
> Drawback is that this leaves the module-pom projects with funny empty
> marker files in the project folder and the files cannot be looked up
in the
> repository as they are no architypes.
>
> What I find rather annoying is that even the activiation condition
based on
> properties will not work as the parent profiles will only be triggered
by
> parent properties and not by properties defined in the module-pom.
>
> So I just hope someday or earlier then later someone will add a
feature to
> Maven to resolved the parent properties, then the child properties and
then
> start resolving the profiles only.
>
> Or let us keep the hope up some one delivers the MIXIN feature.
>
> /Richard
>
>
> -----Original Message-----
> From: ext Wayne Fay [mailto:waynefay@gmail.com]
> Sent: Wednesday, April 13, 2011 8:19 PM
> To: Maven Users List
> Subject: Re: Expected implementation date for Maven MIXIN Feature
>
> > AM gets the version from A through the parent relationship.
> > AM gets the plugin sce.model from the MIXIN relationship to M.
> >
> > AI gets the version from A through the parent relationship.
> > AI gets the plugin sce.compile from the MIXIN relationship to I.
>
> Sounds roughly like composition of objects/projects in the POM, is
> that about right? I haven't really been following any discussion of
> Mixins previously.
>
> Wayne
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Expected implementation date for Maven MIXIN Feature

Posted by Anders Hammar <an...@hammar.net>.
Please, don't call it a super-pom. There is only one (and will only be just
one) super-POM and it lives in Maven core. What you are talking about is a
parent-pom and should be called that.

Also, you're talking about archetypes which is something completely
different from "artifacts" which I believe you're referring to. Please pay
attention to the wording as it makes it easier for other people to
understand what you're explaining.

As you've noticed, the actual profile isn't inherited but rather the effect
of the profile. One of those tricky things with profiles but that's by
design. The simplest thing is to try staying away from profiles all together
as they very often trick you into doing something which isn't the Maven
Way..

/Anders

On Wed, Apr 13, 2011 at 20:32, Bock, Richard (NSN - DE/Munich) <
richard.bock@nsn.com> wrote:

> Today I found a workaround which is somehow not optional but keeps me
> alive.
>
> All the base artifact types of a certain platform type will be put into a
> super-pom for that platform type. E.g. jee-super-pom. Each artifact base
> type plugin and properties is encapsulated into a Profile. The profile is
> activated by a file that exists in the child project.
>
> Now the aggregator project myapp-pom can inherit from the jee-super.pom.
>
> Each module module-pom will have a file e.g. javalib-architype,
> groovylib-architype, basemodel-architype, testimpl-architype. This will
> activate the base architype profiles.
>
> Drawback is that this leaves the module-pom projects with funny empty
> marker files in the project folder and the files cannot be looked up in the
> repository as they are no architypes.
>
> What I find rather annoying is that even the activiation condition based on
> properties will not work as the parent profiles will only be triggered by
> parent properties and not by properties defined in the module-pom.
>
> So I just hope someday or earlier then later someone will add a feature to
> Maven to resolved the parent properties, then the child properties and then
> start resolving the profiles only.
>
> Or let us keep the hope up some one delivers the MIXIN feature.
>
> /Richard
>
>
> -----Original Message-----
> From: ext Wayne Fay [mailto:waynefay@gmail.com]
> Sent: Wednesday, April 13, 2011 8:19 PM
> To: Maven Users List
> Subject: Re: Expected implementation date for Maven MIXIN Feature
>
> > AM gets the version from A through the parent relationship.
> > AM gets the plugin sce.model from the MIXIN relationship to M.
> >
> > AI gets the version from A through the parent relationship.
> > AI gets the plugin sce.compile from the MIXIN relationship to I.
>
> Sounds roughly like composition of objects/projects in the POM, is
> that about right? I haven't really been following any discussion of
> Mixins previously.
>
> Wayne
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

RE: Expected implementation date for Maven MIXIN Feature

Posted by "Bock, Richard (NSN - DE/Munich)" <ri...@nsn.com>.
Today I found a workaround which is somehow not optional but keeps me alive.

All the base artifact types of a certain platform type will be put into a super-pom for that platform type. E.g. jee-super-pom. Each artifact base type plugin and properties is encapsulated into a Profile. The profile is activated by a file that exists in the child project.

Now the aggregator project myapp-pom can inherit from the jee-super.pom.

Each module module-pom will have a file e.g. javalib-architype, groovylib-architype, basemodel-architype, testimpl-architype. This will activate the base architype profiles.

Drawback is that this leaves the module-pom projects with funny empty marker files in the project folder and the files cannot be looked up in the repository as they are no architypes.

What I find rather annoying is that even the activiation condition based on properties will not work as the parent profiles will only be triggered by parent properties and not by properties defined in the module-pom.

So I just hope someday or earlier then later someone will add a feature to Maven to resolved the parent properties, then the child properties and then start resolving the profiles only. 

Or let us keep the hope up some one delivers the MIXIN feature.

/Richard


-----Original Message-----
From: ext Wayne Fay [mailto:waynefay@gmail.com] 
Sent: Wednesday, April 13, 2011 8:19 PM
To: Maven Users List
Subject: Re: Expected implementation date for Maven MIXIN Feature

> AM gets the version from A through the parent relationship.
> AM gets the plugin sce.model from the MIXIN relationship to M.
>
> AI gets the version from A through the parent relationship.
> AI gets the plugin sce.compile from the MIXIN relationship to I.

Sounds roughly like composition of objects/projects in the POM, is
that about right? I haven't really been following any discussion of
Mixins previously.

Wayne

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Expected implementation date for Maven MIXIN Feature

Posted by Wayne Fay <wa...@gmail.com>.
> AM gets the version from A through the parent relationship.
> AM gets the plugin sce.model from the MIXIN relationship to M.
>
> AI gets the version from A through the parent relationship.
> AI gets the plugin sce.compile from the MIXIN relationship to I.

Sounds roughly like composition of objects/projects in the POM, is
that about right? I haven't really been following any discussion of
Mixins previously.

Wayne

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


RE: Expected implementation date for Maven MIXIN Feature

Posted by "Bock, Richard (NSN - DE/Munich)" <ri...@nsn.com>.
Hi Wayne,

I want to give a small sample to make it more clear what I am requiring from MIXIN feature:

Project M is the base artifact for all modeling artifacts and defines the plugin sce.model with the required dependencies.

Project I is the base artifact for all implementation artifacts and defines the plugin sce.compile with the required dependencies.

Project A is the aggregation and defines an application <version>2.0.0</version>
And has two modules "AM" and "AI"

Project AM is the model artifact of the application A and has as a parent A and as a MIXIN M.

Project AI is the implementation artifact of the application A and has  as a parent A and as a MIXIN I.

AM gets the version from A through the parent relationship.
AM gets the plugin sce.model from the MIXIN relationship to M.

AI gets the version from A through the parent relationship.
AI gets the plugin sce.compile from the MIXIN relationship to I.

I hope this makes it more clear what I would expect the MIXIN feature to do.

Regards

Richard


 
-----Original Message-----
From: ext Wayne Fay [mailto:waynefay@gmail.com] 
Sent: Wednesday, April 13, 2011 6:49 AM
To: Maven Users List
Subject: Re: Expected implementation date for Maven MIXIN Feature

> The only solution out of this problem I understood when reading the
> Internet is the MIXIN feature.  You can find in the Internet references

I guess I don't understand the requirement very well. Some practical
examples might be helpful for all of us.

> Do you consider to include the MIXIN feature into Maven 3.0 as an
> important update?

Personally, no, I don't need it. I won't prevent someone else from
adding it, if it makes sense.

> 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.

Maven is open source. The best way for something like this to get done
is for someone who cares about this issue and perhaps needs it for
their own projects/work to roll up their sleeves and take a stab at an
implementation. Assuming it works and makes sense, the changed code
could be donated back and considered for inclusion in a future release
of Maven. Even if it wasn't accepted, there is nothing stopping
someone from continuing to run (and support) their own internal build
of Maven with additional features (this happens now and then).

Short of this, you can find an existing Jira issue and vote/watch it
or file one if you can't find an issue that captures the mixin
feature, and then just wait for someone who cares more about it than
you do to implement it on your behalf.

Wayne

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Expected implementation date for Maven MIXIN Feature

Posted by Wayne Fay <wa...@gmail.com>.
> The only solution out of this problem I understood when reading the
> Internet is the MIXIN feature.  You can find in the Internet references

I guess I don't understand the requirement very well. Some practical
examples might be helpful for all of us.

> Do you consider to include the MIXIN feature into Maven 3.0 as an
> important update?

Personally, no, I don't need it. I won't prevent someone else from
adding it, if it makes sense.

> 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.

Maven is open source. The best way for something like this to get done
is for someone who cares about this issue and perhaps needs it for
their own projects/work to roll up their sleeves and take a stab at an
implementation. Assuming it works and makes sense, the changed code
could be donated back and considered for inclusion in a future release
of Maven. Even if it wasn't accepted, there is nothing stopping
someone from continuing to run (and support) their own internal build
of Maven with additional features (this happens now and then).

Short of this, you can find an existing Jira issue and vote/watch it
or file one if you can't find an issue that captures the mixin
feature, and then just wait for someone who cares more about it than
you do to implement it on your behalf.

Wayne

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org