Hi, Sergiu. Sergiu Dumitriu wrote:
On 5/8/07, Artem Melentyev <melenartem@ya.ru> 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