That would substitute the actual name of the artifact in the <name> tag,
though, wouldn't it?
Jonathan Woods wrote:
> ${project.artifactId} might help.
>
> Jon
>
>
>> -----Original Message-----
>> From: David C. Hicks [mailto:dhi...@i-hicks.org]
>> Sent: 10 August 2009 18:12
>> To: Maven Users
>> Subject: Profile Activation Help?
>>
>> I'm trying to get a profile to activate for my parent project
>> but not for the children. Unfortunately, the children
>> inherit from the parent to get dependency information. So,
>> they also inherit everything else.
>> My solution (or so I thought) was to use the
>> project.artifactId property in my activation section...
>>
>> <activation>
>> <activeByDefault>false</activeByDefault>
>> <property>
>> <name>project.artifactId</name>
>> <value>salient</value>
>> </property>
>> </activation>
>>
>> Since only the parent project has this artifact Id, I assumed
>> that it would activate only for the parent. However, there
>> was no activation of this profile at all.
>>
>> My overall goal is to try to get the maven-changes-plugin to
>> do an announcement email using changes.xml in the parent
>> project. I do not want announcements for all of the children, though.
>>
>> Any help?
>> Thanks,
>> Dave
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
