#1164 ✓resolved
Andrew Skiba

PATCH: NetBeans project generated with no references to Play sources (fix included)

Reported by Andrew Skiba | October 16th, 2011 @ 02:04 PM | in 1.2.4 (closed)

I noticed that neatbeansify generates project with reference only to play.jar, and the sources of play are not available when you try to go to the definitions of different APIs. I checked eclipsify, and it does specify the sources. So I created a patch to fix that for NetBeans projects, too.

Framework version:
1.2.3, and the same problem on master.

Platform you're using:
OSX

Reproduction steps:
1. go to samples-and-tests/yabe
2. run 'play nb'
3. open the project in NetBeans
4. open Application.java, press command-click on renderArgs.put on line 16 or 17. Sources of RenderArgs.put are not available
5. apply the attached patch, run 'play nb' again and reopen the project in NetBeans. Sources are shown correctly now.

Details:

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.

Attachments

Pages