Hello Dmitry
I can start builds now - thanks! I absolutely agree we have to upgrade JDK. However, 1.6 has also reached EOL [1] - If we do upgrade, I suppose upgrading to 1.7 would be the right thing to do. The question really is if there are any non-legacy stakeholders requiring 1.6 compatibility *and* continued updates. Regards, Olaf [1] <http://www.oracle.com/technetwork/java/eol-135779.html> http://www.oracle.com/technetwork/java/eol-135779.html From: [email protected] [mailto:[email protected]] On Behalf Of Dmitry Sklyut Sent: Freitag, 25. Oktober 2013 15:12 To: Gemini and sub-projects developer discussions Subject: Re: [gemini-dev] Blueprint builds Olaf, I got the full set of permissions. See if you can kick off a build and let me know if you run into issues. One final build issues that needs to be ironed out - what jdk do we build with. I will put this out on the forum. With 5.0 EOLed in 09 - I think we should jack up compiler to 1.6. Need to see how many are there using old jdk. Also need to get builds into nexus. Regards, Dmitry On Fri, Oct 25, 2013 at 8:39 AM, Olaf Otto <[email protected]> wrote: Hello Markus Thanks a lot! Role-based permissions sound like a very good idea indeed. Dmitry, I suppose you have the required permissions to change these settings - what do you think? Cheers, Olaf From: [email protected] [mailto:[email protected]] On Behalf Of Markus Knauer Sent: Freitag, 25. Oktober 2013 14:36 To: Gemini and sub-projects developer discussions Subject: Re: [gemini-dev] Blueprint builds It's not my business, I know... but I stumbled upon this mailing list post and thought it would make sense to add the required rights for ROLE_RT.GEMINI.BLUEPRINT to the three Hudson Blueprint job configurations. This allows commiters to start a job, or to look into the workspace on Hudson. If this is not what you want, just delete the rights given to this role from the Hudson user interface, but I think it may be useful. Regards, Markus On Fri, Oct 25, 2013 at 2:08 PM, Olaf Otto <[email protected]> wrote: Hi Dmitry I have taken the liberty to refactor the test case using Mockito. I am currently not authorized to start the integration build, but I believe this may resolve most of the issues. Regards, Olaf From: [email protected] [mailto:[email protected]] On Behalf Of Dmitry Sklyut Sent: Freitag, 25. Oktober 2013 03:10 To: Gemini and sub-projects developer discussions Subject: [gemini-dev] Blueprint builds Hi All, I pushed a set of changes to new branch "build". Basic cleanup of the pom and upgrade to bundlor. It runs perfectly fine on my local machine. Fails miserably on hudson[1]. It fails in places that make no sense to me. One example is reflection code, i.e. setting a property on a bean. Second is reading an xml file of classpath (class.getResource). Has anyone experienced issues with shared hudson instance? I tried almost all of the jdks and maven configs possible. Just for sanity check, anyone who is interested - please pull down the code and try to do a local build. I would like to make sure that these issues are isolated to eclipse hudson vs. something on my box. I looked at other gemini jobs that use maven and I see nothing in configuration that would make those jobs run and blueprint fail. Regards, Dmitry [1] https://hudson.eclipse.org/hudson/job/gemini-blueprint-equinox/493/consoleFu ll _______________________________________________ gemini-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/gemini-dev _______________________________________________ gemini-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/gemini-dev
_______________________________________________ gemini-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/gemini-dev
