consider the in any situation where you want to change things based on flags 
its gets complicated.

why not just have a separate artifact that is very simple for each scenario...

there might be a little more setup but it means for a maven aware developer 
they know that you have 5 projects therefore 5 artifacts and if you say 
install or package on them you can get five results...

now consider your profile scenario... how many profiles... how many 
combinations... in order to understand any one of your projects a deveoper 
would need to read and understand all the profiles...


On Sat, 11 Oct 2008 22:55:15 Stephen Connolly wrote:
> I would think a better way would be to specify the different artifacts
> as dependencies only in different profiles.
>
> You can then just activate the profile for the artifact you want, and
> everything is self-contained in the pom
>
> 2008/10/11 Brett Porter <[EMAIL PROTECTED]>:
> > mvn help:effective-* will show the profiles actually used.
> >
> > This seems like a very bad idea for build reproducibility however - I
> > wouldn't recommend it.
> >
> > - Brett
> >
> > 2008/10/11 Lucie <[EMAIL PROTECTED]>:
> >> This is defined pom.xml:
> >>
> >> <dependency>
> >>    <groupId><groupId>
> >>   <artifcactId>${my.artifactId}</artifactId>
> >>   <vesion></version>
> >> </dependency>
> >>
> >> I have a profile defined in profiles.xml to pass the ${my.artifactId} as
> >> a property at build time.
> >> This doesn't work - no value is passed. What may have caused to failed?
> >>
> >> Lucie
> >>
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Changing-dependency-in-pom.xml-using-profiles-tp19
> >>927738p19927738.html Sent from the Maven - Users mailing list archive at
> >> Nabble.com.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >
> > --
> > Brett Porter
> > Blog: http://blogs.exist.com/bporter/
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]



-- 
Michael McCallum
Enterprise Engineer
mailto:[EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to