Well, from the Ant 1.5.3 online manual: "This works only on weblogic 4.5.1"
Many of us have gone way past WebLogic 4.5.1. Seeing as this patch handles 6.1, 7.0, and 8.1, I would assume it would be desired by many. As to the process for submitting changes, please read http://jakarta.apache.org/site/getinvolved.html especially http://jakarta.apache.org/site/source.html#Patches The bottom line of all this reading is that you don't make a change directly. You open a Bugzilla to document the proposed patch, and when committers have time to look at it, they will evaluate your proposal. If accepted, they will commit your patch, perhaps with some changes. If you contribute regularly, you could end up being nominated by the existing committers to become a new committer. -----Original Message----- From: Peter Nimmervoll [mailto:[EMAIL PROTECTED] Sent: Monday, July 07, 2003 5:38 PM To: Ant Developers List Subject: Re: Newbie contributor wannabe - WebLogic JSP Compiler Hmm, what is the problem with the current WebLogic JSP Compiler Ant Task? On Monday 07 July 2003 21:29, [EMAIL PROTECTED] wrote: > I would like to contribute to the Ant project by providing an upgrade > to the existing WebLogic JSP Compiler Ant Task. > > I have created an Ant Task for Weblogic JSP Compiler and have done > some prelimary tests for: > > - BEA WebLogic 6.1 SP3 on Windows 2000, RedHat 8.0, and Solaris 8 OS > - BEA WebLogic 7.0 SP2 on Windows 2000, RedHat 8.0, and Solaris 8 OS > - BEA WebLogic 8.1 on Windows 2000 > > But I am unable to test it against the older versions of BEA Weblogic, > especially version 4.5.1 as documented by the current stable release > of the WebLogic JSP Compiler optional Ant Task. > Also, this task was written from the ground up with no re-use of the > existing code base in WLJspc.java > > In this instance, what is the standard procedure or policy ? Do I > introduce this as a new optional task or upgrade the existing task ? > > The other question is how do I contribute my source? > > As far as I can tell, I need the following: > 1. Get a cvs login (how does one get a cvs login)? > 2. Sign a Contributor License Agreement. > > Are there more administrative steps? If anyone can point to references > or elaborate the steps, I would be much obliged. > > Regards, > John Liao --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
