FYI: The apache-release target checks for JDK 1.4.2 before allowing a release build to proceed.
- Dave On 8/31/06, Anil Gangolli <[EMAIL PROTECTED]> wrote:
No problem. I have fixed and committed the trivial change to address this. I'm just suggesting that to avoid this in the future you probably want to set your dev env up to use a JDK 1.4.2 compiler for Roller. Here's the diff URL: http://svn.apache.org/viewvc?rev=438815&view=rev You can mail to: [EMAIL PROTECTED] for an automated help response on subscribing, etc. to the commits list. --a. ----- Original Message ----- From: "Elias Torres" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Thursday, August 31, 2006 6:50 AM Subject: Re: Roller 3.0 branch build broken? > Definitely my bad. Did you fix or would you like me to fix? > > I'm not subscribed to roller-commits. Anybody can perform that magic? > Thanks. > > -Elias > > Anil Gangolli wrote: >> >> I'm seeing this: >> >> javac >> >> C:\IdeaProjects\roller-svn\roller\branches\roller_3.0\build.xml:331: >> Compile failed; see the compiler error output for details. >> C:\IdeaProjects\roller-svn\roller\branches\roller_3.0\src\org\apache\roller\ui\core\security\CustomUserRegistry.java >> (95:7)setEnabled(java.lang.Boolean) in org.apache.roller.pojos.UserData >> cannot be applied to (boolean) >> C:\IdeaProjects\roller-svn\roller\branches\roller_3.0\src\org\apache\roller\ui\core\security\CustomUserRegistry.java:95: >> setEnabled(java.lang.Boolean) in org.apache.roller.pojos.UserData cannot >> be applied to (boolean) >> C:\IdeaProjects\roller-svn\roller\branches\roller_3.0\build.xml:331: >> Compile failed; see the compiler error output for details. >> C:\IdeaProjects\roller-svn\roller\branches\roller_3.0\build.xml:331: >> Compile failed; see the compiler error output for details. >> >> >> I plan to fix this right now. >> >> However, it suggests that one of the committers (Elias? perhaps?) has a >> dev environment setup with JDK 1.5 as the build compiler, >> where autoboxing would accept this. Committers' should be building with >> 1.4.2 at least to verify things do build under 1.4.2. >> >> --a. >> >> >> >> >
