Re: Property access from a plugin
Yeah,
I'm just saying what I vaguely recall from the list a couple of months back.
It's nothing to do with me and I don't even pretend to understand it ;-)
-Stephen
On Fri, Sep 12, 2008 at 4:48 AM, EJ Ciramella <[EMAIL PROTECTED]>wrote:
> This is hit or miss as well - if I do -P+base,+override, it ignores the
> activeByDefaults profiles.
>
> If I do -P+profile1 -P+profile2, then it doesn't take profile2 at all
> (so my plugin isn't activated).
>
>
>
> -Original Message-
> From: Stephen Connolly [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 11, 2008 8:02 PM
> To: Maven Users List
> Subject: Re: Property access from a plugin
>
> You need to do
>
> -P+base,+override
>
> I think
>
> On Fri, Sep 12, 2008 at 1:01 AM, Stephen Connolly <
> [EMAIL PROTECTED]> wrote:
>
> > activation on the comandline will disable any defaults.
> >
> > there is (added at some stage not sure what maven version) the ability
> to
> > add and remove with -P+otherProfile or -P-otherProfile
> >
> >
> > On Fri, Sep 12, 2008 at 12:34 AM, EJ Ciramella
> <[EMAIL PROTECTED]>wrote:
> >
> >> So with further research, if within a single pom, you have an
> >> activeByDefault plugin and one that you're activating by specifying
> an
> >> ID on the commandline, the activeByDefault one is ignored.
> >>
> >> Additionally, I set up three profiles, two of which are active by
> >> default and when you activate the third profile, the other two are
> >> deactivated.
> >>
> >> When did this change? This seems broken
> >>
> >> -Original Message-
> >> From: EJ Ciramella [mailto:[EMAIL PROTECTED]
> >> Sent: Thursday, September 11, 2008 7:03 PM
> >> To: Maven Users List
> >> Subject: RE: Property access from a plugin
> >>
> >> Can you give me an example of what you're talking about?
> >>
> >> The properties that are coming from this profile are used for
> filtering
> >> other files during process-resources. If I do a
> >> mavenProject().getProperties() the missing properties are not
> listed...
> >>
> >> The profile is truly active:
> >>
> >> System.out.println(mavenProject.getActiveProfiles());
> >>
> >> Yields:
> >>
> >> E:\work\>mvn process-resources -Dtest=asdf -Pbase,override
> >> [INFO] Scanning for projects...
> >> [INFO]
> >> -
> >> [INFO] Building Backoffice Process
> >> [INFO]task-segment: [process-resources]
> >> [INFO]
> >> -
> >> [INFO] [prop-override:override {execution: default}]
> >> [
> >> Profile {id: common-defaults, source: pom}
> >> Profile {id: base, source: settings.xml}
> >> Profile {id: proxies, source: settings.xml}
> >> Profile {id: proxies, source: settings.xml}
> >> ]
> >> [INFO] [dependency:unpack-dependencies {execution: unpack}]
> >> [INFO] lty-utils-resources-1.0.0.16.jar already exists in
> destination.
> >> [INFO] [resources:resources]
> >> [INFO] Using default encoding to copy filtered resources.
> >> [INFO] [antrun:run {execution: default}]
> >> [INFO] Executing tasks
> >> [INFO] Executed tasks
> >> [INFO]
> >> -
> >> [INFO] BUILD SUCCESSFUL
> >> [INFO]
> >> -
> >> [INFO] Total time: 9 seconds
> >> [INFO] Finished at: Thu Sep 11 18:42:39 EDT 2008
> >> [INFO] Final Memory: 13M/26M
> >> [INFO]
> >> -
> >>
> >> Additionally, in the commandline specified above, do you notice the
> >> -Pbase,override?
> >>
> >> Base is a profile in my settings.xml, override is in the pom at the
> root
> >> of the project (the parent pom). Override is a plugin INSIDE a
> profile.
> >> Common-defaults is also a profile inside the root level pom (override
> >> and common-defaults are right next to each other) - where to activate
> >> override, you have to either specify -Doverride or -Poverride and
> >> common-defaults is activeByDefault - why would activating manually
> ONE
> >> profile deactivate another one? Maven shows it's active (see my
Re: Property access from a plugin
On Thu, Sep 11, 2008 at 4:34 PM, EJ Ciramella <[EMAIL PROTECTED]> wrote: > So with further research, if within a single pom, you have an > activeByDefault plugin and one that you're activating by specifying an > ID on the commandline, the activeByDefault one is ignored. Correct. Unless something has changed recently, (and I do rememeber some discussion...) activeByDefault means "active if no other profiles are explicitly activated". AIUI, it was meant for the simple case of activating exactly one of a set of profiles. In practice I haven't found it to be very useful, I usually have more than one set of profiles. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Property access from a plugin
This is hit or miss as well - if I do -P+base,+override, it ignores the
activeByDefaults profiles.
If I do -P+profile1 -P+profile2, then it doesn't take profile2 at all
(so my plugin isn't activated).
-Original Message-
From: Stephen Connolly [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 11, 2008 8:02 PM
To: Maven Users List
Subject: Re: Property access from a plugin
You need to do
-P+base,+override
I think
On Fri, Sep 12, 2008 at 1:01 AM, Stephen Connolly <
[EMAIL PROTECTED]> wrote:
> activation on the comandline will disable any defaults.
>
> there is (added at some stage not sure what maven version) the ability
to
> add and remove with -P+otherProfile or -P-otherProfile
>
>
> On Fri, Sep 12, 2008 at 12:34 AM, EJ Ciramella
<[EMAIL PROTECTED]>wrote:
>
>> So with further research, if within a single pom, you have an
>> activeByDefault plugin and one that you're activating by specifying
an
>> ID on the commandline, the activeByDefault one is ignored.
>>
>> Additionally, I set up three profiles, two of which are active by
>> default and when you activate the third profile, the other two are
>> deactivated.
>>
>> When did this change? This seems broken
>>
>> -Original Message-
>> From: EJ Ciramella [mailto:[EMAIL PROTECTED]
>> Sent: Thursday, September 11, 2008 7:03 PM
>> To: Maven Users List
>> Subject: RE: Property access from a plugin
>>
>> Can you give me an example of what you're talking about?
>>
>> The properties that are coming from this profile are used for
filtering
>> other files during process-resources. If I do a
>> mavenProject().getProperties() the missing properties are not
listed...
>>
>> The profile is truly active:
>>
>> System.out.println(mavenProject.getActiveProfiles());
>>
>> Yields:
>>
>> E:\work\>mvn process-resources -Dtest=asdf -Pbase,override
>> [INFO] Scanning for projects...
>> [INFO]
>> -
>> [INFO] Building Backoffice Process
>> [INFO]task-segment: [process-resources]
>> [INFO]
>> -
>> [INFO] [prop-override:override {execution: default}]
>> [
>> Profile {id: common-defaults, source: pom}
>> Profile {id: base, source: settings.xml}
>> Profile {id: proxies, source: settings.xml}
>> Profile {id: proxies, source: settings.xml}
>> ]
>> [INFO] [dependency:unpack-dependencies {execution: unpack}]
>> [INFO] lty-utils-resources-1.0.0.16.jar already exists in
destination.
>> [INFO] [resources:resources]
>> [INFO] Using default encoding to copy filtered resources.
>> [INFO] [antrun:run {execution: default}]
>> [INFO] Executing tasks
>> [INFO] Executed tasks
>> [INFO]
>> -
>> [INFO] BUILD SUCCESSFUL
>> [INFO]
>> -
>> [INFO] Total time: 9 seconds
>> [INFO] Finished at: Thu Sep 11 18:42:39 EDT 2008
>> [INFO] Final Memory: 13M/26M
>> [INFO]
>> -
>>
>> Additionally, in the commandline specified above, do you notice the
>> -Pbase,override?
>>
>> Base is a profile in my settings.xml, override is in the pom at the
root
>> of the project (the parent pom). Override is a plugin INSIDE a
profile.
>> Common-defaults is also a profile inside the root level pom (override
>> and common-defaults are right next to each other) - where to activate
>> override, you have to either specify -Doverride or -Poverride and
>> common-defaults is activeByDefault - why would activating manually
ONE
>> profile deactivate another one? Maven shows it's active (see my
snippet
>> above), but it's truly NOT putting the properties stored in it into
>> play.
>>
>> -Original Message-
>> From: Stephen Connolly [mailto:[EMAIL PROTECTED]
>> Sent: Thursday, September 11, 2008 6:39 PM
>> To: Maven Users List
>> Subject: Re: Property access from a plugin
>>
>> On Thu, Sep 11, 2008 at 11:33 PM, EJ Ciramella
>> <[EMAIL PROTECTED]>wrote:
>>
>> > So what's happening is, I'm activating a few profiles, yet the
>> > properties that are missing are set in an
profile.
>> It
>> > appears that the profile is either not activated
or
>> > ignored.
>> >
>> > If I turn on this profile (along with my other profiles), the
&g
RE: Property access from a plugin
That's simply not true -
If you have:
Parent pom -> child pom
Both have a profile called "props" and both are active by default, when
you enable a different profile in the parent pom, the child version
(because it is active by default) still turns on and makes its
properties available.
There's just no consistency - if -P truly deactivates "activeByDefault"
then shouldn't it do that everywhere?
Since when did the -P+/- stuff get added? I can see the
-Pprofile1,profile2 work with 2.0.5 properly.
-Original Message-
From: Stephen Connolly [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 11, 2008 8:01 PM
To: Maven Users List
Subject: Re: Property access from a plugin
activation on the comandline will disable any defaults.
there is (added at some stage not sure what maven version) the ability
to
add and remove with -P+otherProfile or -P-otherProfile
On Fri, Sep 12, 2008 at 12:34 AM, EJ Ciramella
<[EMAIL PROTECTED]>wrote:
> So with further research, if within a single pom, you have an
> activeByDefault plugin and one that you're activating by specifying an
> ID on the commandline, the activeByDefault one is ignored.
>
> Additionally, I set up three profiles, two of which are active by
> default and when you activate the third profile, the other two are
> deactivated.
>
> When did this change? This seems broken
>
> -Original Message-
> From: EJ Ciramella [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 11, 2008 7:03 PM
> To: Maven Users List
> Subject: RE: Property access from a plugin
>
> Can you give me an example of what you're talking about?
>
> The properties that are coming from this profile are used for
filtering
> other files during process-resources. If I do a
> mavenProject().getProperties() the missing properties are not
listed...
>
> The profile is truly active:
>
> System.out.println(mavenProject.getActiveProfiles());
>
> Yields:
>
> E:\work\>mvn process-resources -Dtest=asdf -Pbase,override
> [INFO] Scanning for projects...
> [INFO]
> -
> [INFO] Building Backoffice Process
> [INFO]task-segment: [process-resources]
> [INFO]
> -
> [INFO] [prop-override:override {execution: default}]
> [
> Profile {id: common-defaults, source: pom}
> Profile {id: base, source: settings.xml}
> Profile {id: proxies, source: settings.xml}
> Profile {id: proxies, source: settings.xml}
> ]
> [INFO] [dependency:unpack-dependencies {execution: unpack}]
> [INFO] lty-utils-resources-1.0.0.16.jar already exists in destination.
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [antrun:run {execution: default}]
> [INFO] Executing tasks
> [INFO] Executed tasks
> [INFO]
> -
> [INFO] BUILD SUCCESSFUL
> [INFO]
> -
> [INFO] Total time: 9 seconds
> [INFO] Finished at: Thu Sep 11 18:42:39 EDT 2008
> [INFO] Final Memory: 13M/26M
> [INFO]
> -
>
> Additionally, in the commandline specified above, do you notice the
> -Pbase,override?
>
> Base is a profile in my settings.xml, override is in the pom at the
root
> of the project (the parent pom). Override is a plugin INSIDE a
profile.
> Common-defaults is also a profile inside the root level pom (override
> and common-defaults are right next to each other) - where to activate
> override, you have to either specify -Doverride or -Poverride and
> common-defaults is activeByDefault - why would activating manually ONE
> profile deactivate another one? Maven shows it's active (see my
snippet
> above), but it's truly NOT putting the properties stored in it into
> play.
>
> -Original Message-
> From: Stephen Connolly [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 11, 2008 6:39 PM
> To: Maven Users List
> Subject: Re: Property access from a plugin
>
> On Thu, Sep 11, 2008 at 11:33 PM, EJ Ciramella
> <[EMAIL PROTECTED]>wrote:
>
> > So what's happening is, I'm activating a few profiles, yet the
> > properties that are missing are set in an profile.
> It
> > appears that the profile is either not activated
or
> > ignored.
> >
> > If I turn on this profile (along with my other profiles), the
> properties
> > are expanded properly.
> >
> > My plugin is simply loading some properties from a property file and
> > pushing them into the mavenProject property listing.
Re: Property access from a plugin
You need to do
-P+base,+override
I think
On Fri, Sep 12, 2008 at 1:01 AM, Stephen Connolly <
[EMAIL PROTECTED]> wrote:
> activation on the comandline will disable any defaults.
>
> there is (added at some stage not sure what maven version) the ability to
> add and remove with -P+otherProfile or -P-otherProfile
>
>
> On Fri, Sep 12, 2008 at 12:34 AM, EJ Ciramella <[EMAIL PROTECTED]>wrote:
>
>> So with further research, if within a single pom, you have an
>> activeByDefault plugin and one that you're activating by specifying an
>> ID on the commandline, the activeByDefault one is ignored.
>>
>> Additionally, I set up three profiles, two of which are active by
>> default and when you activate the third profile, the other two are
>> deactivated.
>>
>> When did this change? This seems broken
>>
>> -Original Message-
>> From: EJ Ciramella [mailto:[EMAIL PROTECTED]
>> Sent: Thursday, September 11, 2008 7:03 PM
>> To: Maven Users List
>> Subject: RE: Property access from a plugin
>>
>> Can you give me an example of what you're talking about?
>>
>> The properties that are coming from this profile are used for filtering
>> other files during process-resources. If I do a
>> mavenProject().getProperties() the missing properties are not listed...
>>
>> The profile is truly active:
>>
>> System.out.println(mavenProject.getActiveProfiles());
>>
>> Yields:
>>
>> E:\work\>mvn process-resources -Dtest=asdf -Pbase,override
>> [INFO] Scanning for projects...
>> [INFO]
>> -
>> [INFO] Building Backoffice Process
>> [INFO]task-segment: [process-resources]
>> [INFO]
>> -
>> [INFO] [prop-override:override {execution: default}]
>> [
>> Profile {id: common-defaults, source: pom}
>> Profile {id: base, source: settings.xml}
>> Profile {id: proxies, source: settings.xml}
>> Profile {id: proxies, source: settings.xml}
>> ]
>> [INFO] [dependency:unpack-dependencies {execution: unpack}]
>> [INFO] lty-utils-resources-1.0.0.16.jar already exists in destination.
>> [INFO] [resources:resources]
>> [INFO] Using default encoding to copy filtered resources.
>> [INFO] [antrun:run {execution: default}]
>> [INFO] Executing tasks
>> [INFO] Executed tasks
>> [INFO]
>> -
>> [INFO] BUILD SUCCESSFUL
>> [INFO]
>> -
>> [INFO] Total time: 9 seconds
>> [INFO] Finished at: Thu Sep 11 18:42:39 EDT 2008
>> [INFO] Final Memory: 13M/26M
>> [INFO]
>> -
>>
>> Additionally, in the commandline specified above, do you notice the
>> -Pbase,override?
>>
>> Base is a profile in my settings.xml, override is in the pom at the root
>> of the project (the parent pom). Override is a plugin INSIDE a profile.
>> Common-defaults is also a profile inside the root level pom (override
>> and common-defaults are right next to each other) - where to activate
>> override, you have to either specify -Doverride or -Poverride and
>> common-defaults is activeByDefault - why would activating manually ONE
>> profile deactivate another one? Maven shows it's active (see my snippet
>> above), but it's truly NOT putting the properties stored in it into
>> play.
>>
>> -Original Message-
>> From: Stephen Connolly [mailto:[EMAIL PROTECTED]
>> Sent: Thursday, September 11, 2008 6:39 PM
>> To: Maven Users List
>> Subject: Re: Property access from a plugin
>>
>> On Thu, Sep 11, 2008 at 11:33 PM, EJ Ciramella
>> <[EMAIL PROTECTED]>wrote:
>>
>> > So what's happening is, I'm activating a few profiles, yet the
>> > properties that are missing are set in an profile.
>> It
>> > appears that the profile is either not activated or
>> > ignored.
>> >
>> > If I turn on this profile (along with my other profiles), the
>> properties
>> > are expanded properly.
>> >
>> > My plugin is simply loading some properties from a property file and
>> > pushing them into the mavenProject property listing.
>> >
>> > So two questions:
>> >
>> > 1 - do I need to do anything special to load all the properties
>> defined
>> > in any activ
Re: Property access from a plugin
activation on the comandline will disable any defaults.
there is (added at some stage not sure what maven version) the ability to
add and remove with -P+otherProfile or -P-otherProfile
On Fri, Sep 12, 2008 at 12:34 AM, EJ Ciramella <[EMAIL PROTECTED]>wrote:
> So with further research, if within a single pom, you have an
> activeByDefault plugin and one that you're activating by specifying an
> ID on the commandline, the activeByDefault one is ignored.
>
> Additionally, I set up three profiles, two of which are active by
> default and when you activate the third profile, the other two are
> deactivated.
>
> When did this change? This seems broken
>
> -Original Message-
> From: EJ Ciramella [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 11, 2008 7:03 PM
> To: Maven Users List
> Subject: RE: Property access from a plugin
>
> Can you give me an example of what you're talking about?
>
> The properties that are coming from this profile are used for filtering
> other files during process-resources. If I do a
> mavenProject().getProperties() the missing properties are not listed...
>
> The profile is truly active:
>
> System.out.println(mavenProject.getActiveProfiles());
>
> Yields:
>
> E:\work\>mvn process-resources -Dtest=asdf -Pbase,override
> [INFO] Scanning for projects...
> [INFO]
> -
> [INFO] Building Backoffice Process
> [INFO]task-segment: [process-resources]
> [INFO]
> -
> [INFO] [prop-override:override {execution: default}]
> [
> Profile {id: common-defaults, source: pom}
> Profile {id: base, source: settings.xml}
> Profile {id: proxies, source: settings.xml}
> Profile {id: proxies, source: settings.xml}
> ]
> [INFO] [dependency:unpack-dependencies {execution: unpack}]
> [INFO] lty-utils-resources-1.0.0.16.jar already exists in destination.
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [antrun:run {execution: default}]
> [INFO] Executing tasks
> [INFO] Executed tasks
> [INFO]
> -
> [INFO] BUILD SUCCESSFUL
> [INFO]
> -
> [INFO] Total time: 9 seconds
> [INFO] Finished at: Thu Sep 11 18:42:39 EDT 2008
> [INFO] Final Memory: 13M/26M
> [INFO]
> -
>
> Additionally, in the commandline specified above, do you notice the
> -Pbase,override?
>
> Base is a profile in my settings.xml, override is in the pom at the root
> of the project (the parent pom). Override is a plugin INSIDE a profile.
> Common-defaults is also a profile inside the root level pom (override
> and common-defaults are right next to each other) - where to activate
> override, you have to either specify -Doverride or -Poverride and
> common-defaults is activeByDefault - why would activating manually ONE
> profile deactivate another one? Maven shows it's active (see my snippet
> above), but it's truly NOT putting the properties stored in it into
> play.
>
> -Original Message-
> From: Stephen Connolly [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 11, 2008 6:39 PM
> To: Maven Users List
> Subject: Re: Property access from a plugin
>
> On Thu, Sep 11, 2008 at 11:33 PM, EJ Ciramella
> <[EMAIL PROTECTED]>wrote:
>
> > So what's happening is, I'm activating a few profiles, yet the
> > properties that are missing are set in an profile.
> It
> > appears that the profile is either not activated or
> > ignored.
> >
> > If I turn on this profile (along with my other profiles), the
> properties
> > are expanded properly.
> >
> > My plugin is simply loading some properties from a property file and
> > pushing them into the mavenProject property listing.
> >
> > So two questions:
> >
> > 1 - do I need to do anything special to load all the properties
> defined
> > in any activeByDefault profiles?
> >
> > 2 - What lifecycle goal should I bind my plugin to?
> >
>
> The earliest possible phase (validate AFAIK)
>
> Note that any properties that are required _while_ building the model
> cannot
> be supplied by your plugin as your plugin will only run after the model
> has
> been constructed... making your plugin less useful than you'd think in
> most
> cases
>
>
> >
> > -Original Message-
> > From: EJ Ciramella [mailto:[EMAIL PROTECTED]
> > Sent: T
RE: Property access from a plugin
So with further research, if within a single pom, you have an
activeByDefault plugin and one that you're activating by specifying an
ID on the commandline, the activeByDefault one is ignored.
Additionally, I set up three profiles, two of which are active by
default and when you activate the third profile, the other two are
deactivated.
When did this change? This seems broken
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 11, 2008 7:03 PM
To: Maven Users List
Subject: RE: Property access from a plugin
Can you give me an example of what you're talking about?
The properties that are coming from this profile are used for filtering
other files during process-resources. If I do a
mavenProject().getProperties() the missing properties are not listed...
The profile is truly active:
System.out.println(mavenProject.getActiveProfiles());
Yields:
E:\work\>mvn process-resources -Dtest=asdf -Pbase,override
[INFO] Scanning for projects...
[INFO]
-
[INFO] Building Backoffice Process
[INFO]task-segment: [process-resources]
[INFO]
-
[INFO] [prop-override:override {execution: default}]
[
Profile {id: common-defaults, source: pom}
Profile {id: base, source: settings.xml}
Profile {id: proxies, source: settings.xml}
Profile {id: proxies, source: settings.xml}
]
[INFO] [dependency:unpack-dependencies {execution: unpack}]
[INFO] lty-utils-resources-1.0.0.16.jar already exists in destination.
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[INFO] Executed tasks
[INFO]
-
[INFO] BUILD SUCCESSFUL
[INFO]
-
[INFO] Total time: 9 seconds
[INFO] Finished at: Thu Sep 11 18:42:39 EDT 2008
[INFO] Final Memory: 13M/26M
[INFO]
-
Additionally, in the commandline specified above, do you notice the
-Pbase,override?
Base is a profile in my settings.xml, override is in the pom at the root
of the project (the parent pom). Override is a plugin INSIDE a profile.
Common-defaults is also a profile inside the root level pom (override
and common-defaults are right next to each other) - where to activate
override, you have to either specify -Doverride or -Poverride and
common-defaults is activeByDefault - why would activating manually ONE
profile deactivate another one? Maven shows it's active (see my snippet
above), but it's truly NOT putting the properties stored in it into
play.
-Original Message-
From: Stephen Connolly [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 11, 2008 6:39 PM
To: Maven Users List
Subject: Re: Property access from a plugin
On Thu, Sep 11, 2008 at 11:33 PM, EJ Ciramella
<[EMAIL PROTECTED]>wrote:
> So what's happening is, I'm activating a few profiles, yet the
> properties that are missing are set in an profile.
It
> appears that the profile is either not activated or
> ignored.
>
> If I turn on this profile (along with my other profiles), the
properties
> are expanded properly.
>
> My plugin is simply loading some properties from a property file and
> pushing them into the mavenProject property listing.
>
> So two questions:
>
> 1 - do I need to do anything special to load all the properties
defined
> in any activeByDefault profiles?
>
> 2 - What lifecycle goal should I bind my plugin to?
>
The earliest possible phase (validate AFAIK)
Note that any properties that are required _while_ building the model
cannot
be supplied by your plugin as your plugin will only run after the model
has
been constructed... making your plugin less useful than you'd think in
most
cases
>
> -Original Message-
> From: EJ Ciramella [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 11, 2008 5:05 PM
> To: users@maven.apache.org
> Subject: Property access from a plugin
>
> If you have a set of properties set within a profile that is active by
> default, programmatically, how do you access them?
>
>
>
> If I do help:effective-pom, I can see that they are set and if I do
> help:active-profiles, I can see the profile is also active, just when
I
> list the properties, the are not set.
>
>
>
> My plugin is defined as an aggregate plugin bound to process-sources
(so
> POST initialize).
>
>
>
> mavenProject.getProperties() shows them as unset, any suggestions?
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail:
RE: Property access from a plugin
Can you give me an example of what you're talking about?
The properties that are coming from this profile are used for filtering
other files during process-resources. If I do a
mavenProject().getProperties() the missing properties are not listed...
The profile is truly active:
System.out.println(mavenProject.getActiveProfiles());
Yields:
E:\work\>mvn process-resources -Dtest=asdf -Pbase,override
[INFO] Scanning for projects...
[INFO]
-
[INFO] Building Backoffice Process
[INFO]task-segment: [process-resources]
[INFO]
-
[INFO] [prop-override:override {execution: default}]
[
Profile {id: common-defaults, source: pom}
Profile {id: base, source: settings.xml}
Profile {id: proxies, source: settings.xml}
Profile {id: proxies, source: settings.xml}
]
[INFO] [dependency:unpack-dependencies {execution: unpack}]
[INFO] lty-utils-resources-1.0.0.16.jar already exists in destination.
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[INFO] Executed tasks
[INFO]
-
[INFO] BUILD SUCCESSFUL
[INFO]
-
[INFO] Total time: 9 seconds
[INFO] Finished at: Thu Sep 11 18:42:39 EDT 2008
[INFO] Final Memory: 13M/26M
[INFO]
-
Additionally, in the commandline specified above, do you notice the
-Pbase,override?
Base is a profile in my settings.xml, override is in the pom at the root
of the project (the parent pom). Override is a plugin INSIDE a profile.
Common-defaults is also a profile inside the root level pom (override
and common-defaults are right next to each other) - where to activate
override, you have to either specify -Doverride or -Poverride and
common-defaults is activeByDefault - why would activating manually ONE
profile deactivate another one? Maven shows it's active (see my snippet
above), but it's truly NOT putting the properties stored in it into
play.
-Original Message-
From: Stephen Connolly [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 11, 2008 6:39 PM
To: Maven Users List
Subject: Re: Property access from a plugin
On Thu, Sep 11, 2008 at 11:33 PM, EJ Ciramella
<[EMAIL PROTECTED]>wrote:
> So what's happening is, I'm activating a few profiles, yet the
> properties that are missing are set in an profile.
It
> appears that the profile is either not activated or
> ignored.
>
> If I turn on this profile (along with my other profiles), the
properties
> are expanded properly.
>
> My plugin is simply loading some properties from a property file and
> pushing them into the mavenProject property listing.
>
> So two questions:
>
> 1 - do I need to do anything special to load all the properties
defined
> in any activeByDefault profiles?
>
> 2 - What lifecycle goal should I bind my plugin to?
>
The earliest possible phase (validate AFAIK)
Note that any properties that are required _while_ building the model
cannot
be supplied by your plugin as your plugin will only run after the model
has
been constructed... making your plugin less useful than you'd think in
most
cases
>
> -Original Message-
> From: EJ Ciramella [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 11, 2008 5:05 PM
> To: users@maven.apache.org
> Subject: Property access from a plugin
>
> If you have a set of properties set within a profile that is active by
> default, programmatically, how do you access them?
>
>
>
> If I do help:effective-pom, I can see that they are set and if I do
> help:active-profiles, I can see the profile is also active, just when
I
> list the properties, the are not set.
>
>
>
> My plugin is defined as an aggregate plugin bound to process-sources
(so
> POST initialize).
>
>
>
> mavenProject.getProperties() shows them as unset, any suggestions?
>
>
> -
> 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]
Re: Property access from a plugin
On Thu, Sep 11, 2008 at 11:33 PM, EJ Ciramella <[EMAIL PROTECTED]>wrote: > So what's happening is, I'm activating a few profiles, yet the > properties that are missing are set in an profile. It > appears that the profile is either not activated or > ignored. > > If I turn on this profile (along with my other profiles), the properties > are expanded properly. > > My plugin is simply loading some properties from a property file and > pushing them into the mavenProject property listing. > > So two questions: > > 1 - do I need to do anything special to load all the properties defined > in any activeByDefault profiles? > > 2 - What lifecycle goal should I bind my plugin to? > The earliest possible phase (validate AFAIK) Note that any properties that are required _while_ building the model cannot be supplied by your plugin as your plugin will only run after the model has been constructed... making your plugin less useful than you'd think in most cases > > -Original Message- > From: EJ Ciramella [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 11, 2008 5:05 PM > To: users@maven.apache.org > Subject: Property access from a plugin > > If you have a set of properties set within a profile that is active by > default, programmatically, how do you access them? > > > > If I do help:effective-pom, I can see that they are set and if I do > help:active-profiles, I can see the profile is also active, just when I > list the properties, the are not set. > > > > My plugin is defined as an aggregate plugin bound to process-sources (so > POST initialize). > > > > mavenProject.getProperties() shows them as unset, any suggestions? > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
RE: Property access from a plugin
So what's happening is, I'm activating a few profiles, yet the properties that are missing are set in an profile. It appears that the profile is either not activated or ignored. If I turn on this profile (along with my other profiles), the properties are expanded properly. My plugin is simply loading some properties from a property file and pushing them into the mavenProject property listing. So two questions: 1 - do I need to do anything special to load all the properties defined in any activeByDefault profiles? 2 - What lifecycle goal should I bind my plugin to? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, September 11, 2008 5:05 PM To: users@maven.apache.org Subject: Property access from a plugin If you have a set of properties set within a profile that is active by default, programmatically, how do you access them? If I do help:effective-pom, I can see that they are set and if I do help:active-profiles, I can see the profile is also active, just when I list the properties, the are not set. My plugin is defined as an aggregate plugin bound to process-sources (so POST initialize). mavenProject.getProperties() shows them as unset, any suggestions? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Property access from a plugin
If you have a set of properties set within a profile that is active by default, programmatically, how do you access them? If I do help:effective-pom, I can see that they are set and if I do help:active-profiles, I can see the profile is also active, just when I list the properties, the are not set. My plugin is defined as an aggregate plugin bound to process-sources (so POST initialize). mavenProject.getProperties() shows them as unset, any suggestions?
