#1040 ✓resolved
Alice Murphy

Module version number cannot be set via command line args to build-module if dependencies.yml exists

Reported by Alice Murphy | August 16th, 2011 @ 04:52 PM | in 1.3 (closed)

Framework version: 1.2.1 / 1.2.2
Platform you're using: Ubuntu 10.10 32-bit

Reproduction steps:

  1. Create a module with a "self:" line set in dependencies.yml with artifactId and/or groupId. version is optional.

  2. Build the module from the command line with

    play bm --version ${version}

    where ${version} is the version number that you specify.

  3. The resulting archive will have an incorrect version specified in its filename.


No matter what you have set for version in dependencies.yml, it will always override the value you specified at the command line. If you do have a version set in dependencies.yml, that one will override the one you set at the command line. If you don't, your artifactId/groupId (in fact, whatever is the last-indexed value when the "self:" line is split on " ") will override the value that you set at the command line.

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