[
http://jira.codehaus.org/browse/MJSPC-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Susan Liebeskind updated MJSPC-36:
----------------------------------
Attachment: patch.txt
removed readOnly annotation so that the classpath can be changed (in our case,
we change it to ${project.runtimeClasspathElements} so we can find the tag
classes being compiled in the same project)
> Allow configuration of classpath passed to the Jasper compiler
> --------------------------------------------------------------
>
> Key: MJSPC-36
> URL: http://jira.codehaus.org/browse/MJSPC-36
> Project: Maven 2.x JSPC Plugin
> Issue Type: New Feature
> Affects Versions: 2.0-alpha-2
> Reporter: Susan Liebeskind
> Attachments: patch.txt
>
>
> The mojo currently specifies the classpath as readOnly, and defaults to
> ${project.compileClasspathElements}. There are situations in our large
> project where we actually need to use the project runtime classpath, not the
> compile classpath, in order to precompile our JSPS during development.
> Can we remove the readOnly annotation of the classpath parameter in
> CompileMojo.groovy? This allows folks to easily override the default setting
> of ${project.compileClasspathElements} with a configuration element like this
> to use the runtime classpath
> <plugin>
> ...
> <artifactId>jspc-maven-plugin>
> ...
> <configuration>
>
> <classpathElements>${project.runtimeClasspathElements}</classpathElements>
> </configuration>
> </plugin>
> Thanks
>
--
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 from this list, please visit:
http://xircles.codehaus.org/manage_email
