[xwiki-users] Recommendations on writing automated functional tests for xar extensions ?
Hello, I would like to discuss a little on writing of Selenium2 tests, as described in test strategy [1], ie use Selenium 2 and apply Page Objects pattern. My particular use-case is that I'm on a mission : write some functional tests for my mail archive application. I also think these would be the best tests for my app, as it greatly relies on 2 external interfaces (xwiki for persistence/conf, javamail and mail accounts on another side). There are some good unit tests to write of course, but the main logic of the app has more meaning to be tested in "real life", or close to that. To do that, I decided to try and plug myself in xwiki test framework, in order to avoid redeveloping everything (such as deploying / launching an xwiki instance from the tests). I added 2 modules in my project: - xwiki-contrib-mailarchive-test-pageobjects - xwiki-contrib-mailarchive-test-ui Both inherit from org.xwiki.enterprise:xwiki-enterprise-test pom, and are greatly inspired from poms of xwiki-enterprise-test-pageobjects and xwiki-enterprise-test-ui poms. It's unfinished and untested, but I believe I'll be able to have xwiki instance installed, launched, and tests run automatically. My main question, is how should I do in order to also deploy my app in this wiki instance prior to run the tests ? For now I have several possible solutions that come to my mind, but I don't know what would be the best... : A- - grab xwiki-standalone zip version x.y.z, unzip it, launch it - make EM install my application (call some REST API ? GET some page with proper parameters ?) - run the tests B- - grab xwiki-standalone zip version x.y.z, unzip it - "patch" it in some way with my application binaries, (ie, add things directly under permanent directory / extension / repository ?) - launch it and run the tests I personnally prefer A-, but it supposes also that the xwiki instance knows any of my "dev" maven repositories (either my local repository .m2, or my local instance of Nexus), so it would mean an additional step would be to "patch" the standalone wiki xwiki.properties to add my personal repo. Or maybe I can add such repo programmatically in the wiki instance from java by looking up and using the right component ? Maybe this point has already been solved by anyone, so if you have any samples it would be good enough. I did not search exhaustively, but I don't remember having seen such use-cases on existing extensions on github. Also, I think it might be interesting to extract from all this some kind of maven archetype for functional testing of UI extension ? So contributors could just call the archetype and get everything properly prepared, and just have to add page objects and tests for their app ... WDYT ? BR, Jeremie [1] http://dev.xwiki.org/xwiki/bin/view/Community/Testing#HSelenium2-basedFramew...
Hi Jeremie, We have started moving functional tests from xwiki-enterprise to xwiki-platform so that they are grouped by functional domain. Thus xwiki-enterprise-test-ui is not the best example. You should take a look at the platform modules that have functional tests: https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik... https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik... https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik... to name a few. The packager maven plugin is taking care of importing (installing) your XAR and (I believe) adding the required jar dependencies to the WAR. You should follow this practice. Hope this helps, Marius On Wed, Mar 20, 2013 at 1:07 PM, Jeremie BOUSQUET <[email protected]> wrote:
Hello,
I would like to discuss a little on writing of Selenium2 tests, as described in test strategy [1], ie use Selenium 2 and apply Page Objects pattern.
My particular use-case is that I'm on a mission : write some functional tests for my mail archive application. I also think these would be the best tests for my app, as it greatly relies on 2 external interfaces (xwiki for persistence/conf, javamail and mail accounts on another side). There are some good unit tests to write of course, but the main logic of the app has more meaning to be tested in "real life", or close to that.
To do that, I decided to try and plug myself in xwiki test framework, in order to avoid redeveloping everything (such as deploying / launching an xwiki instance from the tests). I added 2 modules in my project: - xwiki-contrib-mailarchive-test-pageobjects - xwiki-contrib-mailarchive-test-ui
Both inherit from org.xwiki.enterprise:xwiki-enterprise-test pom, and are greatly inspired from poms of xwiki-enterprise-test-pageobjects and xwiki-enterprise-test-ui poms. It's unfinished and untested, but I believe I'll be able to have xwiki instance installed, launched, and tests run automatically.
My main question, is how should I do in order to also deploy my app in this wiki instance prior to run the tests ? For now I have several possible solutions that come to my mind, but I don't know what would be the best... : A- - grab xwiki-standalone zip version x.y.z, unzip it, launch it - make EM install my application (call some REST API ? GET some page with proper parameters ?) - run the tests B- - grab xwiki-standalone zip version x.y.z, unzip it - "patch" it in some way with my application binaries, (ie, add things directly under permanent directory / extension / repository ?) - launch it and run the tests
I personnally prefer A-, but it supposes also that the xwiki instance knows any of my "dev" maven repositories (either my local repository .m2, or my local instance of Nexus), so it would mean an additional step would be to "patch" the standalone wiki xwiki.properties to add my personal repo. Or maybe I can add such repo programmatically in the wiki instance from java by looking up and using the right component ?
Maybe this point has already been solved by anyone, so if you have any samples it would be good enough. I did not search exhaustively, but I don't remember having seen such use-cases on existing extensions on github. Also, I think it might be interesting to extract from all this some kind of maven archetype for functional testing of UI extension ? So contributors could just call the archetype and get everything properly prepared, and just have to add page objects and tests for their app ...
WDYT ?
BR, Jeremie
[1] http://dev.xwiki.org/xwiki/bin/view/Community/Testing#HSelenium2-basedFramew... _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
Thanks Marius, that's exactly what I was looking for ! I'll follow that practice, BR, Jeremie 2013/3/20 Marius Dumitru Florea <[email protected]>
Hi Jeremie,
We have started moving functional tests from xwiki-enterprise to xwiki-platform so that they are grouped by functional domain. Thus xwiki-enterprise-test-ui is not the best example. You should take a look at the platform modules that have functional tests:
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik...
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik...
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik...
to name a few. The packager maven plugin is taking care of importing (installing) your XAR and (I believe) adding the required jar dependencies to the WAR. You should follow this practice.
Hope this helps, Marius
On Wed, Mar 20, 2013 at 1:07 PM, Jeremie BOUSQUET <[email protected]> wrote:
Hello,
I would like to discuss a little on writing of Selenium2 tests, as described in test strategy [1], ie use Selenium 2 and apply Page Objects pattern.
My particular use-case is that I'm on a mission : write some functional tests for my mail archive application. I also think these would be the best tests for my app, as it greatly relies on 2 external interfaces (xwiki for persistence/conf, javamail and mail accounts on another side). There are some good unit tests to write of course, but the main logic of the app has more meaning to be tested in "real life", or close to that.
To do that, I decided to try and plug myself in xwiki test framework, in order to avoid redeveloping everything (such as deploying / launching an xwiki instance from the tests). I added 2 modules in my project: - xwiki-contrib-mailarchive-test-pageobjects - xwiki-contrib-mailarchive-test-ui
Both inherit from org.xwiki.enterprise:xwiki-enterprise-test pom, and are greatly inspired from poms of xwiki-enterprise-test-pageobjects and xwiki-enterprise-test-ui poms. It's unfinished and untested, but I believe I'll be able to have xwiki instance installed, launched, and tests run automatically.
My main question, is how should I do in order to also deploy my app in this wiki instance prior to run the tests ? For now I have several possible solutions that come to my mind, but I don't know what would be the best... : A- - grab xwiki-standalone zip version x.y.z, unzip it, launch it - make EM install my application (call some REST API ? GET some page with proper parameters ?) - run the tests B- - grab xwiki-standalone zip version x.y.z, unzip it - "patch" it in some way with my application binaries, (ie, add things directly under permanent directory / extension / repository ?) - launch it and run the tests
I personnally prefer A-, but it supposes also that the xwiki instance knows any of my "dev" maven repositories (either my local repository .m2, or my local instance of Nexus), so it would mean an additional step would be to "patch" the standalone wiki xwiki.properties to add my personal repo. Or maybe I can add such repo programmatically in the wiki instance from java by looking up and using the right component ?
Maybe this point has already been solved by anyone, so if you have any samples it would be good enough. I did not search exhaustively, but I don't remember having seen such use-cases on existing extensions on github. Also, I think it might be interesting to extract from all this some kind of maven archetype for functional testing of UI extension ? So contributors could just call the archetype and get everything properly prepared, and just have to add page objects and tests for their app ...
WDYT ?
BR, Jeremie
[1]
http://dev.xwiki.org/xwiki/bin/view/Community/Testing#HSelenium2-basedFramew...
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
Hummm, running through a strange issue during build: [ERROR] Failed to execute goal org.xwiki.platform:xwiki-platform-tool-packager-plugin:4.5.2:package (default) on project xwiki-contrib-mailarchive-test-tests: Failed to resolve art ifact [org.xwiki.platform:xwiki-platform-tool-jetty-resources:zip:0.3-SNAPSHOT:]: Failure to find org.xwiki.platform:xwiki-platform-tool-jetty-resources:zip:0.3-SNAPSHOT in http:// nexus.xwiki.org/nexus/content/groups/public-snapshots was cached in the local repository, resolution will not be reattempted until the update interval of xwiki-snapshots has elapse d or updates are forced 4.5.2 is ${platform.version}, 0.3-SNAPSHOT is ${project.version}. The packager plugin is declared in my pom in version ${platform.version} of course. Surprisingly though, here's an extract of the output of "dependency:resolve-plugins": [INFO] Plugin Resolved: xwiki-platform-tool-packager-plugin-4.5.2.jar [...] [INFO] Plugin Dependency Resolved: xwiki-platform-tool-jetty-resources-4.5.2.zip [...] Seems that it finds correct 4.5.2 version for same dependency, that it doesn't find at runtime ... Maybe an issue on packager plugin, "invisible" until you use it on a non-xwiki project ? :-) BR, Jeremie 2013/3/25 Jeremie BOUSQUET <[email protected]>
Thanks Marius, that's exactly what I was looking for ! I'll follow that practice,
BR, Jeremie
2013/3/20 Marius Dumitru Florea <[email protected]>
Hi Jeremie,
We have started moving functional tests from xwiki-enterprise to xwiki-platform so that they are grouped by functional domain. Thus xwiki-enterprise-test-ui is not the best example. You should take a look at the platform modules that have functional tests:
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik...
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik...
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik...
to name a few. The packager maven plugin is taking care of importing (installing) your XAR and (I believe) adding the required jar dependencies to the WAR. You should follow this practice.
Hope this helps, Marius
On Wed, Mar 20, 2013 at 1:07 PM, Jeremie BOUSQUET <[email protected]> wrote:
Hello,
I would like to discuss a little on writing of Selenium2 tests, as described in test strategy [1], ie use Selenium 2 and apply Page Objects pattern.
My particular use-case is that I'm on a mission : write some functional tests for my mail archive application. I also think these would be the best tests for my app, as it greatly relies on 2 external interfaces (xwiki for persistence/conf, javamail and mail accounts on another side). There are some good unit tests to write of course, but the main logic of the app has more meaning to be tested in "real life", or close to that.
To do that, I decided to try and plug myself in xwiki test framework, in order to avoid redeveloping everything (such as deploying / launching an xwiki instance from the tests). I added 2 modules in my project: - xwiki-contrib-mailarchive-test-pageobjects - xwiki-contrib-mailarchive-test-ui
Both inherit from org.xwiki.enterprise:xwiki-enterprise-test pom, and are greatly inspired from poms of xwiki-enterprise-test-pageobjects and xwiki-enterprise-test-ui poms. It's unfinished and untested, but I believe I'll be able to have xwiki instance installed, launched, and tests run automatically.
My main question, is how should I do in order to also deploy my app in this wiki instance prior to run the tests ? For now I have several possible solutions that come to my mind, but I don't know what would be the best... : A- - grab xwiki-standalone zip version x.y.z, unzip it, launch it - make EM install my application (call some REST API ? GET some page with proper parameters ?) - run the tests B- - grab xwiki-standalone zip version x.y.z, unzip it - "patch" it in some way with my application binaries, (ie, add things directly under permanent directory / extension / repository ?) - launch it and run the tests
I personnally prefer A-, but it supposes also that the xwiki instance knows any of my "dev" maven repositories (either my local repository .m2, or my local instance of Nexus), so it would mean an additional step would be to "patch" the standalone wiki xwiki.properties to add my personal repo. Or maybe I can add such repo programmatically in the wiki instance from java by looking up and using the right component ?
Maybe this point has already been solved by anyone, so if you have any samples it would be good enough. I did not search exhaustively, but I don't remember having seen such use-cases on existing extensions on github. Also, I think it might be interesting to extract from all this some kind of maven archetype for functional testing of UI extension ? So contributors could just call the archetype and get everything properly prepared, and just have to add page objects and tests for their app ...
WDYT ?
BR, Jeremie
[1]
http://dev.xwiki.org/xwiki/bin/view/Community/Testing#HSelenium2-basedFramew...
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
Note: it goes a bit further if I declare a bunch of xwiki platform dependencies in my pom, but breaks again, trying to look at those platform artifacts for version ${project.version} instead of ${platform.version} : [INFO] Copying JAR dependencies ... [WARNING] Missing POM for org.xwiki.platform:xwiki-platform-wysiwyg-server:jar:0.3-SNAPSHOT [WARNING] Missing POM for org.xwiki.platform:xwiki-platform-localization-script:jar:0.3-SNAPSHOT [WARNING] Missing POM for org.xwiki.platform:xwiki-platform-oldcore:jar:0.3-SNAPSHOT [...] [ERROR] Failed to execute goal org.xwiki.platform:xwiki-platform-tool-packager-plugi datory artifacts: Missing: [ERROR] ---------- [ERROR] 1) org.xwiki.platform:xwiki-platform-localization-script:jar:0.3-SNAPSHOT [ERROR] [ERROR] Try downloading the file manually from the project website. [...] Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to resolve mandatory artifacts at org.xwiki.tool.packager.PackageMojo.resolveTransitively(PackageMojo.java:614) at org.xwiki.tool.packager.PackageMojo.resolveJarArtifacts(PackageMojo.java:543) at org.xwiki.tool.packager.PackageMojo.execute(PackageMojo.java:209) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more 2013/3/25 Jeremie BOUSQUET <[email protected]>
Hummm, running through a strange issue during build:
[ERROR] Failed to execute goal org.xwiki.platform:xwiki-platform-tool-packager-plugin:4.5.2:package (default) on project xwiki-contrib-mailarchive-test-tests: Failed to resolve art ifact [org.xwiki.platform:xwiki-platform-tool-jetty-resources:zip:0.3-SNAPSHOT:]: Failure to find org.xwiki.platform:xwiki-platform-tool-jetty-resources:zip:0.3-SNAPSHOT in http:// nexus.xwiki.org/nexus/content/groups/public-snapshots was cached in the local repository, resolution will not be reattempted until the update interval of xwiki-snapshots has elapse d or updates are forced
4.5.2 is ${platform.version}, 0.3-SNAPSHOT is ${project.version}. The packager plugin is declared in my pom in version ${platform.version} of course.
Surprisingly though, here's an extract of the output of "dependency:resolve-plugins":
[INFO] Plugin Resolved: xwiki-platform-tool-packager-plugin-4.5.2.jar [...] [INFO] Plugin Dependency Resolved: xwiki-platform-tool-jetty-resources-4.5.2.zip [...]
Seems that it finds correct 4.5.2 version for same dependency, that it doesn't find at runtime ... Maybe an issue on packager plugin, "invisible" until you use it on a non-xwiki project ? :-)
BR, Jeremie
2013/3/25 Jeremie BOUSQUET <[email protected]>
Thanks Marius, that's exactly what I was looking for ! I'll follow that practice,
BR, Jeremie
2013/3/20 Marius Dumitru Florea <[email protected]>
Hi Jeremie,
We have started moving functional tests from xwiki-enterprise to xwiki-platform so that they are grouped by functional domain. Thus xwiki-enterprise-test-ui is not the best example. You should take a look at the platform modules that have functional tests:
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik...
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik...
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik...
to name a few. The packager maven plugin is taking care of importing (installing) your XAR and (I believe) adding the required jar dependencies to the WAR. You should follow this practice.
Hope this helps, Marius
On Wed, Mar 20, 2013 at 1:07 PM, Jeremie BOUSQUET <[email protected]> wrote:
Hello,
I would like to discuss a little on writing of Selenium2 tests, as described in test strategy [1], ie use Selenium 2 and apply Page Objects pattern.
My particular use-case is that I'm on a mission : write some functional tests for my mail archive application. I also think these would be the best tests for my app, as it greatly relies on 2 external interfaces (xwiki for persistence/conf, javamail and mail accounts on another side). There are some good unit tests to write of course, but the main logic of the app has more meaning to be tested in "real life", or close to that.
To do that, I decided to try and plug myself in xwiki test framework, in order to avoid redeveloping everything (such as deploying / launching an xwiki instance from the tests). I added 2 modules in my project: - xwiki-contrib-mailarchive-test-pageobjects - xwiki-contrib-mailarchive-test-ui
Both inherit from org.xwiki.enterprise:xwiki-enterprise-test pom, and are greatly inspired from poms of xwiki-enterprise-test-pageobjects and xwiki-enterprise-test-ui poms. It's unfinished and untested, but I believe I'll be able to have xwiki instance installed, launched, and tests run automatically.
My main question, is how should I do in order to also deploy my app in this wiki instance prior to run the tests ? For now I have several possible solutions that come to my mind, but I don't know what would be the best... : A- - grab xwiki-standalone zip version x.y.z, unzip it, launch it - make EM install my application (call some REST API ? GET some page with proper parameters ?) - run the tests B- - grab xwiki-standalone zip version x.y.z, unzip it - "patch" it in some way with my application binaries, (ie, add things directly under permanent directory / extension / repository ?) - launch it and run the tests
I personnally prefer A-, but it supposes also that the xwiki instance knows any of my "dev" maven repositories (either my local repository .m2, or my local instance of Nexus), so it would mean an additional step would be to "patch" the standalone wiki xwiki.properties to add my personal repo. Or maybe I can add such repo programmatically in the wiki instance from java by looking up and using the right component ?
Maybe this point has already been solved by anyone, so if you have any samples it would be good enough. I did not search exhaustively, but I don't remember having seen such use-cases on existing extensions on github. Also, I think it might be interesting to extract from all this some kind of maven archetype for functional testing of UI extension ? So contributors could just call the archetype and get everything properly prepared, and just have to add page objects and tests for their app ...
WDYT ?
BR, Jeremie
[1]
http://dev.xwiki.org/xwiki/bin/view/Community/Testing#HSelenium2-basedFramew...
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
I think the problem lies on this kind of expressions [1] ... The packager plugin defines version for all mandatory platform artifacts with "this.getProject().getVersion()", meaning if I'm correct that it returns correct version only if project is part of xwiki platform - or if it shares the same version. Maybe it should use property "platform.version" instead ? BR, Jeremie [1] https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-tools/xwi... 2013/3/25 Jeremie BOUSQUET <[email protected]>
Note: it goes a bit further if I declare a bunch of xwiki platform dependencies in my pom, but breaks again, trying to look at those platform artifacts for version ${project.version} instead of ${platform.version} :
[INFO] Copying JAR dependencies ... [WARNING] Missing POM for org.xwiki.platform:xwiki-platform-wysiwyg-server:jar:0.3-SNAPSHOT [WARNING] Missing POM for org.xwiki.platform:xwiki-platform-localization-script:jar:0.3-SNAPSHOT [WARNING] Missing POM for org.xwiki.platform:xwiki-platform-oldcore:jar:0.3-SNAPSHOT [...] [ERROR] Failed to execute goal org.xwiki.platform:xwiki-platform-tool-packager-plugi datory artifacts: Missing: [ERROR] ---------- [ERROR] 1) org.xwiki.platform:xwiki-platform-localization-script:jar:0.3-SNAPSHOT [ERROR] [ERROR] Try downloading the file manually from the project website. [...] Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to resolve mandatory artifacts at org.xwiki.tool.packager.PackageMojo.resolveTransitively(PackageMojo.java:614) at org.xwiki.tool.packager.PackageMojo.resolveJarArtifacts(PackageMojo.java:543) at org.xwiki.tool.packager.PackageMojo.execute(PackageMojo.java:209) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more
2013/3/25 Jeremie BOUSQUET <[email protected]>
Hummm, running through a strange issue during build:
[ERROR] Failed to execute goal org.xwiki.platform:xwiki-platform-tool-packager-plugin:4.5.2:package (default) on project xwiki-contrib-mailarchive-test-tests: Failed to resolve art ifact [org.xwiki.platform:xwiki-platform-tool-jetty-resources:zip:0.3-SNAPSHOT:]: Failure to find org.xwiki.platform:xwiki-platform-tool-jetty-resources:zip:0.3-SNAPSHOT in http:// nexus.xwiki.org/nexus/content/groups/public-snapshots was cached in the local repository, resolution will not be reattempted until the update interval of xwiki-snapshots has elapse d or updates are forced
4.5.2 is ${platform.version}, 0.3-SNAPSHOT is ${project.version}. The packager plugin is declared in my pom in version ${platform.version} of course.
Surprisingly though, here's an extract of the output of "dependency:resolve-plugins":
[INFO] Plugin Resolved: xwiki-platform-tool-packager-plugin-4.5.2.jar [...] [INFO] Plugin Dependency Resolved: xwiki-platform-tool-jetty-resources-4.5.2.zip [...]
Seems that it finds correct 4.5.2 version for same dependency, that it doesn't find at runtime ... Maybe an issue on packager plugin, "invisible" until you use it on a non-xwiki project ? :-)
BR, Jeremie
2013/3/25 Jeremie BOUSQUET <[email protected]>
Thanks Marius, that's exactly what I was looking for ! I'll follow that practice,
BR, Jeremie
2013/3/20 Marius Dumitru Florea <[email protected]>
Hi Jeremie,
We have started moving functional tests from xwiki-enterprise to xwiki-platform so that they are grouped by functional domain. Thus xwiki-enterprise-test-ui is not the best example. You should take a look at the platform modules that have functional tests:
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik...
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik...
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik...
to name a few. The packager maven plugin is taking care of importing (installing) your XAR and (I believe) adding the required jar dependencies to the WAR. You should follow this practice.
Hope this helps, Marius
On Wed, Mar 20, 2013 at 1:07 PM, Jeremie BOUSQUET <[email protected]> wrote:
Hello,
I would like to discuss a little on writing of Selenium2 tests, as described in test strategy [1], ie use Selenium 2 and apply Page Objects pattern.
My particular use-case is that I'm on a mission : write some functional tests for my mail archive application. I also think these would be the best tests for my app, as it greatly relies on 2 external interfaces (xwiki for persistence/conf, javamail and mail accounts on another side). There are some good unit tests to write of course, but the main logic of the app has more meaning to be tested in "real life", or close to that.
To do that, I decided to try and plug myself in xwiki test framework, in order to avoid redeveloping everything (such as deploying / launching an xwiki instance from the tests). I added 2 modules in my project: - xwiki-contrib-mailarchive-test-pageobjects - xwiki-contrib-mailarchive-test-ui
Both inherit from org.xwiki.enterprise:xwiki-enterprise-test pom, and are greatly inspired from poms of xwiki-enterprise-test-pageobjects and xwiki-enterprise-test-ui poms. It's unfinished and untested, but I believe I'll be able to have xwiki instance installed, launched, and tests run automatically.
My main question, is how should I do in order to also deploy my app in this wiki instance prior to run the tests ? For now I have several possible solutions that come to my mind, but I don't know what would be the best... : A- - grab xwiki-standalone zip version x.y.z, unzip it, launch it - make EM install my application (call some REST API ? GET some page with proper parameters ?) - run the tests B- - grab xwiki-standalone zip version x.y.z, unzip it - "patch" it in some way with my application binaries, (ie, add things directly under permanent directory / extension / repository ?) - launch it and run the tests
I personnally prefer A-, but it supposes also that the xwiki instance knows any of my "dev" maven repositories (either my local repository .m2, or my local instance of Nexus), so it would mean an additional step would be to "patch" the standalone wiki xwiki.properties to add my personal repo. Or maybe I can add such repo programmatically in the wiki instance from java by looking up and using the right component ?
Maybe this point has already been solved by anyone, so if you have any samples it would be good enough. I did not search exhaustively, but I don't remember having seen such use-cases on existing extensions on github. Also, I think it might be interesting to extract from all this some kind of maven archetype for functional testing of UI extension ? So contributors could just call the archetype and get everything properly prepared, and just have to add page objects and tests for their app ...
WDYT ?
BR, Jeremie
[1]
http://dev.xwiki.org/xwiki/bin/view/Community/Testing#HSelenium2-basedFramew...
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
Hi again, On this topic I created a new JIRA: http://jira.xwiki.org/browse/XWIKI-8960 ... and proposed some sort of solution as a comment. If you agree with the problem and proposal, I could try to contribute a patch, as anyway I need it for the mailarchive tests. Of course if you want to fix it I don't disagree :-) BR, Jeremie 2013/3/25 Jeremie BOUSQUET <[email protected]>
I think the problem lies on this kind of expressions [1] ...
The packager plugin defines version for all mandatory platform artifacts with "this.getProject().getVersion()", meaning if I'm correct that it returns correct version only if project is part of xwiki platform - or if it shares the same version. Maybe it should use property "platform.version" instead ?
BR, Jeremie
[1] https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-tools/xwi...
2013/3/25 Jeremie BOUSQUET <[email protected]>
Note: it goes a bit further if I declare a bunch of xwiki platform dependencies in my pom, but breaks again, trying to look at those platform artifacts for version ${project.version} instead of ${platform.version} :
[INFO] Copying JAR dependencies ... [WARNING] Missing POM for org.xwiki.platform:xwiki-platform-wysiwyg-server:jar:0.3-SNAPSHOT [WARNING] Missing POM for org.xwiki.platform:xwiki-platform-localization-script:jar:0.3-SNAPSHOT [WARNING] Missing POM for org.xwiki.platform:xwiki-platform-oldcore:jar:0.3-SNAPSHOT [...] [ERROR] Failed to execute goal org.xwiki.platform:xwiki-platform-tool-packager-plugi datory artifacts: Missing: [ERROR] ---------- [ERROR] 1) org.xwiki.platform:xwiki-platform-localization-script:jar:0.3-SNAPSHOT [ERROR] [ERROR] Try downloading the file manually from the project website. [...] Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to resolve mandatory artifacts at org.xwiki.tool.packager.PackageMojo.resolveTransitively(PackageMojo.java:614) at org.xwiki.tool.packager.PackageMojo.resolveJarArtifacts(PackageMojo.java:543) at org.xwiki.tool.packager.PackageMojo.execute(PackageMojo.java:209) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more
2013/3/25 Jeremie BOUSQUET <[email protected]>
Hummm, running through a strange issue during build:
[ERROR] Failed to execute goal org.xwiki.platform:xwiki-platform-tool-packager-plugin:4.5.2:package (default) on project xwiki-contrib-mailarchive-test-tests: Failed to resolve art ifact [org.xwiki.platform:xwiki-platform-tool-jetty-resources:zip:0.3-SNAPSHOT:]: Failure to find org.xwiki.platform:xwiki-platform-tool-jetty-resources:zip:0.3-SNAPSHOT in http:// nexus.xwiki.org/nexus/content/groups/public-snapshots was cached in the local repository, resolution will not be reattempted until the update interval of xwiki-snapshots has elapse d or updates are forced
4.5.2 is ${platform.version}, 0.3-SNAPSHOT is ${project.version}. The packager plugin is declared in my pom in version ${platform.version} of course.
Surprisingly though, here's an extract of the output of "dependency:resolve-plugins":
[INFO] Plugin Resolved: xwiki-platform-tool-packager-plugin-4.5.2.jar [...] [INFO] Plugin Dependency Resolved: xwiki-platform-tool-jetty-resources-4.5.2.zip [...]
Seems that it finds correct 4.5.2 version for same dependency, that it doesn't find at runtime ... Maybe an issue on packager plugin, "invisible" until you use it on a non-xwiki project ? :-)
BR, Jeremie
2013/3/25 Jeremie BOUSQUET <[email protected]>
Thanks Marius, that's exactly what I was looking for ! I'll follow that practice,
BR, Jeremie
2013/3/20 Marius Dumitru Florea <[email protected]>
Hi Jeremie,
We have started moving functional tests from xwiki-enterprise to xwiki-platform so that they are grouped by functional domain. Thus xwiki-enterprise-test-ui is not the best example. You should take a look at the platform modules that have functional tests:
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik...
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik...
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik...
to name a few. The packager maven plugin is taking care of importing (installing) your XAR and (I believe) adding the required jar dependencies to the WAR. You should follow this practice.
Hope this helps, Marius
On Wed, Mar 20, 2013 at 1:07 PM, Jeremie BOUSQUET <[email protected]> wrote:
Hello,
I would like to discuss a little on writing of Selenium2 tests, as described in test strategy [1], ie use Selenium 2 and apply Page Objects pattern.
My particular use-case is that I'm on a mission : write some functional tests for my mail archive application. I also think these would be the best tests for my app, as it greatly relies on 2 external interfaces (xwiki for persistence/conf, javamail and mail accounts on another side). There are some good unit tests to write of course, but the main logic of the app has more meaning to be tested in "real life", or close to that.
To do that, I decided to try and plug myself in xwiki test framework, in order to avoid redeveloping everything (such as deploying / launching an xwiki instance from the tests). I added 2 modules in my project: - xwiki-contrib-mailarchive-test-pageobjects - xwiki-contrib-mailarchive-test-ui
Both inherit from org.xwiki.enterprise:xwiki-enterprise-test pom, and are greatly inspired from poms of xwiki-enterprise-test-pageobjects and xwiki-enterprise-test-ui poms. It's unfinished and untested, but I believe I'll be able to have xwiki instance installed, launched, and tests run automatically.
My main question, is how should I do in order to also deploy my app in this wiki instance prior to run the tests ? For now I have several possible solutions that come to my mind, but I don't know what would be the best... : A- - grab xwiki-standalone zip version x.y.z, unzip it, launch it - make EM install my application (call some REST API ? GET some page with proper parameters ?) - run the tests B- - grab xwiki-standalone zip version x.y.z, unzip it - "patch" it in some way with my application binaries, (ie, add things directly under permanent directory / extension / repository ?) - launch it and run the tests
I personnally prefer A-, but it supposes also that the xwiki instance knows any of my "dev" maven repositories (either my local repository .m2, or my local instance of Nexus), so it would mean an additional step would be to "patch" the standalone wiki xwiki.properties to add my personal repo. Or maybe I can add such repo programmatically in the wiki instance from java by looking up and using the right component ?
Maybe this point has already been solved by anyone, so if you have any samples it would be good enough. I did not search exhaustively, but I don't remember having seen such use-cases on existing extensions on github. Also, I think it might be interesting to extract from all this some kind of maven archetype for functional testing of UI extension ? So contributors could just call the archetype and get everything properly prepared, and just have to add page objects and tests for their app ...
WDYT ?
BR, Jeremie
[1]
http://dev.xwiki.org/xwiki/bin/view/Community/Testing#HSelenium2-basedFramew...
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
On Tue, Mar 26, 2013 at 3:44 PM, Jeremie BOUSQUET <[email protected]> wrote:
Hi again,
On this topic I created a new JIRA: http://jira.xwiki.org/browse/XWIKI-8960
Indeed, I can reproduce locally. It seems you are the first to use the packager plugin outside platform and we didn't took this use case into account. I'll try to fix the packager plugin asap. Thanks, Marius
... and proposed some sort of solution as a comment. If you agree with the problem and proposal, I could try to contribute a patch, as anyway I need it for the mailarchive tests. Of course if you want to fix it I don't disagree :-)
BR, Jeremie
2013/3/25 Jeremie BOUSQUET <[email protected]>
I think the problem lies on this kind of expressions [1] ...
The packager plugin defines version for all mandatory platform artifacts with "this.getProject().getVersion()", meaning if I'm correct that it returns correct version only if project is part of xwiki platform - or if it shares the same version. Maybe it should use property "platform.version" instead ?
BR, Jeremie
[1] https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-tools/xwi...
2013/3/25 Jeremie BOUSQUET <[email protected]>
Note: it goes a bit further if I declare a bunch of xwiki platform dependencies in my pom, but breaks again, trying to look at those platform artifacts for version ${project.version} instead of ${platform.version} :
[INFO] Copying JAR dependencies ... [WARNING] Missing POM for org.xwiki.platform:xwiki-platform-wysiwyg-server:jar:0.3-SNAPSHOT [WARNING] Missing POM for org.xwiki.platform:xwiki-platform-localization-script:jar:0.3-SNAPSHOT [WARNING] Missing POM for org.xwiki.platform:xwiki-platform-oldcore:jar:0.3-SNAPSHOT [...] [ERROR] Failed to execute goal org.xwiki.platform:xwiki-platform-tool-packager-plugi datory artifacts: Missing: [ERROR] ---------- [ERROR] 1) org.xwiki.platform:xwiki-platform-localization-script:jar:0.3-SNAPSHOT [ERROR] [ERROR] Try downloading the file manually from the project website. [...] Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to resolve mandatory artifacts at org.xwiki.tool.packager.PackageMojo.resolveTransitively(PackageMojo.java:614) at org.xwiki.tool.packager.PackageMojo.resolveJarArtifacts(PackageMojo.java:543) at org.xwiki.tool.packager.PackageMojo.execute(PackageMojo.java:209) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more
2013/3/25 Jeremie BOUSQUET <[email protected]>
Hummm, running through a strange issue during build:
[ERROR] Failed to execute goal org.xwiki.platform:xwiki-platform-tool-packager-plugin:4.5.2:package (default) on project xwiki-contrib-mailarchive-test-tests: Failed to resolve art ifact [org.xwiki.platform:xwiki-platform-tool-jetty-resources:zip:0.3-SNAPSHOT:]: Failure to find org.xwiki.platform:xwiki-platform-tool-jetty-resources:zip:0.3-SNAPSHOT in http:// nexus.xwiki.org/nexus/content/groups/public-snapshots was cached in the local repository, resolution will not be reattempted until the update interval of xwiki-snapshots has elapse d or updates are forced
4.5.2 is ${platform.version}, 0.3-SNAPSHOT is ${project.version}. The packager plugin is declared in my pom in version ${platform.version} of course.
Surprisingly though, here's an extract of the output of "dependency:resolve-plugins":
[INFO] Plugin Resolved: xwiki-platform-tool-packager-plugin-4.5.2.jar [...] [INFO] Plugin Dependency Resolved: xwiki-platform-tool-jetty-resources-4.5.2.zip [...]
Seems that it finds correct 4.5.2 version for same dependency, that it doesn't find at runtime ... Maybe an issue on packager plugin, "invisible" until you use it on a non-xwiki project ? :-)
BR, Jeremie
2013/3/25 Jeremie BOUSQUET <[email protected]>
Thanks Marius, that's exactly what I was looking for ! I'll follow that practice,
BR, Jeremie
2013/3/20 Marius Dumitru Florea <[email protected]>
Hi Jeremie,
We have started moving functional tests from xwiki-enterprise to xwiki-platform so that they are grouped by functional domain. Thus xwiki-enterprise-test-ui is not the best example. You should take a look at the platform modules that have functional tests:
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik...
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik...
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik...
to name a few. The packager maven plugin is taking care of importing (installing) your XAR and (I believe) adding the required jar dependencies to the WAR. You should follow this practice.
Hope this helps, Marius
On Wed, Mar 20, 2013 at 1:07 PM, Jeremie BOUSQUET <[email protected]> wrote: > Hello, > > I would like to discuss a little on writing of Selenium2 tests, as > described in test strategy [1], ie use Selenium 2 and apply Page Objects > pattern. > > My particular use-case is that I'm on a mission : write some functional > tests for my mail archive application. > I also think these would be the best tests for my app, as it greatly relies > on 2 external interfaces (xwiki for persistence/conf, javamail and mail > accounts on another side). There are some good unit tests to write of > course, but the main logic of the app has more meaning to be tested in > "real life", or close to that. > > To do that, I decided to try and plug myself in xwiki test framework, in > order to avoid redeveloping everything (such as deploying / launching an > xwiki instance from the tests). > I added 2 modules in my project: > - xwiki-contrib-mailarchive-test-pageobjects > - xwiki-contrib-mailarchive-test-ui > > Both inherit from org.xwiki.enterprise:xwiki-enterprise-test pom, and are > greatly inspired from poms of xwiki-enterprise-test-pageobjects and > xwiki-enterprise-test-ui poms. > It's unfinished and untested, but I believe I'll be able to have xwiki > instance installed, launched, and tests run automatically. > > My main question, is how should I do in order to also deploy my app in this > wiki instance prior to run the tests ? > For now I have several possible solutions that come to my mind, but I don't > know what would be the best... : > A- > - grab xwiki-standalone zip version x.y.z, unzip it, launch it > - make EM install my application (call some REST API ? GET some page with > proper parameters ?) > - run the tests > B- > - grab xwiki-standalone zip version x.y.z, unzip it > - "patch" it in some way with my application binaries, (ie, add things > directly under permanent directory / extension / repository ?) > - launch it and run the tests > > I personnally prefer A-, but it supposes also that the xwiki instance knows > any of my "dev" maven repositories (either my local repository .m2, or my > local instance of Nexus), so it would mean an additional step would be to > "patch" the standalone wiki xwiki.properties to add my personal repo. > Or maybe I can add such repo programmatically in the wiki instance from > java by looking up and using the right component ? > > Maybe this point has already been solved by anyone, so if you have any > samples it would be good enough. I did not search exhaustively, but I don't > remember having seen such use-cases on existing extensions on github. > Also, I think it might be interesting to extract from all this some kind of > maven archetype for functional testing of UI extension ? So contributors > could just call the archetype and get everything properly prepared, and > just have to add page objects and tests for their app ... > > WDYT ? > > BR, > Jeremie > > > [1] > http://dev.xwiki.org/xwiki/bin/view/Community/Testing#HSelenium2-basedFramew... > _______________________________________________ > users mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/users _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
Hi, I proposed a pull request to fix XWIKI-8960: https://github.com/xwiki/xwiki-platform/pull/89 Seems to work well, and I added an IT test to check it. I'm not sure of the naming though ... It's my first pull request so I hope I did things correctly :-) Br, Jeremie 2013/3/27 Marius Dumitru Florea <[email protected]>
On Tue, Mar 26, 2013 at 3:44 PM, Jeremie BOUSQUET <[email protected]> wrote:
Hi again,
On this topic I created a new JIRA: http://jira.xwiki.org/browse/XWIKI-8960
Indeed, I can reproduce locally. It seems you are the first to use the packager plugin outside platform and we didn't took this use case into account. I'll try to fix the packager plugin asap.
Thanks, Marius
... and proposed some sort of solution as a comment. If you agree with the problem and proposal, I could try to contribute a patch, as anyway I need it for the mailarchive tests. Of course if you want to fix it I don't disagree :-)
BR, Jeremie
2013/3/25 Jeremie BOUSQUET <[email protected]>
I think the problem lies on this kind of expressions [1] ...
The packager plugin defines version for all mandatory platform artifacts with "this.getProject().getVersion()", meaning if I'm correct that it returns correct version only if project is part of xwiki platform - or
if
it shares the same version. Maybe it should use property "platform.version" instead ?
BR, Jeremie
[1]
https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-tools/xwi...
2013/3/25 Jeremie BOUSQUET <[email protected]>
Note: it goes a bit further if I declare a bunch of xwiki platform dependencies in my pom, but breaks again, trying to look at those
platform
artifacts for version ${project.version} instead of ${platform.version} :
[INFO] Copying JAR dependencies ... [WARNING] Missing POM for org.xwiki.platform:xwiki-platform-wysiwyg-server:jar:0.3-SNAPSHOT [WARNING] Missing POM for org.xwiki.platform:xwiki-platform-localization-script:jar:0.3-SNAPSHOT [WARNING] Missing POM for org.xwiki.platform:xwiki-platform-oldcore:jar:0.3-SNAPSHOT [...] [ERROR] Failed to execute goal org.xwiki.platform:xwiki-platform-tool-packager-plugi datory artifacts: Missing: [ERROR] ---------- [ERROR] 1) org.xwiki.platform:xwiki-platform-localization-script:jar:0.3-SNAPSHOT [ERROR] [ERROR] Try downloading the file manually from the project website. [...] Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to resolve mandatory artifacts at
org.xwiki.tool.packager.PackageMojo.resolveTransitively(PackageMojo.java:614)
at
org.xwiki.tool.packager.PackageMojo.resolveJarArtifacts(PackageMojo.java:543)
at org.xwiki.tool.packager.PackageMojo.execute(PackageMojo.java:209) at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
2013/3/25 Jeremie BOUSQUET <[email protected]>
Hummm, running through a strange issue during build:
[ERROR] Failed to execute goal org.xwiki.platform:xwiki-platform-tool-packager-plugin:4.5.2:package (default) on project xwiki-contrib-mailarchive-test-tests: Failed to resolve art ifact
[org.xwiki.platform:xwiki-platform-tool-jetty-resources:zip:0.3-SNAPSHOT:]:
Failure to find
org.xwiki.platform:xwiki-platform-tool-jetty-resources:zip:0.3-SNAPSHOT in
http:// nexus.xwiki.org/nexus/content/groups/public-snapshots was cached in the local repository, resolution will not be reattempted until the update interval of xwiki-snapshots has elapse d or updates are forced
4.5.2 is ${platform.version}, 0.3-SNAPSHOT is ${project.version}. The packager plugin is declared in my pom in version ${platform.version} of course.
Surprisingly though, here's an extract of the output of "dependency:resolve-plugins":
[INFO] Plugin Resolved: xwiki-platform-tool-packager-plugin-4.5.2.jar [...] [INFO] Plugin Dependency Resolved: xwiki-platform-tool-jetty-resources-4.5.2.zip [...]
Seems that it finds correct 4.5.2 version for same dependency, that it doesn't find at runtime ... Maybe an issue on packager plugin, "invisible" until you use it on a non-xwiki project ? :-)
BR, Jeremie
2013/3/25 Jeremie BOUSQUET <[email protected]>
Thanks Marius, that's exactly what I was looking for ! I'll follow that practice,
BR, Jeremie
2013/3/20 Marius Dumitru Florea <[email protected]>
> Hi Jeremie, > > We have started moving functional tests from xwiki-enterprise to > xwiki-platform so that they are grouped by functional domain. Thus > xwiki-enterprise-test-ui is not the best example. You should take a > look at the platform modules that have functional tests: > > > https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik... > > https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik... > > https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik... > > to name a few. The packager maven plugin is taking care of importing > (installing) your XAR and (I believe) adding the required jar > dependencies to the WAR. You should follow this practice. > > Hope this helps, > Marius > > On Wed, Mar 20, 2013 at 1:07 PM, Jeremie BOUSQUET > <[email protected]> wrote: > > Hello, > > > > I would like to discuss a little on writing of Selenium2 tests, as > > described in test strategy [1], ie use Selenium 2 and apply Page > Objects > > pattern. > > > > My particular use-case is that I'm on a mission : write some > functional > > tests for my mail archive application. > > I also think these would be the best tests for my app, as it greatly > relies > > on 2 external interfaces (xwiki for persistence/conf, javamail and > mail > > accounts on another side). There are some good unit tests to write of > > course, but the main logic of the app has more meaning to be tested > in > > "real life", or close to that. > > > > To do that, I decided to try and plug myself in xwiki test > framework, in > > order to avoid redeveloping everything (such as deploying / > launching an > > xwiki instance from the tests). > > I added 2 modules in my project: > > - xwiki-contrib-mailarchive-test-pageobjects > > - xwiki-contrib-mailarchive-test-ui > > > > Both inherit from org.xwiki.enterprise:xwiki-enterprise-test pom, > and are > > greatly inspired from poms of xwiki-enterprise-test-pageobjects and > > xwiki-enterprise-test-ui poms. > > It's unfinished and untested, but I believe I'll be able to have > xwiki > > instance installed, launched, and tests run automatically. > > > > My main question, is how should I do in order to also deploy my app > in this > > wiki instance prior to run the tests ? > > For now I have several possible solutions that come to my mind, but > I don't > > know what would be the best... : > > A- > > - grab xwiki-standalone zip version x.y.z, unzip it, launch it > > - make EM install my application (call some REST API ? GET some > page with > > proper parameters ?) > > - run the tests > > B- > > - grab xwiki-standalone zip version x.y.z, unzip it > > - "patch" it in some way with my application binaries, (ie, add > things > > directly under permanent directory / extension / repository ?) > > - launch it and run the tests > > > > I personnally prefer A-, but it supposes also that the xwiki > instance knows > > any of my "dev" maven repositories (either my local repository .m2, > or my > > local instance of Nexus), so it would mean an additional step would > be to > > "patch" the standalone wiki xwiki.properties to add my personal repo. > > Or maybe I can add such repo programmatically in the wiki instance > from > > java by looking up and using the right component ? > > > > Maybe this point has already been solved by anyone, so if you have > any > > samples it would be good enough. I did not search exhaustively, but > I don't > > remember having seen such use-cases on existing extensions on github. > > Also, I think it might be interesting to extract from all this some > kind of > > maven archetype for functional testing of UI extension ? So > contributors > > could just call the archetype and get everything properly prepared, > and > > just have to add page objects and tests for their app ... > > > > WDYT ? > > > > BR, > > Jeremie > > > > > > [1] > > > http://dev.xwiki.org/xwiki/bin/view/Community/Testing#HSelenium2-basedFramew... > > _______________________________________________ > > users mailing list > > [email protected] > > http://lists.xwiki.org/mailman/listinfo/users > _______________________________________________ > users mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/users >
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
On Thu, Mar 28, 2013 at 2:36 PM, Jeremie BOUSQUET <[email protected]> wrote:
Hi,
I proposed a pull request to fix XWIKI-8960: https://github.com/xwiki/xwiki-platform/pull/89
Seems to work well, and I added an IT test to check it. I'm not sure of the naming though ... It's my first pull request so I hope I did things correctly :-)
Looks good to me, applied it.
Br, Jeremie
2013/3/27 Marius Dumitru Florea <[email protected]>
On Tue, Mar 26, 2013 at 3:44 PM, Jeremie BOUSQUET <[email protected]> wrote:
Hi again,
On this topic I created a new JIRA: http://jira.xwiki.org/browse/XWIKI-8960
Indeed, I can reproduce locally. It seems you are the first to use the packager plugin outside platform and we didn't took this use case into account. I'll try to fix the packager plugin asap.
Thanks, Marius
... and proposed some sort of solution as a comment. If you agree with the problem and proposal, I could try to contribute a patch, as anyway I need it for the mailarchive tests. Of course if you want to fix it I don't disagree :-)
BR, Jeremie
2013/3/25 Jeremie BOUSQUET <[email protected]>
I think the problem lies on this kind of expressions [1] ...
The packager plugin defines version for all mandatory platform artifacts with "this.getProject().getVersion()", meaning if I'm correct that it returns correct version only if project is part of xwiki platform - or
if
it shares the same version. Maybe it should use property "platform.version" instead ?
BR, Jeremie
[1]
https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-tools/xwi...
2013/3/25 Jeremie BOUSQUET <[email protected]>
Note: it goes a bit further if I declare a bunch of xwiki platform dependencies in my pom, but breaks again, trying to look at those
platform
artifacts for version ${project.version} instead of ${platform.version} :
[INFO] Copying JAR dependencies ... [WARNING] Missing POM for org.xwiki.platform:xwiki-platform-wysiwyg-server:jar:0.3-SNAPSHOT [WARNING] Missing POM for org.xwiki.platform:xwiki-platform-localization-script:jar:0.3-SNAPSHOT [WARNING] Missing POM for org.xwiki.platform:xwiki-platform-oldcore:jar:0.3-SNAPSHOT [...] [ERROR] Failed to execute goal org.xwiki.platform:xwiki-platform-tool-packager-plugi datory artifacts: Missing: [ERROR] ---------- [ERROR] 1) org.xwiki.platform:xwiki-platform-localization-script:jar:0.3-SNAPSHOT [ERROR] [ERROR] Try downloading the file manually from the project website. [...] Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to resolve mandatory artifacts at
org.xwiki.tool.packager.PackageMojo.resolveTransitively(PackageMojo.java:614)
at
org.xwiki.tool.packager.PackageMojo.resolveJarArtifacts(PackageMojo.java:543)
at org.xwiki.tool.packager.PackageMojo.execute(PackageMojo.java:209) at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
2013/3/25 Jeremie BOUSQUET <[email protected]>
Hummm, running through a strange issue during build:
[ERROR] Failed to execute goal org.xwiki.platform:xwiki-platform-tool-packager-plugin:4.5.2:package (default) on project xwiki-contrib-mailarchive-test-tests: Failed to resolve art ifact
[org.xwiki.platform:xwiki-platform-tool-jetty-resources:zip:0.3-SNAPSHOT:]:
Failure to find
org.xwiki.platform:xwiki-platform-tool-jetty-resources:zip:0.3-SNAPSHOT in
http:// nexus.xwiki.org/nexus/content/groups/public-snapshots was cached in the local repository, resolution will not be reattempted until the update interval of xwiki-snapshots has elapse d or updates are forced
4.5.2 is ${platform.version}, 0.3-SNAPSHOT is ${project.version}. The packager plugin is declared in my pom in version ${platform.version} of course.
Surprisingly though, here's an extract of the output of "dependency:resolve-plugins":
[INFO] Plugin Resolved: xwiki-platform-tool-packager-plugin-4.5.2.jar [...] [INFO] Plugin Dependency Resolved: xwiki-platform-tool-jetty-resources-4.5.2.zip [...]
Seems that it finds correct 4.5.2 version for same dependency, that it doesn't find at runtime ... Maybe an issue on packager plugin, "invisible" until you use it on a non-xwiki project ? :-)
BR, Jeremie
2013/3/25 Jeremie BOUSQUET <[email protected]>
> Thanks Marius, that's exactly what I was looking for ! > I'll follow that practice, > > BR, > Jeremie > > > 2013/3/20 Marius Dumitru Florea <[email protected]> > >> Hi Jeremie, >> >> We have started moving functional tests from xwiki-enterprise to >> xwiki-platform so that they are grouped by functional domain. Thus >> xwiki-enterprise-test-ui is not the best example. You should take a >> look at the platform modules that have functional tests: >> >> >> https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik... >> >> https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik... >> >> https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik... >> >> to name a few. The packager maven plugin is taking care of importing >> (installing) your XAR and (I believe) adding the required jar >> dependencies to the WAR. You should follow this practice. >> >> Hope this helps, >> Marius >> >> On Wed, Mar 20, 2013 at 1:07 PM, Jeremie BOUSQUET >> <[email protected]> wrote: >> > Hello, >> > >> > I would like to discuss a little on writing of Selenium2 tests, as >> > described in test strategy [1], ie use Selenium 2 and apply Page >> Objects >> > pattern. >> > >> > My particular use-case is that I'm on a mission : write some >> functional >> > tests for my mail archive application. >> > I also think these would be the best tests for my app, as it greatly >> relies >> > on 2 external interfaces (xwiki for persistence/conf, javamail and >> mail >> > accounts on another side). There are some good unit tests to write of >> > course, but the main logic of the app has more meaning to be tested >> in >> > "real life", or close to that. >> > >> > To do that, I decided to try and plug myself in xwiki test >> framework, in >> > order to avoid redeveloping everything (such as deploying / >> launching an >> > xwiki instance from the tests). >> > I added 2 modules in my project: >> > - xwiki-contrib-mailarchive-test-pageobjects >> > - xwiki-contrib-mailarchive-test-ui >> > >> > Both inherit from org.xwiki.enterprise:xwiki-enterprise-test pom, >> and are >> > greatly inspired from poms of xwiki-enterprise-test-pageobjects and >> > xwiki-enterprise-test-ui poms. >> > It's unfinished and untested, but I believe I'll be able to have >> xwiki >> > instance installed, launched, and tests run automatically. >> > >> > My main question, is how should I do in order to also deploy my app >> in this >> > wiki instance prior to run the tests ? >> > For now I have several possible solutions that come to my mind, but >> I don't >> > know what would be the best... : >> > A- >> > - grab xwiki-standalone zip version x.y.z, unzip it, launch it >> > - make EM install my application (call some REST API ? GET some >> page with >> > proper parameters ?) >> > - run the tests >> > B- >> > - grab xwiki-standalone zip version x.y.z, unzip it >> > - "patch" it in some way with my application binaries, (ie, add >> things >> > directly under permanent directory / extension / repository ?) >> > - launch it and run the tests >> > >> > I personnally prefer A-, but it supposes also that the xwiki >> instance knows >> > any of my "dev" maven repositories (either my local repository .m2, >> or my >> > local instance of Nexus), so it would mean an additional step would >> be to >> > "patch" the standalone wiki xwiki.properties to add my personal repo. >> > Or maybe I can add such repo programmatically in the wiki instance >> from >> > java by looking up and using the right component ? >> > >> > Maybe this point has already been solved by anyone, so if you have >> any >> > samples it would be good enough. I did not search exhaustively, but >> I don't >> > remember having seen such use-cases on existing extensions on github. >> > Also, I think it might be interesting to extract from all this some >> kind of >> > maven archetype for functional testing of UI extension ? So >> contributors >> > could just call the archetype and get everything properly prepared, >> and >> > just have to add page objects and tests for their app ... >> > >> > WDYT ? >> > >> > BR, >> > Jeremie >> > >> > >> > [1] >> > >> http://dev.xwiki.org/xwiki/bin/view/Community/Testing#HSelenium2-basedFramew... >> > _______________________________________________ >> > users mailing list >> > [email protected] >> > http://lists.xwiki.org/mailman/listinfo/users >> _______________________________________________ >> users mailing list >> [email protected] >> http://lists.xwiki.org/mailman/listinfo/users >> > >
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Thomas Mortagne
Thanks ! Jeremie 2013/3/28 Thomas Mortagne <[email protected]>
On Thu, Mar 28, 2013 at 2:36 PM, Jeremie BOUSQUET <[email protected]> wrote:
Hi,
I proposed a pull request to fix XWIKI-8960: https://github.com/xwiki/xwiki-platform/pull/89
Seems to work well, and I added an IT test to check it. I'm not sure of the naming though ... It's my first pull request so I hope I did things correctly :-)
Looks good to me, applied it.
Br, Jeremie
2013/3/27 Marius Dumitru Florea <[email protected]>
On Tue, Mar 26, 2013 at 3:44 PM, Jeremie BOUSQUET <[email protected]> wrote:
Hi again,
On this topic I created a new JIRA: http://jira.xwiki.org/browse/XWIKI-8960
Indeed, I can reproduce locally. It seems you are the first to use the packager plugin outside platform and we didn't took this use case into account. I'll try to fix the packager plugin asap.
Thanks, Marius
... and proposed some sort of solution as a comment. If you agree with the problem and proposal, I could try to contribute
a
patch, as anyway I need it for the mailarchive tests. Of course if you want to fix it I don't disagree :-)
BR, Jeremie
2013/3/25 Jeremie BOUSQUET <[email protected]>
I think the problem lies on this kind of expressions [1] ...
The packager plugin defines version for all mandatory platform artifacts with "this.getProject().getVersion()", meaning if I'm correct that it returns correct version only if project is part of xwiki platform - or if it shares the same version. Maybe it should use property "platform.version" instead ?
BR, Jeremie
[1]
https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-tools/xwi...
2013/3/25 Jeremie BOUSQUET <[email protected]>
Note: it goes a bit further if I declare a bunch of xwiki platform dependencies in my pom, but breaks again, trying to look at those
platform
artifacts for version ${project.version} instead of ${platform.version} :
[INFO] Copying JAR dependencies ... [WARNING] Missing POM for org.xwiki.platform:xwiki-platform-wysiwyg-server:jar:0.3-SNAPSHOT [WARNING] Missing POM for
org.xwiki.platform:xwiki-platform-localization-script:jar:0.3-SNAPSHOT
[WARNING] Missing POM for org.xwiki.platform:xwiki-platform-oldcore:jar:0.3-SNAPSHOT [...] [ERROR] Failed to execute goal org.xwiki.platform:xwiki-platform-tool-packager-plugi datory artifacts: Missing: [ERROR] ---------- [ERROR] 1)
org.xwiki.platform:xwiki-platform-localization-script:jar:0.3-SNAPSHOT
[ERROR] [ERROR] Try downloading the file manually from the project website. [...] Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to resolve mandatory artifacts at
org.xwiki.tool.packager.PackageMojo.resolveTransitively(PackageMojo.java:614)
at
org.xwiki.tool.packager.PackageMojo.resolveJarArtifacts(PackageMojo.java:543)
at org.xwiki.tool.packager.PackageMojo.execute(PackageMojo.java:209) at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
2013/3/25 Jeremie BOUSQUET <[email protected]>
> Hummm, running through a strange issue during build: > > [ERROR] Failed to execute goal >
org.xwiki.platform:xwiki-platform-tool-packager-plugin:4.5.2:package
> (default) on project xwiki-contrib-mailarchive-test-tests: Failed to > resolve art > ifact >
[org.xwiki.platform:xwiki-platform-tool-jetty-resources:zip:0.3-SNAPSHOT:]:
> Failure to find > org.xwiki.platform:xwiki-platform-tool-jetty-resources:zip:0.3-SNAPSHOT in > http:// > nexus.xwiki.org/nexus/content/groups/public-snapshots was cached in the > local repository, resolution will not be reattempted until the update > interval of xwiki-snapshots has elapse > d or updates are forced > > 4.5.2 is ${platform.version}, 0.3-SNAPSHOT is ${project.version}. The > packager plugin is declared in my pom in version ${platform.version} of > course. > > Surprisingly though, here's an extract of the output of > "dependency:resolve-plugins": > > [INFO] Plugin Resolved: xwiki-platform-tool-packager-plugin-4.5.2.jar > [...] > [INFO] Plugin Dependency Resolved: > xwiki-platform-tool-jetty-resources-4.5.2.zip > [...] > > Seems that it finds correct 4.5.2 version for same dependency, that it > doesn't find at runtime ... Maybe an issue on packager plugin, "invisible" > until you use it on a non-xwiki project ? :-) > > BR, > Jeremie > > > > > > 2013/3/25 Jeremie BOUSQUET <[email protected]> > >> Thanks Marius, that's exactly what I was looking for ! >> I'll follow that practice, >> >> BR, >> Jeremie >> >> >> 2013/3/20 Marius Dumitru Florea <[email protected]> >> >>> Hi Jeremie, >>> >>> We have started moving functional tests from xwiki-enterprise to >>> xwiki-platform so that they are grouped by functional domain. Thus >>> xwiki-enterprise-test-ui is not the best example. You should take a >>> look at the platform modules that have functional tests: >>> >>> >>>
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik...
>>> >>>
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik...
>>> >>>
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik...
>>> >>> to name a few. The packager maven plugin is taking care of importing >>> (installing) your XAR and (I believe) adding the required jar >>> dependencies to the WAR. You should follow this practice. >>> >>> Hope this helps, >>> Marius >>> >>> On Wed, Mar 20, 2013 at 1:07 PM, Jeremie BOUSQUET >>> <[email protected]> wrote: >>> > Hello, >>> > >>> > I would like to discuss a little on writing of Selenium2 tests, as >>> > described in test strategy [1], ie use Selenium 2 and apply Page >>> Objects >>> > pattern. >>> > >>> > My particular use-case is that I'm on a mission : write some >>> functional >>> > tests for my mail archive application. >>> > I also think these would be the best tests for my app, as it greatly >>> relies >>> > on 2 external interfaces (xwiki for persistence/conf, javamail and >>> mail >>> > accounts on another side). There are some good unit tests to write of >>> > course, but the main logic of the app has more meaning to be tested >>> in >>> > "real life", or close to that. >>> > >>> > To do that, I decided to try and plug myself in xwiki test >>> framework, in >>> > order to avoid redeveloping everything (such as deploying / >>> launching an >>> > xwiki instance from the tests). >>> > I added 2 modules in my project: >>> > - xwiki-contrib-mailarchive-test-pageobjects >>> > - xwiki-contrib-mailarchive-test-ui >>> > >>> > Both inherit from org.xwiki.enterprise:xwiki-enterprise-test pom, >>> and are >>> > greatly inspired from poms of xwiki-enterprise-test-pageobjects and >>> > xwiki-enterprise-test-ui poms. >>> > It's unfinished and untested, but I believe I'll be able to have >>> xwiki >>> > instance installed, launched, and tests run automatically. >>> > >>> > My main question, is how should I do in order to also deploy my app >>> in this >>> > wiki instance prior to run the tests ? >>> > For now I have several possible solutions that come to my mind, but >>> I don't >>> > know what would be the best... : >>> > A- >>> > - grab xwiki-standalone zip version x.y.z, unzip it, launch it >>> > - make EM install my application (call some REST API ? GET some >>> page with >>> > proper parameters ?) >>> > - run the tests >>> > B- >>> > - grab xwiki-standalone zip version x.y.z, unzip it >>> > - "patch" it in some way with my application binaries, (ie, add >>> things >>> > directly under permanent directory / extension / repository ?) >>> > - launch it and run the tests >>> > >>> > I personnally prefer A-, but it supposes also that the xwiki >>> instance knows >>> > any of my "dev" maven repositories (either my local repository .m2, >>> or my >>> > local instance of Nexus), so it would mean an additional step would >>> be to >>> > "patch" the standalone wiki xwiki.properties to add my personal repo. >>> > Or maybe I can add such repo programmatically in the wiki instance >>> from >>> > java by looking up and using the right component ? >>> > >>> > Maybe this point has already been solved by anyone, so if you have >>> any >>> > samples it would be good enough. I did not search exhaustively, but >>> I don't >>> > remember having seen such use-cases on existing extensions on github. >>> > Also, I think it might be interesting to extract from all this some >>> kind of >>> > maven archetype for functional testing of UI extension ? So >>> contributors >>> > could just call the archetype and get everything properly prepared, >>> and >>> > just have to add page objects and tests for their app ... >>> > >>> > WDYT ? >>> > >>> > BR, >>> > Jeremie >>> > >>> > >>> > [1] >>> > >>>
http://dev.xwiki.org/xwiki/bin/view/Community/Testing#HSelenium2-basedFramew...
>>> > _______________________________________________ >>> > users mailing list >>> > [email protected] >>> > http://lists.xwiki.org/mailman/listinfo/users >>> _______________________________________________ >>> users mailing list >>> [email protected] >>> http://lists.xwiki.org/mailman/listinfo/users >>> >> >> >
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Thomas Mortagne _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
Hello, Me again ... :-) With fixed version of packager plugin, things go better now. XWiki is downloaded and launched, my test browses to the page as I expect. Problem is that when browsing to my page, I can see the following in the html content logged by the build: <div id="xwikicontent"> <div class="xwikirenderingerror" style="cursor: pointer;" title="Read technical information related to this error">Unknown macro: velocity[...] In fact, it seems wiki is running, but can't find any macro ... I tried to add a dependency on xwiki-enterprise-ui-all xar, but with same result. I'm not sure of what could be missing ? BR, Jeremie 2013/3/28 Jeremie BOUSQUET <[email protected]>
Thanks !
Jeremie
2013/3/28 Thomas Mortagne <[email protected]>
On Thu, Mar 28, 2013 at 2:36 PM, Jeremie BOUSQUET <[email protected]> wrote:
Hi,
I proposed a pull request to fix XWIKI-8960: https://github.com/xwiki/xwiki-platform/pull/89
Seems to work well, and I added an IT test to check it. I'm not sure of the naming though ... It's my first pull request so I hope I did things correctly :-)
Looks good to me, applied it.
Br, Jeremie
2013/3/27 Marius Dumitru Florea <[email protected]>
On Tue, Mar 26, 2013 at 3:44 PM, Jeremie BOUSQUET <[email protected]> wrote:
Hi again,
On this topic I created a new JIRA: http://jira.xwiki.org/browse/XWIKI-8960
Indeed, I can reproduce locally. It seems you are the first to use the packager plugin outside platform and we didn't took this use case into account. I'll try to fix the packager plugin asap.
Thanks, Marius
... and proposed some sort of solution as a comment. If you agree with the problem and proposal, I could try to
contribute a
patch, as anyway I need it for the mailarchive tests. Of course if you want to fix it I don't disagree :-)
BR, Jeremie
2013/3/25 Jeremie BOUSQUET <[email protected]>
I think the problem lies on this kind of expressions [1] ...
The packager plugin defines version for all mandatory platform artifacts with "this.getProject().getVersion()", meaning if I'm correct that it returns correct version only if project is part of xwiki platform - or if it shares the same version. Maybe it should use property "platform.version" instead ?
BR, Jeremie
[1]
https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-tools/xwi...
2013/3/25 Jeremie BOUSQUET <[email protected]>
> Note: it goes a bit further if I declare a bunch of xwiki platform > dependencies in my pom, but breaks again, trying to look at those
platform
> artifacts for version ${project.version} instead of ${platform.version} : > > [INFO] Copying JAR dependencies ... > [WARNING] Missing POM for > org.xwiki.platform:xwiki-platform-wysiwyg-server:jar:0.3-SNAPSHOT > [WARNING] Missing POM for > org.xwiki.platform:xwiki-platform-localization-script:jar:0.3-SNAPSHOT > [WARNING] Missing POM for > org.xwiki.platform:xwiki-platform-oldcore:jar:0.3-SNAPSHOT > [...] > [ERROR] Failed to execute goal > org.xwiki.platform:xwiki-platform-tool-packager-plugi > datory artifacts: Missing: > [ERROR] ---------- > [ERROR] 1) > org.xwiki.platform:xwiki-platform-localization-script:jar:0.3-SNAPSHOT > [ERROR] > [ERROR] Try downloading the file manually from the project website. > [...] > Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to > resolve mandatory artifacts > at >
org.xwiki.tool.packager.PackageMojo.resolveTransitively(PackageMojo.java:614)
> at >
org.xwiki.tool.packager.PackageMojo.resolveJarArtifacts(PackageMojo.java:543)
> at > org.xwiki.tool.packager.PackageMojo.execute(PackageMojo.java:209) > at >
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at >
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 19 more > > > 2013/3/25 Jeremie BOUSQUET <[email protected]> > >> Hummm, running through a strange issue during build: >> >> [ERROR] Failed to execute goal >> org.xwiki.platform:xwiki-platform-tool-packager-plugin:4.5.2:package >> (default) on project xwiki-contrib-mailarchive-test-tests: Failed to >> resolve art >> ifact >>
[org.xwiki.platform:xwiki-platform-tool-jetty-resources:zip:0.3-SNAPSHOT:]:
>> Failure to find >>
org.xwiki.platform:xwiki-platform-tool-jetty-resources:zip:0.3-SNAPSHOT in
>> http:// >> nexus.xwiki.org/nexus/content/groups/public-snapshots was cached in the >> local repository, resolution will not be reattempted until the update >> interval of xwiki-snapshots has elapse >> d or updates are forced >> >> 4.5.2 is ${platform.version}, 0.3-SNAPSHOT is ${project.version}. The >> packager plugin is declared in my pom in version ${platform.version} of >> course. >> >> Surprisingly though, here's an extract of the output of >> "dependency:resolve-plugins": >> >> [INFO] Plugin Resolved: xwiki-platform-tool-packager-plugin-4.5.2.jar >> [...] >> [INFO] Plugin Dependency Resolved: >> xwiki-platform-tool-jetty-resources-4.5.2.zip >> [...] >> >> Seems that it finds correct 4.5.2 version for same dependency, that it >> doesn't find at runtime ... Maybe an issue on packager plugin, "invisible" >> until you use it on a non-xwiki project ? :-) >> >> BR, >> Jeremie >> >> >> >> >> >> 2013/3/25 Jeremie BOUSQUET <[email protected]> >> >>> Thanks Marius, that's exactly what I was looking for ! >>> I'll follow that practice, >>> >>> BR, >>> Jeremie >>> >>> >>> 2013/3/20 Marius Dumitru Florea <[email protected]> >>> >>>> Hi Jeremie, >>>> >>>> We have started moving functional tests from xwiki-enterprise to >>>> xwiki-platform so that they are grouped by functional domain. Thus >>>> xwiki-enterprise-test-ui is not the best example. You should take a >>>> look at the platform modules that have functional tests: >>>> >>>> >>>>
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik...
>>>> >>>>
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik...
>>>> >>>>
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik...
>>>> >>>> to name a few. The packager maven plugin is taking care of importing >>>> (installing) your XAR and (I believe) adding the required jar >>>> dependencies to the WAR. You should follow this practice. >>>> >>>> Hope this helps, >>>> Marius >>>> >>>> On Wed, Mar 20, 2013 at 1:07 PM, Jeremie BOUSQUET >>>> <[email protected]> wrote: >>>> > Hello, >>>> > >>>> > I would like to discuss a little on writing of Selenium2 tests, as >>>> > described in test strategy [1], ie use Selenium 2 and apply Page >>>> Objects >>>> > pattern. >>>> > >>>> > My particular use-case is that I'm on a mission : write some >>>> functional >>>> > tests for my mail archive application. >>>> > I also think these would be the best tests for my app, as it greatly >>>> relies >>>> > on 2 external interfaces (xwiki for persistence/conf, javamail and >>>> mail >>>> > accounts on another side). There are some good unit tests to write of >>>> > course, but the main logic of the app has more meaning to be tested >>>> in >>>> > "real life", or close to that. >>>> > >>>> > To do that, I decided to try and plug myself in xwiki test >>>> framework, in >>>> > order to avoid redeveloping everything (such as deploying / >>>> launching an >>>> > xwiki instance from the tests). >>>> > I added 2 modules in my project: >>>> > - xwiki-contrib-mailarchive-test-pageobjects >>>> > - xwiki-contrib-mailarchive-test-ui >>>> > >>>> > Both inherit from org.xwiki.enterprise:xwiki-enterprise-test pom, >>>> and are >>>> > greatly inspired from poms of xwiki-enterprise-test-pageobjects and >>>> > xwiki-enterprise-test-ui poms. >>>> > It's unfinished and untested, but I believe I'll be able to have >>>> xwiki >>>> > instance installed, launched, and tests run automatically. >>>> > >>>> > My main question, is how should I do in order to also deploy my app >>>> in this >>>> > wiki instance prior to run the tests ? >>>> > For now I have several possible solutions that come to my mind, but >>>> I don't >>>> > know what would be the best... : >>>> > A- >>>> > - grab xwiki-standalone zip version x.y.z, unzip it, launch it >>>> > - make EM install my application (call some REST API ? GET some >>>> page with >>>> > proper parameters ?) >>>> > - run the tests >>>> > B- >>>> > - grab xwiki-standalone zip version x.y.z, unzip it >>>> > - "patch" it in some way with my application binaries, (ie, add >>>> things >>>> > directly under permanent directory / extension / repository ?) >>>> > - launch it and run the tests >>>> > >>>> > I personnally prefer A-, but it supposes also that the xwiki >>>> instance knows >>>> > any of my "dev" maven repositories (either my local repository .m2, >>>> or my >>>> > local instance of Nexus), so it would mean an additional step would >>>> be to >>>> > "patch" the standalone wiki xwiki.properties to add my personal repo. >>>> > Or maybe I can add such repo programmatically in the wiki instance >>>> from >>>> > java by looking up and using the right component ? >>>> > >>>> > Maybe this point has already been solved by anyone, so if you have >>>> any >>>> > samples it would be good enough. I did not search exhaustively, but >>>> I don't >>>> > remember having seen such use-cases on existing extensions on github. >>>> > Also, I think it might be interesting to extract from all this some >>>> kind of >>>> > maven archetype for functional testing of UI extension ? So >>>> contributors >>>> > could just call the archetype and get everything properly prepared, >>>> and >>>> > just have to add page objects and tests for their app ... >>>> > >>>> > WDYT ? >>>> > >>>> > BR, >>>> > Jeremie >>>> > >>>> > >>>> > [1] >>>> > >>>>
http://dev.xwiki.org/xwiki/bin/view/Community/Testing#HSelenium2-basedFramew...
>>>> > _______________________________________________ >>>> > users mailing list >>>> > [email protected] >>>> > http://lists.xwiki.org/mailman/listinfo/users >>>> _______________________________________________ >>>> users mailing list >>>> [email protected] >>>> http://lists.xwiki.org/mailman/listinfo/users >>>> >>> >>> >> >
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Thomas Mortagne _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
On Fri, Mar 29, 2013 at 11:03 AM, Jeremie BOUSQUET <[email protected]> wrote:
Hello,
Me again ... :-) With fixed version of packager plugin, things go better now. XWiki is downloaded and launched, my test browses to the page as I expect.
Problem is that when browsing to my page, I can see the following in the html content logged by the build:
<div id="xwikicontent"> <div class="xwikirenderingerror" style="cursor: pointer;" title="Read technical information related to this error">Unknown macro: velocity[...]
In fact, it seems wiki is running, but can't find any macro ... I tried to add a dependency on xwiki-enterprise-ui-all xar, but with same result. I'm not sure of what could be missing ?
Packager plugin job is not to create a XE, it just create the minimum to have a running thing we could call XWiki. You need put indicate what you are depending on and the packager will add them. For example if your extension need the velocity macro you should say it, etc...
BR, Jeremie
2013/3/28 Jeremie BOUSQUET <[email protected]>
Thanks !
Jeremie
2013/3/28 Thomas Mortagne <[email protected]>
On Thu, Mar 28, 2013 at 2:36 PM, Jeremie BOUSQUET <[email protected]> wrote:
Hi,
I proposed a pull request to fix XWIKI-8960: https://github.com/xwiki/xwiki-platform/pull/89
Seems to work well, and I added an IT test to check it. I'm not sure of the naming though ... It's my first pull request so I hope I did things correctly :-)
Looks good to me, applied it.
Br, Jeremie
2013/3/27 Marius Dumitru Florea <[email protected]>
On Tue, Mar 26, 2013 at 3:44 PM, Jeremie BOUSQUET <[email protected]> wrote:
Hi again,
On this topic I created a new JIRA: http://jira.xwiki.org/browse/XWIKI-8960
Indeed, I can reproduce locally. It seems you are the first to use the packager plugin outside platform and we didn't took this use case into account. I'll try to fix the packager plugin asap.
Thanks, Marius
... and proposed some sort of solution as a comment. If you agree with the problem and proposal, I could try to
contribute a
patch, as anyway I need it for the mailarchive tests. Of course if you want to fix it I don't disagree :-)
BR, Jeremie
2013/3/25 Jeremie BOUSQUET <[email protected]>
> I think the problem lies on this kind of expressions [1] ... > > The packager plugin defines version for all mandatory platform artifacts > with "this.getProject().getVersion()", meaning if I'm correct that it > returns correct version only if project is part of xwiki platform - or if > it shares the same version. > Maybe it should use property "platform.version" instead ? > > > BR, > Jeremie > > > [1] >
https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-tools/xwi...
> > > 2013/3/25 Jeremie BOUSQUET <[email protected]> > >> Note: it goes a bit further if I declare a bunch of xwiki platform >> dependencies in my pom, but breaks again, trying to look at those platform >> artifacts for version ${project.version} instead of ${platform.version} : >> >> [INFO] Copying JAR dependencies ... >> [WARNING] Missing POM for >> org.xwiki.platform:xwiki-platform-wysiwyg-server:jar:0.3-SNAPSHOT >> [WARNING] Missing POM for >> org.xwiki.platform:xwiki-platform-localization-script:jar:0.3-SNAPSHOT >> [WARNING] Missing POM for >> org.xwiki.platform:xwiki-platform-oldcore:jar:0.3-SNAPSHOT >> [...] >> [ERROR] Failed to execute goal >> org.xwiki.platform:xwiki-platform-tool-packager-plugi >> datory artifacts: Missing: >> [ERROR] ---------- >> [ERROR] 1) >> org.xwiki.platform:xwiki-platform-localization-script:jar:0.3-SNAPSHOT >> [ERROR] >> [ERROR] Try downloading the file manually from the project website. >> [...] >> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to >> resolve mandatory artifacts >> at >>
org.xwiki.tool.packager.PackageMojo.resolveTransitively(PackageMojo.java:614)
>> at >>
org.xwiki.tool.packager.PackageMojo.resolveJarArtifacts(PackageMojo.java:543)
>> at >> org.xwiki.tool.packager.PackageMojo.execute(PackageMojo.java:209) >> at >>
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
>> at >>
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>> ... 19 more >> >> >> 2013/3/25 Jeremie BOUSQUET <[email protected]> >> >>> Hummm, running through a strange issue during build: >>> >>> [ERROR] Failed to execute goal >>> org.xwiki.platform:xwiki-platform-tool-packager-plugin:4.5.2:package >>> (default) on project xwiki-contrib-mailarchive-test-tests: Failed to >>> resolve art >>> ifact >>>
[org.xwiki.platform:xwiki-platform-tool-jetty-resources:zip:0.3-SNAPSHOT:]:
>>> Failure to find >>>
org.xwiki.platform:xwiki-platform-tool-jetty-resources:zip:0.3-SNAPSHOT in
>>> http:// >>> nexus.xwiki.org/nexus/content/groups/public-snapshots was cached in the >>> local repository, resolution will not be reattempted until the update >>> interval of xwiki-snapshots has elapse >>> d or updates are forced >>> >>> 4.5.2 is ${platform.version}, 0.3-SNAPSHOT is ${project.version}. The >>> packager plugin is declared in my pom in version ${platform.version} of >>> course. >>> >>> Surprisingly though, here's an extract of the output of >>> "dependency:resolve-plugins": >>> >>> [INFO] Plugin Resolved: xwiki-platform-tool-packager-plugin-4.5.2.jar >>> [...] >>> [INFO] Plugin Dependency Resolved: >>> xwiki-platform-tool-jetty-resources-4.5.2.zip >>> [...] >>> >>> Seems that it finds correct 4.5.2 version for same dependency, that it >>> doesn't find at runtime ... Maybe an issue on packager plugin, "invisible" >>> until you use it on a non-xwiki project ? :-) >>> >>> BR, >>> Jeremie >>> >>> >>> >>> >>> >>> 2013/3/25 Jeremie BOUSQUET <[email protected]> >>> >>>> Thanks Marius, that's exactly what I was looking for ! >>>> I'll follow that practice, >>>> >>>> BR, >>>> Jeremie >>>> >>>> >>>> 2013/3/20 Marius Dumitru Florea <[email protected]> >>>> >>>>> Hi Jeremie, >>>>> >>>>> We have started moving functional tests from xwiki-enterprise to >>>>> xwiki-platform so that they are grouped by functional domain. Thus >>>>> xwiki-enterprise-test-ui is not the best example. You should take a >>>>> look at the platform modules that have functional tests: >>>>> >>>>> >>>>>
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik...
>>>>> >>>>>
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik...
>>>>> >>>>>
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik...
>>>>> >>>>> to name a few. The packager maven plugin is taking care of importing >>>>> (installing) your XAR and (I believe) adding the required jar >>>>> dependencies to the WAR. You should follow this practice. >>>>> >>>>> Hope this helps, >>>>> Marius >>>>> >>>>> On Wed, Mar 20, 2013 at 1:07 PM, Jeremie BOUSQUET >>>>> <[email protected]> wrote: >>>>> > Hello, >>>>> > >>>>> > I would like to discuss a little on writing of Selenium2 tests, as >>>>> > described in test strategy [1], ie use Selenium 2 and apply Page >>>>> Objects >>>>> > pattern. >>>>> > >>>>> > My particular use-case is that I'm on a mission : write some >>>>> functional >>>>> > tests for my mail archive application. >>>>> > I also think these would be the best tests for my app, as it greatly >>>>> relies >>>>> > on 2 external interfaces (xwiki for persistence/conf, javamail and >>>>> mail >>>>> > accounts on another side). There are some good unit tests to write of >>>>> > course, but the main logic of the app has more meaning to be tested >>>>> in >>>>> > "real life", or close to that. >>>>> > >>>>> > To do that, I decided to try and plug myself in xwiki test >>>>> framework, in >>>>> > order to avoid redeveloping everything (such as deploying / >>>>> launching an >>>>> > xwiki instance from the tests). >>>>> > I added 2 modules in my project: >>>>> > - xwiki-contrib-mailarchive-test-pageobjects >>>>> > - xwiki-contrib-mailarchive-test-ui >>>>> > >>>>> > Both inherit from org.xwiki.enterprise:xwiki-enterprise-test pom, >>>>> and are >>>>> > greatly inspired from poms of xwiki-enterprise-test-pageobjects and >>>>> > xwiki-enterprise-test-ui poms. >>>>> > It's unfinished and untested, but I believe I'll be able to have >>>>> xwiki >>>>> > instance installed, launched, and tests run automatically. >>>>> > >>>>> > My main question, is how should I do in order to also deploy my app >>>>> in this >>>>> > wiki instance prior to run the tests ? >>>>> > For now I have several possible solutions that come to my mind, but >>>>> I don't >>>>> > know what would be the best... : >>>>> > A- >>>>> > - grab xwiki-standalone zip version x.y.z, unzip it, launch it >>>>> > - make EM install my application (call some REST API ? GET some >>>>> page with >>>>> > proper parameters ?) >>>>> > - run the tests >>>>> > B- >>>>> > - grab xwiki-standalone zip version x.y.z, unzip it >>>>> > - "patch" it in some way with my application binaries, (ie, add >>>>> things >>>>> > directly under permanent directory / extension / repository ?) >>>>> > - launch it and run the tests >>>>> > >>>>> > I personnally prefer A-, but it supposes also that the xwiki >>>>> instance knows >>>>> > any of my "dev" maven repositories (either my local repository .m2, >>>>> or my >>>>> > local instance of Nexus), so it would mean an additional step would >>>>> be to >>>>> > "patch" the standalone wiki xwiki.properties to add my personal repo. >>>>> > Or maybe I can add such repo programmatically in the wiki instance >>>>> from >>>>> > java by looking up and using the right component ? >>>>> > >>>>> > Maybe this point has already been solved by anyone, so if you have >>>>> any >>>>> > samples it would be good enough. I did not search exhaustively, but >>>>> I don't >>>>> > remember having seen such use-cases on existing extensions on github. >>>>> > Also, I think it might be interesting to extract from all this some >>>>> kind of >>>>> > maven archetype for functional testing of UI extension ? So >>>>> contributors >>>>> > could just call the archetype and get everything properly prepared, >>>>> and >>>>> > just have to add page objects and tests for their app ... >>>>> > >>>>> > WDYT ? >>>>> > >>>>> > BR, >>>>> > Jeremie >>>>> > >>>>> > >>>>> > [1] >>>>> > >>>>>
http://dev.xwiki.org/xwiki/bin/view/Community/Testing#HSelenium2-basedFramew...
>>>>> > _______________________________________________ >>>>> > users mailing list >>>>> > [email protected] >>>>> > http://lists.xwiki.org/mailman/listinfo/users >>>>> _______________________________________________ >>>>> users mailing list >>>>> [email protected] >>>>> http://lists.xwiki.org/mailman/listinfo/users >>>>> >>>> >>>> >>> >> > _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Thomas Mortagne _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Thomas Mortagne
On Mar 29, 2013, at 11:03 AM, Jeremie BOUSQUET <[email protected]> wrote:
Hello,
Me again ... :-) With fixed version of packager plugin, things go better now. XWiki is downloaded and launched, my test browses to the page as I expect.
Problem is that when browsing to my page, I can see the following in the html content logged by the build:
<div id="xwikicontent"> <div class="xwikirenderingerror" style="cursor: pointer;" title="Read technical information related to this error">Unknown macro: velocity[...]
In fact, it seems wiki is running, but can't find any macro ... I tried to add a dependency on xwiki-enterprise-ui-all xar, but with same result. I'm not sure of what could be missing ?
I think I've noticed a bug related to this. For ex in my contrib project I depend on org.xwiki.platform:xwiki-platform-administration-ui. I was surprised when running my func test that the admin screen was missing the velocity and include macros for example. The reason I think is because in xwiki-platform-administration-ui the deps on velocity and include macros are of scope "runtime". So IMO there's a bug in PackageMojo: it should draw transitive dependencies for the "runtime" scope. I'll look into this. However as Thomas said, you need to add the **direct** deps you need at runtime. Thanks -Vincent [snip]
Thanks, I understand ... I added dependency on velocity macro, but of course a whole bunch of dependencies are still missing. I would have 2 feedbacks on that point: - I understand your point, but when writing a contrib app xar, you target it to work on a specific XE version, and not on a combination of platform/commons/rendering artifacts. So it could be nice, from a functional test POV, to be able to materialize this as a unique dependency, and get everything transitively. - Adding bits one by one is difficult, for example to find what jar is needed to register a wiki macro, is not so obvious (BTW I couldn't find it, I thought it was xwiki-application-wiki-macro-bridge.jar, but it's not bundled with this name in XE war). Well, it's not that complex, but requires some deeper knowledge of xwiki, deeper than what is needed to merely write an extension. - in the end, does it mean that to be fully complete, my extension xar should depend on all these xwiki artifacts (and not merely on some needed extensions) ? With the idea that my app could be installed even in an empty wiki ? (well, given there's at least EM in it ...) BR, Jeremie 2013/3/29 Thomas Mortagne <[email protected]>
On Fri, Mar 29, 2013 at 11:03 AM, Jeremie BOUSQUET <[email protected]> wrote:
Hello,
Me again ... :-) With fixed version of packager plugin, things go better now. XWiki is downloaded and launched, my test browses to the page as I expect.
Problem is that when browsing to my page, I can see the following in the html content logged by the build:
<div id="xwikicontent"> <div class="xwikirenderingerror" style="cursor: pointer;" title="Read technical information related to this error">Unknown macro: velocity[...]
In fact, it seems wiki is running, but can't find any macro ... I tried to add a dependency on xwiki-enterprise-ui-all xar, but with same result. I'm not sure of what could be missing ?
Packager plugin job is not to create a XE, it just create the minimum to have a running thing we could call XWiki. You need put indicate what you are depending on and the packager will add them.
For example if your extension need the velocity macro you should say it, etc...
BR, Jeremie
2013/3/28 Jeremie BOUSQUET <[email protected]>
Thanks !
Jeremie
2013/3/28 Thomas Mortagne <[email protected]>
On Thu, Mar 28, 2013 at 2:36 PM, Jeremie BOUSQUET <[email protected]> wrote:
Hi,
I proposed a pull request to fix XWIKI-8960: https://github.com/xwiki/xwiki-platform/pull/89
Seems to work well, and I added an IT test to check it. I'm not sure
of
the
naming though ... It's my first pull request so I hope I did things correctly :-)
Looks good to me, applied it.
Br, Jeremie
2013/3/27 Marius Dumitru Florea <[email protected]>
On Tue, Mar 26, 2013 at 3:44 PM, Jeremie BOUSQUET <[email protected]> wrote: > Hi again, > > On this topic I created a new JIRA: > http://jira.xwiki.org/browse/XWIKI-8960
Indeed, I can reproduce locally. It seems you are the first to use
the
packager plugin outside platform and we didn't took this use case into account. I'll try to fix the packager plugin asap.
Thanks, Marius
> > ... and proposed some sort of solution as a comment. > If you agree with the problem and proposal, I could try to contribute a > patch, as anyway I need it for the mailarchive tests. > Of course if you want to fix it I don't disagree :-) > > BR, > Jeremie > > > 2013/3/25 Jeremie BOUSQUET <[email protected]> > >> I think the problem lies on this kind of expressions [1] ... >> >> The packager plugin defines version for all mandatory platform artifacts >> with "this.getProject().getVersion()", meaning if I'm correct that it >> returns correct version only if project is part of xwiki platform - or if >> it shares the same version. >> Maybe it should use property "platform.version" instead ? >> >> >> BR, >> Jeremie >> >> >> [1] >>
https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-tools/xwi...
>> >> >> 2013/3/25 Jeremie BOUSQUET <[email protected]> >> >>> Note: it goes a bit further if I declare a bunch of xwiki platform >>> dependencies in my pom, but breaks again, trying to look at those platform >>> artifacts for version ${project.version} instead of ${platform.version} : >>> >>> [INFO] Copying JAR dependencies ... >>> [WARNING] Missing POM for >>> org.xwiki.platform:xwiki-platform-wysiwyg-server:jar:0.3-SNAPSHOT >>> [WARNING] Missing POM for >>> org.xwiki.platform:xwiki-platform-localization-script:jar:0.3-SNAPSHOT >>> [WARNING] Missing POM for >>> org.xwiki.platform:xwiki-platform-oldcore:jar:0.3-SNAPSHOT >>> [...] >>> [ERROR] Failed to execute goal >>> org.xwiki.platform:xwiki-platform-tool-packager-plugi >>> datory artifacts: Missing: >>> [ERROR] ---------- >>> [ERROR] 1) >>> org.xwiki.platform:xwiki-platform-localization-script:jar:0.3-SNAPSHOT >>> [ERROR] >>> [ERROR] Try downloading the file manually from the project website. >>> [...] >>> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to >>> resolve mandatory artifacts >>> at >>>
org.xwiki.tool.packager.PackageMojo.resolveTransitively(PackageMojo.java:614)
>>> at >>>
org.xwiki.tool.packager.PackageMojo.resolveJarArtifacts(PackageMojo.java:543)
>>> at >>> org.xwiki.tool.packager.PackageMojo.execute(PackageMojo.java:209) >>> at >>>
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
>>> at >>>
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>>> ... 19 more >>> >>> >>> 2013/3/25 Jeremie BOUSQUET <[email protected]> >>> >>>> Hummm, running through a strange issue during build: >>>> >>>> [ERROR] Failed to execute goal >>>> org.xwiki.platform:xwiki-platform-tool-packager-plugin:4.5.2:package >>>> (default) on project xwiki-contrib-mailarchive-test-tests: Failed to >>>> resolve art >>>> ifact >>>>
[org.xwiki.platform:xwiki-platform-tool-jetty-resources:zip:0.3-SNAPSHOT:]:
>>>> Failure to find >>>>
org.xwiki.platform:xwiki-platform-tool-jetty-resources:zip:0.3-SNAPSHOT in
>>>> http:// >>>> nexus.xwiki.org/nexus/content/groups/public-snapshots was cached in the >>>> local repository, resolution will not be reattempted until the update >>>> interval of xwiki-snapshots has elapse >>>> d or updates are forced >>>> >>>> 4.5.2 is ${platform.version}, 0.3-SNAPSHOT is ${project.version}. The >>>> packager plugin is declared in my pom in version ${platform.version} of >>>> course. >>>> >>>> Surprisingly though, here's an extract of the output of >>>> "dependency:resolve-plugins": >>>> >>>> [INFO] Plugin Resolved: xwiki-platform-tool-packager-plugin-4.5.2.jar >>>> [...] >>>> [INFO] Plugin Dependency Resolved: >>>> xwiki-platform-tool-jetty-resources-4.5.2.zip >>>> [...] >>>> >>>> Seems that it finds correct 4.5.2 version for same dependency, that it >>>> doesn't find at runtime ... Maybe an issue on packager plugin, "invisible" >>>> until you use it on a non-xwiki project ? :-) >>>> >>>> BR, >>>> Jeremie >>>> >>>> >>>> >>>> >>>> >>>> 2013/3/25 Jeremie BOUSQUET <[email protected]> >>>> >>>>> Thanks Marius, that's exactly what I was looking for ! >>>>> I'll follow that practice, >>>>> >>>>> BR, >>>>> Jeremie >>>>> >>>>> >>>>> 2013/3/20 Marius Dumitru Florea < [email protected]> >>>>> >>>>>> Hi Jeremie, >>>>>> >>>>>> We have started moving functional tests from xwiki-enterprise to >>>>>> xwiki-platform so that they are grouped by functional domain. Thus >>>>>> xwiki-enterprise-test-ui is not the best example. You should take a >>>>>> look at the platform modules that have functional tests: >>>>>> >>>>>> >>>>>>
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik...
>>>>>> >>>>>>
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik...
>>>>>> >>>>>>
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik...
>>>>>> >>>>>> to name a few. The packager maven plugin is taking care of importing >>>>>> (installing) your XAR and (I believe) adding the required jar >>>>>> dependencies to the WAR. You should follow this practice. >>>>>> >>>>>> Hope this helps, >>>>>> Marius >>>>>> >>>>>> On Wed, Mar 20, 2013 at 1:07 PM, Jeremie BOUSQUET >>>>>> <[email protected]> wrote: >>>>>> > Hello, >>>>>> > >>>>>> > I would like to discuss a little on writing of Selenium2 tests, as >>>>>> > described in test strategy [1], ie use Selenium 2 and apply Page >>>>>> Objects >>>>>> > pattern. >>>>>> > >>>>>> > My particular use-case is that I'm on a mission : write some >>>>>> functional >>>>>> > tests for my mail archive application. >>>>>> > I also think these would be the best tests for my app, as it greatly >>>>>> relies >>>>>> > on 2 external interfaces (xwiki for persistence/conf, javamail and >>>>>> mail >>>>>> > accounts on another side). There are some good unit tests to write of >>>>>> > course, but the main logic of the app has more meaning to be tested >>>>>> in >>>>>> > "real life", or close to that. >>>>>> > >>>>>> > To do that, I decided to try and plug myself in xwiki test >>>>>> framework, in >>>>>> > order to avoid redeveloping everything (such as deploying / >>>>>> launching an >>>>>> > xwiki instance from the tests). >>>>>> > I added 2 modules in my project: >>>>>> > - xwiki-contrib-mailarchive-test-pageobjects >>>>>> > - xwiki-contrib-mailarchive-test-ui >>>>>> > >>>>>> > Both inherit from org.xwiki.enterprise:xwiki-enterprise-test pom, >>>>>> and are >>>>>> > greatly inspired from poms of xwiki-enterprise-test-pageobjects and >>>>>> > xwiki-enterprise-test-ui poms. >>>>>> > It's unfinished and untested, but I believe I'll be able to have >>>>>> xwiki >>>>>> > instance installed, launched, and tests run automatically. >>>>>> > >>>>>> > My main question, is how should I do in order to also deploy my app >>>>>> in this >>>>>> > wiki instance prior to run the tests ? >>>>>> > For now I have several possible solutions that come to my mind, but >>>>>> I don't >>>>>> > know what would be the best... : >>>>>> > A- >>>>>> > - grab xwiki-standalone zip version x.y.z, unzip it, launch it >>>>>> > - make EM install my application (call some REST API ? GET some >>>>>> page with >>>>>> > proper parameters ?) >>>>>> > - run the tests >>>>>> > B- >>>>>> > - grab xwiki-standalone zip version x.y.z, unzip it >>>>>> > - "patch" it in some way with my application binaries, (ie, add >>>>>> things >>>>>> > directly under permanent directory / extension / repository ?) >>>>>> > - launch it and run the tests >>>>>> > >>>>>> > I personnally prefer A-, but it supposes also that the xwiki >>>>>> instance knows >>>>>> > any of my "dev" maven repositories (either my local repository .m2, >>>>>> or my >>>>>> > local instance of Nexus), so it would mean an additional step would >>>>>> be to >>>>>> > "patch" the standalone wiki xwiki.properties to add my personal repo. >>>>>> > Or maybe I can add such repo programmatically in the wiki instance >>>>>> from >>>>>> > java by looking up and using the right component ? >>>>>> > >>>>>> > Maybe this point has already been solved by anyone, so if you have >>>>>> any >>>>>> > samples it would be good enough. I did not search exhaustively, but >>>>>> I don't >>>>>> > remember having seen such use-cases on existing extensions on github. >>>>>> > Also, I think it might be interesting to extract from all this some >>>>>> kind of >>>>>> > maven archetype for functional testing of UI extension ? So >>>>>> contributors >>>>>> > could just call the archetype and get everything properly prepared, >>>>>> and >>>>>> > just have to add page objects and tests for their app ... >>>>>> > >>>>>> > WDYT ? >>>>>> > >>>>>> > BR, >>>>>> > Jeremie >>>>>> > >>>>>> > >>>>>> > [1] >>>>>> > >>>>>>
http://dev.xwiki.org/xwiki/bin/view/Community/Testing#HSelenium2-basedFramew...
>>>>>> > _______________________________________________ >>>>>> > users mailing list >>>>>> > [email protected] >>>>>> > http://lists.xwiki.org/mailman/listinfo/users >>>>>> _______________________________________________ >>>>>> users mailing list >>>>>> [email protected] >>>>>> http://lists.xwiki.org/mailman/listinfo/users >>>>>> >>>>> >>>>> >>>> >>> >> > _______________________________________________ > users mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/users _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Thomas Mortagne _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Thomas Mortagne _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
On Fri, Mar 29, 2013 at 12:31 PM, Jeremie BOUSQUET <[email protected]> wrote:
Thanks, I understand ... I added dependency on velocity macro, but of course a whole bunch of dependencies are still missing. I would have 2 feedbacks on that point: - I understand your point, but when writing a contrib app xar, you target it to work on a specific XE version, and not on a combination of platform/commons/rendering artifacts. So it could be nice, from a functional test POV, to be able to materialize this as a unique dependency, and get everything transitively. - Adding bits one by one is difficult, for example to find what jar is needed to register a wiki macro, is not so obvious (BTW I couldn't find it, I thought it was xwiki-application-wiki-macro-bridge.jar, but it's not bundled with this name in XE war). Well, it's not that complex, but requires some deeper knowledge of xwiki, deeper than what is needed to merely write an extension. - in the end, does it mean that to be fully complete, my extension xar should depend on all these xwiki artifacts (and not merely on some needed extensions) ? With the idea that my app could be installed even in an empty wiki ? (well, given there's at least EM in it ...)
Yes the general idea is to move to releasing a pretty much empty XWiki with what's needed to make Extension Manager work and you transitively get everything you need to make whatever extension you installed work.
BR, Jeremie
2013/3/29 Thomas Mortagne <[email protected]>
On Fri, Mar 29, 2013 at 11:03 AM, Jeremie BOUSQUET <[email protected]> wrote:
Hello,
Me again ... :-) With fixed version of packager plugin, things go better now. XWiki is downloaded and launched, my test browses to the page as I expect.
Problem is that when browsing to my page, I can see the following in the html content logged by the build:
<div id="xwikicontent"> <div class="xwikirenderingerror" style="cursor: pointer;" title="Read technical information related to this error">Unknown macro: velocity[...]
In fact, it seems wiki is running, but can't find any macro ... I tried to add a dependency on xwiki-enterprise-ui-all xar, but with same result. I'm not sure of what could be missing ?
Packager plugin job is not to create a XE, it just create the minimum to have a running thing we could call XWiki. You need put indicate what you are depending on and the packager will add them.
For example if your extension need the velocity macro you should say it, etc...
BR, Jeremie
2013/3/28 Jeremie BOUSQUET <[email protected]>
Thanks !
Jeremie
2013/3/28 Thomas Mortagne <[email protected]>
On Thu, Mar 28, 2013 at 2:36 PM, Jeremie BOUSQUET <[email protected]> wrote:
Hi,
I proposed a pull request to fix XWIKI-8960: https://github.com/xwiki/xwiki-platform/pull/89
Seems to work well, and I added an IT test to check it. I'm not sure
of
the
naming though ... It's my first pull request so I hope I did things correctly :-)
Looks good to me, applied it.
Br, Jeremie
2013/3/27 Marius Dumitru Florea <[email protected]>
> On Tue, Mar 26, 2013 at 3:44 PM, Jeremie BOUSQUET > <[email protected]> wrote: > > Hi again, > > > > On this topic I created a new JIRA: > > http://jira.xwiki.org/browse/XWIKI-8960 > > Indeed, I can reproduce locally. It seems you are the first to use
the
> packager plugin outside platform and we didn't took this use case into > account. I'll try to fix the packager plugin asap. > > Thanks, > Marius > > > > > ... and proposed some sort of solution as a comment. > > If you agree with the problem and proposal, I could try to contribute a > > patch, as anyway I need it for the mailarchive tests. > > Of course if you want to fix it I don't disagree :-) > > > > BR, > > Jeremie > > > > > > 2013/3/25 Jeremie BOUSQUET <[email protected]> > > > >> I think the problem lies on this kind of expressions [1] ... > >> > >> The packager plugin defines version for all mandatory platform artifacts > >> with "this.getProject().getVersion()", meaning if I'm correct that it > >> returns correct version only if project is part of xwiki platform - or > if > >> it shares the same version. > >> Maybe it should use property "platform.version" instead ? > >> > >> > >> BR, > >> Jeremie > >> > >> > >> [1] > >> >
https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-tools/xwi...
> >> > >> > >> 2013/3/25 Jeremie BOUSQUET <[email protected]> > >> > >>> Note: it goes a bit further if I declare a bunch of xwiki platform > >>> dependencies in my pom, but breaks again, trying to look at those > platform > >>> artifacts for version ${project.version} instead of > ${platform.version} : > >>> > >>> [INFO] Copying JAR dependencies ... > >>> [WARNING] Missing POM for > >>> org.xwiki.platform:xwiki-platform-wysiwyg-server:jar:0.3-SNAPSHOT > >>> [WARNING] Missing POM for > >>> org.xwiki.platform:xwiki-platform-localization-script:jar:0.3-SNAPSHOT > >>> [WARNING] Missing POM for > >>> org.xwiki.platform:xwiki-platform-oldcore:jar:0.3-SNAPSHOT > >>> [...] > >>> [ERROR] Failed to execute goal > >>> org.xwiki.platform:xwiki-platform-tool-packager-plugi > >>> datory artifacts: Missing: > >>> [ERROR] ---------- > >>> [ERROR] 1) > >>> org.xwiki.platform:xwiki-platform-localization-script:jar:0.3-SNAPSHOT > >>> [ERROR] > >>> [ERROR] Try downloading the file manually from the project website. > >>> [...] > >>> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to > >>> resolve mandatory artifacts > >>> at > >>> >
org.xwiki.tool.packager.PackageMojo.resolveTransitively(PackageMojo.java:614)
> >>> at > >>> >
org.xwiki.tool.packager.PackageMojo.resolveJarArtifacts(PackageMojo.java:543)
> >>> at > >>> org.xwiki.tool.packager.PackageMojo.execute(PackageMojo.java:209) > >>> at > >>> >
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> >>> at > >>> >
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> >>> ... 19 more > >>> > >>> > >>> 2013/3/25 Jeremie BOUSQUET <[email protected]> > >>> > >>>> Hummm, running through a strange issue during build: > >>>> > >>>> [ERROR] Failed to execute goal > >>>> org.xwiki.platform:xwiki-platform-tool-packager-plugin:4.5.2:package > >>>> (default) on project xwiki-contrib-mailarchive-test-tests: Failed to > >>>> resolve art > >>>> ifact > >>>> >
[org.xwiki.platform:xwiki-platform-tool-jetty-resources:zip:0.3-SNAPSHOT:]:
> >>>> Failure to find > >>>> >
org.xwiki.platform:xwiki-platform-tool-jetty-resources:zip:0.3-SNAPSHOT in
> >>>> http:// > >>>> nexus.xwiki.org/nexus/content/groups/public-snapshots was cached in > the > >>>> local repository, resolution will not be reattempted until the update > >>>> interval of xwiki-snapshots has elapse > >>>> d or updates are forced > >>>> > >>>> 4.5.2 is ${platform.version}, 0.3-SNAPSHOT is ${project.version}. The > >>>> packager plugin is declared in my pom in version ${platform.version} > of > >>>> course. > >>>> > >>>> Surprisingly though, here's an extract of the output of > >>>> "dependency:resolve-plugins": > >>>> > >>>> [INFO] Plugin Resolved: xwiki-platform-tool-packager-plugin-4.5.2.jar > >>>> [...] > >>>> [INFO] Plugin Dependency Resolved: > >>>> xwiki-platform-tool-jetty-resources-4.5.2.zip > >>>> [...] > >>>> > >>>> Seems that it finds correct 4.5.2 version for same dependency, that it > >>>> doesn't find at runtime ... Maybe an issue on packager plugin, > "invisible" > >>>> until you use it on a non-xwiki project ? :-) > >>>> > >>>> BR, > >>>> Jeremie > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> 2013/3/25 Jeremie BOUSQUET <[email protected]> > >>>> > >>>>> Thanks Marius, that's exactly what I was looking for ! > >>>>> I'll follow that practice, > >>>>> > >>>>> BR, > >>>>> Jeremie > >>>>> > >>>>> > >>>>> 2013/3/20 Marius Dumitru Florea < [email protected]> > >>>>> > >>>>>> Hi Jeremie, > >>>>>> > >>>>>> We have started moving functional tests from xwiki-enterprise to > >>>>>> xwiki-platform so that they are grouped by functional domain. Thus > >>>>>> xwiki-enterprise-test-ui is not the best example. You should take a > >>>>>> look at the platform modules that have functional tests: > >>>>>> > >>>>>> > >>>>>> >
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik...
> >>>>>> > >>>>>> >
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik...
> >>>>>> > >>>>>> >
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik...
> >>>>>> > >>>>>> to name a few. The packager maven plugin is taking care of importing > >>>>>> (installing) your XAR and (I believe) adding the required jar > >>>>>> dependencies to the WAR. You should follow this practice. > >>>>>> > >>>>>> Hope this helps, > >>>>>> Marius > >>>>>> > >>>>>> On Wed, Mar 20, 2013 at 1:07 PM, Jeremie BOUSQUET > >>>>>> <[email protected]> wrote: > >>>>>> > Hello, > >>>>>> > > >>>>>> > I would like to discuss a little on writing of Selenium2 tests, as > >>>>>> > described in test strategy [1], ie use Selenium 2 and apply Page > >>>>>> Objects > >>>>>> > pattern. > >>>>>> > > >>>>>> > My particular use-case is that I'm on a mission : write some > >>>>>> functional > >>>>>> > tests for my mail archive application. > >>>>>> > I also think these would be the best tests for my app, as it > greatly > >>>>>> relies > >>>>>> > on 2 external interfaces (xwiki for persistence/conf, javamail and > >>>>>> mail > >>>>>> > accounts on another side). There are some good unit tests to > write of > >>>>>> > course, but the main logic of the app has more meaning to be > tested > >>>>>> in > >>>>>> > "real life", or close to that. > >>>>>> > > >>>>>> > To do that, I decided to try and plug myself in xwiki test > >>>>>> framework, in > >>>>>> > order to avoid redeveloping everything (such as deploying / > >>>>>> launching an > >>>>>> > xwiki instance from the tests). > >>>>>> > I added 2 modules in my project: > >>>>>> > - xwiki-contrib-mailarchive-test-pageobjects > >>>>>> > - xwiki-contrib-mailarchive-test-ui > >>>>>> > > >>>>>> > Both inherit from org.xwiki.enterprise:xwiki-enterprise-test pom, > >>>>>> and are > >>>>>> > greatly inspired from poms of xwiki-enterprise-test-pageobjects > and > >>>>>> > xwiki-enterprise-test-ui poms. > >>>>>> > It's unfinished and untested, but I believe I'll be able to have > >>>>>> xwiki > >>>>>> > instance installed, launched, and tests run automatically. > >>>>>> > > >>>>>> > My main question, is how should I do in order to also deploy my > app > >>>>>> in this > >>>>>> > wiki instance prior to run the tests ? > >>>>>> > For now I have several possible solutions that come to my mind, > but > >>>>>> I don't > >>>>>> > know what would be the best... : > >>>>>> > A- > >>>>>> > - grab xwiki-standalone zip version x.y.z, unzip it, launch it > >>>>>> > - make EM install my application (call some REST API ? GET some > >>>>>> page with > >>>>>> > proper parameters ?) > >>>>>> > - run the tests > >>>>>> > B- > >>>>>> > - grab xwiki-standalone zip version x.y.z, unzip it > >>>>>> > - "patch" it in some way with my application binaries, (ie, add > >>>>>> things > >>>>>> > directly under permanent directory / extension / repository ?) > >>>>>> > - launch it and run the tests > >>>>>> > > >>>>>> > I personnally prefer A-, but it supposes also that the xwiki > >>>>>> instance knows > >>>>>> > any of my "dev" maven repositories (either my local repository > .m2, > >>>>>> or my > >>>>>> > local instance of Nexus), so it would mean an additional step > would > >>>>>> be to > >>>>>> > "patch" the standalone wiki xwiki.properties to add my personal > repo. > >>>>>> > Or maybe I can add such repo programmatically in the wiki instance > >>>>>> from > >>>>>> > java by looking up and using the right component ? > >>>>>> > > >>>>>> > Maybe this point has already been solved by anyone, so if you have > >>>>>> any > >>>>>> > samples it would be good enough. I did not search exhaustively, > but > >>>>>> I don't > >>>>>> > remember having seen such use-cases on existing extensions on > github. > >>>>>> > Also, I think it might be interesting to extract from all this > some > >>>>>> kind of > >>>>>> > maven archetype for functional testing of UI extension ? So > >>>>>> contributors > >>>>>> > could just call the archetype and get everything properly > prepared, > >>>>>> and > >>>>>> > just have to add page objects and tests for their app ... > >>>>>> > > >>>>>> > WDYT ? > >>>>>> > > >>>>>> > BR, > >>>>>> > Jeremie > >>>>>> > > >>>>>> > > >>>>>> > [1] > >>>>>> > > >>>>>> >
http://dev.xwiki.org/xwiki/bin/view/Community/Testing#HSelenium2-basedFramew...
> >>>>>> > _______________________________________________ > >>>>>> > users mailing list > >>>>>> > [email protected] > >>>>>> > http://lists.xwiki.org/mailman/listinfo/users > >>>>>> _______________________________________________ > >>>>>> users mailing list > >>>>>> [email protected] > >>>>>> http://lists.xwiki.org/mailman/listinfo/users > >>>>>> > >>>>> > >>>>> > >>>> > >>> > >> > > _______________________________________________ > > users mailing list > > [email protected] > > http://lists.xwiki.org/mailman/listinfo/users > _______________________________________________ > users mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/users > _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Thomas Mortagne _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Thomas Mortagne _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Thomas Mortagne
On Mar 29, 2013, at 12:21 PM, Vincent Massol <[email protected]> wrote:
On Mar 29, 2013, at 11:03 AM, Jeremie BOUSQUET <[email protected]> wrote:
Hello,
Me again ... :-) With fixed version of packager plugin, things go better now. XWiki is downloaded and launched, my test browses to the page as I expect.
Problem is that when browsing to my page, I can see the following in the html content logged by the build:
<div id="xwikicontent"> <div class="xwikirenderingerror" style="cursor: pointer;" title="Read technical information related to this error">Unknown macro: velocity[...]
In fact, it seems wiki is running, but can't find any macro ... I tried to add a dependency on xwiki-enterprise-ui-all xar, but with same result. I'm not sure of what could be missing ?
I think I've noticed a bug related to this. For ex in my contrib project I depend on org.xwiki.platform:xwiki-platform-administration-ui. I was surprised when running my func test that the admin screen was missing the velocity and include macros for example. The reason I think is because in xwiki-platform-administration-ui the deps on velocity and include macros are of scope "runtime".
So IMO there's a bug in PackageMojo: it should draw transitive dependencies for the "runtime" scope.
I'll look into this.
Fixed in http://jira.xwiki.org/jira/browse/XWIKI-8983 Thanks -Vincent
However as Thomas said, you need to add the **direct** deps you need at runtime.
Thanks -Vincent
[snip]
Thanks ! I'm progressing, but it seems I have a hard time finding what to declare to get the info/warning/error macros ... BR, Jeremie 2013/3/29 Vincent Massol <[email protected]>
On Mar 29, 2013, at 12:21 PM, Vincent Massol <[email protected]> wrote:
On Mar 29, 2013, at 11:03 AM, Jeremie BOUSQUET <
[email protected]> wrote:
Hello,
Me again ... :-) With fixed version of packager plugin, things go better now. XWiki is downloaded and launched, my test browses to the page as I expect.
Problem is that when browsing to my page, I can see the following in the html content logged by the build:
<div id="xwikicontent"> <div class="xwikirenderingerror" style="cursor: pointer;" title="Read technical information related to this error">Unknown macro:
velocity[...]
In fact, it seems wiki is running, but can't find any macro ... I tried
to
add a dependency on xwiki-enterprise-ui-all xar, but with same result. I'm not sure of what could be missing ?
I think I've noticed a bug related to this. For ex in my contrib project I depend on org.xwiki.platform:xwiki-platform-administration-ui. I was surprised when running my func test that the admin screen was missing the velocity and include macros for example. The reason I think is because in xwiki-platform-administration-ui the deps on velocity and include macros are of scope "runtime".
So IMO there's a bug in PackageMojo: it should draw transitive dependencies for the "runtime" scope.
I'll look into this.
Fixed in http://jira.xwiki.org/jira/browse/XWIKI-8983
Thanks -Vincent
However as Thomas said, you need to add the **direct** deps you need at runtime.
Thanks -Vincent
[snip]
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
Ok found it in xwiki-rendering-macro-message. That's nice, looking into it, just realized that there existed a {{success}} macro ! Seems nice, is it intended that it's not described on extensions wiki as info/warning/error are ? Thanks, Jeremie 2013/3/29 Jeremie BOUSQUET <[email protected]>
Thanks ! I'm progressing, but it seems I have a hard time finding what to declare to get the info/warning/error macros ...
BR, Jeremie
2013/3/29 Vincent Massol <[email protected]>
On Mar 29, 2013, at 12:21 PM, Vincent Massol <[email protected]> wrote:
On Mar 29, 2013, at 11:03 AM, Jeremie BOUSQUET <
[email protected]> wrote:
Hello,
Me again ... :-) With fixed version of packager plugin, things go better now. XWiki is downloaded and launched, my test browses to the page as I expect.
Problem is that when browsing to my page, I can see the following in
the
html content logged by the build:
<div id="xwikicontent"> <div class="xwikirenderingerror" style="cursor: pointer;" title="Read technical information related to this error">Unknown macro: velocity[...]
In fact, it seems wiki is running, but can't find any macro ... I tried to add a dependency on xwiki-enterprise-ui-all xar, but with same result. I'm not sure of what could be missing ?
I think I've noticed a bug related to this. For ex in my contrib project I depend on org.xwiki.platform:xwiki-platform-administration-ui. I was surprised when running my func test that the admin screen was missing the velocity and include macros for example. The reason I think is because in xwiki-platform-administration-ui the deps on velocity and include macros are of scope "runtime".
So IMO there's a bug in PackageMojo: it should draw transitive dependencies for the "runtime" scope.
I'll look into this.
Fixed in http://jira.xwiki.org/jira/browse/XWIKI-8983
Thanks -Vincent
However as Thomas said, you need to add the **direct** deps you need at runtime.
Thanks -Vincent
[snip]
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
On Fri, Mar 29, 2013 at 3:05 PM, Jeremie BOUSQUET <[email protected]> wrote:
Ok found it in xwiki-rendering-macro-message. That's nice, looking into it, just realized that there existed a {{success}} macro ! Seems nice, is it intended that it's not described on extensions wiki as info/warning/error are ?
Probably been forgotten by the dev who introduced it.
Thanks, Jeremie
2013/3/29 Jeremie BOUSQUET <[email protected]>
Thanks ! I'm progressing, but it seems I have a hard time finding what to declare to get the info/warning/error macros ...
BR, Jeremie
2013/3/29 Vincent Massol <[email protected]>
On Mar 29, 2013, at 12:21 PM, Vincent Massol <[email protected]> wrote:
On Mar 29, 2013, at 11:03 AM, Jeremie BOUSQUET <
[email protected]> wrote:
Hello,
Me again ... :-) With fixed version of packager plugin, things go better now. XWiki is downloaded and launched, my test browses to the page as I expect.
Problem is that when browsing to my page, I can see the following in
the
html content logged by the build:
<div id="xwikicontent"> <div class="xwikirenderingerror" style="cursor: pointer;" title="Read technical information related to this error">Unknown macro: velocity[...]
In fact, it seems wiki is running, but can't find any macro ... I tried to add a dependency on xwiki-enterprise-ui-all xar, but with same result. I'm not sure of what could be missing ?
I think I've noticed a bug related to this. For ex in my contrib project I depend on org.xwiki.platform:xwiki-platform-administration-ui. I was surprised when running my func test that the admin screen was missing the velocity and include macros for example. The reason I think is because in xwiki-platform-administration-ui the deps on velocity and include macros are of scope "runtime".
So IMO there's a bug in PackageMojo: it should draw transitive dependencies for the "runtime" scope.
I'll look into this.
Fixed in http://jira.xwiki.org/jira/browse/XWIKI-8983
Thanks -Vincent
However as Thomas said, you need to add the **direct** deps you need at runtime.
Thanks -Vincent
[snip]
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Thomas Mortagne
Mmmm, what could explain that standard login for "Admin" user does not work in the xwiki created by the packager plugin ? ("invalid credentials"). It used to work, maybe when I had dependency on xwiki-enterprise-ui-all ... ? Br, Jeremie 2013/3/29 Thomas Mortagne <[email protected]>
On Fri, Mar 29, 2013 at 3:05 PM, Jeremie BOUSQUET <[email protected]> wrote:
Ok found it in xwiki-rendering-macro-message. That's nice, looking into it, just realized that there existed a {{success}} macro ! Seems nice, is it intended that it's not described on extensions wiki as info/warning/error are ?
Probably been forgotten by the dev who introduced it.
Thanks, Jeremie
2013/3/29 Jeremie BOUSQUET <[email protected]>
Thanks ! I'm progressing, but it seems I have a hard time finding what to declare to get the info/warning/error macros ...
BR, Jeremie
2013/3/29 Vincent Massol <[email protected]>
On Mar 29, 2013, at 12:21 PM, Vincent Massol <[email protected]>
wrote:
On Mar 29, 2013, at 11:03 AM, Jeremie BOUSQUET <
[email protected]> wrote:
Hello,
Me again ... :-) With fixed version of packager plugin, things go better now. XWiki
is
downloaded and launched, my test browses to the page as I expect.
Problem is that when browsing to my page, I can see the following in the html content logged by the build:
<div id="xwikicontent"> <div class="xwikirenderingerror" style="cursor: pointer;" title="Read technical information related to this error">Unknown macro: velocity[...]
In fact, it seems wiki is running, but can't find any macro ... I tried to add a dependency on xwiki-enterprise-ui-all xar, but with same result. I'm not sure of what could be missing ?
I think I've noticed a bug related to this. For ex in my contrib project I depend on org.xwiki.platform:xwiki-platform-administration-ui. I was surprised when running my func test that the admin screen was missing the velocity and include macros for example. The reason I think is because in xwiki-platform-administration-ui the deps on velocity and include macros are of scope "runtime".
So IMO there's a bug in PackageMojo: it should draw transitive dependencies for the "runtime" scope.
I'll look into this.
Fixed in http://jira.xwiki.org/jira/browse/XWIKI-8983
Thanks -Vincent
However as Thomas said, you need to add the **direct** deps you need at runtime.
Thanks -Vincent
[snip]
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Thomas Mortagne _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
On Fri, Mar 29, 2013 at 4:47 PM, Jeremie BOUSQUET <[email protected]> wrote:
Mmmm, what could explain that standard login for "Admin" user does not work in the xwiki created by the packager plugin ? ("invalid credentials"). It used to work, maybe when I had dependency on xwiki-enterprise-ui-all ... ?
It's not really standard XWiki login, the Admin user come from adminitsrtion-ui, if you have that xar then you have the user.
Br, Jeremie
2013/3/29 Thomas Mortagne <[email protected]>
On Fri, Mar 29, 2013 at 3:05 PM, Jeremie BOUSQUET <[email protected]> wrote:
Ok found it in xwiki-rendering-macro-message. That's nice, looking into it, just realized that there existed a {{success}} macro ! Seems nice, is it intended that it's not described on extensions wiki as info/warning/error are ?
Probably been forgotten by the dev who introduced it.
Thanks, Jeremie
2013/3/29 Jeremie BOUSQUET <[email protected]>
Thanks ! I'm progressing, but it seems I have a hard time finding what to declare to get the info/warning/error macros ...
BR, Jeremie
2013/3/29 Vincent Massol <[email protected]>
On Mar 29, 2013, at 12:21 PM, Vincent Massol <[email protected]>
wrote:
On Mar 29, 2013, at 11:03 AM, Jeremie BOUSQUET <
[email protected]> wrote:
> Hello, > > Me again ... :-) > With fixed version of packager plugin, things go better now. XWiki
is
> downloaded and launched, my test browses to the page as I expect. > > Problem is that when browsing to my page, I can see the following in the > html content logged by the build: > > <div id="xwikicontent"> > <div class="xwikirenderingerror" style="cursor: pointer;" title="Read > technical information related to this error">Unknown macro: velocity[...] > > In fact, it seems wiki is running, but can't find any macro ... I tried to > add a dependency on xwiki-enterprise-ui-all xar, but with same result. I'm > not sure of what could be missing ?
I think I've noticed a bug related to this. For ex in my contrib project I depend on org.xwiki.platform:xwiki-platform-administration-ui. I was surprised when running my func test that the admin screen was missing the velocity and include macros for example. The reason I think is because in xwiki-platform-administration-ui the deps on velocity and include macros are of scope "runtime".
So IMO there's a bug in PackageMojo: it should draw transitive dependencies for the "runtime" scope.
I'll look into this.
Fixed in http://jira.xwiki.org/jira/browse/XWIKI-8983
Thanks -Vincent
However as Thomas said, you need to add the **direct** deps you need at runtime.
Thanks -Vincent
[snip]
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Thomas Mortagne _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Thomas Mortagne
On Fri, Mar 29, 2013 at 4:56 PM, Thomas Mortagne <[email protected]> wrote:
On Fri, Mar 29, 2013 at 4:47 PM, Jeremie BOUSQUET <[email protected]> wrote:
Mmmm, what could explain that standard login for "Admin" user does not work in the xwiki created by the packager plugin ? ("invalid credentials"). It used to work, maybe when I had dependency on xwiki-enterprise-ui-all ... ?
It's not really standard XWiki login, the Admin user come from adminitsrtion-ui, if you have that xar then you have the user.
administration-ui
Br, Jeremie
2013/3/29 Thomas Mortagne <[email protected]>
On Fri, Mar 29, 2013 at 3:05 PM, Jeremie BOUSQUET <[email protected]> wrote:
Ok found it in xwiki-rendering-macro-message. That's nice, looking into it, just realized that there existed a {{success}} macro ! Seems nice, is it intended that it's not described on extensions wiki as info/warning/error are ?
Probably been forgotten by the dev who introduced it.
Thanks, Jeremie
2013/3/29 Jeremie BOUSQUET <[email protected]>
Thanks ! I'm progressing, but it seems I have a hard time finding what to declare to get the info/warning/error macros ...
BR, Jeremie
2013/3/29 Vincent Massol <[email protected]>
On Mar 29, 2013, at 12:21 PM, Vincent Massol <[email protected]>
wrote:
> > On Mar 29, 2013, at 11:03 AM, Jeremie BOUSQUET < [email protected]> wrote: > >> Hello, >> >> Me again ... :-) >> With fixed version of packager plugin, things go better now. XWiki
is
>> downloaded and launched, my test browses to the page as I expect. >> >> Problem is that when browsing to my page, I can see the following in the >> html content logged by the build: >> >> <div id="xwikicontent"> >> <div class="xwikirenderingerror" style="cursor: pointer;" title="Read >> technical information related to this error">Unknown macro: velocity[...] >> >> In fact, it seems wiki is running, but can't find any macro ... I tried to >> add a dependency on xwiki-enterprise-ui-all xar, but with same result. I'm >> not sure of what could be missing ? > > I think I've noticed a bug related to this. For ex in my contrib project I depend on org.xwiki.platform:xwiki-platform-administration-ui. I was surprised when running my func test that the admin screen was missing the velocity and include macros for example. The reason I think is because in xwiki-platform-administration-ui the deps on velocity and include macros are of scope "runtime". > > So IMO there's a bug in PackageMojo: it should draw transitive dependencies for the "runtime" scope. > > I'll look into this.
Fixed in http://jira.xwiki.org/jira/browse/XWIKI-8983
Thanks -Vincent
> However as Thomas said, you need to add the **direct** deps you need at runtime. > > Thanks > -Vincent > > [snip]
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Thomas Mortagne _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Thomas Mortagne
-- Thomas Mortagne
Thanks Thomas, and sorry for that stack of questions :-/ Jeremie 2013/3/29 Thomas Mortagne <[email protected]>
On Fri, Mar 29, 2013 at 4:56 PM, Thomas Mortagne <[email protected]> wrote:
On Fri, Mar 29, 2013 at 4:47 PM, Jeremie BOUSQUET <[email protected]> wrote:
Mmmm, what could explain that standard login for "Admin" user does not work in the xwiki created by the packager plugin ? ("invalid credentials"). It used to work, maybe when I had dependency on xwiki-enterprise-ui-all ... ?
It's not really standard XWiki login, the Admin user come from adminitsrtion-ui, if you have that xar then you have the user.
administration-ui
Br, Jeremie
2013/3/29 Thomas Mortagne <[email protected]>
On Fri, Mar 29, 2013 at 3:05 PM, Jeremie BOUSQUET <[email protected]> wrote:
Ok found it in xwiki-rendering-macro-message. That's nice, looking into it, just realized that there existed a {{success}} macro ! Seems nice, is it intended that it's not
described on
extensions wiki as info/warning/error are ?
Probably been forgotten by the dev who introduced it.
Thanks, Jeremie
2013/3/29 Jeremie BOUSQUET <[email protected]>
Thanks ! I'm progressing, but it seems I have a hard time finding what to
declare
to get the info/warning/error macros ...
BR, Jeremie
2013/3/29 Vincent Massol <[email protected]>
> > On Mar 29, 2013, at 12:21 PM, Vincent Massol <[email protected]> wrote: > > > > > On Mar 29, 2013, at 11:03 AM, Jeremie BOUSQUET < > [email protected]> wrote: > > > >> Hello, > >> > >> Me again ... :-) > >> With fixed version of packager plugin, things go better now. XWiki is > >> downloaded and launched, my test browses to the page as I expect. > >> > >> Problem is that when browsing to my page, I can see the following in > the > >> html content logged by the build: > >> > >> <div id="xwikicontent"> > >> <div class="xwikirenderingerror" style="cursor: pointer;" title="Read > >> technical information related to this error">Unknown macro: > velocity[...] > >> > >> In fact, it seems wiki is running, but can't find any macro ... I > tried to > >> add a dependency on xwiki-enterprise-ui-all xar, but with same result. > I'm > >> not sure of what could be missing ? > > > > I think I've noticed a bug related to this. For ex in my contrib > project I depend on org.xwiki.platform:xwiki-platform-administration-ui. I > was surprised when running my func test that the admin screen was missing > the velocity and include macros for example. The reason I think is because > in xwiki-platform-administration-ui the deps on velocity and include macros > are of scope "runtime". > > > > So IMO there's a bug in PackageMojo: it should draw transitive > dependencies for the "runtime" scope. > > > > I'll look into this. > > Fixed in http://jira.xwiki.org/jira/browse/XWIKI-8983 > > Thanks > -Vincent > > > However as Thomas said, you need to add the **direct** deps you need at > runtime. > > > > Thanks > > -Vincent > > > > [snip] > > _______________________________________________ > users mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/users >
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Thomas Mortagne _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Thomas Mortagne
-- Thomas Mortagne _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
Another one: I'm debugging a livetable display, that shows empty rows instead of expected values. The issue I have seems to drill down to the fact that "$request.limit" resolves to "10" (well, the limit value), while "$request.get('limit')" resolves to null. Also, "$request.reqNo" equals "1" as expected, but "$util.parseInt($request.reqNo)" is null. I'm pretty sure that works on a standard XE, so there must be some magical spice missing in my dependencies (or configuration ?), in relation with velocity and bindings ... Do you know what could be that magical spice ? Thanks, Jeremie 2013/3/29 Jeremie BOUSQUET <[email protected]>
Thanks Thomas, and sorry for that stack of questions :-/
Jeremie
2013/3/29 Thomas Mortagne <[email protected]>
On Fri, Mar 29, 2013 at 4:56 PM, Thomas Mortagne <[email protected]> wrote:
On Fri, Mar 29, 2013 at 4:47 PM, Jeremie BOUSQUET <[email protected]> wrote:
Mmmm, what could explain that standard login for "Admin" user does not work in the xwiki created by the packager plugin ? ("invalid credentials"). It used to work, maybe when I had dependency on xwiki-enterprise-ui-all ... ?
It's not really standard XWiki login, the Admin user come from adminitsrtion-ui, if you have that xar then you have the user.
administration-ui
Br, Jeremie
2013/3/29 Thomas Mortagne <[email protected]>
On Fri, Mar 29, 2013 at 3:05 PM, Jeremie BOUSQUET <[email protected]> wrote:
Ok found it in xwiki-rendering-macro-message. That's nice, looking into it, just realized that there existed a {{success}} macro ! Seems nice, is it intended that it's not
described on
extensions wiki as info/warning/error are ?
Probably been forgotten by the dev who introduced it.
Thanks, Jeremie
2013/3/29 Jeremie BOUSQUET <[email protected]>
> Thanks ! > I'm progressing, but it seems I have a hard time finding what to
declare
> to get the info/warning/error macros ... > > BR, > Jeremie > > > > 2013/3/29 Vincent Massol <[email protected]> > >> >> On Mar 29, 2013, at 12:21 PM, Vincent Massol <[email protected]> wrote: >> >> > >> > On Mar 29, 2013, at 11:03 AM, Jeremie BOUSQUET < >> [email protected]> wrote: >> > >> >> Hello, >> >> >> >> Me again ... :-) >> >> With fixed version of packager plugin, things go better now. XWiki is >> >> downloaded and launched, my test browses to the page as I expect. >> >> >> >> Problem is that when browsing to my page, I can see the following in >> the >> >> html content logged by the build: >> >> >> >> <div id="xwikicontent"> >> >> <div class="xwikirenderingerror" style="cursor: pointer;" title="Read >> >> technical information related to this error">Unknown macro: >> velocity[...] >> >> >> >> In fact, it seems wiki is running, but can't find any macro ... I >> tried to >> >> add a dependency on xwiki-enterprise-ui-all xar, but with same result. >> I'm >> >> not sure of what could be missing ? >> > >> > I think I've noticed a bug related to this. For ex in my contrib >> project I depend on org.xwiki.platform:xwiki-platform-administration-ui. I >> was surprised when running my func test that the admin screen was missing >> the velocity and include macros for example. The reason I think is because >> in xwiki-platform-administration-ui the deps on velocity and include macros >> are of scope "runtime". >> > >> > So IMO there's a bug in PackageMojo: it should draw transitive >> dependencies for the "runtime" scope. >> > >> > I'll look into this. >> >> Fixed in http://jira.xwiki.org/jira/browse/XWIKI-8983 >> >> Thanks >> -Vincent >> >> > However as Thomas said, you need to add the **direct** deps you need at >> runtime. >> > >> > Thanks >> > -Vincent >> > >> > [snip] >> >> _______________________________________________ >> users mailing list >> [email protected] >> http://lists.xwiki.org/mailman/listinfo/users >> > > _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Thomas Mortagne _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Thomas Mortagne
-- Thomas Mortagne _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
Hello, Pinging about last point below ... I really don't understand what's bad in my setup, so any help to unblock would be very nice :-) BR, Jeremie 2013/3/29 Jeremie BOUSQUET <[email protected]>
Another one: I'm debugging a livetable display, that shows empty rows instead of expected values. The issue I have seems to drill down to the fact that "$request.limit" resolves to "10" (well, the limit value), while "$request.get('limit')" resolves to null. Also, "$request.reqNo" equals "1" as expected, but "$util.parseInt($request.reqNo)" is null. I'm pretty sure that works on a standard XE, so there must be some magical spice missing in my dependencies (or configuration ?), in relation with velocity and bindings ... Do you know what could be that magical spice ?
Thanks, Jeremie
2013/3/29 Jeremie BOUSQUET <[email protected]>
Thanks Thomas, and sorry for that stack of questions :-/
Jeremie
2013/3/29 Thomas Mortagne <[email protected]>
On Fri, Mar 29, 2013 at 4:56 PM, Thomas Mortagne <[email protected]> wrote:
On Fri, Mar 29, 2013 at 4:47 PM, Jeremie BOUSQUET <[email protected]> wrote:
Mmmm, what could explain that standard login for "Admin" user does not work in the xwiki created by the packager plugin ? ("invalid credentials"). It used to work, maybe when I had dependency on xwiki-enterprise-ui-all ... ?
It's not really standard XWiki login, the Admin user come from adminitsrtion-ui, if you have that xar then you have the user.
administration-ui
Br, Jeremie
2013/3/29 Thomas Mortagne <[email protected]>
On Fri, Mar 29, 2013 at 3:05 PM, Jeremie BOUSQUET <[email protected]> wrote: > Ok found it in xwiki-rendering-macro-message. > That's nice, looking into it, just realized that there existed a > {{success}} macro ! Seems nice, is it intended that it's not
described on
> extensions wiki as info/warning/error are ?
Probably been forgotten by the dev who introduced it.
> > Thanks, > Jeremie > > > 2013/3/29 Jeremie BOUSQUET <[email protected]> > >> Thanks ! >> I'm progressing, but it seems I have a hard time finding what to declare >> to get the info/warning/error macros ... >> >> BR, >> Jeremie >> >> >> >> 2013/3/29 Vincent Massol <[email protected]> >> >>> >>> On Mar 29, 2013, at 12:21 PM, Vincent Massol <[email protected]
wrote: >>> >>> > >>> > On Mar 29, 2013, at 11:03 AM, Jeremie BOUSQUET < >>> [email protected]> wrote: >>> > >>> >> Hello, >>> >> >>> >> Me again ... :-) >>> >> With fixed version of packager plugin, things go better now. XWiki is >>> >> downloaded and launched, my test browses to the page as I expect. >>> >> >>> >> Problem is that when browsing to my page, I can see the following in >>> the >>> >> html content logged by the build: >>> >> >>> >> <div id="xwikicontent"> >>> >> <div class="xwikirenderingerror" style="cursor: pointer;" title="Read >>> >> technical information related to this error">Unknown macro: >>> velocity[...] >>> >> >>> >> In fact, it seems wiki is running, but can't find any macro ... I >>> tried to >>> >> add a dependency on xwiki-enterprise-ui-all xar, but with same result. >>> I'm >>> >> not sure of what could be missing ? >>> > >>> > I think I've noticed a bug related to this. For ex in my contrib >>> project I depend on org.xwiki.platform:xwiki-platform-administration-ui. I >>> was surprised when running my func test that the admin screen was missing >>> the velocity and include macros for example. The reason I think is because >>> in xwiki-platform-administration-ui the deps on velocity and include macros >>> are of scope "runtime". >>> > >>> > So IMO there's a bug in PackageMojo: it should draw transitive >>> dependencies for the "runtime" scope. >>> > >>> > I'll look into this. >>> >>> Fixed in http://jira.xwiki.org/jira/browse/XWIKI-8983 >>> >>> Thanks >>> -Vincent >>> >>> > However as Thomas said, you need to add the **direct** deps you need at >>> runtime. >>> > >>> > Thanks >>> > -Vincent >>> > >>> > [snip] >>> >>> _______________________________________________ >>> users mailing list >>> [email protected] >>> http://lists.xwiki.org/mailman/listinfo/users >>> >> >> > _______________________________________________ > users mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/users
-- Thomas Mortagne _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Thomas Mortagne
-- Thomas Mortagne _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
I would check the index tests ( https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik... ) since they test indirectly the live table. Hope this helps, Marius On Thu, Apr 25, 2013 at 6:41 PM, Jeremie BOUSQUET <[email protected]> wrote:
Hello,
Pinging about last point below ... I really don't understand what's bad in my setup, so any help to unblock would be very nice :-)
BR, Jeremie
2013/3/29 Jeremie BOUSQUET <[email protected]>
Another one: I'm debugging a livetable display, that shows empty rows instead of expected values. The issue I have seems to drill down to the fact that "$request.limit" resolves to "10" (well, the limit value), while "$request.get('limit')" resolves to null. Also, "$request.reqNo" equals "1" as expected, but "$util.parseInt($request.reqNo)" is null. I'm pretty sure that works on a standard XE, so there must be some magical spice missing in my dependencies (or configuration ?), in relation with velocity and bindings ... Do you know what could be that magical spice ?
Thanks, Jeremie
2013/3/29 Jeremie BOUSQUET <[email protected]>
Thanks Thomas, and sorry for that stack of questions :-/
Jeremie
2013/3/29 Thomas Mortagne <[email protected]>
On Fri, Mar 29, 2013 at 4:56 PM, Thomas Mortagne <[email protected]> wrote:
On Fri, Mar 29, 2013 at 4:47 PM, Jeremie BOUSQUET <[email protected]> wrote:
Mmmm, what could explain that standard login for "Admin" user does not work in the xwiki created by the packager plugin ? ("invalid credentials"). It used to work, maybe when I had dependency on xwiki-enterprise-ui-all ... ?
It's not really standard XWiki login, the Admin user come from adminitsrtion-ui, if you have that xar then you have the user.
administration-ui
Br, Jeremie
2013/3/29 Thomas Mortagne <[email protected]>
> On Fri, Mar 29, 2013 at 3:05 PM, Jeremie BOUSQUET > <[email protected]> wrote: > > Ok found it in xwiki-rendering-macro-message. > > That's nice, looking into it, just realized that there existed a > > {{success}} macro ! Seems nice, is it intended that it's not
described on
> > extensions wiki as info/warning/error are ? > > Probably been forgotten by the dev who introduced it. > > > > > Thanks, > > Jeremie > > > > > > 2013/3/29 Jeremie BOUSQUET <[email protected]> > > > >> Thanks ! > >> I'm progressing, but it seems I have a hard time finding what to declare > >> to get the info/warning/error macros ... > >> > >> BR, > >> Jeremie > >> > >> > >> > >> 2013/3/29 Vincent Massol <[email protected]> > >> > >>> > >>> On Mar 29, 2013, at 12:21 PM, Vincent Massol <[email protected]
> wrote: > >>> > >>> > > >>> > On Mar 29, 2013, at 11:03 AM, Jeremie BOUSQUET < > >>> [email protected]> wrote: > >>> > > >>> >> Hello, > >>> >> > >>> >> Me again ... :-) > >>> >> With fixed version of packager plugin, things go better now. XWiki > is > >>> >> downloaded and launched, my test browses to the page as I expect. > >>> >> > >>> >> Problem is that when browsing to my page, I can see the following in > >>> the > >>> >> html content logged by the build: > >>> >> > >>> >> <div id="xwikicontent"> > >>> >> <div class="xwikirenderingerror" style="cursor: pointer;" > title="Read > >>> >> technical information related to this error">Unknown macro: > >>> velocity[...] > >>> >> > >>> >> In fact, it seems wiki is running, but can't find any macro ... I > >>> tried to > >>> >> add a dependency on xwiki-enterprise-ui-all xar, but with same > result. > >>> I'm > >>> >> not sure of what could be missing ? > >>> > > >>> > I think I've noticed a bug related to this. For ex in my contrib > >>> project I depend on > org.xwiki.platform:xwiki-platform-administration-ui. I > >>> was surprised when running my func test that the admin screen was > missing > >>> the velocity and include macros for example. The reason I think is > because > >>> in xwiki-platform-administration-ui the deps on velocity and include > macros > >>> are of scope "runtime". > >>> > > >>> > So IMO there's a bug in PackageMojo: it should draw transitive > >>> dependencies for the "runtime" scope. > >>> > > >>> > I'll look into this. > >>> > >>> Fixed in http://jira.xwiki.org/jira/browse/XWIKI-8983 > >>> > >>> Thanks > >>> -Vincent > >>> > >>> > However as Thomas said, you need to add the **direct** deps you need > at > >>> runtime. > >>> > > >>> > Thanks > >>> > -Vincent > >>> > > >>> > [snip] > >>> > >>> _______________________________________________ > >>> users mailing list > >>> [email protected] > >>> http://lists.xwiki.org/mailman/listinfo/users > >>> > >> > >> > > _______________________________________________ > > users mailing list > > [email protected] > > http://lists.xwiki.org/mailman/listinfo/users > > > > -- > Thomas Mortagne > _______________________________________________ > users mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/users > _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Thomas Mortagne
-- Thomas Mortagne _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
Thanks, But I did not find any noticeable differences with my own setup ... I've got the same list of dependencies, with additional ones. Only difference would be that I depend on 4.5.3 artifacts, and use packager plugin 5.0-milestone-2 (for a fix I need). I tried also with packager 5.0-rc-1, but with same result. BR, Jeremie 2013/4/25 Marius Dumitru Florea <[email protected]>
I would check the index tests (
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik... ) since they test indirectly the live table.
Hope this helps, Marius
On Thu, Apr 25, 2013 at 6:41 PM, Jeremie BOUSQUET <[email protected]> wrote:
Hello,
Pinging about last point below ... I really don't understand what's bad in my setup, so any help to unblock would be very nice :-)
BR, Jeremie
2013/3/29 Jeremie BOUSQUET <[email protected]>
Another one: I'm debugging a livetable display, that shows empty rows instead of expected values. The issue I have seems to drill down to the fact that "$request.limit" resolves to "10" (well, the limit value), while "$request.get('limit')" resolves to null. Also, "$request.reqNo" equals "1" as expected, but "$util.parseInt($request.reqNo)" is null. I'm pretty sure that works on a standard XE, so there must be some magical spice missing in my dependencies (or configuration ?), in relation with velocity and bindings ... Do you know what could be that magical spice ?
Thanks, Jeremie
2013/3/29 Jeremie BOUSQUET <[email protected]>
Thanks Thomas, and sorry for that stack of questions :-/
Jeremie
2013/3/29 Thomas Mortagne <[email protected]>
On Fri, Mar 29, 2013 at 4:56 PM, Thomas Mortagne <[email protected]> wrote:
On Fri, Mar 29, 2013 at 4:47 PM, Jeremie BOUSQUET <[email protected]> wrote: > Mmmm, what could explain that standard login for "Admin" user does not work > in the xwiki created by the packager plugin ? ("invalid credentials"). > It used to work, maybe when I had dependency on xwiki-enterprise-ui-all ... > ?
It's not really standard XWiki login, the Admin user come from adminitsrtion-ui, if you have that xar then you have the user.
administration-ui
> > Br, > Jeremie > > > 2013/3/29 Thomas Mortagne <[email protected]> > >> On Fri, Mar 29, 2013 at 3:05 PM, Jeremie BOUSQUET >> <[email protected]> wrote: >> > Ok found it in xwiki-rendering-macro-message. >> > That's nice, looking into it, just realized that there existed a >> > {{success}} macro ! Seems nice, is it intended that it's not
described on
>> > extensions wiki as info/warning/error are ? >> >> Probably been forgotten by the dev who introduced it. >> >> > >> > Thanks, >> > Jeremie >> > >> > >> > 2013/3/29 Jeremie BOUSQUET <[email protected]> >> > >> >> Thanks ! >> >> I'm progressing, but it seems I have a hard time finding what to declare >> >> to get the info/warning/error macros ... >> >> >> >> BR, >> >> Jeremie >> >> >> >> >> >> >> >> 2013/3/29 Vincent Massol <[email protected]> >> >> >> >>> >> >>> On Mar 29, 2013, at 12:21 PM, Vincent Massol < [email protected]
>> wrote: >> >>> >> >>> > >> >>> > On Mar 29, 2013, at 11:03 AM, Jeremie BOUSQUET < >> >>> [email protected]> wrote: >> >>> > >> >>> >> Hello, >> >>> >> >> >>> >> Me again ... :-) >> >>> >> With fixed version of packager plugin, things go better now. XWiki >> is >> >>> >> downloaded and launched, my test browses to the page as I expect. >> >>> >> >> >>> >> Problem is that when browsing to my page, I can see the following in >> >>> the >> >>> >> html content logged by the build: >> >>> >> >> >>> >> <div id="xwikicontent"> >> >>> >> <div class="xwikirenderingerror" style="cursor: pointer;" >> title="Read >> >>> >> technical information related to this error">Unknown macro: >> >>> velocity[...] >> >>> >> >> >>> >> In fact, it seems wiki is running, but can't find any macro ... I >> >>> tried to >> >>> >> add a dependency on xwiki-enterprise-ui-all xar, but with same >> result. >> >>> I'm >> >>> >> not sure of what could be missing ? >> >>> > >> >>> > I think I've noticed a bug related to this. For ex in my contrib >> >>> project I depend on >> org.xwiki.platform:xwiki-platform-administration-ui. I >> >>> was surprised when running my func test that the admin screen was >> missing >> >>> the velocity and include macros for example. The reason I think is >> because >> >>> in xwiki-platform-administration-ui the deps on velocity and include >> macros >> >>> are of scope "runtime". >> >>> > >> >>> > So IMO there's a bug in PackageMojo: it should draw transitive >> >>> dependencies for the "runtime" scope. >> >>> > >> >>> > I'll look into this. >> >>> >> >>> Fixed in http://jira.xwiki.org/jira/browse/XWIKI-8983 >> >>> >> >>> Thanks >> >>> -Vincent >> >>> >> >>> > However as Thomas said, you need to add the **direct** deps you need >> at >> >>> runtime. >> >>> > >> >>> > Thanks >> >>> > -Vincent >> >>> > >> >>> > [snip] >> >>> >> >>> _______________________________________________ >> >>> users mailing list >> >>> [email protected] >> >>> http://lists.xwiki.org/mailman/listinfo/users >> >>> >> >> >> >> >> > _______________________________________________ >> > users mailing list >> > [email protected] >> > http://lists.xwiki.org/mailman/listinfo/users >> >> >> >> -- >> Thomas Mortagne >> _______________________________________________ >> users mailing list >> [email protected] >> http://lists.xwiki.org/mailman/listinfo/users >> > _______________________________________________ > users mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/users
-- Thomas Mortagne
-- Thomas Mortagne _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
Hello, I think I found the problem and why it happened ... I performed a diff between a fresh install of xe 4.5.2 and the xwiki created by my functional tests, and restricted to the following list of dependencies that were missing: xwiki-platform-legacy-annotation-4.5.2.jar xwiki-platform-legacy-model-4.5.2.jar xwiki-platform-legacy-observation-4.5.2.jar xwiki-platform-legacy-oldcore-4.5.2.jar I think it's because I used customized pages for LiveTableResults and LiveTableResultsMacros, but based on an older version... BR, Jeremie 2013/4/26 Jeremie BOUSQUET <[email protected]>
Thanks,
But I did not find any noticeable differences with my own setup ... I've got the same list of dependencies, with additional ones. Only difference would be that I depend on 4.5.3 artifacts, and use packager plugin 5.0-milestone-2 (for a fix I need). I tried also with packager 5.0-rc-1, but with same result.
BR, Jeremie
2013/4/25 Marius Dumitru Florea <[email protected]>
I would check the index tests (
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik... ) since they test indirectly the live table.
Hope this helps, Marius
On Thu, Apr 25, 2013 at 6:41 PM, Jeremie BOUSQUET <[email protected]> wrote:
Hello,
Pinging about last point below ... I really don't understand what's bad in my setup, so any help to unblock would be very nice :-)
BR, Jeremie
2013/3/29 Jeremie BOUSQUET <[email protected]>
Another one: I'm debugging a livetable display, that shows empty rows instead of expected values. The issue I have seems to drill down to the fact that "$request.limit" resolves to "10" (well, the limit value), while "$request.get('limit')" resolves to null. Also, "$request.reqNo" equals "1" as expected, but "$util.parseInt($request.reqNo)" is null. I'm pretty sure that works on a standard XE, so there must be some magical spice missing in my dependencies (or configuration ?), in relation with velocity and bindings ... Do you know what could be that magical spice ?
Thanks, Jeremie
2013/3/29 Jeremie BOUSQUET <[email protected]>
Thanks Thomas, and sorry for that stack of questions :-/
Jeremie
2013/3/29 Thomas Mortagne <[email protected]>
On Fri, Mar 29, 2013 at 4:56 PM, Thomas Mortagne <[email protected]> wrote: > On Fri, Mar 29, 2013 at 4:47 PM, Jeremie BOUSQUET > <[email protected]> wrote: >> Mmmm, what could explain that standard login for "Admin" user does not work >> in the xwiki created by the packager plugin ? ("invalid credentials"). >> It used to work, maybe when I had dependency on xwiki-enterprise-ui-all ... >> ? > > It's not really standard XWiki login, the Admin user come from > adminitsrtion-ui, if you have that xar then you have the user.
administration-ui
> >> >> Br, >> Jeremie >> >> >> 2013/3/29 Thomas Mortagne <[email protected]> >> >>> On Fri, Mar 29, 2013 at 3:05 PM, Jeremie BOUSQUET >>> <[email protected]> wrote: >>> > Ok found it in xwiki-rendering-macro-message. >>> > That's nice, looking into it, just realized that there existed a >>> > {{success}} macro ! Seems nice, is it intended that it's not described on >>> > extensions wiki as info/warning/error are ? >>> >>> Probably been forgotten by the dev who introduced it. >>> >>> > >>> > Thanks, >>> > Jeremie >>> > >>> > >>> > 2013/3/29 Jeremie BOUSQUET <[email protected]> >>> > >>> >> Thanks ! >>> >> I'm progressing, but it seems I have a hard time finding what to declare >>> >> to get the info/warning/error macros ... >>> >> >>> >> BR, >>> >> Jeremie >>> >> >>> >> >>> >> >>> >> 2013/3/29 Vincent Massol <[email protected]> >>> >> >>> >>> >>> >>> On Mar 29, 2013, at 12:21 PM, Vincent Massol < [email protected] > >>> wrote: >>> >>> >>> >>> > >>> >>> > On Mar 29, 2013, at 11:03 AM, Jeremie BOUSQUET < >>> >>> [email protected]> wrote: >>> >>> > >>> >>> >> Hello, >>> >>> >> >>> >>> >> Me again ... :-) >>> >>> >> With fixed version of packager plugin, things go better now. XWiki >>> is >>> >>> >> downloaded and launched, my test browses to the page as I expect. >>> >>> >> >>> >>> >> Problem is that when browsing to my page, I can see the following in >>> >>> the >>> >>> >> html content logged by the build: >>> >>> >> >>> >>> >> <div id="xwikicontent"> >>> >>> >> <div class="xwikirenderingerror" style="cursor: pointer;" >>> title="Read >>> >>> >> technical information related to this error">Unknown macro: >>> >>> velocity[...] >>> >>> >> >>> >>> >> In fact, it seems wiki is running, but can't find any macro ... I >>> >>> tried to >>> >>> >> add a dependency on xwiki-enterprise-ui-all xar, but with same >>> result. >>> >>> I'm >>> >>> >> not sure of what could be missing ? >>> >>> > >>> >>> > I think I've noticed a bug related to this. For ex in my contrib >>> >>> project I depend on >>> org.xwiki.platform:xwiki-platform-administration-ui. I >>> >>> was surprised when running my func test that the admin screen was >>> missing >>> >>> the velocity and include macros for example. The reason I think is >>> because >>> >>> in xwiki-platform-administration-ui the deps on velocity and include >>> macros >>> >>> are of scope "runtime". >>> >>> > >>> >>> > So IMO there's a bug in PackageMojo: it should draw transitive >>> >>> dependencies for the "runtime" scope. >>> >>> > >>> >>> > I'll look into this. >>> >>> >>> >>> Fixed in http://jira.xwiki.org/jira/browse/XWIKI-8983 >>> >>> >>> >>> Thanks >>> >>> -Vincent >>> >>> >>> >>> > However as Thomas said, you need to add the **direct** deps you need >>> at >>> >>> runtime. >>> >>> > >>> >>> > Thanks >>> >>> > -Vincent >>> >>> > >>> >>> > [snip] >>> >>> >>> >>> _______________________________________________ >>> >>> users mailing list >>> >>> [email protected] >>> >>> http://lists.xwiki.org/mailman/listinfo/users >>> >>> >>> >> >>> >> >>> > _______________________________________________ >>> > users mailing list >>> > [email protected] >>> > http://lists.xwiki.org/mailman/listinfo/users >>> >>> >>> >>> -- >>> Thomas Mortagne >>> _______________________________________________ >>> users mailing list >>> [email protected] >>> http://lists.xwiki.org/mailman/listinfo/users >>> >> _______________________________________________ >> users mailing list >> [email protected] >> http://lists.xwiki.org/mailman/listinfo/users > > > > -- > Thomas Mortagne
-- Thomas Mortagne _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
Mmmm... [WARNING] Rule 0: org.xwiki.tool.enforcer.XWikiBannedDependencies failed with message: Don't depend on a XWiki Legacy module! Found Banned Dependency: org.xwiki.platform:xwiki-platform-legacy-annotation:jar:4.5.2 Found Banned Dependency: org.xwiki.platform:xwiki-platform-legacy-observation:jar:4.5.2 Found Banned Dependency: org.xwiki.platform:xwiki-platform-legacy-model:jar:4.5.2 Use 'mvn dependency:tree' to locate the source of the banned dependencies. Why's that ? Why are they banned considering they are released with xwiki ? BR, Jeremie 2013/5/18 Jeremie BOUSQUET <[email protected]>
Hello,
I think I found the problem and why it happened ... I performed a diff between a fresh install of xe 4.5.2 and the xwiki created by my functional tests, and restricted to the following list of dependencies that were missing: xwiki-platform-legacy-annotation-4.5.2.jar xwiki-platform-legacy-model-4.5.2.jar xwiki-platform-legacy-observation-4.5.2.jar xwiki-platform-legacy-oldcore-4.5.2.jar
I think it's because I used customized pages for LiveTableResults and LiveTableResultsMacros, but based on an older version...
BR, Jeremie
2013/4/26 Jeremie BOUSQUET <[email protected]>
Thanks,
But I did not find any noticeable differences with my own setup ... I've got the same list of dependencies, with additional ones. Only difference would be that I depend on 4.5.3 artifacts, and use packager plugin 5.0-milestone-2 (for a fix I need). I tried also with packager 5.0-rc-1, but with same result.
BR, Jeremie
2013/4/25 Marius Dumitru Florea <[email protected]>
I would check the index tests (
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik... ) since they test indirectly the live table.
Hope this helps, Marius
On Thu, Apr 25, 2013 at 6:41 PM, Jeremie BOUSQUET <[email protected]> wrote:
Hello,
Pinging about last point below ... I really don't understand what's bad in my setup, so any help to unblock would be very nice :-)
BR, Jeremie
2013/3/29 Jeremie BOUSQUET <[email protected]>
Another one: I'm debugging a livetable display, that shows empty rows instead of expected values. The issue I have seems to drill down to the fact that "$request.limit" resolves to "10" (well, the limit value), while "$request.get('limit')" resolves to null. Also, "$request.reqNo" equals "1" as expected, but "$util.parseInt($request.reqNo)" is null. I'm pretty sure that works on a standard XE, so there must be some magical spice missing in my dependencies (or configuration ?), in relation with velocity and bindings ... Do you know what could be that magical spice ?
Thanks, Jeremie
2013/3/29 Jeremie BOUSQUET <[email protected]>
Thanks Thomas, and sorry for that stack of questions :-/
Jeremie
2013/3/29 Thomas Mortagne <[email protected]>
> On Fri, Mar 29, 2013 at 4:56 PM, Thomas Mortagne > <[email protected]> wrote: > > On Fri, Mar 29, 2013 at 4:47 PM, Jeremie BOUSQUET > > <[email protected]> wrote: > >> Mmmm, what could explain that standard login for "Admin" user does > not work > >> in the xwiki created by the packager plugin ? ("invalid credentials"). > >> It used to work, maybe when I had dependency on > xwiki-enterprise-ui-all ... > >> ? > > > > It's not really standard XWiki login, the Admin user come from > > adminitsrtion-ui, if you have that xar then you have the user. > > administration-ui > > > > >> > >> Br, > >> Jeremie > >> > >> > >> 2013/3/29 Thomas Mortagne <[email protected]> > >> > >>> On Fri, Mar 29, 2013 at 3:05 PM, Jeremie BOUSQUET > >>> <[email protected]> wrote: > >>> > Ok found it in xwiki-rendering-macro-message. > >>> > That's nice, looking into it, just realized that there existed a > >>> > {{success}} macro ! Seems nice, is it intended that it's not > described on > >>> > extensions wiki as info/warning/error are ? > >>> > >>> Probably been forgotten by the dev who introduced it. > >>> > >>> > > >>> > Thanks, > >>> > Jeremie > >>> > > >>> > > >>> > 2013/3/29 Jeremie BOUSQUET <[email protected]> > >>> > > >>> >> Thanks ! > >>> >> I'm progressing, but it seems I have a hard time finding what to > declare > >>> >> to get the info/warning/error macros ... > >>> >> > >>> >> BR, > >>> >> Jeremie > >>> >> > >>> >> > >>> >> > >>> >> 2013/3/29 Vincent Massol <[email protected]> > >>> >> > >>> >>> > >>> >>> On Mar 29, 2013, at 12:21 PM, Vincent Massol < [email protected] > > > >>> wrote: > >>> >>> > >>> >>> > > >>> >>> > On Mar 29, 2013, at 11:03 AM, Jeremie BOUSQUET < > >>> >>> [email protected]> wrote: > >>> >>> > > >>> >>> >> Hello, > >>> >>> >> > >>> >>> >> Me again ... :-) > >>> >>> >> With fixed version of packager plugin, things go better now. > XWiki > >>> is > >>> >>> >> downloaded and launched, my test browses to the page as I > expect. > >>> >>> >> > >>> >>> >> Problem is that when browsing to my page, I can see the > following in > >>> >>> the > >>> >>> >> html content logged by the build: > >>> >>> >> > >>> >>> >> <div id="xwikicontent"> > >>> >>> >> <div class="xwikirenderingerror" style="cursor: pointer;" > >>> title="Read > >>> >>> >> technical information related to this error">Unknown macro: > >>> >>> velocity[...] > >>> >>> >> > >>> >>> >> In fact, it seems wiki is running, but can't find any macro > ... I > >>> >>> tried to > >>> >>> >> add a dependency on xwiki-enterprise-ui-all xar, but with same > >>> result. > >>> >>> I'm > >>> >>> >> not sure of what could be missing ? > >>> >>> > > >>> >>> > I think I've noticed a bug related to this. For ex in my > contrib > >>> >>> project I depend on > >>> org.xwiki.platform:xwiki-platform-administration-ui. I > >>> >>> was surprised when running my func test that the admin screen was > >>> missing > >>> >>> the velocity and include macros for example. The reason I think > is > >>> because > >>> >>> in xwiki-platform-administration-ui the deps on velocity and > include > >>> macros > >>> >>> are of scope "runtime". > >>> >>> > > >>> >>> > So IMO there's a bug in PackageMojo: it should draw transitive > >>> >>> dependencies for the "runtime" scope. > >>> >>> > > >>> >>> > I'll look into this. > >>> >>> > >>> >>> Fixed in http://jira.xwiki.org/jira/browse/XWIKI-8983 > >>> >>> > >>> >>> Thanks > >>> >>> -Vincent > >>> >>> > >>> >>> > However as Thomas said, you need to add the **direct** deps > you need > >>> at > >>> >>> runtime. > >>> >>> > > >>> >>> > Thanks > >>> >>> > -Vincent > >>> >>> > > >>> >>> > [snip] > >>> >>> > >>> >>> _______________________________________________ > >>> >>> users mailing list > >>> >>> [email protected] > >>> >>> http://lists.xwiki.org/mailman/listinfo/users > >>> >>> > >>> >> > >>> >> > >>> > _______________________________________________ > >>> > users mailing list > >>> > [email protected] > >>> > http://lists.xwiki.org/mailman/listinfo/users > >>> > >>> > >>> > >>> -- > >>> Thomas Mortagne > >>> _______________________________________________ > >>> users mailing list > >>> [email protected] > >>> http://lists.xwiki.org/mailman/listinfo/users > >>> > >> _______________________________________________ > >> users mailing list > >> [email protected] > >> http://lists.xwiki.org/mailman/listinfo/users > > > > > > > > -- > > Thomas Mortagne > > > > -- > Thomas Mortagne > _______________________________________________ > users mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/users >
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
So, after merging back the 4.5.2 macros, my test works !! That was... exhausting :) J. Le 18 mai 2013 18:09, "Jeremie BOUSQUET" <[email protected]> a écrit :
Mmmm...
[WARNING] Rule 0: org.xwiki.tool.enforcer.XWikiBannedDependencies failed with message: Don't depend on a XWiki Legacy module! Found Banned Dependency: org.xwiki.platform:xwiki-platform-legacy-annotation:jar:4.5.2 Found Banned Dependency: org.xwiki.platform:xwiki-platform-legacy-observation:jar:4.5.2 Found Banned Dependency: org.xwiki.platform:xwiki-platform-legacy-model:jar:4.5.2 Use 'mvn dependency:tree' to locate the source of the banned dependencies.
Why's that ? Why are they banned considering they are released with xwiki ?
BR, Jeremie
2013/5/18 Jeremie BOUSQUET <[email protected]>
Hello,
I think I found the problem and why it happened ... I performed a diff between a fresh install of xe 4.5.2 and the xwiki created by my functional tests, and restricted to the following list of dependencies that were missing: xwiki-platform-legacy-annotation-4.5.2.jar xwiki-platform-legacy-model-4.5.2.jar xwiki-platform-legacy-observation-4.5.2.jar xwiki-platform-legacy-oldcore-4.5.2.jar
I think it's because I used customized pages for LiveTableResults and LiveTableResultsMacros, but based on an older version...
BR, Jeremie
2013/4/26 Jeremie BOUSQUET <[email protected]>
Thanks,
But I did not find any noticeable differences with my own setup ... I've got the same list of dependencies, with additional ones. Only difference would be that I depend on 4.5.3 artifacts, and use packager plugin 5.0-milestone-2 (for a fix I need). I tried also with packager 5.0-rc-1, but with same result.
BR, Jeremie
2013/4/25 Marius Dumitru Florea <[email protected]>
I would check the index tests (
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik... ) since they test indirectly the live table.
Hope this helps, Marius
On Thu, Apr 25, 2013 at 6:41 PM, Jeremie BOUSQUET <[email protected]> wrote:
Hello,
Pinging about last point below ... I really don't understand what's bad in my setup, so any help to unblock would be very nice :-)
BR, Jeremie
2013/3/29 Jeremie BOUSQUET <[email protected]>
Another one: I'm debugging a livetable display, that shows empty rows instead of expected values. The issue I have seems to drill down to the fact that "$request.limit" resolves to "10" (well, the limit value), while "$request.get('limit')" resolves to null. Also, "$request.reqNo" equals "1" as expected, but "$util.parseInt($request.reqNo)" is null. I'm pretty sure that works on a standard XE, so there must be some magical spice missing in my dependencies (or configuration ?), in relation with velocity and bindings ... Do you know what could be that magical spice ?
Thanks, Jeremie
2013/3/29 Jeremie BOUSQUET <[email protected]>
> Thanks Thomas, and sorry for that stack of questions :-/ > > Jeremie > > > 2013/3/29 Thomas Mortagne <[email protected]> > >> On Fri, Mar 29, 2013 at 4:56 PM, Thomas Mortagne >> <[email protected]> wrote: >> > On Fri, Mar 29, 2013 at 4:47 PM, Jeremie BOUSQUET >> > <[email protected]> wrote: >> >> Mmmm, what could explain that standard login for "Admin" user does >> not work >> >> in the xwiki created by the packager plugin ? ("invalid credentials"). >> >> It used to work, maybe when I had dependency on >> xwiki-enterprise-ui-all ... >> >> ? >> > >> > It's not really standard XWiki login, the Admin user come from >> > adminitsrtion-ui, if you have that xar then you have the user. >> >> administration-ui >> >> > >> >> >> >> Br, >> >> Jeremie >> >> >> >> >> >> 2013/3/29 Thomas Mortagne <[email protected]> >> >> >> >>> On Fri, Mar 29, 2013 at 3:05 PM, Jeremie BOUSQUET >> >>> <[email protected]> wrote: >> >>> > Ok found it in xwiki-rendering-macro-message. >> >>> > That's nice, looking into it, just realized that there existed a >> >>> > {{success}} macro ! Seems nice, is it intended that it's not >> described on >> >>> > extensions wiki as info/warning/error are ? >> >>> >> >>> Probably been forgotten by the dev who introduced it. >> >>> >> >>> > >> >>> > Thanks, >> >>> > Jeremie >> >>> > >> >>> > >> >>> > 2013/3/29 Jeremie BOUSQUET <[email protected]> >> >>> > >> >>> >> Thanks ! >> >>> >> I'm progressing, but it seems I have a hard time finding what to >> declare >> >>> >> to get the info/warning/error macros ... >> >>> >> >> >>> >> BR, >> >>> >> Jeremie >> >>> >> >> >>> >> >> >>> >> >> >>> >> 2013/3/29 Vincent Massol <[email protected]> >> >>> >> >> >>> >>> >> >>> >>> On Mar 29, 2013, at 12:21 PM, Vincent Massol < [email protected] >> > >> >>> wrote: >> >>> >>> >> >>> >>> > >> >>> >>> > On Mar 29, 2013, at 11:03 AM, Jeremie BOUSQUET < >> >>> >>> [email protected]> wrote: >> >>> >>> > >> >>> >>> >> Hello, >> >>> >>> >> >> >>> >>> >> Me again ... :-) >> >>> >>> >> With fixed version of packager plugin, things go better now. >> XWiki >> >>> is >> >>> >>> >> downloaded and launched, my test browses to the page as I >> expect. >> >>> >>> >> >> >>> >>> >> Problem is that when browsing to my page, I can see the >> following in >> >>> >>> the >> >>> >>> >> html content logged by the build: >> >>> >>> >> >> >>> >>> >> <div id="xwikicontent"> >> >>> >>> >> <div class="xwikirenderingerror" style="cursor: pointer;" >> >>> title="Read >> >>> >>> >> technical information related to this error">Unknown macro: >> >>> >>> velocity[...] >> >>> >>> >> >> >>> >>> >> In fact, it seems wiki is running, but can't find any macro >> ... I >> >>> >>> tried to >> >>> >>> >> add a dependency on xwiki-enterprise-ui-all xar, but with same >> >>> result. >> >>> >>> I'm >> >>> >>> >> not sure of what could be missing ? >> >>> >>> > >> >>> >>> > I think I've noticed a bug related to this. For ex in my >> contrib >> >>> >>> project I depend on >> >>> org.xwiki.platform:xwiki-platform-administration-ui. I >> >>> >>> was surprised when running my func test that the admin screen was >> >>> missing >> >>> >>> the velocity and include macros for example. The reason I think >> is >> >>> because >> >>> >>> in xwiki-platform-administration-ui the deps on velocity and >> include >> >>> macros >> >>> >>> are of scope "runtime". >> >>> >>> > >> >>> >>> > So IMO there's a bug in PackageMojo: it should draw transitive >> >>> >>> dependencies for the "runtime" scope. >> >>> >>> > >> >>> >>> > I'll look into this. >> >>> >>> >> >>> >>> Fixed in http://jira.xwiki.org/jira/browse/XWIKI-8983 >> >>> >>> >> >>> >>> Thanks >> >>> >>> -Vincent >> >>> >>> >> >>> >>> > However as Thomas said, you need to add the **direct** deps >> you need >> >>> at >> >>> >>> runtime. >> >>> >>> > >> >>> >>> > Thanks >> >>> >>> > -Vincent >> >>> >>> > >> >>> >>> > [snip] >> >>> >>> >> >>> >>> _______________________________________________ >> >>> >>> users mailing list >> >>> >>> [email protected] >> >>> >>> http://lists.xwiki.org/mailman/listinfo/users >> >>> >>> >> >>> >> >> >>> >> >> >>> > _______________________________________________ >> >>> > users mailing list >> >>> > [email protected] >> >>> > http://lists.xwiki.org/mailman/listinfo/users >> >>> >> >>> >> >>> >> >>> -- >> >>> Thomas Mortagne >> >>> _______________________________________________ >> >>> users mailing list >> >>> [email protected] >> >>> http://lists.xwiki.org/mailman/listinfo/users >> >>> >> >> _______________________________________________ >> >> users mailing list >> >> [email protected] >> >> http://lists.xwiki.org/mailman/listinfo/users >> > >> > >> > >> > -- >> > Thomas Mortagne >> >> >> >> -- >> Thomas Mortagne >> _______________________________________________ >> users mailing list >> [email protected] >> http://lists.xwiki.org/mailman/listinfo/users >> > >
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
On Sat, May 18, 2013 at 7:09 PM, Jeremie BOUSQUET <[email protected]> wrote:
Mmmm...
[WARNING] Rule 0: org.xwiki.tool.enforcer.XWikiBannedDependencies failed with message: Don't depend on a XWiki Legacy module! Found Banned Dependency: org.xwiki.platform:xwiki-platform-legacy-annotation:jar:4.5.2 Found Banned Dependency: org.xwiki.platform:xwiki-platform-legacy-observation:jar:4.5.2 Found Banned Dependency: org.xwiki.platform:xwiki-platform-legacy-model:jar:4.5.2 Use 'mvn dependency:tree' to locate the source of the banned dependencies.
Why's that ? Why are they banned considering they are released with xwiki ?
They are packaged in order to preserve backwards compatibility but the code in platform and the code that uses the platform POMs should not depend on the legacy modules. This ensures that the platform code doesn't use legacy code (which is kept, as I said, only for backwards compatibility). Hope this helps, Marius
BR, Jeremie
2013/5/18 Jeremie BOUSQUET <[email protected]>
Hello,
I think I found the problem and why it happened ... I performed a diff between a fresh install of xe 4.5.2 and the xwiki created by my functional tests, and restricted to the following list of dependencies that were missing: xwiki-platform-legacy-annotation-4.5.2.jar xwiki-platform-legacy-model-4.5.2.jar xwiki-platform-legacy-observation-4.5.2.jar xwiki-platform-legacy-oldcore-4.5.2.jar
I think it's because I used customized pages for LiveTableResults and LiveTableResultsMacros, but based on an older version...
BR, Jeremie
2013/4/26 Jeremie BOUSQUET <[email protected]>
Thanks,
But I did not find any noticeable differences with my own setup ... I've got the same list of dependencies, with additional ones. Only difference would be that I depend on 4.5.3 artifacts, and use packager plugin 5.0-milestone-2 (for a fix I need). I tried also with packager 5.0-rc-1, but with same result.
BR, Jeremie
2013/4/25 Marius Dumitru Florea <[email protected]>
I would check the index tests (
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik... ) since they test indirectly the live table.
Hope this helps, Marius
On Thu, Apr 25, 2013 at 6:41 PM, Jeremie BOUSQUET <[email protected]> wrote:
Hello,
Pinging about last point below ... I really don't understand what's bad in my setup, so any help to unblock would be very nice :-)
BR, Jeremie
2013/3/29 Jeremie BOUSQUET <[email protected]>
Another one: I'm debugging a livetable display, that shows empty rows instead of expected values. The issue I have seems to drill down to the fact that "$request.limit" resolves to "10" (well, the limit value), while "$request.get('limit')" resolves to null. Also, "$request.reqNo" equals "1" as expected, but "$util.parseInt($request.reqNo)" is null. I'm pretty sure that works on a standard XE, so there must be some magical spice missing in my dependencies (or configuration ?), in relation with velocity and bindings ... Do you know what could be that magical spice ?
Thanks, Jeremie
2013/3/29 Jeremie BOUSQUET <[email protected]>
> Thanks Thomas, and sorry for that stack of questions :-/ > > Jeremie > > > 2013/3/29 Thomas Mortagne <[email protected]> > >> On Fri, Mar 29, 2013 at 4:56 PM, Thomas Mortagne >> <[email protected]> wrote: >> > On Fri, Mar 29, 2013 at 4:47 PM, Jeremie BOUSQUET >> > <[email protected]> wrote: >> >> Mmmm, what could explain that standard login for "Admin" user does >> not work >> >> in the xwiki created by the packager plugin ? ("invalid credentials"). >> >> It used to work, maybe when I had dependency on >> xwiki-enterprise-ui-all ... >> >> ? >> > >> > It's not really standard XWiki login, the Admin user come from >> > adminitsrtion-ui, if you have that xar then you have the user. >> >> administration-ui >> >> > >> >> >> >> Br, >> >> Jeremie >> >> >> >> >> >> 2013/3/29 Thomas Mortagne <[email protected]> >> >> >> >>> On Fri, Mar 29, 2013 at 3:05 PM, Jeremie BOUSQUET >> >>> <[email protected]> wrote: >> >>> > Ok found it in xwiki-rendering-macro-message. >> >>> > That's nice, looking into it, just realized that there existed a >> >>> > {{success}} macro ! Seems nice, is it intended that it's not >> described on >> >>> > extensions wiki as info/warning/error are ? >> >>> >> >>> Probably been forgotten by the dev who introduced it. >> >>> >> >>> > >> >>> > Thanks, >> >>> > Jeremie >> >>> > >> >>> > >> >>> > 2013/3/29 Jeremie BOUSQUET <[email protected]> >> >>> > >> >>> >> Thanks ! >> >>> >> I'm progressing, but it seems I have a hard time finding what to >> declare >> >>> >> to get the info/warning/error macros ... >> >>> >> >> >>> >> BR, >> >>> >> Jeremie >> >>> >> >> >>> >> >> >>> >> >> >>> >> 2013/3/29 Vincent Massol <[email protected]> >> >>> >> >> >>> >>> >> >>> >>> On Mar 29, 2013, at 12:21 PM, Vincent Massol < [email protected] >> > >> >>> wrote: >> >>> >>> >> >>> >>> > >> >>> >>> > On Mar 29, 2013, at 11:03 AM, Jeremie BOUSQUET < >> >>> >>> [email protected]> wrote: >> >>> >>> > >> >>> >>> >> Hello, >> >>> >>> >> >> >>> >>> >> Me again ... :-) >> >>> >>> >> With fixed version of packager plugin, things go better now. >> XWiki >> >>> is >> >>> >>> >> downloaded and launched, my test browses to the page as I >> expect. >> >>> >>> >> >> >>> >>> >> Problem is that when browsing to my page, I can see the >> following in >> >>> >>> the >> >>> >>> >> html content logged by the build: >> >>> >>> >> >> >>> >>> >> <div id="xwikicontent"> >> >>> >>> >> <div class="xwikirenderingerror" style="cursor: pointer;" >> >>> title="Read >> >>> >>> >> technical information related to this error">Unknown macro: >> >>> >>> velocity[...] >> >>> >>> >> >> >>> >>> >> In fact, it seems wiki is running, but can't find any macro >> ... I >> >>> >>> tried to >> >>> >>> >> add a dependency on xwiki-enterprise-ui-all xar, but with same >> >>> result. >> >>> >>> I'm >> >>> >>> >> not sure of what could be missing ? >> >>> >>> > >> >>> >>> > I think I've noticed a bug related to this. For ex in my >> contrib >> >>> >>> project I depend on >> >>> org.xwiki.platform:xwiki-platform-administration-ui. I >> >>> >>> was surprised when running my func test that the admin screen was >> >>> missing >> >>> >>> the velocity and include macros for example. The reason I think >> is >> >>> because >> >>> >>> in xwiki-platform-administration-ui the deps on velocity and >> include >> >>> macros >> >>> >>> are of scope "runtime". >> >>> >>> > >> >>> >>> > So IMO there's a bug in PackageMojo: it should draw transitive >> >>> >>> dependencies for the "runtime" scope. >> >>> >>> > >> >>> >>> > I'll look into this. >> >>> >>> >> >>> >>> Fixed in http://jira.xwiki.org/jira/browse/XWIKI-8983 >> >>> >>> >> >>> >>> Thanks >> >>> >>> -Vincent >> >>> >>> >> >>> >>> > However as Thomas said, you need to add the **direct** deps >> you need >> >>> at >> >>> >>> runtime. >> >>> >>> > >> >>> >>> > Thanks >> >>> >>> > -Vincent >> >>> >>> > >> >>> >>> > [snip] >> >>> >>> >> >>> >>> _______________________________________________ >> >>> >>> users mailing list >> >>> >>> [email protected] >> >>> >>> http://lists.xwiki.org/mailman/listinfo/users >> >>> >>> >> >>> >> >> >>> >> >> >>> > _______________________________________________ >> >>> > users mailing list >> >>> > [email protected] >> >>> > http://lists.xwiki.org/mailman/listinfo/users >> >>> >> >>> >> >>> >> >>> -- >> >>> Thomas Mortagne >> >>> _______________________________________________ >> >>> users mailing list >> >>> [email protected] >> >>> http://lists.xwiki.org/mailman/listinfo/users >> >>> >> >> _______________________________________________ >> >> users mailing list >> >> [email protected] >> >> http://lists.xwiki.org/mailman/listinfo/users >> > >> > >> > >> > -- >> > Thomas Mortagne >> >> >> >> -- >> Thomas Mortagne >> _______________________________________________ >> users mailing list >> [email protected] >> http://lists.xwiki.org/mailman/listinfo/users >> > >
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
Thanks Marius ! BR, Jeremie 2013/5/19 Marius Dumitru Florea <[email protected]>
On Sat, May 18, 2013 at 7:09 PM, Jeremie BOUSQUET <[email protected]> wrote:
Mmmm...
[WARNING] Rule 0: org.xwiki.tool.enforcer.XWikiBannedDependencies failed with message: Don't depend on a XWiki Legacy module! Found Banned Dependency: org.xwiki.platform:xwiki-platform-legacy-annotation:jar:4.5.2 Found Banned Dependency: org.xwiki.platform:xwiki-platform-legacy-observation:jar:4.5.2 Found Banned Dependency: org.xwiki.platform:xwiki-platform-legacy-model:jar:4.5.2 Use 'mvn dependency:tree' to locate the source of the banned dependencies.
Why's that ? Why are they banned considering they are released with xwiki ?
They are packaged in order to preserve backwards compatibility but the code in platform and the code that uses the platform POMs should not depend on the legacy modules. This ensures that the platform code doesn't use legacy code (which is kept, as I said, only for backwards compatibility).
Hope this helps, Marius
BR, Jeremie
2013/5/18 Jeremie BOUSQUET <[email protected]>
Hello,
I think I found the problem and why it happened ... I performed a diff between a fresh install of xe 4.5.2 and the xwiki created by my functional tests, and restricted to the following list of dependencies that were missing: xwiki-platform-legacy-annotation-4.5.2.jar xwiki-platform-legacy-model-4.5.2.jar xwiki-platform-legacy-observation-4.5.2.jar xwiki-platform-legacy-oldcore-4.5.2.jar
I think it's because I used customized pages for LiveTableResults and LiveTableResultsMacros, but based on an older version...
BR, Jeremie
2013/4/26 Jeremie BOUSQUET <[email protected]>
Thanks,
But I did not find any noticeable differences with my own setup ...
I've
got the same list of dependencies, with additional ones. Only difference would be that I depend on 4.5.3 artifacts, and use packager plugin 5.0-milestone-2 (for a fix I need). I tried also with packager 5.0-rc-1, but with same result.
BR, Jeremie
2013/4/25 Marius Dumitru Florea <[email protected]>
I would check the index tests (
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwik...
) since they test indirectly the live table.
Hope this helps, Marius
On Thu, Apr 25, 2013 at 6:41 PM, Jeremie BOUSQUET <[email protected]> wrote:
Hello,
Pinging about last point below ... I really don't understand what's bad in my setup, so any help to unblock would be very nice :-)
BR, Jeremie
2013/3/29 Jeremie BOUSQUET <[email protected]>
> Another one: I'm debugging a livetable display, that shows empty rows > instead of expected values. > The issue I have seems to drill down to the fact that "$request.limit" > resolves to "10" (well, the limit value), while "$request.get('limit')" > resolves to null. Also, "$request.reqNo" equals "1" as expected, but > "$util.parseInt($request.reqNo)" is null. > I'm pretty sure that works on a standard XE, so there must be some magical > spice missing in my dependencies (or configuration ?), in relation with > velocity and bindings ... > Do you know what could be that magical spice ? > > Thanks, > Jeremie > > > 2013/3/29 Jeremie BOUSQUET <[email protected]> > >> Thanks Thomas, and sorry for that stack of questions :-/ >> >> Jeremie >> >> >> 2013/3/29 Thomas Mortagne <[email protected]> >> >>> On Fri, Mar 29, 2013 at 4:56 PM, Thomas Mortagne >>> <[email protected]> wrote: >>> > On Fri, Mar 29, 2013 at 4:47 PM, Jeremie BOUSQUET >>> > <[email protected]> wrote: >>> >> Mmmm, what could explain that standard login for "Admin" user does >>> not work >>> >> in the xwiki created by the packager plugin ? ("invalid credentials"). >>> >> It used to work, maybe when I had dependency on >>> xwiki-enterprise-ui-all ... >>> >> ? >>> > >>> > It's not really standard XWiki login, the Admin user come from >>> > adminitsrtion-ui, if you have that xar then you have the user. >>> >>> administration-ui >>> >>> > >>> >> >>> >> Br, >>> >> Jeremie >>> >> >>> >> >>> >> 2013/3/29 Thomas Mortagne <[email protected]> >>> >> >>> >>> On Fri, Mar 29, 2013 at 3:05 PM, Jeremie BOUSQUET >>> >>> <[email protected]> wrote: >>> >>> > Ok found it in xwiki-rendering-macro-message. >>> >>> > That's nice, looking into it, just realized that there existed a >>> >>> > {{success}} macro ! Seems nice, is it intended that it's not >>> described on >>> >>> > extensions wiki as info/warning/error are ? >>> >>> >>> >>> Probably been forgotten by the dev who introduced it. >>> >>> >>> >>> > >>> >>> > Thanks, >>> >>> > Jeremie >>> >>> > >>> >>> > >>> >>> > 2013/3/29 Jeremie BOUSQUET <[email protected]> >>> >>> > >>> >>> >> Thanks ! >>> >>> >> I'm progressing, but it seems I have a hard time finding what to >>> declare >>> >>> >> to get the info/warning/error macros ... >>> >>> >> >>> >>> >> BR, >>> >>> >> Jeremie >>> >>> >> >>> >>> >> >>> >>> >> >>> >>> >> 2013/3/29 Vincent Massol <[email protected]> >>> >>> >> >>> >>> >>> >>> >>> >>> On Mar 29, 2013, at 12:21 PM, Vincent Massol < [email protected] >>> > >>> >>> wrote: >>> >>> >>> >>> >>> >>> > >>> >>> >>> > On Mar 29, 2013, at 11:03 AM, Jeremie BOUSQUET < >>> >>> >>> [email protected]> wrote: >>> >>> >>> > >>> >>> >>> >> Hello, >>> >>> >>> >> >>> >>> >>> >> Me again ... :-) >>> >>> >>> >> With fixed version of packager plugin, things go better now. >>> XWiki >>> >>> is >>> >>> >>> >> downloaded and launched, my test browses to the page as I >>> expect. >>> >>> >>> >> >>> >>> >>> >> Problem is that when browsing to my page, I can see the >>> following in >>> >>> >>> the >>> >>> >>> >> html content logged by the build: >>> >>> >>> >> >>> >>> >>> >> <div id="xwikicontent"> >>> >>> >>> >> <div class="xwikirenderingerror" style="cursor: pointer;" >>> >>> title="Read >>> >>> >>> >> technical information related to this error">Unknown macro: >>> >>> >>> velocity[...] >>> >>> >>> >> >>> >>> >>> >> In fact, it seems wiki is running, but can't find any macro >>> ... I >>> >>> >>> tried to >>> >>> >>> >> add a dependency on xwiki-enterprise-ui-all xar, but with same >>> >>> result. >>> >>> >>> I'm >>> >>> >>> >> not sure of what could be missing ? >>> >>> >>> > >>> >>> >>> > I think I've noticed a bug related to this. For ex in my >>> contrib >>> >>> >>> project I depend on >>> >>> org.xwiki.platform:xwiki-platform-administration-ui. I >>> >>> >>> was surprised when running my func test that the admin screen was >>> >>> missing >>> >>> >>> the velocity and include macros for example. The reason I think >>> is >>> >>> because >>> >>> >>> in xwiki-platform-administration-ui the deps on velocity and >>> include >>> >>> macros >>> >>> >>> are of scope "runtime". >>> >>> >>> > >>> >>> >>> > So IMO there's a bug in PackageMojo: it should draw transitive >>> >>> >>> dependencies for the "runtime" scope. >>> >>> >>> > >>> >>> >>> > I'll look into this. >>> >>> >>> >>> >>> >>> Fixed in http://jira.xwiki.org/jira/browse/XWIKI-8983 >>> >>> >>> >>> >>> >>> Thanks >>> >>> >>> -Vincent >>> >>> >>> >>> >>> >>> > However as Thomas said, you need to add the **direct** deps >>> you need >>> >>> at >>> >>> >>> runtime. >>> >>> >>> > >>> >>> >>> > Thanks >>> >>> >>> > -Vincent >>> >>> >>> > >>> >>> >>> > [snip] >>> >>> >>> >>> >>> >>> _______________________________________________ >>> >>> >>> users mailing list >>> >>> >>> [email protected] >>> >>> >>> http://lists.xwiki.org/mailman/listinfo/users >>> >>> >>> >>> >>> >> >>> >>> >> >>> >>> > _______________________________________________ >>> >>> > users mailing list >>> >>> > [email protected] >>> >>> > http://lists.xwiki.org/mailman/listinfo/users >>> >>> >>> >>> >>> >>> >>> >>> -- >>> >>> Thomas Mortagne >>> >>> _______________________________________________ >>> >>> users mailing list >>> >>> [email protected] >>> >>> http://lists.xwiki.org/mailman/listinfo/users >>> >>> >>> >> _______________________________________________ >>> >> users mailing list >>> >> [email protected] >>> >> http://lists.xwiki.org/mailman/listinfo/users >>> > >>> > >>> > >>> > -- >>> > Thomas Mortagne >>> >>> >>> >>> -- >>> Thomas Mortagne >>> _______________________________________________ >>> users mailing list >>> [email protected] >>> http://lists.xwiki.org/mailman/listinfo/users >>> >> >> > _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
participants (4)
-
Jeremie BOUSQUET -
Marius Dumitru Florea -
Thomas Mortagne -
Vincent Massol