Building the archetype from a clean checkout will not include the
content.xml from core's test resources.
However, somewhere during the first 'mvn clean install', the copied
content.xml from the core module is indeed copied to
src/main/archetype-resources. This has the effect that the second and
subsequent times the built archetype does have the content.xml included.
Another side effect: because content.xml is copied to src/main/resources,
SVN clients will see it as unversioned file.
I'm afraid this is caused by rev 1151, "Linking archetype's content.xml to
I'm sorry, but could not yet envision a fix for this, other than reverting
It seems there's no official postprocess-hook for an archetype's resources
where this could belong.
Prior to issue 1151,
was a separate file from core/src/test/resources/content.xml.
Since Syncope core's source code is evolving quickly - especially these
days - and since the data in core/src/test/resources/content.xml is likely
to change (almost) at every commit, we thought it was cleaner to make the
archetype building process itself to copy content.xml from its "main"
location to archetype's.
Maven archetypes are meant to be installed and then retrieved from local or
remote maven repository and the current procedure should respect this
I'm sorry, I think my description of the issue is not clear.
I do know that archetypes are meant to be downloaded and used 'as is',
without building them yourselves.
However, when you, as a syncope-developer, would build and deploy the
snapshot archetype from a clean checkout, then content.xml will not be
included. (probably because the copying is done too late)
Only after having built the archetype once, content.xml is included.
svn co https://syncope.googlecode.com/svn/trunk syncope-trunk-test
mvn clean install
check directory archetype-resources/core/src/test/resources/ (no