[jboss-jira] [JBoss JIRA] (WFLY-695) make-pristine.sh to reset an AS installation to factory settings

[Stuart Douglas (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stuart Douglas resolved WFLY-695.
---------------------------------

    Resolution: Won't Fix


I can't really see this happening. The only way you can really do this is to keep an exact copy of the pristine server config somewhere, and then delete everything and copy it over. Even then the modules directory would not be pristine, so if there were any changes to the modules then this would not help. 

Patching would also add further complications. 

I don't really think that we want to support this when you can get the same effect just by unzipping a new copy of the server. With that said though we may actually end up with similar functionality as a result of splitting up the code base for Wildly 9, basically some kind of assembly tool that could provision a pristine server. 
                
> make-pristine.sh to reset an AS installation to factory settings
> ----------------------------------------------------------------
>
>                 Key: WFLY-695
>                 URL: https://issues.jboss.org/browse/WFLY-695
>             Project: WildFly
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: Scripts
>            Reporter: Bob McWhirter
>             Fix For: Awaiting Volunteers
>
>
> Not sure how this is better than unzip -q jboss-as-bin.zip, but being able to "reset" the domain and such (and bootstrap logging props) to out-of-the-box settings might be nice.
> Perhaps a separate script to clean the deployments and content repo.

--
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