[Issue 755] New - Default JDK meening in project options is confusing.

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

[Issue 755] New - Default JDK meening in project options is confusing.

teilo-2
https://hudson.dev.java.net/issues/show_bug.cgi?id=755
                 Issue #|755
                 Summary|Default JDK meening in project options is confusing.
               Component|hudson
                 Version|current
                Platform|HP
              OS/Version|Windows XP
                     URL|http://www.nabble.com/Hudson-ignoring-JAVA_HOME-in-con
                        |figuration--tf4298778.html
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|ENHANCEMENT
                Priority|P3
            Subcomponent|maven2
             Assigned to|issues@hudson
             Reported by|teilo






------- Additional comments from [hidden email] Tue Aug 21 09:18:21 +0000 2007 -------
When the option for which JDK to use for native m2 builds is set to "default"
and there is only one jdk configured in hudson the builds should use that jdk
not the jdk/jre of the container.

if there are more jdks' configured hudson should use the first one configured
at the system level for default.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Issue 755] Default JDK meening in project options is confusing.

Kohsuke Kawaguchi
Administrator
https://hudson.dev.java.net/issues/show_bug.cgi?id=755






------- Additional comments from [hidden email] Fri Apr  3 05:19:33 +0000 2009 -------
Maybe it's better off if we just get rid of this "default" thing altogether.
Does it really buy us anything?

If there's only one JDK configured in Hudson, I suppose we shouldn't even
display the JDK selection drop-down and just stick to that JDK.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Issue 755] Default JDK meening in project options is confusing.

teilo-2
In reply to this post by teilo-2
https://hudson.dev.java.net/issues/show_bug.cgi?id=755






------- Additional comments from [hidden email] Fri Apr  3 17:22:50 +0000 2009 -------
Alternativly if you only have one that is the default, but if you have multiple
then you can select which is the default.

Then if you wish to upgrade and most of your jobs are using the default you can
do it in just one place. (and let the projects that need a different jdk use it.)

ALthough I guess you could do this already by calling a jdk install "latest" and
just change the path to which jdk it uses...

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Issue 755] Default JDK meening in project options is confusing.

bimargulies-2
In reply to this post by teilo-2
https://hudson.dev.java.net/issues/show_bug.cgi?id=755






------- Additional comments from [hidden email] Sun Jun 28 00:37:13 +0000 2009 -------
This problem seems more severe to me.

I added a second JDK, and selected one of them for my project, and the project
is still running with the JRE as JAVA_HOME instead of the JDK. I need the JDK.

Either that or the maven-antrun-plugin is playing a nasty prank on me.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]