Subject says it all I suppose. 1.8 is very old and it was totally redesigned
for 2.x (akin to the apache changes from 1.x - 2.x).
Some changes are needed to the ebuild. In case someone is more informed on the
issue (or just on Gentoo-java) I'll give it a day or so before I submit my own
updated ebuild (which I havent made yet). Of course, if any developers followed
Cocoon then I guess there wouldnt be a 1.x ebuild laying around.....
1) Attach your ebuild to this bug
2) Build all of Coocoon from sources.
Between Tom von Schwerdtner and I, we've come up with an ebuild for Cocoon 2.0.2. I'm attaching it to this bug. This fix requires a patch and a new ebuild; I'm including those along with the digest. The patch fixes a bug introduced in Cocoon 2.0.x that keeps Cocoon from compiling with JDK 1.4. I've also posted the bugfix to Cocoon bugzilla, so hopefully this patch can be dropped in future Cocoon releases. I've tested this ebuild against Blackdown's JDK1.3 and Sun's JDK1.4, and it works for both. Tom added some code in the ebuild for optional PHP, JDNI, and JFOR support; the PHP and JFOR stuff is a hack until we add PHP and JFOR Portage packages.
Created attachment 1781 [details]
Ebuild (+patch) for cocoon 2.0.2
Contains digest, changelog, patch, and ebuild for 2.0.2; compiles with JDK 1.4
and JDK 1.3; requires tomcat 4.0.4.
Crap. I guess there's no auto-word-wrap in this form.
Anyway, one last thing: Karl, that ebuild requires Tomcat 4.0.4, but that
isn't strictly necessary. Cocoon is incompatible with Tomcat 4.0.3, but
it should actually work with Tomcat < 4.0.3; EG 4.0.2. I'm still getting the
hang of portage, so I didn't do the dependancy the way I should have. Would
you mind changing the dependancy to: tomcat != 4.0.3?
Added to Portage, but it remains masked until you guys take it out for a spin
again. Attach comments to this bug if it appears to work, and I'll let it loose
on the hordes shortly afterwards.
I made a few changes:
1) We no longer depend on jdk-1.3, so that we don't need a separate JNDI
2) Jikes is used to build if the jikes use flags is set (except it doesn't work).
If any of you have the time to contribute the JFOR and/or PHP java stuff, that'd
make my life all that much easier.
I must say, this is probably the best ebuild I've received ever, good work!
Thanks! Maybe I'll make some more ;-) PHP is going to be problematic, I've discovered, because it means downloading and compiling the entire PHP suite just to get the Java .jar built. PHP, of course, depends on Apache. Ergo, if we want to /build/ PHP support for Cocoon, we add a dependancy all the way back to Apache, which wouldn't otherwise exist. Tomcat is it's own Web server, and while not many people will probably have Tomcat installed without Apache, I'd hate to add a dependancy to software they won't use for those that don't. JFOR should be easier. I've got a prototype ebuild for it, and I'll get back to hacking on it. By the way, I must admit that I'm entirely clueless about how to get the stuff that is in Portage but is masked. Is there a document describing this process on gentoo.org? Thanks.
Yes, the apache dep is unacceptable. We will need to figure a way around that.
The file /usr/portage/profiles/package.mask contains the list of packages that
are masked. Just comment out the line that mentoins cocoon, and you should be
ready do go.
I'm marking this one as "REMIND" for now; please reopen when you figure out more.