Hi, Thanks for the suggestion. I have tried this and it seems to lack some features that I really need in my plugin. So appearently I will need to write my own plugin. However, I analyzed some of the code in this plugin and it doesn't seem to do a lot more different stuff that I am doing, since the standard transformation API is used. The only difference seems to be that the xml-maven-plugin is run at build time, while mine is run at report time (in the <reporting> section). Could this be a cause why the transformer is not loaded?
Thanks On Fri, Mar 28, 2008 at 5:29 PM, Wayne Fay <[EMAIL PROTECTED]> wrote: > There is already an XML plugin in Codehaus which has XSLT > functionality. Why don't you just take a look at it before moving too > far down this path of possibly re-implementing an existing solution? > > http://mojo.codehaus.org/xml-maven-plugin/ > > Wayne > > On 3/28/08, Cosmin Marginean <[EMAIL PROTECTED]> wrote: > > It seems that this goes deeper. What I actually need to do is create a > Maven > > plugin that performs an XSL transformation using Saxon 9. I unpacked the > > Saxon 9 jar and added the classes to my plugin jar to make sure the > > transformer is loaded. However, it seems that the transformer won't get > > loaded, even when I run Maven with > > - > > > Djava.xml.transform.TransformerFactory=net.sf.saxon.TransformerFactoryImpl > > Some people seem to have worked around this by specifying the Saxon > > dependency in the client pom.xml but this doesn't seem to work if I make > the > > transformation call from the plugin Jar. I even set the property > manually in > > the plugin: > > TransformerFactory factory = TransformerFactory.newInstance(); > > But without any luck. The transformer will not be found > > > > Thanks in advance > > > > On Fri, Mar 28, 2008 at 9:04 AM, Cosmin Marginean <[EMAIL PROTECTED]> > > wrote: > > > > > Hello guys, > > > > > > Sorry to bother you with such issues, but I've googling my brains out > with > > > this without any relevant results. > > > I have a question regarding bundling a 3rd party jar in a Maven > Plugin. I > > > am a bit new to Maven and Maven plugins. > > > I tried bundling it in the plugin jar and adding it to the Class-Path > > > attribute of MANIFEST.MF, but it seems to be ignored when using the > > > plugin. > > > Another question would be: assuming that somehow this 3rd party jar > will > > > make it into a public repository, what is the proper way to configure > the > > > dependency to make sure that the client (plugin user) will download > and load > > > this jar correctly without having to configure 3rd third party > dependency in > > > the pom.xml? > > > > > > Many thanks in advance > > > > > > -- > > > Cosmin Marginean > > > > > > > > > > -- > > Cosmin Marginean > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Cosmin Marginean
