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]
