Yeah that would settle this once and for all ;)
Except you probably have to be able to specify the delimiters per
resource set sigh.
John Casey wrote:
I've seen several unix commands that allow configurable
delimiters...maybe that would be a better option?
-john
On Jul 10, 2007, at 12:5
I've seen several unix commands that allow configurable
delimiters...maybe that would be a better option?
-john
On Jul 10, 2007, at 12:55 PM, Kenney Westerhof wrote:
Daniel Kulp wrote:
Personally, I was thinking of just doing $$ -> $.
Yah, that's already in place for plugin parameters.
Daniel Kulp wrote:
Personally, I was thinking of just doing $$ -> $.
Yah, that's already in place for plugin parameters.
Thus, if you want ${pom.version} outputted, it would be $${pom.version}.
I think @@ also needs to be done.
Yup.
My original idea was to use both by default but allow
Personally, I was thinking of just doing $$ -> $.
Thus, if you want ${pom.version} outputted, it would be $${pom.version}.
I think @@ also needs to be done.
Dan
On Tuesday 10 July 2007 12:05, John Casey wrote:
> Yeah, escaping makes more sense to me, too. IMO it's a bit of a duct-
> tape sol
Yeah, escaping makes more sense to me, too. IMO it's a bit of a duct-
tape solution to say this is only applicable in {archetype,
appserver, other-limited-effect-plugins...} when those are the
examples given... People can use filtering for just about anything,
and they may use the '${...}' f
It's not just archetype - this has come up in appserver too, where
you need some properties in a file escaped and others left.
I suspect adding escape handling to the InterpolationFilterReader
might be a good way to go.
Andy
On 10 Jul 2007, at 11:35, Kenney Westerhof wrote:
Daniel Kulp w
What about choosing the sources of property whose be filtering? So we
can have an way to escape properties
For example, in the pom.xml:
MavenProject
pom.version
Daniel Kulp wrote:
On Monday 09 July 2007 19:08, Kenney Westerhof wrote:
Daniel Kulp wrote:
On Monday 09 July 2007 14:42, Kenney Westerhof wrote:
Daniel Kulp wrote:
Yep. That's the #1 issue.I've completely given up on trying to
get the string "${pom.version}" outputted into the file.
On Monday 09 July 2007 19:08, Kenney Westerhof wrote:
> Daniel Kulp wrote:
> > On Monday 09 July 2007 14:42, Kenney Westerhof wrote:
> >> Daniel Kulp wrote:
> > Yep. That's the #1 issue.I've completely given up on trying to
> > get the string "${pom.version}" outputted into the file.
>
> Ok,
Daniel Kulp wrote:
On Monday 09 July 2007 14:42, Kenney Westerhof wrote:
Daniel Kulp wrote:
After battling with the braindead resource filtering once again for
the ump-teenth time, I've decided I need to do something about
it
You dissin' my code huh? :)
The main thing I'd like to do is
On Monday 09 July 2007 14:42, Kenney Westerhof wrote:
> Daniel Kulp wrote:
> > After battling with the braindead resource filtering once again for
> > the ump-teenth time, I've decided I need to do something about
> > it
>
> You dissin' my code huh? :)
>
> > The main thing I'd like to do is all
Daniel Kulp wrote:
After battling with the braindead resource filtering once again for the
ump-teenth time, I've decided I need to do something about it
You dissin' my code huh? :)
The main thing I'd like to do is allow use of a better filter engine
(like velocity) that would provid
After battling with the braindead resource filtering once again for the
ump-teenth time, I've decided I need to do something about it
The main thing I'd like to do is allow use of a better filter engine
(like velocity) that would provide much more flexibility. The issue is
how to do i
13 matches
Mail list logo
