New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deploy as Oxygen Add-on? #1
Comments
(Oops, didn't mean to close.) We'll certainly do this, if not a better alternative, once things have "matured" a bit. |
I had thought about using the Zip of the 'master' branch as the add-on distribution as you did, but I think you're going to have to increment the version number in the descriptor before Oxygen will notice any differences in the add-on, plus you'll make it harder for users to report problems if no-one can tell exactly where the files were up to when they downloaded the archive. As a convenience for you for testing or as a stop-gap until you do your BITs bits, it does make sense, however. |
Tony, You're giving me too much credit for being deliberate and knowing what I am In any case, I'm going to have to update documentation regarding "how to do Cheers, Wendell Wendell Piez | http://www.wendellpiez.com On Fri, Oct 25, 2013 at 7:41 PM, Mentea notifications@github.com wrote:
|
I just updated the add-on descritor XML to release version 1.0.0 of the add-on, I also left a 0.9.0 version in it pointing to an older ZIP archive from GIT. Users will by default see the 1.0.0 version as an installable add-on but there is also a checkbox called "Show only the latest version of the add-on" which they can uncheck to also see older versions. |
Consider zipping everything up and making it available as a hosted add-on for Oxygen.
See http://www.oxygenxml.com/doc/ug-editor/topics/dg-deploying-addons.html
The text was updated successfully, but these errors were encountered: