[xwiki-devs] [ANN] Legacy modules are now only built when the "ci" profile is active
Hi devs, I've made the following change today: * Legacy modules are not built nor packaged anymore by default when you build commons, platform and enterprise. * They are still built and packaged when the ci profile is activated and thus Jenkins still generates and run tests with legacy modules active (as before) This allows: * To speed up the developer builds (on my machine I win 2 minutes by not building commons and platform legacy modules) * Developers run without legacy modules by default which mean they can discover when we have wiki pages still using deprecated apis that have been moved to legacy Next step (that will require a vote) will be to provide a package without legacy modules for end users (details to be discussed too). Thanks -Vincent
This is exciting, I would like most for the non-legacy distribution to be called "xwiki-enterprise", perhaps the legacy version could be "xwiki-enterprise-lts"? Even if that is not agreeable, we should make an effort to see that new users don't accidentally download the legacy version. While we're making the decision, I'd be happy to setup a temporary "xwiki-enterprise-nolegacy" just for running the tests on. WDYT? Caleb On 03/29/2012 02:20 PM, Vincent Massol wrote:
Hi devs,
I've made the following change today: * Legacy modules are not built nor packaged anymore by default when you build commons, platform and enterprise. * They are still built and packaged when the ci profile is activated and thus Jenkins still generates and run tests with legacy modules active (as before)
This allows: * To speed up the developer builds (on my machine I win 2 minutes by not building commons and platform legacy modules) * Developers run without legacy modules by default which mean they can discover when we have wiki pages still using deprecated apis that have been moved to legacy
Next step (that will require a vote) will be to provide a package without legacy modules for end users (details to be discussed too).
Thanks -Vincent _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On Thu, Mar 29, 2012 at 9:27 PM, Caleb James DeLisle <[email protected]> wrote:
This is exciting, I would like most for the non-legacy distribution to be called "xwiki-enterprise", perhaps the legacy version could be "xwiki-enterprise-lts"? Even if that is not agreeable, we should make an effort to see that new users don't accidentally download the legacy version.
While we're making the decision, I'd be happy to setup a temporary "xwiki-enterprise-nolegacy" just for running the tests on.
You mean a jenkins job ?
WDYT?
Caleb
On 03/29/2012 02:20 PM, Vincent Massol wrote:
Hi devs,
I've made the following change today: * Legacy modules are not built nor packaged anymore by default when you build commons, platform and enterprise. * They are still built and packaged when the ci profile is activated and thus Jenkins still generates and run tests with legacy modules active (as before)
This allows: * To speed up the developer builds (on my machine I win 2 minutes by not building commons and platform legacy modules) * Developers run without legacy modules by default which mean they can discover when we have wiki pages still using deprecated apis that have been moved to legacy
Next step (that will require a vote) will be to provide a package without legacy modules for end users (details to be discussed too).
Thanks -Vincent _______________________________________________ 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
On 03/30/2012 04:40 AM, Thomas Mortagne wrote:
On Thu, Mar 29, 2012 at 9:27 PM, Caleb James DeLisle <[email protected]> wrote:
This is exciting, I would like most for the non-legacy distribution to be called "xwiki-enterprise", perhaps the legacy version could be "xwiki-enterprise-lts"? Even if that is not agreeable, we should make an effort to see that new users don't accidentally download the legacy version.
While we're making the decision, I'd be happy to setup a temporary "xwiki-enterprise-nolegacy" just for running the tests on.
You mean a jenkins job ?
I was thinking we would have to put the "non-legacy" version of XE into nexus but I suppose we can build and test it, relying on the build agent's .m2/repository. At any rate, we'll need to give it a different name so that it doesn't flush out the "with-legacy" version from the repository. We could just wait for agreement on shipping without legacy and do it then but that's a complex decision and I'd like to see test results ASAP. Caleb
WDYT?
Caleb
On 03/29/2012 02:20 PM, Vincent Massol wrote:
Hi devs,
I've made the following change today: * Legacy modules are not built nor packaged anymore by default when you build commons, platform and enterprise. * They are still built and packaged when the ci profile is activated and thus Jenkins still generates and run tests with legacy modules active (as before)
This allows: * To speed up the developer builds (on my machine I win 2 minutes by not building commons and platform legacy modules) * Developers run without legacy modules by default which mean they can discover when we have wiki pages still using deprecated apis that have been moved to legacy
Next step (that will require a vote) will be to provide a package without legacy modules for end users (details to be discussed too).
Thanks -Vincent _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
participants (3)
-
Caleb James DeLisle -
Thomas Mortagne -
Vincent Massol