|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
On second thought what do we want to achieve here? The settings file as discussed on the wiki is to confirm a release. It is not needed for the release process. I guess we could add a fully automated step where we try to compile something using only the staging settings as discussed on the wiki page, but I am not sure that is necessary.
For the actual release process the most important thing is the <server> settings, but they are user specific and cannot be shared.
Regarding the local repo, I think I prefer to use a command line switch for that (-Dmaven.repo.local=...) if we are going down the route of writing a release script.