Scott T Weaver wrote:
Is this supposed to happen? If so I really don't think this is such a great idea as it destroys your existing portal project's descriptor. Are their any work-arounds to fix this?
Scott,
This is *not* supposed to happen. And I just tested it out again and can't reproduce it here. Very weird this can happen... The project.xml (and the other, inherited maven project files for that matter) is created with the j2:portal.conf.project goal (as invoked from j2:portal.genapp). If you look at that goal, you'll see both project.xml and project-info.xml are copied using attribute overwrite="false". So, if those files are not available they will be created but should _never_ be updated. If that is happening nonetheless, I guess something must be wrong with maven, ant or the plugin itself...
Regards, -Scott
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
