Summary: | dev-java/continuum: integration server for building Java based projects | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Guenther Schroettner <linux> |
Component: | [OLD] Server | Assignee: | Default Assignee for New Packages <maintainer-wanted> |
Status: | RESOLVED OBSOLETE | ||
Severity: | enhancement | CC: | java, phuber, schrepfler |
Priority: | High | Keywords: | EBUILD |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://maven.apache.org/continuum/ | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
ebuild for continuum 1.0.3
continuum-bin-1.0.3 (includes cleanups) continuum dependencies from readme.txt running maven from an ebuild |
Description
Guenther Schroettner
2006-01-16 06:07:02 UTC
What's the status for continuum under gentoo, did someone try/is trying to package it? Just to bump the issue and tell that 1.0.3 is out. Created attachment 95381 [details] ebuild for continuum 1.0.3 Here's an ebuild for dev-java/continuum-bin-1.0.3... It's a Q & D but it works for me... latest version's here: https://svn.swisstech.net/gentoo/ebuild/ Feedback on https://svn.swisstech.net/gentoo/ebuild/dev-java/continuum-bin/continuum-bin-1.0.3.ebuild to improve your ebuild writing skills. inherit java-pkg All new java packages that go in should use generation 2 http://www.gentoo.org/proj/en/java/java-devel.xml continuum-${PV} you use this in two places so you could make it ${MY_P} src_install() { echo "*** `pwd`" echo "*** ${S}" useless debug stuff mkdir -p ${D}/opt/continuum cp -r ${S}/* ${D}/opt/continuum insinto and doins are good helper functions to use # init script mkdir -p ${D}/etc/init.d cp ${FILESDIR}/continuum ${D}/etc/init.d/continuum chmod +x ${D}/etc/init.d/continuum there is doinitd for this Anyway we will not be adding new binary packages because it is our policy to build packages from source. Thank you for your feedback! I'll integrate it and maybe make an src-based ebuild if time permits. (In reply to comment #5) > Thank you for your feedback! I'll integrate it and maybe make an src-based > ebuild if time permits. > Please post here when you integrate it and/or add a src-based ebuild. Created attachment 95925 [details]
continuum-bin-1.0.3 (includes cleanups)
added the suggested cleanups / still binary
(In reply to comment #7) > Created an attachment (id=95925) [edit] > continuum-bin-1.0.3 (includes cleanups) > > added the suggested cleanups / still binary > I believe there is some svn files lying around the archive. I think the no-binaries requirement is silly with java apps but I can understand also why. Is continuum built with maven2 or ant? I can agree with at least 5 of the 8 points given, I'm sold for. Created attachment 96212 [details]
continuum dependencies from readme.txt
The attachment lists a section from the continuum readme.txt there are a bunch of libraries required. a quick qsearch showed that there's an ebuild for one of them - require the user to install them manually or create ebuilds for every one of them?
Created attachment 96213 [details]
running maven from an ebuild
has anyone actually used maven in an ebuild? a grep trough /usr/portage found nothing... see the attached file for the errors. Is it even possible to run maven in an ebuild? if yes, how?
> has anyone actually used maven in an ebuild? a grep trough /usr/portage found > nothing... see the attached file for the errors. Is it even possible to run > maven in an ebuild? if yes, how? It will be possible after 2.0.5 is released. For now use `mvn ant:ant` to get build.xml - you'll need to set few variables, for example see this ebuild: http://overlays.gentoo.org/dev/nelchael/browser/dev-java/jline/jline-0.9.9.ebuild the build.xml comes from ant:ant. I remember at the time the gentoo dev's were very much against the use of maven(2), is this still true? My comment on it would be that when it works it's heavenly but it's flakey meaning that sometimes it fails randomly which goes against one on those 8 bullets someone passed me before ("We guarantee to our users that the source exists and compiles properly, the basis of regular open-source development."). Also it tends to use a repository of binaries which is against another bullet. That said if we as gentoo make our mirrors also package repositories in sync with ibiblio and other (like the sun repository),or even add packages ourselves we'd have a much more robust maven story but still, a bit risky one. Then again, if projects themselves rely on maven to compile themselves, why should gentoo reinvent the wheel and spend resources in alternative build systems (that would probably also have to have a list of other binaries to suck into from somewhere). To me the source built java libs is a bit of utopia and although usefull it's a bit of an overkill. I as a gentoo user would prefer an up-to-date java system with binaries then all the advantages that building from source provide. Why? Because we can always add that step later when it's properly done and because we already provide binaries to jumpstart the system. The point on optimizing the bytecode kind of looks bogus these days, as the optimization is mostly done by a jitter, but things like obfuscation are much more important - so add that as a bullet. These are just thoughts, I'm not trying to shove these arguments too hard, just try to contribute to the general discussion on how might the portage evolve from a layman point of view. @Srepfler Bugzilla isn't the best venue for that kind of discussion.The gentoo-java mailing list is better for it. This is mostly there is a larger audience, and that there have been discussions along those lines already. Hi folks This bug is 9 years old. Is there still an interest in getting this ebuild in to Portage? Please make yourself known if you do. I will close this bug if not. Consider using dev-util/jenkins-bin if you want a continuous integration server. It's packaged for Gentoo. |