Bugzilla Bug 63252

The ebuild needs to be updated to build the packages from source

Created an attachment (id=39806) [edit]
tared up ebuild files.

I have created an ebuild to build log4j from source code. To aquire the source
for this ebuild you will need to check the source code out from apache. 

cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic co -r v1_2-branch
logging-log4j

Once the checkout is complete you will need to mv the directory logging-log4j
to log4j-1.2.8 and  zip that up into a file named log4j-1.2.8.zip. It is
assumed the base folder in the zip file will be /log4j-1.2.8 .

Once this zip file is created it will need to be uploaded to a web server and
the URL in the ebuild will need to be changed.

There are three TODO items mentioned in the ebuild file these are as follows:
 - Incorporate a use flag for java-mail to build the SMTPAppender
 - Incorporate a use flag for JMX to add JMX service support
 - Add jaxp to the build package so it will build on 1.3 vms

I would love some suggestions on how we handle these as I am not sure what to
do  next.

Hmm the source is just in the tarball from apache?
commited with 
todo 1 + 2 completed

I can't keep track of what jdk has which api or what they get replaced with
do we have an ebuild for jaxp?

jaxp is built into version 1.4 vms. 

Gentoo does NOT have a jaxp (from sun) ebuild for use with 1.3 version vms as far as I know. There is an alternative jaxp-gnu in portage but I have not used it with log4j before.  

So have you added a USE flag for java-mail and jmx ? If you have I can add some code to the ebuild to take advantage of these flags and build the extra modules for log4j.

Thanks mate,

fixed, builds from source, yuo'll need a 1.4 unless someone submits an ebuild
for jaxp