Hi,
platform!all
means that the profile will be active when the system property
"platform" is not defined, or is defined with a value different than
"all". Put another way, it is always active unless "platform" is equal
to "all". This explains your observations, where both platform-reactor
a
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 whole reactor, and n
is to have as much of the build process as possible self-contained
in the POM files and executed from a single mvn command.
> -Original Message-
> From: Jörg Schaible [mailto:joerg.schai...@gmx.de]
> Sent: Tuesday, November 10, 2015 4:26 PM
> To: users@maven.apache.org
> S
Justin Georgeson wrote:
> So here's a minimal parent pom.xml, which lists 2 child modules that I
> created with 'mvn archetype:generate' choosing the
> 'maven-archetype-quickstart' archetype. My goal was that if I
>
> mvn package
>
> Then the compile/test/package occurs with no attempt to sign.
r profile is not automatically activated.
> -Original Message-
> From: Justin Georgeson [mailto:jgeorge...@lgc.com]
> Sent: Friday, November 06, 2015 9:39 AM
> To: Maven Users List
> Subject: [EXTERNAL] RE: profile activation with multiple conditions
>
> Sorry about that craz
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] profile activation
I know this is an old thread, but for the lurkers of the internets, I might
post a possible answer. In stead of using "family" as the identifier, one
could use "name" - either in stead of or in addition to "family".
The following should thus be an unambigious activation
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.
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"
> From: ljnel...@gmail.com
> To
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:
Anders Hammar wrote:
> You need Maven 3.0 to be able to activate profiles in the pom by
> properties set in a profile in settings.xml.
The point is that this functionality is superfluous. If you want a profile
be activated based on properties in settings.xml, you may as well simply add
it there
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
You need Maven 3.0 to be able to activate profiles in the pom by properties
set in a profile in settings.xml.
/Anders
On Wed, Oct 27, 2010 at 01:44, Jörg Schaible wrote:
> Jon Paynter wrote:
>
> > On Tue, Oct 26, 2010 at 4:12 PM, Jörg Schaible
> > wrote:
> >
> >> Hi Jon,
> >>
> >>
> >> > what a
Jon Paynter wrote:
> 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 fin
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
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
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
[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
>
> -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'
.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 maven & subsystems
>
> First, the pdf is missing. Without that I'm not sure I fully understand your
> thoug
>
> 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
First, the pdf is missing. Without that I'm not sure I fully understand your
thoughts.
In general, having your dependencies defined by a profile being active is
IMHO bad practice. The biggest reason for this, however possible not so
important for you if you have a "subsystem", is that if some othe
>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
Sorry, thanks for reply, but this resolution wouldn't help me. :-)
Lukas Fryc wrote:
>
> Thanks Martin,
>
> I tried all of the possible combinations in property name/value, like:
>
> containerId
> !containerId
> containerId
> containerId!
>
>
> mgainty wrote:
>>
>>
>> i would use the not
Thanks Martin,
I tried all of the possible combinations in property name/value, like:
containerId
!containerId
containerId
containerId!
mgainty wrote:
>
>
> i would use the not on the property's name e.g.
>
>
> !containerId
> Martin Gainty
> ___
i would use the not on the property's name e.g.
!containerId
Martin Gainty
__
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger
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
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
>
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 file
> *is
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
That would substitute the actual name of the artifact in the 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
>> S
${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
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
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 executed.
Adding other executions of other plugins to a prof
Hi,
You could activate a profile by -Pprofile flag in comman line. Wont help
you? [?]
2009/8/5 Dominic Mitchell
> Hi all,
>
> I'm wondering — is there a way to activate a profile based on the plugin
> specified on the command line?
>
> The reason for this is that I'm working with a cocoon proje
Use two hudson jobs. Oh and _please_ file an issue with
hudson.dev.java.netto get the batch-tasks plugin to work with m2
project types!
On Jan 24, 2008 2:37 AM, Paul Benedict <[EMAIL PROTECTED]> wrote:
> I believe you can write your own profile activation class, but that's a
> feature of Maven 2.
I believe you can write your own profile activation class, but that's a
feature of Maven 2.1
Paul
On Jan 23, 2008 7:43 PM, Ravi Luthra <[EMAIL PROTECTED]> wrote:
> Does anyone know how to activate a profile in maven if the time is
> between a certain hour of the day?
>
> I'm using a CI to build
On Dec 11, 2007, at 2:31 AM, Thorsten Möller wrote:
Based on the documentation that is available from the Maven Web site
it is
unclear to me what the exact semantic of the tag is: will it be
activated for i) all major Versions greather or equal than the one
specified
including sub version
On 12/11/07, Thorsten Möller <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> my question is regarding activation of profiles based on the tag.
> Assume that a POM specifies two profiles, one that should trigger for JDK
> 1.5.x and one for JDK 1.6.x. The POM would look like this:
>
>
>1.5
>
From: Steven Rowe [mailto:[EMAIL PROTECTED]
Sent: Tue 7/17/2007 9:03 AM
To: Maven Users List
Subject: Re: Profile activation - release
Hi Barrett,
Here's what I do in this situation:
maven-release-plugin
...
-Pmy.release.profile
the "-P" argument activates when the
Hi Barrett,
Here's what I do in this situation:
maven-release-plugin
...
-Pmy.release.profile
the "-P" argument activates when the release:*
goals are run.
Steve
Barrett Nuzum wrote:
> Hi everyone.
>
> I have a plugin that needs to be executed in two different configuratio
On 6/9/07, Den Orlov <[EMAIL PROTECTED]> wrote:
Just realized that isn't so MNG-2136
doesn't make sense for my case.
It looks like some bug. When I just mention desired profile at settings.xml:
...
Construct a sample project and a test script-- in this case just a
complete pom.xml and setti
Just realized that isn't so MNG-2136
doesn't make sense for my case.
It looks like some bug. When I just mention desired profile at settings.xml:
env-prod
env-prod
I got both as activated:
mvn help:active-profiles -Dmaven.test.skip=t
and to be clear (sorry), the build still completes ok, but the
resulting filtering is using the one derived from settings.xml, and
not the explicit profile asked for on the command line..
Paul
On 06/06/2007, at 9:56 AM, Paul Smith wrote:
mvn 2.0.4
I'm sure this is plainly my misunderstandi
Thanks for this detailled reply.
I'll have to find an alternative to profiles. Ability to activate parent-POM
profiles from a POM would be really nice as it would enable pulling up lot's
of common configuration to corporate POMs.
For now, I'll use an archetype to add all the profiles to the gene
Unfortunately, this doesn't work in Maven 2.0.x.
The reason is that the profile activator actually uses
System.getProperty( "project.target.jre" ), not project.getProperties
().getProperty( "project.target.jre" ).
It's actually a fairly involved process to check the POM for
properties duri
Thierry Lach wrote:
That might be because the activation is based on a relative pathname.
But I
tried to use the following
${basedir}/module2/pom.xml
and it doesn't work as expected.
Using ${basedir} on OSX doesn't either. The profiles don't get activated
(is that what you get on Windows?
ossi petz wrote:
hallo
what is the command line and path you used to fire up maven?
and where did you put these profiles?
The profiles are in my pom.xml file, and the command line is just plain
"mvn clean" (or any other target), after setting the MAVEN_PROXY_URL
environment variable.,
I e
hallo
what is the command line and path you used to fire up maven?
and where did you put these profiles?
Christian Goetze schrieb:
Why does this not work?
proxy
env.MAVEN_PROXY_URL
proxy
Maven proxy defined by environment
Ah-Ha! Thank you so much.
I think that is the best solution yet! Although, even better would be
if maven had an additional param on in which it meant
inherited, but not run. And then I wouldn't even have to put the
definition there. One can dream...
Thanks again,
-Ben
Brad Szabo wrot
I only use in my main pom.
I let my modules only use what I defined in my master pom.xml
On 2/27/07, Brad Szabo <[EMAIL PROTECTED]> wrote:
Have you considered using the build/pluginManagement element to define
common inheritable plugin configurations instead of using profiles?
-Brad
On Tue
Have you considered using the build/pluginManagement element to define
common inheritable plugin configurations instead of using profiles?
-Brad
On Tue, 2007-02-27 at 14:15 -0500, Ben Tatham wrote:
> basically, I have a parent pom...ie a maven project with
> pom
>
> Each of my projects use tha
do submodules have to be
subdirectories?
Yes.
Does the top-level pom module have to be able to build
on its own, because it won't in my configuration because it expects
certain directories to exist that don't exist except for in the real
projects.
No, not if there are no actual artifacts that you
basically, I have a parent pom...ie a maven project with
pom
Each of my projects use that as the .
Option one sounds interesting...do submodules have to be
subdirectories? Does the top-level pom module have to be able to build
on its own, because it won't in my configuration because it expe
Hmm. Not sure I understand.
But you can always create a master pom, and have each of your projects
create a sub module on your project that way they will always extend your
master pom.xml for everyone.
You could also mandate that each pom.xml only have access to your remote
repo not the main mave
between projects -- we don't use modules. and the projects are pretty
separate except for the build tools required.
Is it possible to make my own plugin of plugins easily...with just xml?
is there another solution for this?
-Ben
Mick Knutson wrote:
Are you trying to share plugin info betw
Are you trying to share plugin info between projects, or modules?
On 2/27/07, Ben Tatham <[EMAIL PROTECTED]> wrote:
Nope. Apparently profiles are not inherited. Excerpt from POM Reference:
The elements in the parent POM that are inherited by its children are:
* dependencies
* d
Nope. Apparently profiles are not inherited. Excerpt from POM Reference:
The elements in the parent POM that are inherited by its children are:
* dependencies
* developers and contributors
* plugin lists
* reports lists
* plugin executions with matching ids
* plugin configura
Well, I realized my first mistake. Profiles are not inherited from
poms. Uh oh. Anybody have any other ideas on how to do this?
Thanks in advance, again!
-Ben
Ben Tatham wrote:
Hello All,
I am having trouble getting a profile to activate.
My scenario is as follows...I have a complicated b
try mvn -P build-web install -e
On 2/27/07, Ben Tatham <[EMAIL PROTECTED]> wrote:
Hello All,
I am having trouble getting a profile to activate.
My scenario is as follows...I have a complicated build process for
making webapps that includes xdoclet and jspc. I have all the necessary
plugins d
Haroon Rafique <[EMAIL PROTECTED]> writes:
>
> Hi Arnaud,
>
> Thanks for the reply, but I'm positive I want environment variables and
> not system properties. From http://maven.apache.org/settings.html
>
> env.X: Prefixing a variable with "env." will return the shell's
> environment variable. For
On Today at 11:07am, AB=>Arnaud Bailly <[EMAIL PROTECTED]> wrote:
AB> [..snip..]
AB>
AB> Not sure but I think that what you call environment variables are
AB> actually system properties set on maven's cli: Try
AB>
AB>
AB>
AB> BLAH
AB> blah
AB>
AB>
AB>
AB> mvn -DBLAH=
Haroon Rafique <[EMAIL PROTECTED]> writes:
> Hi,
>
> I'm using maven 2.0.4 on a Gentoo Linux machine. Does anyone have
> experience in activating profiles based on environment variables? I
> figure using the env prefix would do the trick. So, far I have tried:
>
>
> haroon-wor
ccadete wrote:
but how can it be activated for 1.5, or better.
Vote for
http://jira.codehaus.org/browse/MNG-1910
Relatively trivial patch, but ignored since more than 7 months. :-(
Jochen
-
To unsubscribe, e-mail: [EMA
I am having the same problem.
Initially I put the profile combinations into a 'master-pom' but want to
move this definition to the global settings to eliminate a site-specific
pom. The does work at the pom/master-pom level, but I
can't make it work at the settings.xml or profiles.xml level.
An
Maybe I should clarify this a little more, seeing I didn't get any response so
far...
My build is basically looking like this:
../hermes-person-shared
../hermes-person-external-client
person
..
What is the exact use case? If you want to do something only when releasing,
you can create a profile with a predefined name (release-profile I think,
check the new m2 book to be sure) that gets activated upon release.
regards,
Wim
2006/5/2, Darren Hartford <[EMAIL PROTECTED]>:
Hey all,
I'm h
Is it ${settings.localRepository}?
-Original Message-
From: Paul Hepworth [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 23, 2006 4:43 AM
To: Maven Users List
Subject: Profile Activation
I have quite a complex project with many sub-modules. What I need to be
able to do is look in th
82 matches
Mail list logo
