I have seen this syntax used in many plugins, and I also do not get it to work. Seems like Jelly has a problem with the periods in the variable names? To test if the pom id is empty, for example, I have to do the following
<!-- check that required information is there --> <j:set var="pomCurrentVersion" value="${pom.currentVersion}"/> <j:if test="${empty(pomCurrentVersion)}"> <ant:fail>You must define currentVersion in your POM.</ant:fail> </j:if> The test on pomp.currentVersion (${empty(pom.currentVersion)}) does not work. - Will > ----- Message from [EMAIL PROTECTED] on Fri, 16 Jul 2004 13:26: > 32 -0400 ----- > > To: > > "Maven Users List" <[EMAIL PROTECTED]> > > Subject: > > Re: Problems with if tests in plugins > > I've come across at least 2 plugins with the constructs I've documented > (jetspeed and torque). The question is, did they ever work as written? Is > it possible that they were simply never tested? > > Making the change you suggest works, as well as renaming > maven.jetspeed.debug to maven_jetspeed_debug. However, this isn't a > workable solution because I didn't write the plugins in question. > > Can anyone clarify the situation? Did the original expression work in the > past, and the plugin hasn't been updated? Or is something else going on > here? > > > > > > Jagadeesh Danala <[EMAIL PROTECTED]> > 07/16/2004 01:11 PM > Please respond to "Maven Users List" > > > To: Maven Users List <[EMAIL PROTECTED]> > cc: > Subject: Re: Problems with if tests in plugins > > > Hi > > The problem is with your expression > > <j:if test ="${maven.jetspeed.debug}"> should work if the value of the > property is set to true. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]