I write all my mojo's with 1.5. You just need to avoid using annotations and generics in the signature of your classes (fields, methods and their annotations).
Tom On 11/27/06, Nicolas DE LOOF <[EMAIL PROTECTED]> wrote:
Maven should depends on the latests Java version to allow plugins to use latest technology ! The maven-plugin-tools is a good example that demonstrate some user may get issue because maven is not up to date with latest tools. I'm building a Java 1.3 project for Websphere 5.0 using maven under Java5 (I'm using Java5 testing tools, like Watij). The target runtime may be java 1.1 or JME, this has nothing to do with maven requirements. Not beeing able to build a Java5 project/plugin with maven is a real issue. For maven plugins to support Java5 keywords, we should update maven requirements to Java5. Is there similar limitation not beeing able to build Java6 project/plugin using maven ? (is there some new Java6 keyword not supported in a Jav5 environment ?) Nico. Emmanuel Hugonnet a écrit : > Brett Porter a écrit : >> This would have zero impact on applications built with Maven. >> >> I'd been meaning to follow this up. Let me see what happened with the >> user survey... >> >> - Brett >> >> On 26/11/2006, at 12:49 PM, Brian E. Fox wrote: >> >>> Our experience with our products is that not enough of the available >>> portal and app servers support JDK 1.5 or our customers haven't yet >>> upgraded. That unfortunately means we are stuck on 1.4 for the near >>> future. I think many business customers are in the same predicament >>> where we can't dictate the JDK required. If maven suddenly required >>> Java >>> 1.5, we would be in a serious bind and it would limit adoption of Maven >>> 2.1. >>> >>> >>> -----Original Message----- >>> From: Rahul Thakur [mailto:[EMAIL PROTECTED] >>> Sent: Saturday, November 25, 2006 7:55 PM >>> To: Maven Developers List >>> Subject: Re: [discuss] Java 5 >>> >>> This thread kinda died off silently.... >>> >>> Just wondering if there was a user survey about switching to Java 5.0? >>> >>> Rahul >>> >>> >>> ----- Original Message ----- >>> From: "Jason van Zyl" <[EMAIL PROTECTED]> >>> To: "Maven Developers List" <dev@maven.apache.org> >>> Sent: Sunday, July 09, 2006 6:09 AM >>> Subject: Re: [discuss] Java 5 >>> >>> >>>> >>>> On 7 Jul 06, at 2:36 AM 7 Jul 06, Brett Porter wrote: >>>> >>>>> Hi, >>>>> >>>>> I wanted to get thoughts on starting to require a Java 5 JVM to run >>>>> stuff we build. We currently restrict to 1.4 across the board. >>>>> >>>>> >>>> >>>> I think before this can be done we need to make sure we're not making >>>> life difficult for people. It may be the case that most people don't >>>> have a problem using a 1.5 JDK in their environment but it might be >>>> an ideal time to use one of the online survey services to take a real >>>> poll. If the vast majority of users were not adversely affected by a >>>> move to 1.5 I would be fine with, as I'd like to use 1.5 where >>>> possible. But if it's not the case we probably should hold off on >>>> this requirement. >>>> >>>>> Here's what I'm thinking: >>>>> - MRM and Continuum should switch now. Stuff built there is rarely >>>>> consumed elsewhere, and a Java 5 requirement outside of that is >>>>> reasonable >>>>> - We could switch for Maven 2.1, as long as we have improved support >>> >>>>> for invoking external toolchains. This would facilitate doing some >>>>> much nicer stuff with plugins like annotations. >>>>> - A generified plexus would be very cool, but is an aside here and >>>>> post plexus-1.0 in my opinion. >>>>> - I think it's best to keep the lower requirement on Doxia, Surefire >>> >>>>> (1.3), and Wagon for now. >>>>> >>>>> Does anyone have any thoughts on this? >>>>> >>>>> I'll likely propose a vote on the first point before the first/next >>>>> releases of them unless there are reasons not to. >>>>> >>>>> Cheers, >>>>> Brett >>>>> >>>>> --Apache Maven - http://maven.apache.org/ >>>>> Better Builds with Maven - http://library.mergere.com/ >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>>>> For additional commands, e-mail: [EMAIL PROTECTED] >>>>> >>>>> >>>> >>>> Jason van Zyl >>>> [EMAIL PROTECTED] >>>> >>>> >>>> >>>> >>>> --------------------------------------------------------------------- >>>> 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] >>> >>> >>> >>> >>> --------------------------------------------------------------------- >>> 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] >> >> > Hi, > We are using jdk1.5 and I ran into serious troubles to build a 1.5 > plugin (using enum and generics) because maven-plugin-tools is not > JDK1.5 compatible even in snapshot :(. > My opinion is that a least we should have the ability to use what 1.5 > gives us (annotations for plugin description, enum, generics, > concurrency ...) with an old style tools or retroveawer > (http://retroweaver.sourceforge.net/) to get the 1.4 compatibility. > My 2 cents > Emmanuel > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. --------------------------------------------------------------------- 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]
