#1205 ✓wontfix
Bruce Bolingbroke

Documentation update: How to exclude test dependencies from production code

Reported by Bruce Bolingbroke | November 2nd, 2011 @ 06:23 PM

Framework version: 1.2.3
Platform you're using: Any (documentation)

Reproduction steps: See http://www.playframework.org/documentation/1.2.3/dependency#comment...

Modules like cobertura should not be included in the production code. Application.conf allowed you to specify test mode for cobertura. That has been deprecated in 1.2.3 and superseded by dependency management. We should document how to limit a module to a particular mode in dependency.yml or at least add a note saying that this is no longer possible.

Comments and changes to this ticket

  • Peter Hilton

    Peter Hilton November 8th, 2011 @ 05:47 PM

    • State changed from “new” to “confirmed”
    • Tag set to documentation
  • Peter Hilton

    Peter Hilton November 21st, 2011 @ 11:52 AM

    • State changed from “confirmed” to “wontfix”
    • Assigned user set to “Peter Hilton”

    This is not an issue for the cobertura module, because its documentation states:

    This plugin is written for ‘test’ mode, and will silently do nothing in other modes. Therefore, leaving it activated while running your application in other modes is not a problem.

  • Bruce Bolingbroke

    Bruce Bolingbroke November 21st, 2011 @ 05:13 PM


    The cobertura module is one instance of a more general problem. Application.conf allowed you to specify test mode for modules. That has been deprecated in 1.2.3 and superseded by dependency management. Many people are searching the Internet for a way to only have module dependencies in test mode. Let's update the documentation to say that you can't limit dependencies to test mode in dependencies.yml and state that any modules that are only for test purposes must be built to only run in test mode like cobertura.

  • Peter Hilton

    Peter Hilton November 21st, 2011 @ 05:26 PM

    I don't think it would be appropriate to add documentation to describe a non-feature like this, any more than we want to document everything else you can't do. This might have been relevant in the Play 1.2 release notes, since it reflects a change from declaring test mode modules in application.conf, but now it would only clutter the documentation.

    I would, however, welcome a documentation contribution for the modules chapter that discusses testing the application mode. Note that test, in this context, is a framework ID, not a mode (which can only be PROD or DEV).

  • Lillian Mcneil

    Lillian Mcneil December 23rd, 2017 @ 01:47 PM

    Great post share on, how to exclude test dependencies from production code for essay service review as well. This Reproduction steps post is impressive as well, I hope to read more on this.

  • Arvind Kumar

    Arvind Kumar July 28th, 2018 @ 09:42 AM

    When first time i am using the dell wireless mouse then i am so happy to use this but only in few times they creating some problem then i have to go firstly wireless mouse is not connecting and withou see this i have to go service center then after his coming he say that your connection of the wireless mouse has been not prefect that's why it can't work properly so you must check the connection.

  • Liam Smith

    Liam Smith August 24th, 2018 @ 08:30 AM

    I really happy found this website eventually. Really informative and inoperative, Thanks for the post and effort! Please keep sharing more such blog. We also provide blog My Assignment Help.

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.