On Sun, May 22, 2011 at 8:29 PM, Grant Ingersoll wrote:
> Do we have any convention/policy on how long a job can run before it's
> killed, so as to play nice with others? I've got some long running tests
> that I want to run once a week on Saturday morning (early, US time). For
> now they w
On Mon, May 23, 2011 at 2:41 AM, Todd Lipcon wrote:
> It seems that the configuration for Jenkins changed from a
> 1.5-compatible workspace to a 1.6-compatible workspace. Apparently
> this is changed under "Jenkins -> Manage Jenkins -> Configure System
> -> Subversion Workspace Version".
>
> I as
I recently added a new library, tapestry-javadoc, that defines a
JavaDoc Taglet used when generating Tapestry documentation. The build
works correctly on my local machine, using:
java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b07-334-10M3326)
Java HotSpot(TM) 64-Bit Serve
On Mon, May 23, 2011 at 7:02 PM, Howard Lewis Ship wrote:
> However, it fails on Jenkins (ubuntu2), with errors about classes in
> com.sun.javadoc, not being visible. As far as I know, these classes
> are part of the core runtime in Sun JDKs. What JDK is running on
> ubuntu2? Aren't the com.su
So, I just don't get why the com.sun.javadoc classes are not present.
Any ideas?
On Mon, May 23, 2011 at 10:12 AM, Niklas Gustavsson
wrote:
> On Mon, May 23, 2011 at 7:02 PM, Howard Lewis Ship wrote:
>> However, it fails on Jenkins (ubuntu2), with errors about classes in
>> com.sun.javadoc, not
On Mon, May 23, 2011 at 7:51 PM, Howard Lewis Ship wrote:
> So, I just don't get why the com.sun.javadoc classes are not present.
> Any ideas?
tools.jar for that JDK does contain the class. I'm not very familiar
with gradle, could you debug the build to see which JDK it is really
using?
/niklas
