#949 ✓invalid
Zenklys

Keyword tags for subversion

Reported by Zenklys | June 29th, 2011 @ 11:25 PM | in 1.3 (closed)

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.

Framework version: All
Platform you're using: All

Reproduction steps:

Details:

The folder "tags" is detected as the "tag" folder of Subversion Source Control Management.
Using eclipse, while commiting changes in tags folder, a message prompt appears because Eclipse (or should I say Subclipse) thinks, you're trying to modify the tag of the repository.

One of the solutions would be a renamal of the folder to something else not being a keyword. The other way round, I'm also filling a ticket for the Eclipse SVN plugin, Subclipse as it should not be detecting folder lower than root named tags.

Comments and changes to this ticket

  • Nicolas Leroux

    Nicolas Leroux October 28th, 2011 @ 08:06 PM

    • Assigned user set to “Nicolas Leroux”
    • State changed from “new” to “invalid”
    • Milestone set to 1.3
    • Milestone order changed from “655” to “0”

    Well, I don't think it is really a play issue there.

  • Allenwood

    Allenwood September 11th, 2018 @ 05:00 AM

    Using eclipse, while commiting changes in tags folder, a message prompt appears because Eclipse (or should I say Subclipse) thinks, you're trying to modify the tag of the repository. PEGACPBA73V1 dumps

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