Dear DSpace experts,all of our DSpace 6 customizations are implemented within modules, and usually this works very smooth for us. But now we customized another DSpace file, which is not respected by the build process. The source file in question is:
dspace-xmlui-mirage2/src/main/webapp/xsl/core/forms.xsl
and the corresponding module file is (or should be): dspace/modules/xmlui-mirage2/src/main/webapp/xsl/core/forms.xslDoes anyone know of such module pitfalls? This behaviour is even worse, because changes of the original file will be lost on DSpace source update.
Thanks in advance, Christian --------------------------------- Christian Loeschen, Dipl.-Ing. (FH) Wiss. Mitarbeiter/Research Associate Technische Universität Dresden Center for Information Services and HPC (ZIH) Distributed and Data Intensive Computing 01062 Dresden (Germany) Phone: +49 351 463-42330 Fax : +49 351 463-37773 E-Mail: [email protected] --------------------------------- -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
smime.p7s
Description: S/MIME Cryptographic Signature
