#715 ✓wontfix
Florian Gutmann

dependency management cache

Reported by Florian Gutmann | April 9th, 2011 @ 09:33 AM | in 1.3 (closed)

When using a module that was installed with "play install" as dependency in dependency.yml and removing the installed module afterwards, the dependency management can't find the artifact anymore but doesn't try to download it from the play repository.

This is because the artifact location is cached somewhere in ~/.ivy2/.
After removing the ~/.ivy2 directory, the artifact is found again.

Framework version: 1.2.x
Platform you're using: Ubuntu 10.10 x64

Reproduction steps:

  • Create a project "play new dependency-error"
  • Install sass module to play "play install sass"
  • Add the dependency to the dependencies.yml
  • Fetch dependencies "play deps --sync"
  • Delete the sass installation from play "rm -r $PLAY_HOME/modules/sass-1.0"
  • Fetch dependencies again "play deps --sync" -> This leads to missing artifact error

Dirty fix:

  • Remove the ivy caches rm ~/.ivy2/ -r
  • "play deps --sync" works fine now

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.