Re: fail bootstrap early with wrong jdk
Unless I'm mistaken it was this change: http://svn.apache.org/viewvc?view=rev&rev=442757 Joe Jason Dillon wrote: When did 1.5 specs creep in? I heard some talk about it, but I was not aware that the specs build JDK requirements had changed. --jason On Sep 13, 2006, at 1:41 PM, Joe Bohn wrote: Yes, after building the specs with 1.5 I was able to continue to build everything else with 1.4.2. Sorry I forgot to post that info to this thread earlier. Joe Tim McConnell wrote: Hi Joe, were you able to successfully build the remainder of trunk after getting the specs to build (with a 1.5 jdk) ?? Just wondering I should try the same if it'll help me get trunk built Joe Bohn wrote: I suspect that nobody has reported this before because the java ee 5 specs were just moved into trunk last night by dblevins. Do you have the latest source with these additional specs included? It seems that all the specs do build correctly if I use 1.5 ... but I'm not sure if that will cause some other problems for the overall build (and it's kinda a pain to switch the jdk mid-stream for just one item in the overall build). Dave, how are we supposed to handle building these at the moment? Thanks, Joe Jacek Laskowski wrote: On 9/13/06, Joe Bohn <[EMAIL PROTECTED]> wrote: I just did a fresh checkout and attempted to build specs via "bootstrap specs". I'm suspecting that the introduction of the EE 5 specs mean that we need to start building with JDK 1.5 (in which case failing a bootstrap for using JDK 1.5 would be a bad thing). However, I haven't dug into this error yet so it could be something completely different. ... Failure executing javac, but could not parse the error: javac: invalid target release: 1.5 Usage: javac That's yet another reason to whack bootstrap if it's not used heavily. It seems it's not as noone's reported the issue before. I could build Geronimo, OpenEJB 2 and Specs with no bootstrap and .m2 local repo and wonder whether we really need the bootstrap script yet? Jacek
Re: fail bootstrap early with wrong jdk
When did 1.5 specs creep in? I heard some talk about it, but I was not aware that the specs build JDK requirements had changed. --jason On Sep 13, 2006, at 1:41 PM, Joe Bohn wrote: Yes, after building the specs with 1.5 I was able to continue to build everything else with 1.4.2. Sorry I forgot to post that info to this thread earlier. Joe Tim McConnell wrote: Hi Joe, were you able to successfully build the remainder of trunk after getting the specs to build (with a 1.5 jdk) ?? Just wondering I should try the same if it'll help me get trunk built Joe Bohn wrote: I suspect that nobody has reported this before because the java ee 5 specs were just moved into trunk last night by dblevins. Do you have the latest source with these additional specs included? It seems that all the specs do build correctly if I use 1.5 ... but I'm not sure if that will cause some other problems for the overall build (and it's kinda a pain to switch the jdk mid-stream for just one item in the overall build). Dave, how are we supposed to handle building these at the moment? Thanks, Joe Jacek Laskowski wrote: On 9/13/06, Joe Bohn <[EMAIL PROTECTED]> wrote: I just did a fresh checkout and attempted to build specs via "bootstrap specs". I'm suspecting that the introduction of the EE 5 specs mean that we need to start building with JDK 1.5 (in which case failing a bootstrap for using JDK 1.5 would be a bad thing). However, I haven't dug into this error yet so it could be something completely different. ... Failure executing javac, but could not parse the error: javac: invalid target release: 1.5 Usage: javac That's yet another reason to whack bootstrap if it's not used heavily. It seems it's not as noone's reported the issue before. I could build Geronimo, OpenEJB 2 and Specs with no bootstrap and .m2 local repo and wonder whether we really need the bootstrap script yet? Jacek
Re: fail bootstrap early with wrong jdk
No worries... I was responding to email before I had coffee, ignore me :-) --jason On Sep 13, 2006, at 1:40 PM, Jacek Laskowski wrote: On 9/13/06, Jason Dillon <[EMAIL PROTECTED]> wrote: You know... bootstrap was primarialy created in response to the troubles *you* were having running the m2 build in a clean environment :-P * * * But I am getting rather sick and tired of all this talk and complaining about bootstrap... Hey Jason. Where's your spirit! ;-) I know you know I didn't mean to annoy you with my comments. They were just my personal opinions which I remembered you shared too as you kept saying that the tool's a temporary solution to our build problems. And the last but not least, I couldn't propose anything better and moreover I'm proud I'm in a team you're part of. I had a chance to work on m2 and fell short. You've been doing it at the higest possible rate and am still staggered how easy it was when you've been doing it. No offence intended! Jacek -- Jacek Laskowski http://www.laskowski.net.pl
Re: fail bootstrap early with wrong jdk
I still following the process of running bootstrap in pieces when I have to start from scratch (as in this case). But at least I didn't have to build anything more than once. :-) Here's what I did: rd m2repo /s (my local repo location) md m2repo cd bootstrap clean set PATH and JAVA_HOME for jdk 1.5 bootstrap specs set PATH and JAVA_HOME for jdk 1.4.2 bootstrap modules bootstrap openejb2 bootstrap assemble Joe Jacek Laskowski wrote: On 9/13/06, Tim McConnell <[EMAIL PROTECTED]> wrote: Hi Joe, were you able to successfully build the remainder of trunk after getting the specs to build (with a 1.5 jdk) ?? Just wondering I should try the same if it'll help me get trunk built Did it twice or more. When I saw Rick had troubles building OpenEJB 2 I removed .m2 local repo and gave the build(s) a whirl. I had to build Geronimo, then OpenEJB 2 and then Geronimo again. There are some interdependencies and I couldn't build them all in one shot. Of course, the specs had to be built using java 5. Jacek
Re: fail bootstrap early with wrong jdk
On 9/13/06, Jason Dillon <[EMAIL PROTECTED]> wrote: You know... bootstrap was primarialy created in response to the troubles *you* were having running the m2 build in a clean environment :-P * * * But I am getting rather sick and tired of all this talk and complaining about bootstrap... Hey Jason. Where's your spirit! ;-) I know you know I didn't mean to annoy you with my comments. They were just my personal opinions which I remembered you shared too as you kept saying that the tool's a temporary solution to our build problems. And the last but not least, I couldn't propose anything better and moreover I'm proud I'm in a team you're part of. I had a chance to work on m2 and fell short. You've been doing it at the higest possible rate and am still staggered how easy it was when you've been doing it. No offence intended! Jacek -- Jacek Laskowski http://www.laskowski.net.pl
Re: fail bootstrap early with wrong jdk
On 9/13/06, Tim McConnell <[EMAIL PROTECTED]> wrote: Hi Joe, were you able to successfully build the remainder of trunk after getting the specs to build (with a 1.5 jdk) ?? Just wondering I should try the same if it'll help me get trunk built Did it twice or more. When I saw Rick had troubles building OpenEJB 2 I removed .m2 local repo and gave the build(s) a whirl. I had to build Geronimo, then OpenEJB 2 and then Geronimo again. There are some interdependencies and I couldn't build them all in one shot. Of course, the specs had to be built using java 5. Jacek -- Jacek Laskowski http://www.laskowski.net.pl
Re: fail bootstrap early with wrong jdk
Yes, after building the specs with 1.5 I was able to continue to build everything else with 1.4.2. Sorry I forgot to post that info to this thread earlier. Joe Tim McConnell wrote: Hi Joe, were you able to successfully build the remainder of trunk after getting the specs to build (with a 1.5 jdk) ?? Just wondering I should try the same if it'll help me get trunk built Joe Bohn wrote: I suspect that nobody has reported this before because the java ee 5 specs were just moved into trunk last night by dblevins. Do you have the latest source with these additional specs included? It seems that all the specs do build correctly if I use 1.5 ... but I'm not sure if that will cause some other problems for the overall build (and it's kinda a pain to switch the jdk mid-stream for just one item in the overall build). Dave, how are we supposed to handle building these at the moment? Thanks, Joe Jacek Laskowski wrote: On 9/13/06, Joe Bohn <[EMAIL PROTECTED]> wrote: I just did a fresh checkout and attempted to build specs via "bootstrap specs". I'm suspecting that the introduction of the EE 5 specs mean that we need to start building with JDK 1.5 (in which case failing a bootstrap for using JDK 1.5 would be a bad thing). However, I haven't dug into this error yet so it could be something completely different. ... Failure executing javac, but could not parse the error: javac: invalid target release: 1.5 Usage: javac That's yet another reason to whack bootstrap if it's not used heavily. It seems it's not as noone's reported the issue before. I could build Geronimo, OpenEJB 2 and Specs with no bootstrap and .m2 local repo and wonder whether we really need the bootstrap script yet? Jacek
Re: fail bootstrap early with wrong jdk
I know... I am just complaining about the complaining :-P--jasonOn Sep 13, 2006, at 1:14 PM, Sachin Patel wrote:On Sep 13, 2006, at 3:58 PM, Jason Dillon wrote:But I am getting rather sick and tired of all this talk and complaining about bootstrap... What is wrong with the complaints? Jacek simply addressed his opinion in a non-negative manner. If people have concerns then we should gladly accept them, not deter them from speaking their minds. We all have a right to complain, as you've shown on numerous occasions :). -sachin
Re: fail bootstrap early with wrong jdk
Hi Joe, were you able to successfully build the remainder of trunk after getting the specs to build (with a 1.5 jdk) ?? Just wondering I should try the same if it'll help me get trunk built Joe Bohn wrote: I suspect that nobody has reported this before because the java ee 5 specs were just moved into trunk last night by dblevins. Do you have the latest source with these additional specs included? It seems that all the specs do build correctly if I use 1.5 ... but I'm not sure if that will cause some other problems for the overall build (and it's kinda a pain to switch the jdk mid-stream for just one item in the overall build). Dave, how are we supposed to handle building these at the moment? Thanks, Joe Jacek Laskowski wrote: On 9/13/06, Joe Bohn <[EMAIL PROTECTED]> wrote: I just did a fresh checkout and attempted to build specs via "bootstrap specs". I'm suspecting that the introduction of the EE 5 specs mean that we need to start building with JDK 1.5 (in which case failing a bootstrap for using JDK 1.5 would be a bad thing). However, I haven't dug into this error yet so it could be something completely different. ... Failure executing javac, but could not parse the error: javac: invalid target release: 1.5 Usage: javac That's yet another reason to whack bootstrap if it's not used heavily. It seems it's not as noone's reported the issue before. I could build Geronimo, OpenEJB 2 and Specs with no bootstrap and .m2 local repo and wonder whether we really need the bootstrap script yet? Jacek
Re: fail bootstrap early with wrong jdk
On Sep 13, 2006, at 3:58 PM, Jason Dillon wrote:But I am getting rather sick and tired of all this talk and complaining about bootstrap... What is wrong with the complaints? Jacek simply addressed his opinion in a non-negative manner. If people have concerns then we should gladly accept them, not deter them from speaking their minds. We all have a right to complain, as you've shown on numerous occasions :). -sachin
Re: fail bootstrap early with wrong jdk
On Sep 13, 2006, at 7:43 AM, Jacek Laskowski wrote: That's yet another reason to whack bootstrap if it's not used heavily. It seems it's not as noone's reported the issue before. I could build Geronimo, OpenEJB 2 and Specs with no bootstrap and .m2 local repo and wonder whether we really need the bootstrap script yet? You know... bootstrap was primarialy created in response to the troubles *you* were having running the m2 build in a clean environment :-P * * * But I am getting rather sick and tired of all this talk and complaining about bootstrap... --jason
Re: fail bootstrap early with wrong jdk
I suspect that nobody has reported this before because the java ee 5 specs were just moved into trunk last night by dblevins. Do you have the latest source with these additional specs included? It seems that all the specs do build correctly if I use 1.5 ... but I'm not sure if that will cause some other problems for the overall build (and it's kinda a pain to switch the jdk mid-stream for just one item in the overall build). Dave, how are we supposed to handle building these at the moment? Thanks, Joe Jacek Laskowski wrote: On 9/13/06, Joe Bohn <[EMAIL PROTECTED]> wrote: I just did a fresh checkout and attempted to build specs via "bootstrap specs". I'm suspecting that the introduction of the EE 5 specs mean that we need to start building with JDK 1.5 (in which case failing a bootstrap for using JDK 1.5 would be a bad thing). However, I haven't dug into this error yet so it could be something completely different. ... Failure executing javac, but could not parse the error: javac: invalid target release: 1.5 Usage: javac That's yet another reason to whack bootstrap if it's not used heavily. It seems it's not as noone's reported the issue before. I could build Geronimo, OpenEJB 2 and Specs with no bootstrap and .m2 local repo and wonder whether we really need the bootstrap script yet? Jacek
Re: fail bootstrap early with wrong jdk
Joe Bohn wrote: Funny you should put this out just now. I was just about to ask if we needed to start running bootstrap specifically using JDK 1.5. I just did a fresh checkout and attempted to build specs via "bootstrap specs". I'm suspecting that the introduction of the EE 5 specs mean that we need to start building with JDK 1.5 (in which case failing a bootstrap for using JDK 1.5 would be a bad thing). However, I haven't dug into this error yet so it could be something completely different. openejb2 won't compile yet with JDK 1.5 because of the Sun ORB dependencies. Even once we fix that, we'll probably want to explicitly specify a compilation target of 1.4 for anything that doesn't require 1.5 features. We needed to do that for Yoko so that the core ORB and the omg spec jars were compatible with 1.4 JVMs. Rick Here's the error that I received: [INFO] [INFO] Building JPA 1.0 [INFO]task-segment: [install] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] Compiling 91 source files to C:\apache\geronimo\trunk\target\external\specs\geronimo-jpa_3.0_spec\target\classes [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure Failure executing javac, but could not parse the error: javac: invalid target release: 1.5 Usage: javac Joe Bill Dudney wrote: I think we should fail the bootstrap early if using jdk 1.5 as well as failing the maven build. http://issues.apache.org/jira/browse/GERONIMO-2403 has a patch attached that works, but there might be a way to reuse the mojo that Jason wrote, not sure... Thanks, -bd-
Re: fail bootstrap early with wrong jdk
On 9/13/06, Joe Bohn <[EMAIL PROTECTED]> wrote: I just did a fresh checkout and attempted to build specs via "bootstrap specs". I'm suspecting that the introduction of the EE 5 specs mean that we need to start building with JDK 1.5 (in which case failing a bootstrap for using JDK 1.5 would be a bad thing). However, I haven't dug into this error yet so it could be something completely different. ... Failure executing javac, but could not parse the error: javac: invalid target release: 1.5 Usage: javac That's yet another reason to whack bootstrap if it's not used heavily. It seems it's not as noone's reported the issue before. I could build Geronimo, OpenEJB 2 and Specs with no bootstrap and .m2 local repo and wonder whether we really need the bootstrap script yet? Jacek -- Jacek Laskowski http://www.laskowski.net.pl
Re: fail bootstrap early with wrong jdk
Funny you should put this out just now. I was just about to ask if we needed to start running bootstrap specifically using JDK 1.5. I just did a fresh checkout and attempted to build specs via "bootstrap specs". I'm suspecting that the introduction of the EE 5 specs mean that we need to start building with JDK 1.5 (in which case failing a bootstrap for using JDK 1.5 would be a bad thing). However, I haven't dug into this error yet so it could be something completely different. Here's the error that I received: [INFO] [INFO] Building JPA 1.0 [INFO]task-segment: [install] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] Compiling 91 source files to C:\apache\geronimo\trunk\target\external\specs\geronimo-jpa_3.0_spec\target\classes [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure Failure executing javac, but could not parse the error: javac: invalid target release: 1.5 Usage: javac Joe Bill Dudney wrote: I think we should fail the bootstrap early if using jdk 1.5 as well as failing the maven build. http://issues.apache.org/jira/browse/GERONIMO-2403 has a patch attached that works, but there might be a way to reuse the mojo that Jason wrote, not sure... Thanks, -bd-
fail bootstrap early with wrong jdk
I think we should fail the bootstrap early if using jdk 1.5 as well as failing the maven build. http://issues.apache.org/jira/browse/GERONIMO-2403 has a patch attached that works, but there might be a way to reuse the mojo that Jason wrote, not sure... Thanks, -bd-
