Ah yes, when the resources are processed, there are some scripts that
have ${some.property} in them.This all works flawlessly when some.property has been set, but if this particular profile is activated and it has NOT been set, then this doesn't work. Again, we see this in an environment where we're building from the child pom level (and there is a parent and a parent of a parent further up the tree). -----Original Message----- From: Brian E. Fox [mailto:[EMAIL PROTECTED] Sent: Thursday, May 15, 2008 11:22 AM To: Maven Users List Subject: RE: Bug in maven 2 - Ok, but how is ${some.property} used in your poms? Presumably you are setting it for a reason ;-) -----Original Message----- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, May 15, 2008 10:38 AM To: Maven Users List Subject: RE: Bug in maven 2 - Shoot - sorry, the property used to activate the profile has no relation, I was just typing fast. It could have looked like this instead: <profile> <id>_id_name</id> <activation> <property> <name>property_used_to_activate_this_profile</name> </property> </activation> <build> <resources> <resource> </resource> </resources> </build> <properties> <some.property>${other.value}</some.property> </properties> </profile> -----Original Message----- From: Brian E. Fox [mailto:[EMAIL PROTECTED] Sent: Thursday, May 15, 2008 9:04 AM To: Maven Users List Subject: RE: Bug in maven 2 - Is some_property the same as some.property below? (ie are you redefining it?) How are you using the property that isn't being set? -----Original Message----- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 14, 2008 4:28 PM To: Maven Users List Subject: RE: Bug in maven 2 - I can't really send along a pom, but I can describe things in a bit more detail... 1 - The pom with the property in it is three poms deep (there is a grandparent) 2 - We're running at the child node level 3 - we're activating a profile within this child pom that looks like this: <profile> <id>_id_name</id> <activation> <property> <name>some_property</name> </property> </activation> <build> <resources> <resource> </resource> </resources> </build> <properties> <some.property>${other.value}</some.property> </properties> </profile> If ${some.property} hasn't been set, then the build hangs and scans for projects. -----Original Message----- From: Brian Fox [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 14, 2008 2:32 PM To: Maven Users List Subject: Re: Bug in maven 2 - How are you using these properties? A copy of your PIM would help. Maven shouldn't hang, especially on an undefined property... It just goes through un-interpolated --Brian On May 14, 2008, at 1:44 PM, "EJ Ciramella" <[EMAIL PROTECTED]> wrote: > A colleague and I have found some strange behavior with the way > properties are expanded and how m2 works. > > We've seen it such that if a property is undefined and you've > activated > a profile that has build segments and this undefined property, maven > hangs just scanning for projects. > > I couldn't find a similar bug in jira for this, has anyone else seen > this? > --------------------------------------------------------------------- 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] --------------------------------------------------------------------- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
