I'm not specifically using any of the mentioned plugins. Do you know
if there is any built in support for groovy that could interfeer?

Alin

On Mon, Apr 21, 2008 at 12:44 PM, Stuart McCulloch
<[EMAIL PROTECTED]> wrote:
> On 18/04/2008, Alin Dreghiciu <[EMAIL PROTECTED]> wrote:
>
> > For an example you can look at "GroovyHelloWorldCompositeTest".
> >
> > I also found an "interesting" problem that I could not figure out why
> > it happened:
> > In the above test "HelloWorldSettings" has two properties: phrase and
> > name. While accessing the "phrase" from groovy everything worked fine,
> > accessing "name" was behaving different between running the test from
> > IDEA and from Maven. From idea it was returning the expected (set
> > before) value but from Maven it was returning the maven project name
> > as defined in pom.xml. I guess there was a strange interference
> > between maven groovy support and the run test. As my experience with
> > Groovy is so limited I cannot say exactly why this happen.
>
>
> if you're using the groovy-maven-plugin then it's probably automatically
> passing standard Maven properties like project.name, project.version,
> etc. to Groovy (and probably also aliasing them to name, version, etc.)
>
> afaik there isn't a way to turn this off - unless you switch to using the
> maven-antrun-plugin or the exec-maven-plugin to startup Groovy which
> would avoid the Maven specific integration...
>
> > Alin
> >
> > _______________________________________________
> > qi4j-dev mailing list
> > [email protected]
> > http://lists.ops4j.org/mailman/listinfo/qi4j-dev
> >
>
>
>
> --
> Cheers, Stuart
> _______________________________________________
>  qi4j-dev mailing list
>  [email protected]
>  http://lists.ops4j.org/mailman/listinfo/qi4j-dev
>
>

_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev

Reply via email to