#180 ✓wontfix
Erwan Loisant

classpath issue in launchconfiguration of eclipse

Reported by Erwan Loisant | October 5th, 2010 @ 11:59 AM

I worte a plugin and started the application with the launch-configuration of eclipse.
I struggled because my plugin was loaded twice. The reason was, that
the file play.plugins founded in the source-folder of my module and a
copied version in "eclipse/classes/play.plugins". The solution is to
set in the Preferences -> Java -> Compiler -> Building "filtered
resources" to "*.launch, play.plugins". Ok this could be easily added
to documentation. Not so easy to eclipsify.

But after thinking little bit about the constellation I get a couple
of question?
1. Could I get trouble with the compiled classes, because they are not
enhanced? Then the eclipsify command should change. Or will the
classes enhanced while loading them? I don't analyse the code in
ApplicationClassloader in detail.

  1. Why was the plugin loaded twice? Is there a useful scenario or
    should be a filter to make this impossible?
    See http://groups.google.com/group/play-framework/browse_thread/thread/...#

Imported from Launchpad: https://bugs.launchpad.net/play/+bug/617545

Comments and changes to this ticket

  • Erwan Loisant

    Erwan Loisant June 9th, 2011 @ 12:31 PM

    • State changed from “new” to “wontfix”
  • opensource21

    opensource21 June 9th, 2011 @ 06:11 PM

    I don't understand why it wasn't fixed. At least the first question could be answered. Why are the compiled classes loaded? Normally play should do the compile job? Why is it possible that a class loaded twice? And why isn't the documentation changed?

    I mean if you don't have the time to fix it, then give some thoughts to the problem, so other people can fix it and make a pull request. At the moment it's not clear for me what an acceptable solution will be for the core-team. In the thread I linked in the bug-report Guillaume said he see the problem. For my understanding a problem must be fixed or you must found arguments why it's not a problem.

  • Francis De Brabandere

    Francis De Brabandere February 4th, 2012 @ 10:04 AM

    Clearly the play devs are not that great on communication...

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.

Referenced by

Pages