public inbox for gentoo-java@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joshua Nichols <nichoj@gentoo.org>
To: robert burrell donkin <robertburrelldonkin@gmail.com>
Cc: gentoo-java <gentoo-java@lists.gentoo.org>
Subject: Re: [gentoo-java] Java ideas for Summer of Code
Date: Mon, 08 May 2006 19:29:27 -0500	[thread overview]
Message-ID: <445FE267.2020503@gentoo.org> (raw)
In-Reply-To: <f470f68e0605081537j46aabc2ctd66888391e85f9c3@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

robert burrell donkin wrote:
> one day i'll remember about gmail :-<
> 
> ---------- Forwarded message ----------
> From: robert burrell donkin <robertburrelldonkin@gmail.com>
> Date: May 8, 2006 11:35 PM
> Subject: Re: [gentoo-java] Java ideas for Summer of Code
> To: Joshua Nichols <nichoj@gentoo.org>
> 
> On 5/7/06, Joshua Nichols <nichoj@gentoo.org> wrote:
> 
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> robert burrell donkin wrote:
>> > On 5/5/06, Joshua Nichols <nichoj@gentoo.org> wrote:
>> >>
>> >> robert burrell donkin wrote:
>> >> > On 5/4/06, *Joshua Nichols* <nichoj@gentoo.org
> 
> 
> <snip>
> 
>>> why not open source java?
>> >> >
>> >> Uh, open source java is EXACTLY what I'm talking about :)
>> >
>> >
>> > good :-)
>> >
>> > gump (http://gump.apache.org/ ) builds and tests 700 projects from
>> source
>> > each day. IIRC the classpath team run gump. might be able to dig out an
>> url
>> > if you're interested in seeing the current level of progress.
>> >
>> > in general, finding a way to generate EBUILDs from gump descriptors
>> would
>> > make available a lot of libraries and applications without extensive
>> > effort.
>> > a maven EBUILD plugin would be even better.
>>
>> ebuild isn't an acronym, so you don't need to capitalize it all ;)
> 
> 
> looks better as EBUILD (especially as i don't know where the shift key
> is ;)
> 
> 
> maybe need to fake an acronym for marketing purposes :)
> 
> But having a way to generate ebuilds from gump descriptor or maven
>> project files would be intersting and all well and good... but someone
>> would actually have to do the work to put it together. That person isn't
>> likely me in the foreseeable future, unless someone has a deal on
>> cloning.
>>
> 
> 
> just speculating out load ATM  (on the generation, not the cloning)
> 
>> apache has a lot of API implementations but they are scattered amongst
>> > different projects. it would probably be generally a good thing if they
>> > were
>> > more easily accessible. fixing that would also be a big gain for a
>> small
>>
>> > amount of effort.
>>
>> 'small amount of effort' for whom?
> 
> 
> sorry - ASF hat on there :-/
> 
> actually providing an index of all available implementations in one
> place is
> something that the ASF should really do. make things a little easier for
> those folks downstream consumers looking for clean room implementations and
> a lot easier for users. there's a lot of activity around DOAP ATM and this
> fits in well.

That's actually a really good idea. You should suggest it to somewhere
that can do something about it :) Maybe their bugzilla?

> 
> Adding a lot of packages doesn't
>> particularly sound like a small effort to me.
> 
> Another hurdle is that
>> many projects are switching to maven for building, and as I describe in
>> the project ideas, we aren't quiet ready to handle using it to build.
> 
> 
> i'm not sure i understand why mavenization is such a hurdle. nearly
> anything
> built with maven can be built with ant. (maven can generate an ant build
> from the POM.) projects using techniques such as generation using custom
> maven plugins aren't so easy but that's a definite minority.

That's mostly true for maven1. As you said, you can generate build.xml
files, and we can package stuff using this build.xml. However, for
sophisticated projects (ie multiprojects), build.xml which perfectly
mirror the maven build isn't always possible.

> 
> (but that's not to say that building maven2 isn't a worthy exercise)

Seriously though, it's quite an epic exercise. I've attempted it several
times, and obviously wasn't successful enough, or the point would be moot.

> - robert
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEX+Jn8ATTzZyw6sMRAvnmAJ4wohQFKayhSI4HUUee7gwNnl7kkACeIZgg
4LGbGE0i31sqVXwZo2HOTFQ=
=KWWs
-----END PGP SIGNATURE-----
-- 
gentoo-java@gentoo.org mailing list



      reply	other threads:[~2006-05-09  0:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-04 17:20 [gentoo-java] Java ideas for Summer of Code Joshua Nichols
2006-05-04 18:28 ` Gerry Smith
2006-05-04 19:26   ` Joshua Nichols
     [not found] ` <f470f68e0605050601m38d3c22y5f8cb520feb29787@mail.gmail.com>
2006-05-05 15:21   ` Joshua Nichols
2006-05-06 10:48     ` robert burrell donkin
2006-05-07 13:11       ` Joshua Nichols
     [not found]         ` <f470f68e0605081535n7f6f1ce2m7c418405817ac3ad@mail.gmail.com>
2006-05-08 22:37           ` robert burrell donkin
2006-05-09  0:29             ` Joshua Nichols [this message]

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=445FE267.2020503@gentoo.org \
    --to=nichoj@gentoo.org \
    --cc=gentoo-java@lists.gentoo.org \
    --cc=robertburrelldonkin@gmail.com \
    /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