Gavin wrote:
> > > >
> > > > The above discussed is not a hack but a clear enhancement. Well e.g.
> > > > {forrest:forrest.plugins}/org.apache.forrest.plugin.output.Text/
> > should
> > > > be replaced by something shorter. Awesome would be {this} but not sure
> > > > whether that is easily to implement.
> > >
> > > Don't forget that this would need to be handled by the
> > > Ant target that creates a new plugin from the template:
> > > http://forrest.apache.org/docs/dev/howto/howto-buildPlugin.html#seed
> >
> > I was thinking if they are required lines we could just add them in to the
> > template directly so that they are there already, does that sound ok?
>
> Hmm, I'll expand on that.
>
> In the pluginTemplate we can add commented out example code to
> locationmap.xml like :-
>
> <locator>
> <!-- Uncomment the below matches once you have a stylesheet you wish to use.
> Note that these are needed for the plugin to work on windows. See FOR-1108
> -->
> <!--
> <match pattern="plugin.transform.*.*">
> <select>
> <location src="resources/stylesheets/{1}-to-{2}.xsl" />
> <location
> src="{forrest:forrest.plugins}/@plugin-name@/resources/stylesheets/{1}-to-{2
> }.xsl"/>
> </select>
> </match>
> -->
> </locator>
>
> Currently the <locator /> is empty. Then once a stylesheet has been created
> the dev can uncomment out the example.
My comment referred to the ant target which creates the new
plugin. It already edits some files from the pluginTemplate
on the way to add the plugin name, so it should be trivial
to add this extra locationmap match.
-David
