mvn clean install of xwiki-commons, it failing with the following message:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.16:test (default-test) on project xwiki-commons-crypto-password: There are test failures.
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.16:test (default-test) on project xwiki-commons-crypto-password: There are test failures.
Please refer to /PATH/xwiki-commons/xwiki-commons-core/xwiki-commons-crypto/xwiki-commons-crypto-password/target/surefire-reports for the individual test results.
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoFailureException: There are test failures.
Please refer to /PATH/xwiki-commons/xwiki-commons-core/xwiki-commons-crypto/xwiki-commons-crypto-password/target/surefire-reports for the individual test results.
at org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:82)
at org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:190)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:852)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:720)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
Similarly, building of xwiki-rendering is failing with message: "org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.16:test (default-test) on project xwiki-rendering-api: There are test failures." and building of xwiki-platform is failing with error message: "org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.16:test (default-test) on project xwiki-platform-filter-stream-xar: There are test failures.".
I could successfully build xwiki-enterprise.
I am using Apache Maven 3.0.5 and Java version: 1.8.0_3. 1. I am building on linux.
Using Java version 1.7 (instead of java 1.8), for xwiki-commons, 19 more reactors got built successfully and failed at reactor Extension - Repository - Maven with message: "org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.16:test (default-test) on project xwiki-commons-extension-repository-maven: There are test failures."
Same for xwiki-rendering. Previously with java 8 it was failing at rendering api reactor. With java 7 it could successfully build 17 more reactors and failed at reactor Syntax - DocBook with message: "org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.16:test (default-test) on project xwiki-rendering-syntax-docbook: There are test failures.".
For xwiki-platform it is still failing with the same error at same reactor.
I found a related JIRA: http://jira.xwiki.org/browse/XWIKI-10718
> On 20 Mar 2015 at 10:16:06, vincent(a)massol.net (vincent@massol.net(mailto:vincent@massol.net)) wrote:
>
> > Hi OH,
Sorry, meant OJ :)
-Vincent
> >
> > Following our discussion on IRC of this morning, I have refactored the directory structure and the maven poms to follow our best practices, see the commits at:
> > https://github.com/xwiki-contrib/macro-hpqc/commits/master
> >
> > I’ve also released it and it’s available in our maven repo at:
> > http://maven.xwiki.org/releases/org/xwiki/contrib/hpqc/
> >
> > I’ll let you import it on extensions.xwiki.org and document it!
> >
> > Hope it helps,
> > -Vincent
> >
> > On 20 Mar 2015 at 09:28:34, vincent(a)massol.net (vincent@massol.net(mailto:vincent@massol.net)) wrote:
> >
> > > Hi OJ,
> > >
> > > On 20 Mar 2015 at 09:19:15, O.J. Sousa Rodrigues (osoriojaques@gmail.com(mailto:osoriojaques@gmail.com)) wrote:
> > >
> > > > Hi there!
> > > >
> > > >
> > > > As described[1] i here by ask you kindly to please create a new
> > > > repositoy under xwiki-contrib.
> > > > I want to soon release [1] a new extension / macro that will fetch
> > > > information from HPQC and list them in xwiki.
> > >
> > > Cool!
> > >
> > > Repo transferred at https://github.com/xwiki-contrib/macro-hpqc
> > >
> > > Thanks
> > > -Vincent
> > >
> > > > After the release i will create the documentation at extension.xwiki.org.
> > > >
> > > > XWiki username: vfzevaze
> > > > Github username: 4F2E4A2E
> > > >
> > > > Best regards,
> > > > OJ, Sousa Rodrigues
> > > >
> > > > [1]: http://contrib.xwiki.org/xwiki/bin/view/Main/WebHome
> > > > [2]: http://nexus.xwiki.org/
> > > > [3]: https://github.com/4F2E4A2E/macro-hpqc
> > >
> >
> > _______________________________________________
> > devs mailing list
> > devs(a)xwiki.org
> > http://lists.xwiki.org/mailman/listinfo/devs
>
Hi devs,
After talking with Edy and Marius I’m proposing that we postpone the 7.0RC1 release to Monday (i.e. we’ll be 1 week late compared to our schedule - we were supposed to release on 16th…).
The reason I’m proposing to postpone is because:
* Edy can have http://jira.xwiki.org/browse/XWIKI-11754 finished today
* Marius can have http://jira.xwiki.org/browse/XWIKI-11506 finished before Monday
* GuillaumeD still needs to fix http://jira.xwiki.org/browse/XWIKI-11892 on Oracle
However we need to fully ready to release on Monday morning to not postpone more.
Thus we need to be sure that the build is stable and passing before Friday evening!
WDYT?
Thanks
-Vincent
Hi devs,
>From an API initiated during the last XWiki seminar from the fun and
ambitious idea that it should be possible to retrieve from a running XWiki
instance all the useful entry points for providing a good and extensible
XWiki Scripting API reference documentation, the Scripting Documentation
application is now finally released in version 1.0.
See for some screenshot and more detailed information:
http://extensions.xwiki.org/xwiki/bin/view/Extension/Scripting+Documentatio…
This application is compatible with XWiki 6.2.5 and later 6.2.x, with full
support in XWiki 6.4.1 or later 6.4.x, and support only the Flamingo skin.
It is based on a AngularJS development.
To allows you to discover it, and in the aim to provide online the
documentation of our Scripting API for the latest stable version, I have
also installed it on:
http://platform.xwiki.org/xwiki/bin/view/ScriptingDocumentation
I hope you will found this a good idea, and if nobody complains, I will
link that application from the actual API documentation.
Please let me know your remarks about the application. It is a 1.0 version
and there is obviously room for many improvements. Your comments is
therefore very welcomed.
Thanks,
--
Denis Gervalle
SOFTEC sa - CEO
Hi devs,
I know this comes slightly late in the 7.0 dev timeframe but now is better than later…
So the vote is about moving to Servlet 3.0 right now for 7.0RC1. The issue has been opened a long time ago at http://jira.xwiki.org/browse/XWIKI-9358 and now is a good time.
For full disclosure, my sudden urge comes from the need to use at least Servlet 2.5 to properly and cleanly fix http://jira.xwiki.org/browse/XWIKI-11843, so this would kill 2 birds with one stone.
If someone is -1, then I’d still like to move to Servlet 2.5 at least.
Here’s my +1
Thanks
-Vincent
Hello,
we are a groupe of four students and we are actually working on a XWiki
extension.
This extension will be a modern photo gallery which allows users to
organise and publish photos.
For now, our planned features are the followings:
-Thumbnails display
-Responsive display
-Autoplay (diaporama)
-Nice transitions
-Intuitive configuration page included drag and drop function to upload
images
Do you have another ideas or suggestions to improve our extension ?
Thank you in advance.
Best regards,
CRAY team
Hi devs,
As part of http://jira.xwiki.org/browse/XWIKI-11905, Edy has started using the Java @Priority annotation.
This seems very good and I personally didn’t know about this annotation before (maybe it’s been introduced not that long ago?). So for me it raises the question of: do we want to use this annotation more and how does it compare with what we’ve done so far.
I can think of a few places that could have used it:
* Macros.get/setPriority(). It should be possible to add support for @Priority and modify MacroTransformation to use that annotation.
* Transformations. We have a jira issue opened for adding support for Priority in Transformation’s executions (in TransformationManager).
* @DisposePriority (used by ECM).
* TranslationBundle.get/setPriority()
* … and probably some other places…
However, I think there’s a namespacing problem. For example imagine that we code a Macro and set @Priority on that Macro component. The ECM could interpret it as a dispose priority while the MacroTransformation could interpret it as an execution priority…
Globally I think that use an annotation for expressing priority is great and much better than what we’ve done in the past with get/setPriority() methods. It’s better because priority is not a business concept and we’re polluting the business interface with it.
Now, in order to fix the namespacing issue, I think that the best solution is that each module requiring some priority should introduce its own annotation and should NOT depend on the @Priority one from the JDK (i.e. we ban the usage of it).
WDYT?
Thanks
-Vincent
W