I added the code to copy them too. I just committed them as they were reported changed. Should I delete the files and tell svn to ignore them?
I found that the AbstractDAOTests can not simply create the Activiti properties as the table is not there when we omit the spring xml to initialize Activiti. So I wanted to make the ContentLoader more flexible. This way I was able to replace the xsl based removal of Activiti properties by a java based one. I think this is better than xsl as it is more obvious to see in the code. It took me a while to see that the xsl does this... Christian On 17.01.2013 15:32, Francesco Chicchiriccò wrote: > On 17/01/2013 15:27, cschnei...@apache.org wrote: >> Author: cschneider >> Date: Thu Jan 17 14:27:33 2013 >> New Revision: 1434684 >> >> URL: http://svn.apache.org/viewvc?rev=1434684&view=rev >> Log: >> SYNCOPE-241 Adding new activiticontent.xml to archetype > > Why this activiticontent.xml? Why removing the XSLT dynamic from core > pom.xml? > > Moreover: please consider that archetype resources must be copied from > core and console as part of the build process and not statically > committed as you've just did for content.xml and activiticontent.xml. > > Regards.
