[xwiki-devs] Force reinstall of SNAPSHOT extension from EM
Hello, I'm doing some manual tests of my app, and use EM to install it first, with an extension repository targeting my m2 local repository, my app being in version 0.3-SNAPSHOT. When I fix something, I reinstall a new 0.3-SNAPSHOT of the app in my maven repository, and update the app in my xwiki instance. One thing that would be very nice, would be to be able to force the update of an already installed extension, even if it's in same version (ie, 0.3-SNAPSHOT), or even better to allow this update if a more recent -SNAPSHOT artifact exists (in the artifact, or in one of its dependencies). Currently, it's not possible as EM sees it as installed and proposes nothing else than "uninstall" action. So, to update my app, I have to stop my server, patch each new .jar file directly in xwiki data dir under /extension/repository/blablabla, then restart the server. Uninstalling before does not help as the artifacts are kept in this location anyway (and not rechecked as long as expected version is found). Also, I don't want to uninstall, as usually I edit UI parts directly in xwiki, so I'd eventually prefer a merge as managed by EM. That feature would save my day as developer/tester :) WDYT ? (maybe it's my process that is poor) BR, Jeremie
Hi Jeremie, This is definitely wanted, but there is currently a blocker: http://jira.xwiki.org/browse/XWIKI-7163 Regards, On Sat, Sep 28, 2013 at 8:22 PM, Jeremie BOUSQUET < [email protected]> wrote:
Hello,
I'm doing some manual tests of my app, and use EM to install it first, with an extension repository targeting my m2 local repository, my app being in version 0.3-SNAPSHOT.
When I fix something, I reinstall a new 0.3-SNAPSHOT of the app in my maven repository, and update the app in my xwiki instance.
One thing that would be very nice, would be to be able to force the update of an already installed extension, even if it's in same version (ie, 0.3-SNAPSHOT), or even better to allow this update if a more recent -SNAPSHOT artifact exists (in the artifact, or in one of its dependencies).
Currently, it's not possible as EM sees it as installed and proposes nothing else than "uninstall" action. So, to update my app, I have to stop my server, patch each new .jar file directly in xwiki data dir under /extension/repository/blablabla, then restart the server. Uninstalling before does not help as the artifacts are kept in this location anyway (and not rechecked as long as expected version is found). Also, I don't want to uninstall, as usually I edit UI parts directly in xwiki, so I'd eventually prefer a merge as managed by EM.
That feature would save my day as developer/tester :)
WDYT ? (maybe it's my process that is poor)
BR, Jeremie _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO
This is the plan, what is needed mostly is for EM to got back on the top of my todolist... On Sat, Sep 28, 2013 at 8:22 PM, Jeremie BOUSQUET <[email protected]> wrote:
Hello,
I'm doing some manual tests of my app, and use EM to install it first, with an extension repository targeting my m2 local repository, my app being in version 0.3-SNAPSHOT.
When I fix something, I reinstall a new 0.3-SNAPSHOT of the app in my maven repository, and update the app in my xwiki instance.
One thing that would be very nice, would be to be able to force the update of an already installed extension, even if it's in same version (ie, 0.3-SNAPSHOT), or even better to allow this update if a more recent -SNAPSHOT artifact exists (in the artifact, or in one of its dependencies).
Currently, it's not possible as EM sees it as installed and proposes nothing else than "uninstall" action. So, to update my app, I have to stop my server, patch each new .jar file directly in xwiki data dir under /extension/repository/blablabla, then restart the server. Uninstalling before does not help as the artifacts are kept in this location anyway (and not rechecked as long as expected version is found). Also, I don't want to uninstall, as usually I edit UI parts directly in xwiki, so I'd eventually prefer a merge as managed by EM.
That feature would save my day as developer/tester :)
WDYT ? (maybe it's my process that is poor)
BR, Jeremie _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
Off topic, but I had a quick look at EM code (server+UI) in github, and amount of work is very impressive ... IMO that was a great addition to xwiki ! :) I plan to try to reuse and integrate some bits of it (of the UI part I mean, with logs display and progress bar...) for my app. BR, Jeremie 2013/9/30 Thomas Mortagne <[email protected]>
This is the plan, what is needed mostly is for EM to got back on the top of my todolist...
On Sat, Sep 28, 2013 at 8:22 PM, Jeremie BOUSQUET <[email protected]> wrote:
Hello,
I'm doing some manual tests of my app, and use EM to install it first, with an extension repository targeting my m2 local repository, my app being in version 0.3-SNAPSHOT.
When I fix something, I reinstall a new 0.3-SNAPSHOT of the app in my maven repository, and update the app in my xwiki instance.
One thing that would be very nice, would be to be able to force the update of an already installed extension, even if it's in same version (ie, 0.3-SNAPSHOT), or even better to allow this update if a more recent -SNAPSHOT artifact exists (in the artifact, or in one of its dependencies).
Currently, it's not possible as EM sees it as installed and proposes nothing else than "uninstall" action. So, to update my app, I have to stop my server, patch each new .jar file directly in xwiki data dir under /extension/repository/blablabla, then restart the server. Uninstalling before does not help as the artifacts are kept in this location anyway (and not rechecked as long as expected version is found). Also, I don't want to uninstall, as usually I edit UI parts directly in xwiki, so I'd eventually prefer a merge as managed by EM.
That feature would save my day as developer/tester :)
WDYT ? (maybe it's my process that is poor)
BR, Jeremie _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On Mon, Sep 30, 2013 at 2:45 PM, Jeremie BOUSQUET <[email protected]> wrote:
Off topic, but I had a quick look at EM code (server+UI) in github, and amount of work is very impressive ... IMO that was a great addition to xwiki ! :)
I plan to try to reuse and integrate some bits of it (of the UI part I mean, with logs display and progress bar...) for my app.
Yes all the non strictly extension related stuff are meant to be used for many other things but we still need to take some time to physically separate the UIs from EM codebase even if Marius made them pretty generic already in term of behavior.
BR, Jeremie
2013/9/30 Thomas Mortagne <[email protected]>
This is the plan, what is needed mostly is for EM to got back on the top of my todolist...
On Sat, Sep 28, 2013 at 8:22 PM, Jeremie BOUSQUET <[email protected]> wrote:
Hello,
I'm doing some manual tests of my app, and use EM to install it first, with an extension repository targeting my m2 local repository, my app being in version 0.3-SNAPSHOT.
When I fix something, I reinstall a new 0.3-SNAPSHOT of the app in my maven repository, and update the app in my xwiki instance.
One thing that would be very nice, would be to be able to force the update of an already installed extension, even if it's in same version (ie, 0.3-SNAPSHOT), or even better to allow this update if a more recent -SNAPSHOT artifact exists (in the artifact, or in one of its dependencies).
Currently, it's not possible as EM sees it as installed and proposes nothing else than "uninstall" action. So, to update my app, I have to stop my server, patch each new .jar file directly in xwiki data dir under /extension/repository/blablabla, then restart the server. Uninstalling before does not help as the artifacts are kept in this location anyway (and not rechecked as long as expected version is found). Also, I don't want to uninstall, as usually I edit UI parts directly in xwiki, so I'd eventually prefer a merge as managed by EM.
That feature would save my day as developer/tester :)
WDYT ? (maybe it's my process that is poor)
BR, Jeremie _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
participants (3)
-
Denis Gervalle -
Jeremie BOUSQUET -
Thomas Mortagne