#783 ✓invalid

javadoc generation fails on windows

Reported by peterneish | April 28th, 2011 @ 07:28 AM | in 1.3 (closed)

On windows, running the javadoc command fails with
WindowsError: [Error 2] The system cannot find the file specified

Framework version: 1.2
Platform you're using: Windows XP

Reproduction steps: run the command: play javadoc [app_path]

C:\play_framework\play-1.2>play javadoc samples-and-tests\yabe
~        _            _
~  _ __ | | __ _ _  _| |
~ | '_ \| |/ _' | || |_|
~ |  __/|_|\____|\__ (_)
~ |_|            |__/
~ play! 1.2, http://www.playframework.org
Generating Javadoc in C:\play_framework\play-1.2\samples-and-tests\yabe\javadoc.
Traceback (most recent call last):
  File "C:\play_framework\play-1.2\play", line 146, in <module>
    cmdloader.commands[play_command].execute(command=play_command, app=play_app,
 args=remaining_args, env=play_env, cmdloader=cmdloader)
  File "C:\play_framework\play-1.2\framework\pym\play\commands\javadoc.py", line
 42, in execute
    subprocess.call(javadoc_cmd, env=os.environ, stdout=sout, stderr=serr)
  File "C:\play_framework\play-1.2\python\lib\subprocess.py", line 444, in call
    return Popen(*popenargs, **kwargs).wait()
  File "C:\play_framework\play-1.2\python\lib\subprocess.py", line 595, in __ini
    errread, errwrite)
  File "C:\play_framework\play-1.2\python\lib\subprocess.py", line 821, in _exec
WindowsError: [Error 2] The system cannot find the file specified

Seems to be the same issue as this: http://groups.google.com/group/play-framework/browse_thread/thread/...

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2>Play framework</h2>

Play makes it easier to build Web applications with Java. It is a clean alternative to bloated Enterprise Java stacks. It focuses on developer productivity and targets RESTful architectures. Learn more on the <a href="http://www.playframework.org">http://www.playframework.org</a> website.<br><br>

<h2>Source code is hosted on github</h2>Check out our repository at <a href="http://github.com/playframework/play">http://github.com/playframework/play</a><br><br>

<h2>Contributing, creating a patch</h2> Please read the <a href="http://play.lighthouseapp.com/projects/57987/contributor-guide">contributor guide</a><br><br>

<h2>Reporting Security Vulnerabilities</h2> Since all bug reports are public, please report any security vulnerability directly to <em>guillaume dot bort at gmail dot com</em>.<br><br>

<h2>Creating a bug report</h2> Bug reports are incredibly helpful, so take time to report bugs and request features in our ticket tracker. We’re always grateful for patches to Play’s code. Indeed, bug reports with attached patches will get fixed far quickly than those without any.<br><br>

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.<br><br>

Don't have too much expectations. Unless the bug is really a serious "everything is broken" thing, you're creating a ticket to start a discussion. Having a patch (or a branch on Github we can pull from) is better, but then again we'll only pull high quality branches that make sense to be in the core of Play.

People watching this ticket