From: "m h" <sesquile@gmail.com>
To: gentoo-java@lists.gentoo.org
Subject: [gentoo-java] Some ebuilds you might be interested in
Date: Mon, 9 Oct 2006 12:08:02 -0600 [thread overview]
Message-ID: <e36b84ee0610091108h71c004c4sc894239d21106ed4@mail.gmail.com> (raw)
Java folks-
We[1] are building applications on top of prefixed portage and are
working with the gentoo-alt team for prefixed portage and cygwin
portage.
One of my co-workers has created ebuilds for quite a few java
packages. I'm not sure if the correct way to contribute these ebuilds
is through dev-java or if I should just fill out bug reports for them
on b.g.o.
Anyway, here is a list of them:
(dev-java/acegi-security-bin)
(dev-java/addressing)
(dev-java/alfresco)
(dev-java/buildmagic-tasks)
(dev-java/burlap)
(dev-java/cos)
(dev-java/gjt-jpl-pattern)
(dev-java/gjt-jpl-util)
(dev-java/hibernate)
(dev-java/htmlparser-bin)
(dev-java/httpunit)
(dev-java/jamon)
(dev-java/java-utils-test)
(dev-java/jboss-aop)
(dev-java/jboss-module-cache)
(dev-java/jboss-module-common)
(dev-java/jboss-module-j2ee)
(dev-java/jdbc-rowset-bin)
(dev-java/jibx)
(dev-java/jug)
(dev-java/jug)
(dev-java/myfaces-core-bin)
(dev-java/nekohtml)
(dev-java/one-jar-bin)
(dev-java/opensaml)
(dev-java/pdfbox-bin)
(dev-java/plexus-utils)
(dev-java/pluto)
(dev-java/portlet-api)
(dev-java/spring-framework)
(dev-java/spring-framework)
(dev-java/struts)
(dev-java/taglibrarydoc-bin)
(dev-java/werkz)
(dev-java/wss4j-bin)
(dev-java/xml-security)
Let us know how best to proceed. These ebuilds are for prefix gentoo,
but usually the change for java components is one or two lines to make
it work on normal gentoo. I'm looking forward to any collaboration we
can do. Thanks
-matt harrison
[1] www.spikesource.com
--
gentoo-java@gentoo.org mailing list
next reply other threads:[~2006-10-09 18:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-09 18:08 m h [this message]
2006-10-09 20:10 ` [gentoo-java] Some ebuilds you might be interested in Joshua Nichols
2006-10-10 4:33 ` Alistair Bush
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e36b84ee0610091108h71c004c4sc894239d21106ed4@mail.gmail.com \
--to=sesquile@gmail.com \
--cc=gentoo-java@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox