#991 ✓wontfix

uncomfortable eclipse launcher

Reported by Anton | July 23rd, 2011 @ 12:41 PM | in 1.3 (closed)

Framework version: 1.2.2
Platform you're using: Snow Leopard 10.6.6 / Eclipse Indigo JEE

The default launcher are not realy comfortable, example:

Start the app with Run as, then Debu As the JPDA
First / some times it works, but after edit your code and hot-deployment the debug mode exists. When starting JPDA debug you have no control to stop it. When you start the app again, the dt_socket for debugging changes sometimes:
'Listening for transport dt_socket at address: 9325' -> So you have to edit the JDPA launcher file and adjust the port.

My solution is: Change some argument of the app launcher (Run as -> Run Configurations.. or Debug) and remove in the arguments tab, this VM argument:


then you can use the app lancher APP_NAME.launch for both optios, Run as and Debug as.
You don't have to start the JPDA launcher extra or adjust the port.

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