I'll assume this is a regression in the latest 2.2-beta-2-SNAPSHOT.
http://jira.codehaus.org/browse/MASSEMBLY-256
On Nov 28, 2007 12:45 PM, Mark Reynolds <[EMAIL PROTECTED]>
wrote:
> That wasn't it, but thanks.
>
>
> On Nov 27, 2007 12:36 PM, Wayne Fay <[EMAIL PROTECTED]> wrote:
>
> > I've seen
That wasn't it, but thanks.
On Nov 27, 2007 12:36 PM, Wayne Fay <[EMAIL PROTECTED]> wrote:
> I've seen that mentioned on this list a couple times, and I generally
> use this notation myself as well for no particular reason.
>
> Wayne
>
> On 11/27/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> >
I've seen that mentioned on this list a couple times, and I generally
use this notation myself as well for no particular reason.
Wayne
On 11/27/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> Some time back I encountered a problem with properties in the pom using
> a dot-notation. I solved that
Some time back I encountered a problem with properties in the pom using
a dot-notation. I solved that by using camelHump-notation instead. In
your case that would mean replacing "my.path" with "myPath". Not sure if
it will work in this case, but it's worth a try.
Mark Reynolds wrote:
I was us
I was using maven-assembly-plugin 2.2-SNAPSHOT and tried to switch to
2.2-beta-2-SNAPSHOT but encountered a problem.
I reference properties from my pom in the assembly descriptor, like this:
...
myapp/WEB-INF
..
...
${basedir}/target/config/somefile.conf
$