XWiki Gentoo Linux ebuild
Hello. This email is mainly for Gentoo Linux users/admins/developers. I write a draft version of XWiki ebuild (package analog) for Gentoo Linux distribution: http://jira.xwiki.org/jira/browse/XWIKI-467 ebuild in attachments install instructions in comments For now ebuild can (USE flags): war - simple build war in /usr/share/xwiki-svn-1.0/lib/xwiki.war exowar - build exo portlet integration war in /usr/share/xwiki-svn-1.0/lib/xwiki-exo.war standalone - build standalone distribution (embedded hsqldb and jetty) and install it in /usr/share/xwiki-svn-1.0/standalone run by /etc/init.d/xwiki start tomcat - deploy to tomcat6. simply symlink war file :) write what you want else? ebuild will checkout svn://svn.forge.objectweb.org/svnroot/xwiki/xwiki/branches/XWIKI_1_0 sources for building and uses ant for building. ebuild uses svn because xwiki haven't source distribution yet. But I think for test this ebuild svn is most suitable. Later we will needed source distribution for xwiki releases. ebuild allow to Gentoo user to install xwiki very easily without any knowledge in xwiki. I tested this ebuild on ~amd64 arch, sun-jdk-1.5 & 1.6 (with some patches allowing xwiki to compile at 1.6). I would like to hear some feedbacks,notes,misprints and bugs before we can propose this ebuild to Gentoo java-overlay or java-experimental overlay. -- Artem Melentyev, UralSU, CS401
Hi Artem, I haven't tried the ebuild yet, will do it in a day or two. Some other USE flags I'd like to see: src - for checking out the sources, too. You could check the status on "ant src.dist" doc - runs "ant doc" and places the generated documentation in /usr/share/docs/xwiki/ test - runs the tests, too I don't like the fact that it uses the 1.0 branch. It is not something stable, I don't recall any ebuilds using something dynamic as the source. We could have some other USE flags for this. An ebuild should always have a stable tagged source, meaning that an ebuild will have the used xwiki version. So the first ebuild could be called xwiki-1.0.RC4 (or we can wait for 1.0), which checkouts sources in xwiki/tags/XWIKI_1_0_RC4. We can override this with USE=trunk, which will checkout the sources from trunk. Another option which will be needed shortly is USE=mvn, which compiles everything with maven. What exactly does "/etc/init.d/xwiki start/stop" do? What is the default build target? Or the user has to choose at least one of war, tomcat...? Sergiu. On 5/6/07, Artem Melentyev <[email protected]> wrote:
Hello.
This email is mainly for Gentoo Linux users/admins/developers.
I write a draft version of XWiki ebuild (package analog) for Gentoo Linux distribution:
http://jira.xwiki.org/jira/browse/XWIKI-467 ebuild in attachments install instructions in comments
For now ebuild can (USE flags): war - simple build war in /usr/share/xwiki-svn-1.0/lib/xwiki.war exowar - build exo portlet integration war in /usr/share/xwiki-svn-1.0/lib/xwiki-exo.war standalone - build standalone distribution (embedded hsqldb and jetty) and install it in /usr/share/xwiki-svn-1.0/standalone run by /etc/init.d/xwiki start tomcat - deploy to tomcat6. simply symlink war file :) write what you want else?
ebuild will checkout svn://svn.forge.objectweb.org/svnroot/xwiki/xwiki/branches/XWIKI_1_0 sources for building and uses ant for building. ebuild uses svn because xwiki haven't source distribution yet. But I think for test this ebuild svn is most suitable. Later we will needed source distribution for xwiki releases.
ebuild allow to Gentoo user to install xwiki very easily without any knowledge in xwiki. I tested this ebuild on ~amd64 arch, sun-jdk-1.5 & 1.6 (with some patches allowing xwiki to compile at 1.6).
I would like to hear some feedbacks,notes,misprints and bugs before we can propose this ebuild to Gentoo java-overlay or java-experimental overlay.
-- Artem Melentyev, UralSU, CS401
-- You receive this message as a subscriber of the [email protected] mailing list. To unsubscribe: mailto:[email protected] For general help: mailto:[email protected]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Hi Sergiu. Sergiu Dumitriu wrote:
Some other USE flags I'd like to see: src - for checking out the sources, too. You could check the status on "ant src.dist" There are standard use flag "source". xwiki ebuild use core/src/main/java sources. Current ant src.dist target make only doc, lib (no need in 'source' flag IMHO), and some resources but no sources. I think it is wrong behavior.
doc - runs "ant doc" and places the generated documentation in /usr/share/docs/xwiki/ ok
test - runs the tests, too ok
I don't like the fact that it uses the 1.0 branch. It is not something stable, I don't recall any ebuilds using something dynamic as the source. We could have some other USE flags for this. An ebuild should always have a stable tagged source, meaning that an ebuild will have the used xwiki version. So the first ebuild could be called xwiki-1.0.RC4 (or we can wait for 1.0), which checkouts sources in xwiki/tags/XWIKI_1_0_RC4. ok. In next version i will use stable tag.
We can override this with USE=trunk, which will checkout the sources from trunk. I think it is better to use a separate ebuild for trunk version (xwiki-svn-9999.ebuild for example). Some ebuilds do so (sys-apps/initng-9999).
Another option which will be needed shortly is USE=mvn, which compiles everything with maven. It is much harder. maven2 building in gentoo has some problems. It is using only in java-experimental overlay and very experimental :). There are even (failed:() GSoC07 project in support maven2 in ebuilds :) Some ebuilds using build.xml generated by maven. http://overlays.gentoo.org/proj/java/wiki/Maven_Notes I think in ebuild for 1.0.* maven2 support is minor. If I find some time, I will look at maven2 status in java-experimental overlay.
What exactly does "/etc/init.d/xwiki start/stop" do? Init script will start/stop jetty in standalone xwiki. /usr/share/xwiki-svn-1.0/standalone/ For now it is use following command: su - xwiki -c "${JAVA} ${JETTY_OPTS} -jar start.jar" >> \ /var/log/xwiki.log 2>&1 & Maybe it is not best variant. jetty-5.1.3-r1.ebuild in java-overlay uses /extra/unix/bin/jetty.sh script which I find not in xwiki standalone.
What is the default build target? Or the user has to choose at least one of war, tomcat...? Default ant build target = release. But if user do not select any use flags he gets only /usr/share/xwiki*/lib/xwiki.jar :) We need to consider default behavior for this ebuild.
Thanks for feedback. -- Artem Melentyev, UralSU, CS401
On 5/8/07, Artem Melentyev <[email protected]> wrote:
Hi Sergiu.
Sergiu Dumitriu wrote:
Some other USE flags I'd like to see: src - for checking out the sources, too. You could check the status on "ant src.dist" There are standard use flag "source". xwiki ebuild use core/src/main/java sources. Current ant src.dist target make only doc, lib (no need in 'source' flag IMHO), and some resources but no sources. I think it is wrong behavior.
That's what it does? Hm, wrong behavior, indeed. And yes, the standard USE flag is "source", my bad.
We can override this with USE=trunk, which will checkout the sources from trunk. I think it is better to use a separate ebuild for trunk version (xwiki-svn-9999.ebuild for example). Some ebuilds do so (sys-apps/initng-9999).
OK.
Another option which will be needed shortly is USE=mvn, which compiles everything with maven. It is much harder. maven2 building in gentoo has some problems. It is using only in java-experimental overlay and very experimental :). There are even (failed:() GSoC07 project in support maven2 in ebuilds :) Some ebuilds using build.xml generated by maven. http://overlays.gentoo.org/proj/java/wiki/Maven_Notes I think in ebuild for 1.0.* maven2 support is minor. If I find some time, I will look at maven2 status in java-experimental overlay.
For the moment, the ant build is fine. Let's hope that until it will become deprecated (around 2.0?) Gentoo will have better support for maven builds. One more reason to always keep the ant build up2date.
What exactly does "/etc/init.d/xwiki start/stop" do? Init script will start/stop jetty in standalone xwiki. /usr/share/xwiki-svn-1.0/standalone/ For now it is use following command: su - xwiki -c "${JAVA} ${JETTY_OPTS} -jar start.jar" >> \ /var/log/xwiki.log 2>&1 & Maybe it is not best variant. jetty-5.1.3-r1.ebuild in java-overlay uses /extra/unix/bin/jetty.sh script which I find not in xwiki standalone.
So, we use our own jetty, and not an emerged one, right? What if the user used the tomcat flag? Shouldn't /etc/init.d/xwiki check the status of mysql and tomcat instead? Speaking of mysql, we could also provide some flags for choosing the database.
What is the default build target? Or the user has to choose at least one of war, tomcat...? Default ant build target = release. But if user do not select any use flags he gets only /usr/share/xwiki*/lib/xwiki.jar :) We need to consider default behavior for this ebuild.
xwiki.jar is OK for me as the default behavior. Sergiu -- http://purl.org/net/sergiu
Hi, Sergiu. Sergiu Dumitriu wrote:
On 5/8/07, Artem Melentyev <[email protected]> wrote:
Hi Sergiu.
Sergiu Dumitriu wrote:
Some other USE flags I'd like to see: src - for checking out the sources, too. You could check the status on "ant src.dist" There are standard use flag "source". xwiki ebuild use core/src/main/java sources. Current ant src.dist target make only doc, lib (no need in 'source' flag IMHO), and some resources but no sources. I think it is wrong behavior.
That's what it does? Hm, wrong behavior, indeed. And yes, the standard USE flag is "source", my bad. I think source use flag should make only source zip, without libs and docs, so I think 'use source && java-pkg_dosrc core/src/main/java' is sufficient. This source zip may be using in IDE for example. WDYT?
Another option which will be needed shortly is USE=mvn, which compiles everything with maven. It is much harder. maven2 building in gentoo has some problems. It is using only in java-experimental overlay and very experimental :). There are even (failed:() GSoC07 project in support maven2 in ebuilds :) Some ebuilds using build.xml generated by maven. http://overlays.gentoo.org/proj/java/wiki/Maven_Notes I think in ebuild for 1.0.* maven2 support is minor. If I find some time, I will look at maven2 status in java-experimental overlay.
For the moment, the ant build is fine. Let's hope that until it will become deprecated (around 2.0?) Gentoo will have better support for maven builds. One more reason to always keep the ant build up2date. Ok
What exactly does "/etc/init.d/xwiki start/stop" do? Init script will start/stop jetty in standalone xwiki. /usr/share/xwiki-svn-1.0/standalone/ For now it is use following command: su - xwiki -c "${JAVA} ${JETTY_OPTS} -jar start.jar" >> \ /var/log/xwiki.log 2>&1 & Maybe it is not best variant. jetty-5.1.3-r1.ebuild in java-overlay uses /extra/unix/bin/jetty.sh script which I find not in xwiki standalone.
So, we use our own jetty, and not an emerged one, right? What if the user used the tomcat flag? Shouldn't /etc/init.d/xwiki check the status of mysql and tomcat instead? If user will USE=-standalone then /etc/init.d/xwiki will not be installed. If user will USE=tomcat, then he needs to configure xwiki manually for now. I think it is possible to configure mysql/pgsql in # emerge --config xwiki pkg_config() function in ebuild. ebuild will ask user the root password for mysql/pgsql and create xwiki database.
Speaking of mysql, we could also provide some flags for choosing the database. Yes. I plan to support hsqldb, mysql and postgresql in ebuild.
What is the default build target? Or the user has to choose at least one of war, tomcat...? Default ant build target = release. But if user do not select any use flags he gets only /usr/share/xwiki*/lib/xwiki.jar :) We need to consider default behavior for this ebuild. xwiki.jar is OK for me as the default behavior. Ok
-- Artem Melentyev, UralSU, CS401
Hi Artem, On 5/8/07, Artem Melentyev <[email protected]> wrote:
Hi, Sergiu.
Sergiu Dumitriu wrote:
On 5/8/07, Artem Melentyev <[email protected]> wrote:
Hi Sergiu.
Sergiu Dumitriu wrote:
Some other USE flags I'd like to see: src - for checking out the sources, too. You could check the status on "ant src.dist" There are standard use flag "source". xwiki ebuild use core/src/main/java sources. Current ant src.dist target make only doc, lib (no need in 'source' flag IMHO), and some resources but no sources. I think it is wrong behavior.
That's what it does? Hm, wrong behavior, indeed. And yes, the standard USE flag is "source", my bad. I think source use flag should make only source zip, without libs and docs, so I think 'use source && java-pkg_dosrc core/src/main/java' is sufficient. This source zip may be using in IDE for example. WDYT?
I agree. -- http://purl.org/net/sergiu
Hello. from http://jira.xwiki.org/jira/browse/XWIKI-467 : Attached new version: xwiki-1.0_rc3.ebuild.tar.bz2 changes: * rename from xwiki-svn to xwiki * remove slotting (/usr/share/xwiki/ instead of /usr/share/xwiki-1.0) for simplify * uses stable svn 1.0-RC3 tag sources. (you may change to any svn url) * + useflags: * doc - make javadocs * source - make source zip * test - run xwiki tests before install (FEATURES=test emerge xwiki) -- Artem Melentyev, UralSU, CS401
participants (2)
-
Artem Melentyev -
Sergiu Dumitriu