[ http://jira.codehaus.org/browse/MPGENAPP-24?page=comments#action_49258 ] 

Arnaud Heritier commented on MPGENAPP-24:
-----------------------------------------

Hi Felipe.

Did you see that you could bypass the <i:ask> with something like :
maven -Dtemplate=default -Dmaven.genapp.template.id=myId 
-Dmaven.genapp.template.name="My Name" 
-Dmaven.genapp.template.package=org.apache.mypackage genapp
For the problem of class not found, I don't know what happens.
Did you take a look at the xdoc plugin ? There are some invokeStatic . For 
example :
        <j:invokeStatic className="org.apache.maven.xdoc.util.LocaleUtil" 
method="codeToLocale" var="defaultLocale">
          <j:arg value="${maven.xdoc.locale.default}" type="java.lang.String"/>
        </j:invokeStatic>
I don't understand why it doesn't work for you. It's very similar.

> Allow project to be generated somewhere else ${basedir}
> -------------------------------------------------------
>
>          Key: MPGENAPP-24
>          URL: http://jira.codehaus.org/browse/MPGENAPP-24
>      Project: maven-genapp-plugin
>         Type: Improvement
>     Versions: 2.2
>     Reporter: Felipe Leme
>     Assignee: Felipe Leme
>     Priority: Minor
>      Fix For: 2.3

>
> Original Estimate: 30 minutes
>         Remaining: 30 minutes
>
> When you run genapp, it creates the new project in the current directory. I 
> see at least one situation (which is why I'm creating this issue) where that 
> is not desired: when creating test cases for this plugin!
> So, I will create a maven.genapp.basedir property to fix this issue.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to