On 16 Jun 07, at 11:37 AM 16 Jun 07, Kenney Westerhof wrote:
Jason van Zyl wrote:
On 16 Jun 07, at 9:57 AM 16 Jun 07, Kenney Westerhof wrote:
So before I write something down that's more to the point than an
enumeration of
the flaws in the current implementation and the problems it gives
Jason van Zyl wrote:
On 16 Jun 07, at 9:57 AM 16 Jun 07, Kenney Westerhof wrote:
So before I write something down that's more to the point than an
enumeration of
the flaws in the current implementation and the problems it gives us,
I'd like to
get concensus about the proper way to do it.
On 16 Jun 07, at 9:57 AM 16 Jun 07, Kenney Westerhof wrote:
So before I write something down that's more to the point than an
enumeration of
the flaws in the current implementation and the problems it gives
us, I'd like to
get concensus about the proper way to do it..
People won't pay a
Jason van Zyl wrote:
On 16 Jun 07, at 1:18 AM 16 Jun 07, Kenney Westerhof wrote:
Hi,
where's the spec for this?
I'm working on MNG-2651 and similar, and I'm a bit at a loss as how to
proceed.
What does the 'env.' prefix do? System props, env props, or project
props?
Should 'pom.' be
On 16 Jun 07, at 1:18 AM 16 Jun 07, Kenney Westerhof wrote:
Hi,
where's the spec for this?
I'm working on MNG-2651 and similar, and I'm a bit at a loss as how
to proceed.
What does the 'env.' prefix do? System props, env props, or project
props?
Should 'pom.' be the same as 'project.'
Hi,
where's the spec for this?
I'm working on MNG-2651 and similar, and I'm a bit at a loss as how to proceed.
What does the 'env.' prefix do? System props, env props, or project props?
Should 'pom.' be the same as 'project.' or should one use the Model
and the other MavenProject?
If someone
