Christopher Williams wrote: > Markus, > I know very little about how docbook works in our doc.user plugin. But I > do know that part of our build process with that plugin generates a new > plugin.xml file and overwrites our existing one. I managed to fix the > process to stop breaking the xml inside the plugin, but I'd like to > have it > never overwrite our existing file in the first place. Could you look into > how we could do that? I have substituted the stylesheet eclipse.xsl with a another version (org.rubypeople.rdt.doc.user/docbook/modified_eclipse.xsl) which generates a MANIFEST.MF and a correct plugin.xml, too. Therefore I have removed plugin.xml from the repository, but kept the Manifest so that the plug-in will be valid in the workspace and for the build process without the need to generate anything.
Furthermore I found that the generation in the nightly build failed since we moved to JDK 1.5. The reason was that files were created relative to the current directory (user.dir) and not relative to the destdir property (which is given to the style-task). That is fixed now by calling a new Java process with the current dir set to the plug-in directory. Markus ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Rubyeclipse-development mailing list Rubyeclipse-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
