Noel J. Bergman wrote:
Under site/ would be my suggestion.

That's ok to me but then I should move the current pom.xml/src folder for the main project site generation to site/project/ or site/james-project and create a site/maven-skin folder.

Should I create a maven-skin folder in the root of the james repository?

Did you not understand when I asked that no one change anything in the root
of the repository unless told that the mailer has been modified to allow it?

Isn't "Should...?" a question? ;-)
Can't we change the notification to work automatically on the full james tree without having to use single notifications for the subfolders? We have few products and we agreed that we want to share the team for our products... so why not? This would allow to have all the james commit in a single list and all the notifications automatically handled.

Stefano


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to