[
http://issues.ops4j.org/browse/PAXRUNNER-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12046#action_12046
]
Toni Menzel commented on PAXRUNNER-213:
---------------------------------------
Good idea, This was so far a USP for pax provision.
At its simpliest implementation, for pax runner this can be archieved solely by
having a starter (pax-run.sh *could* be enough, but i am not a bash crack) to
trigger mvn pax:provision and copy artefacts to the correct pax runner install
place afterwards.
> Pax Runner automatic updates
> ----------------------------
>
> Key: PAXRUNNER-213
> URL: http://issues.ops4j.org/browse/PAXRUNNER-213
> Project: Pax Runner
> Issue Type: New Feature
> Reporter: Alin Dreghiciu
> Assignee: Alin Dreghiciu
>
> As Pax Runner has quite an short release cycle, meaning that we do create a
> lot of releases :), it will be great to provide an automatic upgrade feature
> for pax runner. This way the users will not be bothered with
> downloading/installing/configuration of pax runner and get the latest and
> greatest all the time.
> Of course this should be configurable meaning that user could set if the
> starter should check for updates and if the user should be asked or not to
> upgrade.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
