Hi,
Maven allows the user to specify a toolchains file via its --toolchains
parameter (defaulting to ~/.m2/toolchains.xml).
While useful, this ability to override the file's location is
unfortunately a problem if one wants to make the use of the
maven-toolchains-plugin *conditional* upon the pres
Hi all,
I am looking at an issue I encountered while using a Maven plugin that uses
model returned by MavenProject.getOriginalModel(). I noticed that it returns a
Model that is not interpolated (what I expected), with the exception to paths
related to file based profile activation. Both when
June 23, 2017 1:03 AM
> To: users@maven.apache.org
> Subject: [EXTERNAL] Re: project.basedir in file-based profile activation
>
> External Sender: Use caution with links/attachments.
>
>
>
> Justin Georgeson wrote:
>
> > With 3.3.9 and 3.5.0 When I
> -Original Message-
> From: Jörg Schaible [mailto:joerg.schai...@bpm-inspire.com]
> Sent: Friday, June 23, 2017 1:03 AM
> To: users@maven.apache.org
> Subject: [EXTERNAL] Re: project.basedir in file-based profile activation
>
> External Sender: Use caution w
txt
> [for profile jacoco-read-manifest: ${project.basedir} expression not
> [supported during profile activation, use ${basedir} instead
>
> I was under the impression that ${basedir} is deprecated in favor of
> ${project.basedir}, many years ago at that.
That won't help, b
com.example:basedir:jar:1.0-SNAPSHOT
[WARNING] 'profiles.profile[my-profile-id].activation.file.exists' Failed to
interpolate file location ${project.basedir}${file.separator}somefile.txt for
profile jacoco-read-manifest: ${project.basedir} expression not supported
during profile activation, use ${basedir}
bservations, where both platform-reactor
and default-reactor are active when the system property isn't set.
There was the JIRA MNGSITE-293, in which the documentation was clarified
to reflect this.
Guillaume
Le 12/03/2017 à 05:00, Justin Georgeson a écrit :
Seeing that I can ! the prop
Seeing that I can ! the property value in a profile activation, I assumed there
were three states to consider when evaluating the property activation:
1. Property not set
2. Property set and value does not match
3. Property set and value does match
With this assumption I thought
Hi Justin,
Justin Georgeson wrote:
> Thanks. I was hoping that it would evaluate the file-based activation per
> project. I was treating it as a separate issue than the multiple
> conditions. But I think what you're saying is that the profile activation
> happens once for the w
Thanks. I was hoping that it would evaluate the file-based activation per
project. I was treating it as a separate issue than the multiple conditions.
But I think what you're saying is that the profile activation happens once for
the whole reactor, and not per project within the react
ingle copy of the keystore during the package phase
> of the parent project, and the jarsigner profile automatically activates
> during each of the modules due to the presence of the keystore file.
>
> Instead it's deleting the keystore and checking out the keystore file
&g
roject, and the jarsigner profile automatically activates during
each of the modules due to the presence of the keystore file.
Instead it's deleting the keystore and checking out the keystore file during
every project (or instead of and of profile activation conditions), and the
jarsigne
Sorry about that crazy URL, I think that's a network security service my
employer just signed up with.
> -Original Message-
> From: Justin Georgeson [mailto:jgeorge...@lgc.com]
> Sent: Friday, November 06, 2015 9:34 AM
> To: users@maven.apache.org
> Subject: [EXTERNAL
I have a profile defined in my parent POM which I'm trying to activate like this
jarsigner.keystore.scm.url
${keystore.dir}
The goal is that when run with -Djarsig
Thanks for that ingenious solution. It worked perfectly.
--
View this message in context:
http://maven.40175.n5.nabble.com/Work-around-to-the-Maven-restriction-on-AND-condition-profile-activation-tp5782919p5783107.html
Sent from the Maven - Users mailing list archive at Nabble.com
ssage d'origine-
De : laredotornado-3 [mailto:laredotorn...@gmail.com]
Envoyé : vendredi 31 janvier 2014 22:19
À : users@maven.apache.org
Objet : Work-around to the Maven restriction on AND condition profile
activation?
Hi,
I’m using Maven 3.1.1 and Java 1.6. From reading over posts online, it
Hi,
I’m using Maven 3.1.1 and Java 1.6. From reading over posts online, it
seems a profile cannot be activated based on two conditions (i.e. there is
no such thing as logical AND in Maven profile activation). So I was
wondering if someone knows of a work-around for what I want to do. I want
to
Hi,
you don't need to add a new profile. the new plugin is still compatible
with maven 3.0.x (See comment [1])
[1] http://jira.codehaus.org/browse/MSONAR-22
Vincent
2013/8/9 Lyons, Roy
>
> So... They released sonar-maven-plugin 2.1... and my corporate pom is
> nice enough to developers to
So... They released sonar-maven-plugin 2.1... and my corporate pom is nice
enough to developers to choose the right sonar plugin based on maven version...
maven-2
s be an unambigious activation
unix
Linux
You can get the os name by running "mvn help:system |grep os.name"
--
View this message in context:
http://maven.40175.n5.nabble.com/Profile-activation-for-mac-and-linux-tp3263043p5661715.
.
The problem is, that they don't work as described in the settings reference,
when I use more than one condition.
--
View this message in context:
http://maven.40175.n5.nabble.com/Combining-profile-activation-parameters-doesn-t-work-tp5154834p5157799.html
Sent from the Maven - Users mailing list
http://jira.codehaus.org/browse/MNG-4516
http://jira.codehaus.org/browse/MNG-3328
--
View this message in context:
http://maven.40175.n5.nabble.com/Combining-profile-activation-parameters-doesn-t-work-tp5154834p5157134.html
Sent from the Maven - Users mailing list archive at Nabble.com
/Combining-profile-activation-parameters-doesn-t-work-tp5154834p5157134.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e
oblems?
I definitaly can activate Windows and Unix profiles at the same time on the
same machine, just by adding a property.
--
View this message in context:
http://maven.40175.n5.nabble.com/Combining-profile-activation-parameters-doesn-t-work-tp5154834p5156971.html
Sent from the Maven - Users ma
Ok. I mastered it :-)
I have to use the to combine them.
--
View this message in context:
http://maven.40175.n5.nabble.com/Profile-activation-by-OS-Arch-and-by-Property-doesn-t-work-tp5154834p5154899.html
Sent from the Maven - Users mailing list archive at Nabble.com
ermCD), while the other profiles (which
should definitely not run on a windows-32-bit machine) only list the
Cadenza-Profiles.
Can anybody explain this behaviour to me?
Thanks.
Benjamin
--
View this message in context:
http://maven.40175.n5.nabble.com/Profile-activation-by-OS-Arch-and-by-Property-
Yes you can, try: !true
See http://svn.codehaus.org/mojo/trunk/mojo/sql-maven-plugin/pom.xml
> Date: Mon, 24 Oct 2011 17:30:24 -0400
> Subject: Profile activation based on property absence OR property value of
> "false"
> Fr
It looks like activating a profile based on EITHER the absence of a property
OR the presence of that property with a particular value is not possible.
Is that correct?
For example, suppose I wanted to add in a bunch of plugins if the
"skipTests" property was (a) specified with a value of "false" o
To start, I've searched the archives and JIRA and read through a lot
of the background on this issue. For instance,
http://jira.codehaus.org/browse/MNG-2363
With that said, I'm still wondering what the current capability is for
profile activation and what the future direction,
n't think of an alternative.
Any tips please ?
Best regards,
Raymond
--
View this message in context:
http://maven.40175.n5.nabble.com/profile-activation-tp4315068p4315068.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
contains this:
false
false
none
validate
Note that although I have not specified one of the conditions for profile
activation, that profile's property settings have been applied. It's like
the profile was activated, even though one of its conditions for
activation--
It appeared to exhibit the same behavior for me in 3.0.0 and 2.1.0,
which are the versions I keep around. I see that the JIRA is marked
fixed in 3, so either it's not so fixed, or I made some methodological
experiment in trying it in 3 as well as 2.1.
On Sun, Dec 12, 2010 at 2:46 PM, Wendy Smoak
On Sun, Dec 12, 2010 at 1:57 PM, Benson Margulies wrote:
> In a parent profile, I have a profile that is supposed to activate
> based on the presence of a file in the tree of the child that uses the
> parent. It does not, and -X is not helping me ... since it seems to
> contradict itself. I must b
In a parent profile, I have a profile that is supposed to activate
based on the presence of a file in the tree of the child that uses the
parent. It does not, and -X is not helping me ... since it seems to
contradict itself. I must be missing something simple here, no?
[DEBUG] Profile with id: 'pa
Hi,
is there any possibility to activate a Maven profile if a system property has
either value "A" OR value "B" but NOT if it has value "C"?
Unfortunately it is neither allowed to specify multiple "value" entries like
this:
playground
Hi!
I would like to have a bunch of properties set differently for Mac, Linux
and Windows.
So I have inserted this
linux
unix
mac
On Wed, Oct 27, 2010 at 11:41 AM, Anders Hammar wrote:
> You either need to separate the configuration from the binaries, or have
> different artifacts.
>
The configuration is separated from the binaries for the most part. however
some artifacts (like a war file) have environment specific class p
You either need to separate the configuration from the binaries, or have
different artifacts.
Your current solution does not work if you do deploys to a repo and adhere
to the very important Maven rule that a release may NEVER be altered.
/Anders
On Wed, Oct 27, 2010 at 18:52, Jon Paynter wrote:
>> >> first to build the final POM in use. See help:effective-pom.
>> >>
>> >> - Jörg
>> >>
>> >> Well that explains the source of my confusion. I'll just find another
>> >> way
>> > to accomplish the same thing.
&g
On 27/10/2010 1:51 AM, Anders Hammar wrote:
While on the topic, I'd like to mention that having a different build
(through profiles for example) for each environment is not good. In Maven,
there can only be one flavor of a released artifact. So if you build v1.0 of
your war, cannot rebuild it wit
While on the topic, I'd like to mention that having a different build
(through profiles for example) for each environment is not good. In Maven,
there can only be one flavor of a released artifact. So if you build v1.0 of
your war, cannot rebuild it with a different content.
What you should do is
POM in use. See help:effective-pom.
> >>
> >> - Jörg
> >>
> >> Well that explains the source of my confusion. I'll just find another
> >> way
> > to accomplish the sam
arent POM. Profiles are resolved
>> first to build the final POM in use. See help:effective-pom.
>>
>> - Jörg
>>
>> Well that explains the source of my confusion. I'll just find another
>> way
> to accomplish the same thing.
You can set system properties ca
On Tue, Oct 26, 2010 at 4:12 PM, Jörg Schaible wrote:
> Hi Jon,
>
>
> > what am I missing here?
>
> It does simply not work this way. You cannot activate a profile by a
> property defined in the current or parent POM. Profiles are resolved first
> to build the final POM in use. See help:effective-
Hi Jon,
Jon Paynter wrote:
> Im trying to setup some build profiles for our various build environments
> (dev, qa, prod, etc). but I cant get the 'dev' profile to be active. The
> envType property is set to a default value of 'dev' in my top level pom,
> but it will sometimes be given on the com
Im trying to setup some build profiles for our various build environments
(dev, qa, prod, etc). but I cant get the 'dev' profile to be active. The
envType property is set to a default value of 'dev' in my top level pom, but
it will sometimes be given on the command line, and in that case, activate
!true
...
Profile activation can easily be checked with:
mvn help:active-profiles -DskipDocs
mvn help:active-profiles -DskipDocs=true
mvn help:active-profiles -DskipDocs=false
(not specifying a value makes it true).
Regards,
Kees
--
Squins | IT, Honestly
Oranjestraat 23
2983 HL Ridderkerk
The Nether
the profile would become:
>
>
>
>documentation
>
>
> skipDocs
> !true
>
>
> ...
>
>
>
> Profile activation can easily be checked with:
> mvn
...
Profile activation can easily be checked with:
mvn help:active-profiles -DskipDocs
mvn help:active-profiles -DskipDocs=true
mvn help:active-profiles -DskipDocs=false
(not specifying a value makes it true).
Regards,
Kees
--
Squins | IT, Honestly
Oranjestraat 23
2983 HL Ridderkerk
On 10/20/2010 12:35 PM, Wendy Smoak wrote:
On Wed, Oct 20, 2010 at 5:32 AM, Joachim Van der Auwera
wrote:
However, since the switch to maven3 this does not worka anymore and "mvn
-DskipDocs install" will still include the "documentation" module.
Do I have to do something different to make
On Wed, Oct 20, 2010 at 5:32 AM, Joachim Van der Auwera
wrote:
> However, since the switch to maven3 this does not worka anymore and "mvn
> -DskipDocs install" will still include the "documentation" module.
> Do I have to do something different to make this work in maven3?
What happens if you do
Could be a regression then. Create a test project and file a ticket.
/Anders
On Wed, Oct 20, 2010 at 11:32, Joachim Van der Auwera <
joac...@triathlon98.com> wrote:
> I am using the following profile
>
>
>
> documentation
>
>
> !skipDocs
>
>
>
> documentation
>
>
>
>
> However, since t
I am using the following profile
documentation
!skipDocs
documentation
However, since the switch to maven3 this does not worka anymore and "mvn
-DskipDocs install" will still include the "documentation" module.
Do I have to do something different to make this work in maven3?
Thanks
On Sat, Oct 2, 2010 at 1:33 PM, Géraud wrote:
> Thanks for your answer. So, for the same reason, when "server.type" is
> defined as a global property in my pom file, the "type1" profile is not
> active.
>
> But is there a way to automaticallly activate "type1" profile when "env1"
> profile is acti
Thanks for your answer. So, for the same reason, when "server.type" is
defined as a global property in my pom file, the "type1" profile is not
active.
But is there a way to automaticallly activate "type1" profile when "env1"
profile is active ?
Géraud
2010/10/1 Anders Hammar
> Yes, profiles ca
Yes, profiles can only be activated by a system property. server.type is a
maven property, hence it will not activate another profile.
/Anders
On Fri, Oct 1, 2010 at 02:56, Géraud wrote:
> Hi
>
> I'm trying to activate a profile inside another profile :
> here is an example :
>
>
>
>
>
Hi
I'm trying to activate a profile inside another profile :
here is an example :
env1
env
1
type1
type1
server.type
type1
This appears to be a bug that has been re-introduced into mvn 2.2.1:
http://jira.codehaus.org/browse/MPH-16
I've tried it on two different maven installs using the helptest.zip file
attached.
On 16 September 2010 16:33, Xavier D. wrote:
> I am executing a project's pom.xml directly. It has a
I am executing a project's pom.xml directly. It has a parent "common.pom"
(common to many projects). The project is executed directly by mvn.
Profile details were added into the pom.xml and detected automatically and
when specifying the -P on the command line.
Moving the profile details to the
Hello,
Judging from http://docs.codehaus.org/display/MAVENUSER/Profiles, I can't
use properties in the element of profile activation.
Can I use ant pattern ? example :
src/main/resources/**/*.gw
profile activation by properties is activation by _SYSTEM_PROPERTIES_ (i.e.
-Dname=value on the CLI)
so properties defined in the pom will never trigger the profile activation.
so profile b being active will never trigger profile A.
-Stephen
On 19 May 2010 16:48, sebb wrote:
> A profile
A profile (A) can be automatically activated by a property (P).
A profile (B) can also define a property (P).
So if profile B is activated it will define property P.
Will this then always activate profile A?
Seems to me that this will depend on the order in which profiles are processed.
Is thi
enstag, 16. Februar 2010 15:09
An: Maven Users List
Betreff: Re: Profile activation with maven & subsystems
The the answer is yes, he/she needs to create a new version of the parent.
But, I think you're just making things too complicated. A developer just
don't all of a sudden want to
16. Februar 2010 14:47
> An: Maven Users List
> Betreff: Re: Profile activation with maven & subsystems
>
> If I understand you correctly, the reason for putting this in the parent of
> Z is that a developer of Z shouldn't change this. If it's local to Z, it
> shouldnit
g, 16. Februar 2010 14:47
An: Maven Users List
Betreff: Re: Profile activation with maven & subsystems
If I understand you correctly, the reason for putting this in the parent of
Z is that a developer of Z shouldn't change this. If it's local to Z, it
shouldnit go in the parent...
H
[mailto:anders.g.ham...@gmail.com] Im
> Auftrag von Anders Hammar
> Gesendet: Dienstag, 16. Februar 2010 12:42
> An: Maven Users List
> Betreff: Re: Profile activation with maven & subsystems
>
> Yes. So you'll have different version of this pom, but it's still just
ugin/use-latest-snapshots-mojo.html
could be more instructive.
-Ursprüngliche Nachricht-
Von: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] Im Auftrag
von Anders Hammar
Gesendet: Dienstag, 16. Februar 2010 12:42
An: Maven Users List
Betreff: Re: Profile activation with ma
>
> -Ursprüngliche Nachricht-
> Von: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] Im
> Auftrag von Anders Hammar
> Gesendet: Dienstag, 16. Februar 2010 08:58
> An: Maven Users List
> Betreff: Re: Profile activation with maven & subsystems
>
> Don'
iche Nachricht-
Von: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] Im Auftrag
von Anders Hammar
Gesendet: Dienstag, 16. Februar 2010 08:58
An: Maven Users List
Betreff: Re: Profile activation with maven & subsystems
Don't use profiles, as I said in my previous post.
Wha
Don't use profile activation to control what dependencies are used
There are all sorts of subtle ways in which your build will break if
you do that.
The simplest way is to accept that you will change your pom.xml files
during development.
I would keep release versions of dependenci
>
> Thanks in advance
> Chris
>
>
> -Ursprüngliche Nachricht-
> Von: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] Im
> Auftrag von Anders Hammar
> Gesendet: Dienstag, 16. Februar 2010 08:04
> An: Maven Users List
> Betreff: Re: Profile activation w
aven embedder notice
that in the (IDE)?
Thanks in advance
Chris
-Ursprüngliche Nachricht-
Von: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] Im Auftrag
von Anders Hammar
Gesendet: Dienstag, 16. Februar 2010 08:04
An: Maven Users List
Betreff: Re: Profile activation with m
go ahead and activate the profile „subsystem-x“ by a CLI property.
> This would also work, but isn’t really comfortable to working with in IDE’s
> because you had to set this for every component by hand or the IDE won’t
> find any dependency version. Setting these properties in the settings
ind any dependency version. Setting these properties in
the settings.xml for profile activation won't work, it's also not by
design.
So how to easily activate profile "subsystem-x" for maven & maven
embedder in IDE's? Do you have any best practice tip for solving
>From a recently updated
http://maven.apache.org/guides/introduction/introduction-to-profiles.html
"As of Maven 2.0.9, the tags and could be
interpolated. Supported variables are system properties like
${user.home} and enviroment variables like ${env.HOME}. Please note that
properties defined in
légalement obligatoire. Étant donné que
>> les email peuvent facilement être sujets à la manipulation, nous ne
>> pouvons accepter aucune responsabilité pour le contenu fourni.
>>
>>
>>
>>
>>> Date: Thu, 17 Dec 2009 02:31:41 -0800
>>> From: lf
on 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.
>
>
>
>
>> Date: Thu, 17 Dec 200
17 Dec 2009 02:31:41 -0800
> From: lf...@redhat.com
> To: users@maven.apache.org
> Subject: Profile activation
>
>
> Hi guys,
>
> I'm solving issue with issue with Maven 2.1.X,
>
> I want to activate profile when two conditions are satisfied...
&
n.html
says, that this is possible.
--
View this message in context:
http://old.nabble.com/Profile-activation-tp26826008p26826008.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscrib
Hi Jan,
Jan wrote:
> Hi All,
>
> I was just wondering about the following situation
>
> I'm using maven 2.2.1 which requires jdk 1.5 to run, but my modules will
> compile only with 1.4, so i used the 1.4 executable in my compiler plugin.
>
> In this case if i create profile with the activatio
Hi All,
I was just wondering about the following situation
I'm using maven 2.2.1 which requires jdk 1.5 to run, but my modules will
compile only with 1.4, so i used the 1.4 executable in my compiler plugin.
In this case if i create profile with the activation rule for 1.4
when this profile will
thanks for any help or suggestions on how I might make this work.
Obviously my goal is to simple keep database password out of svn and the
project.
Why do you set it in a profile at all? Your settings.xml is private to you.
Thanks. That is just the answer I was looking for actually. I w
James Russo wrote at Dienstag, 8. September 2009 04:33:
> Hello,
>
> In my ~/.m2/settings.xml I have:
>
>
>
>
> setup_database_password
>
> true
>
>
> dev
> secret
>
>
>
>
>
>
> So, this should set environment.type
Thanks Dan..
I've looked at that, and it seems that I have it setup correctly.
However, the profile in my pom (which should be activated by an property
defined in my ~/.m2/settings.xml file) is never activated. Using
help:effective-pom it shows that the property is there, so I know it is
gett
you should be a to search for it
search
maven profile using environment variable
found
http://www.devx.com/Java/Article/32386/1763
good luck.
-D
On Mon, Sep 7, 2009 at 7:33 PM, James Russo wrote:
> Hello,
>
> In my ~/.m2/settings.xml I have:
>
>
>
>
> setup_database_password
>
Hello,
In my ~/.m2/settings.xml I have:
setup_database_password
true
dev
secret
So, this should set environment.type to "dev".
Then in one of my sub-projects pom (beneath parent, not sure that
matters though) I have this:
Yes. I also tried adding the tag with the plugin defined in
the section (not as a profile). I got the same result. The
children still executed the plugin. I defined it to execute on the
deploy phase.
Stephen Connolly wrote:
> Are you saying that if you do sth like this:
>
>
> ...
>
>
That is correct. The build plan is evaluated prior to any plugins
executing... therefore profile activation must be decided up front
AFAIK Maven 3 may be able to fix this somewhat
-Stephen
2009/8/11 David C. Hicks
> Then my experience, I would say, confirms that for both of us. My f
Are you saying that if you do sth like this:
...
...
changes-report
...
...
...
...
false
produce-changes-report
sitedep
Then my experience, I would say, confirms that for both of us. My file
*is* in the top-level, and I found that the profile was activated for
all modules. I had arrived at the same conclusion that they are
evaluated once, at the start of execution.
Benson Margulies wrote:
> You may be walking in
You may be walking into a trap in a multi-module project. It is my
strong impression that activation decisions are not made
module-by-module in the reactor, but only once. When I tried what you
tried I found that, since the top-level project with the modules in it
didn't have the file, the profile
Hi Stephen,
I tried that, but it didn't seem to work. The plugin still tried to
execute for the sub-modules. I ended up punting. I run my
changes:announcement-mail goal in a completely separate Maven run after
my build is completed, but I give it the "-N" switch to keep it from
running child mo
Just define all the _*plugins*_ in your profile as
false
2009/8/10 David C. Hicks
> I take it back. That doesn't help me, either.
> I guess once the profile has been activated at the parent POM level, it
> stays that way for all the children.
>
> David C. Hicks wrote:
> > I must have been blind
I take it back. That doesn't help me, either.
I guess once the profile has been activated at the parent POM level, it
stays that way for all the children.
David C. Hicks wrote:
> I must have been blind when reading through my MDG last night. I found
> what I believe will be my solution.
>
>
I must have been blind when reading through my MDG last night. I found
what I believe will be my solution.
src/changes/changes.xml
Since this is the only module that will have a changes.xml file, this
should do the trick for me. I thought I'd share what I fou
0 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 informatio
${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
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 activat
Sorry — hit send by accident.
On 5 Aug 2009, at 14:43, Dominic Mitchell wrote:
On 5 Aug 2009, at 14:10, Stephen Connolly wrote:
if you think about this a bit more you will realise that what you
are asking
for does not make sense (unless you are trying to configure the
plugin that
you are
On 5 Aug 2009, at 14:10, Stephen Connolly wrote:
if you think about this a bit more you will realise that what you
are asking
for does not make sense (unless you are trying to configure the
plugin that
you are executing.
if you specify a plugin:mojo, then only that plugin:mojo will get
1 - 100 of 217 matches
Mail list logo
