That option we didn't follow, cause the user would have classes then for which he wouldn't find the sources in svn.
If part of the release-build would be that the generated sources are also stored in both svn and as a jar-file, then the world might look different. regards, Martin On 9/22/06, Mario Ivankovits <[EMAIL PROTECTED]> wrote:
Hey. > Or being able to configure maven in a way that it will NOT refactor the > sources, instead it should simply create a shared and shared-source jar. > said that, wouldn't it be possible to revert the shared_ stuff in svn at all? And refactor tomahawk and impl itself only for the release builds? Then we have the best of both worlds, during development no hassle with the shared_ stuff and standalone release builds. Just some thoughts ... Ciao, Mario
-- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
