I checked out the various projects for xwiki (-commons, -rendering,
-platform, and -enterprise) from github yesterday, and have successfully
built all but enterprise project, which fails on the build step for the
windows installer. The error printed alludes to needing a valid JRE, but
according to my java version information, my jre should be fine.
I'm using ubuntu 12.04 LTS, and have tried with and without the unix
profile flag (-Punix) as specified on
http://dev.xwiki.org/xwiki/bin/view/Community/Building (either way gives
the same behavior).
Any thoughts on how to fix this?
- Peter
$ java -version
java version "1.7.0_76"
Java(TM) SE Runtime Environment (build 1.7.0_76-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.76-b04, mixed mode)
$ mvn -v
Apache Maven 3.0.4
Maven home: /usr/share/maven
Java version: 1.7.0_76, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-7-oracle/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.13.0-46-generic", arch: "amd64", family:
"unix"
$ mvn clean install -DskipTests=true
....
[INFO] --- maven-dependency-plugin:2.10:unpack (unpack) @
xwiki-enterprise-installer-windows ---
[INFO] Configured Artifact: launch4j:launch4j:linux:3.0.2:zip
[INFO] Unpacking
/home/likewise-open/ANT/nixpeter/.m2/repository/launch4j/launch4j/3.0.2/launch4j-3.0.2-linux.zip
to
/home/likewise-open/ANT/nixpeter/Projects/xwiki/xwiki-enterprise/xwiki-enterprise-installers/xwiki-enterprise-installer-windows/target/dependency
with includes "" and excludes ""
[INFO]
[INFO] --- maven-antrun-plugin:1.7:run (run-launch4j) @
xwiki-enterprise-installer-windows ---
[WARNING] Parameter tasks is deprecated, use target instead
[INFO] Executing tasks
main:
Compiling resources
Generated resource file...
LANGUAGE 0, 1
2 RCDATA BEGIN "1.7.0\0" END
18 RCDATA BEGIN "1\0" END
1 ICON DISCARDABLE
"~/Projects/xwiki/xwiki-enterprise/xwiki-enterprise-installers/xwiki-enterprise-installer-windows/target/classes/xe.ico"
10 RCDATA BEGIN "XWiki Windows Installer\0" END
21 RCDATA BEGIN "http://java.com/download\0" END
20 RCDATA BEGIN "32\0" END
9 RCDATA BEGIN "true\0" END
101 RCDATA BEGIN "An error occurred while starting the application.\0" END
102 RCDATA BEGIN "This application was configured to use a bundled Java
Runtime Environment but the runtime is missing or corrupted.\0" END
103 RCDATA BEGIN "This application requires a Java Runtime Environment\0"
END
104 RCDATA BEGIN "The registry refers to a nonexistent Java Runtime
Environment installation or the runtime is corrupted.\0" END
17 RCDATA BEGIN "true\0" END
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] XWiki Enterprise - Parent POM ..................... SUCCESS [2.484s]
[INFO] XWiki Enterprise - Distribution Archetype ......... SUCCESS [0.911s]
[INFO] XWiki Enterprise - UI ............................. SUCCESS [0.081s]
[INFO] XWiki Enterprise - UI - Admin User ................ SUCCESS [1.013s]
[INFO] XWiki Enterprise - UI - Main wiki preferences ..... SUCCESS [0.193s]
[INFO] XWiki Enterprise - UI - Common .................... SUCCESS
[3:07.873s]
[INFO] XWiki Enterprise - UI - Wiki ...................... SUCCESS [14.006s]
[INFO] XWiki Enterprise - Distribution - Parent POM ...... SUCCESS [0.063s]
[INFO] XWiki Enterprise - UI - Wiki All .................. SUCCESS [8.231s]
[INFO] XWiki Enterprise - UI - Main wiki ................. SUCCESS [19.991s]
[INFO] XWiki Enterprise - Data - Parent POM .............. SUCCESS [2.157s]
[INFO] XWiki Enterprise - Data - HSQLDB .................. SUCCESS
[2:44.054s]
[INFO] XWiki Enterprise - UI - Main Wiki All ............. SUCCESS [8.391s]
[INFO] XWiki Enterprise - Web ............................ SUCCESS
[1:55.462s]
[INFO] XWiki Enterprise - Distribution - Jetty ........... SUCCESS [2.178s]
[INFO] XWiki Enterprise - Distribution - Jetty - HSQLDB .. SUCCESS [16.062s]
[INFO] XWiki Enterprise - Installers - Parent POM ........ SUCCESS [0.028s]
[INFO] XWiki Enterprise - Installers - Generic ........... SUCCESS [31.620s]
[INFO] XWiki Enterprise - Installers - Windows ........... FAILURE [0.713s]
[INFO] XWiki Enterprise - Installer - Debian ............. SKIPPED
[INFO] XWiki Enterprise - Installer - Debian - Common .... SKIPPED
[INFO] XWiki Enterprise - Installer - Debian - MySQL - Common SKIPPED
[INFO] XWiki Enterprise - Installer - Debian - Postgres SQL - Common
SKIPPED
[INFO] XWiki Enterprise - Installer - Debian - Tomcat .... SKIPPED
[INFO] XWiki Enterprise - Installer - Debian - Tomcat - Common SKIPPED
[INFO] XWiki Enterprise - Installer - Debian - Tomcat 7 - MySQL SKIPPED
[INFO] XWiki Enterprise - Installer - Debian - Tomcat 7 - Postgres SQL
SKIPPED
[INFO] XWiki Enterprise - Installer - Debian - Tomcat 8 - MySQL SKIPPED
[INFO] XWiki Enterprise - Installer - Debian - Tomcat 8 - Postgres SQL
SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 9:40.418s
[INFO] Finished at: Wed Mar 25 15:10:01 PDT 2015
[INFO] Final Memory: 123M/983M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-antrun-plugin:1.7:run (run-launch4j) on
project xwiki-enterprise-installer-windows: An Ant BuildException has
occured: net.sf.launch4j.BuilderException: net.sf.launch4j.ExecException:
java.io.IOException: Cannot run program
"/home/likewise-open/ANT/nixpeter/Projects/xwiki/xwiki-enterprise/xwiki-enterprise-installers/xwiki-enterprise-installer-windows/target/dependency/bin/windres":
error=2, No such file or directory
[ERROR] around Ant part ...<launch4j
configFile="/home/likewise-open/ANT/nixpeter/Projects/xwiki/xwiki-enterprise/xwiki-enterprise-installers/xwiki-enterprise-installer-windows/target/classes/launch4j.xml"/>...
@ 6:183 in
/home/likewise-open/ANT/nixpeter/Projects/xwiki/xwiki-enterprise/xwiki-enterprise-installers/xwiki-enterprise-installer-windows/target/antrun/build-main.xml
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR] mvn <goals> -rf :xwiki-enterprise-installer-windows
Hi devs,
I’ve implemented http://jira.xwiki.org/browse/XWIKI-11961
However it’s causing several tests to fail, proving that it’s changing the script behaviors. For example if you have:
{{groovy}}
var = "toto"
{{/groovy}}
{{velocity}}
$var
{{/velocity}}
Then you’ll see “toto” printed twice. Once for the groovy macro.
The right way to not output content is to use output=false as in:
{{groovy output="false"}}
var = "toto"
{{/groovy}}
{{velocity}}
$var
{{/velocity}}
So we need to decide if we’re ok to go with this even though it changes the behavior.
I don’t completely master the full gamut of consequences this will have but I have the feeling that from a logical point of view, it’s the best thing to have.
WDYT?
Thanks
-Vincent
Hi devs,
In xwiki-enteprise we have XWiki.RequiredRightClass. We’ve started discussing it in the past in the “Split XE pages” mail thread and I’d like to move forward.
So we need to decide what to do about it. Several options:
* We discussed moving it to xwiki-platform-administration but it shouldn’t go there IMO since we’re trying to make this module almost empty (just providing the extension points mechanism) and have admin features dispatched in the modules providing them. Also it would mean forcing unnecessary dependencies on xwiki-platform-administration from several modules (6-7 right now).
* It could go in a new xwiki-platform-security-ui module.
* It could be moved to Java but we don’t have a clear policy nor decision if we want to favor xclasses written in java or opposite, decide that we don’t want that and move away from XClasses in Java. So we’d need to decide this first.
* We could also simply remove it! Rationale:
** I don’t think we’re using that information much and its need is supposed to go away once signed scripts is there
** There’s no way to force pages requiring PR to add such an XObject and thus it’s not done consistently
** We don’t even have a page listing all pages requiring PR and even if we had one I’m not exactly what it would bring. I guess the idea was to make it simpler to install/upgrade XWiki but we’ve fixed this already in the Wiki Creation Wizard for example so the need is less now.
So overall I’m more in favor of dropping this experiment which IMO wasn’t very successful.
WDYT?
Thanks
-Vincent
Hi,
I want to write automated tests for some contrib applications, but I need
you help on some questions.
== Prb 1. Folder Structure + Changing IDs ==
Currently the majority of applications don't have modules.
Also some applications have IDs that don't correspond with the contrib
standard: sometimes wrong groupId like 'org.xwiki.contrib.forum', sometimes
random artifactId.
When wanting to change the groupId for 'org.xwiki.contrib.forum' I was told
that we should change it only if we have a very good reason, otherwise
changing the ID will resolve in upgrading problems within the Extension
Manager. Unfortunately I don't remember exactly the problem with the
changing of the ID, I just know I don't need to do it :) (//sorry Thomas)
Example: https://github.com/xwiki-contrib/application-forum
Theoretically, wanting to add tests I would need to create two modules:
- application-forum-test
- application-forum-ui, and move the current sources here.
Unfortunately this means a change in the ID.
Are 'adding tests' a good reason to change the ID?
Should I not change the ID, and just add a test module?
- application-forum-test
- src/main/resources
== Prb 2. Naming standards ==
We have some conventions on contrib.xwiki.org about name of the project.
We should add maybe some more examples on groupId and artifactId.
Also when looking at the test modules names, some applications have:
- {{full-repository-name}}-tests
- {{full-repository-name}}-test
- {{partial-repository-name}}-test
- {{random-repository-name}}-test
- test
Maybe we should agree also on this and document it.
I guess the correct name would be:
- {{full-repository-name}}-test
-- {{full-repository-name}}-test-pageobjects
-- {{full-repository-name}}-test-tests
- {{full-repository-name}}-ui
Also if we are 'discovering' some applications that don't correspond to the
standard, do we change them or do we let them be? Since changing means a
change in the ID :P
Since in theory we should have automated tests for all our applications,
should we add a convention to always create a
- {{full-repository-name}}-ui ?
Additional question: Also when we will transfer from platform to contrib,
are we going to rename the modules?
Thanks,
Caty
I have a page "Test6" in space "Algemeen". On that page I have uploaded
"three.min.js", a javascript file.
I want to use that script, but how?
{{velocity}}
$xwiki.jsfx.use('Algemeen/Test6/three.min.js')
{{/velocity}}
If I use this and then look at the DOM, then this is what I see:
It refers to the colibri skin...but that's not where my "three.min.js" is
located.
Any help is appreciated!
--
View this message in context: http://xwiki.475771.n2.nabble.com/Refer-to-attached-javascript-file-with-xw…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
The XWiki development team is proud to announce the availability of
XWiki 7.0 Release Candidate 1.
The version is mostly about stabilization before 7.0 final. It
contains diff UI improvements, Extension Repository improvements, a
new component based watchlist module, a new application to edit wiki
skins. XWiki also moved to Servlet 3.0.1 which means various old
application servers versions are not supported anymore.
You can download it here: http://www.xwiki.org/xwiki/bin/view/Main/Download
Make sure to review the release notes:
http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki70RC1
Thanks
-The XWiki dev team
I'm restarting my request, better following the procedure. Sorry for being
imprecise before.
Some contexte for my request: I'm an intern at XWiki SAS doing a small
application for my internshop which finishes this week and I need a place
to deliver my project.
I would like a contrib project for the following application:
Application Name: "Acquisitions Application"
Application Description: "Inventory and Request Management Application.
This application allows to do an inventory of any material (computer,
phones, accessories) done by a company. It allows includes a request
management application to help manage new requests."
For this application I would need:
- A github repository (my username is EmilySterenfeld) names
"application-acquisitionmanagement"
- A jira project XAACQUISTIONS (XWiki Application Acquistion Management)
One I have this, I will commit the code I have worked on a release the
application on extensions.xwiki.org.
Thank you
Emily
--
<http://www.xwiki.com/>*Emily STERENFELD*
*Intern Client Team*
emily.sterenfeld(a)xwiki.com
mobile: 06.09.41.15.38
skype: emily_lucie
Hi devs,
Right now we have a XWiki.RequestsStatus page in xwiki-enterprise. This page shows information about the incoming requests if the monitor plugin is active.
I’m proposing to remove it on the following basis:
* It should be part of the Admin Tools Application (it probably is there already)
* We should move the Admin Tools Application from xwiki-contrib to xwiki-platform and bundle it by default. Of course this should be done after having improved it:
- following best practices
- all pages converted to XWiki 2.1 syntax (several if not all are using XWiki Syntax 1.0!)
- integrate it into the Admin UI (and not from the Applications Bar since I believe this is really admin stuff and best accessed from there). Specifically create a “Monitoring”/“Admin Tools” menu section in the Admin with several subsections for the different features.
* Future: Deprecate the monitor plugin and replace it with a more recent framework such as Codehale Metrics
To summarize, this proposal is about:
* Removing that page and ensuring it’s in the Admin Tools app
* Agreeing that once Admin Tools is nice enough we’ll move it xwiki-platform and bundle it in the base flavor
WDYT?
Thanks
-Vincent