#1141 new
Cory Crowe

DuplicateMemberException when using application-build.xml targets

Reported by Cory Crowe | September 29th, 2011 @ 04:48 PM

Framework version: 1.2.3
Platform you're using: Mac OS X 10.6.8

Reproduction steps:

> unzip play-1.2.3.zip -d play
> ~/play/play-1.2.3/play new test-app
> export PLAY_PATH=~/play/play-1.2.3/
> cd test-app
> ~/play/play-1.2.3/play antify
> ant test

hit url http://localhost:9000/@tests
throws exception

to fix:

> rm $PLAY_PATH/framework/play.jar
> ant test

hit url http://localhost:9000/@tests

When running ant test from an antify build.xml we get a runtime error as follows:

Oops: UnexpectedException
An unexpected error occured caused by exception UnexpectedException: While applying class play.classloading.enhancers.LocalvariablesNamesEnhancer on controllers.TestRunner

play.exceptions.UnexpectedException: While applying play.CorePlugin@7461373f on controllers.TestRunner
    at play.plugins.PluginCollection.enhance(PluginCollection.java:454)
    at play.classloading.ApplicationClasses$ApplicationClass.enhance(ApplicationClasses.java:208)
    at play.classloading.ApplicationClassloader.loadApplicationClass(ApplicationClassloader.java:157)
    at play.classloading.ApplicationClassloader.getAllClasses(ApplicationClassloader.java:417)
    at play.Play.start(Play.java:485)
    at play.Play.detectChanges(Play.java:610)
    at play.Invoker$Invocation.init(Invoker.java:186)
    at Invocation.HTTP Request(Play!)
Caused by: play.exceptions.UnexpectedException: While applying class play.classloading.enhancers.LocalvariablesNamesEnhancer on controllers.TestRunner
    at play.CorePlugin.enhance(CorePlugin.java:296)
    at play.plugins.PluginCollection.enhance(PluginCollection.java:451)
    ... 7 more
Caused by: javassist.bytecode.DuplicateMemberException: duplicate field: $index0
    at javassist.bytecode.ClassFile.testExistingField(ClassFile.java:529)
    at javassist.bytecode.ClassFile.addField(ClassFile.java:515)
    at javassist.CtClassType.addField(CtClassType.java:1164)
    at javassist.CtClass.addField(CtClass.java:878)
    at play.classloading.enhancers.LocalvariablesNamesEnhancer.enhanceThisClass(LocalvariablesNamesEnhancer.java:180)
    at play.CorePlugin.enhance(CorePlugin.java:293)
    ... 8 more

After examining the classpath we found that both ${play.path}/framework/play.jar and ${play.path}/framework/play-1.2.3.jar were being included. The exception stops after removing play.jar. Running play test using the play script only seems to include ${play.path}/framework/play-1.2.3.jar in the classpath. It looks like the culprit is the following code from ${play.path}/resources/application-build.xml:

<path id="play.classpath">
    <fileset dir="${play.path}/framework/lib">
        <include name="*.jar"/>
    <fileset dir="${play.path}/framework">
        <include name="*.jar"/> <!-- THIS LINE INCLUDE BOTH PLAY.JAR AND PLAY-1.2.3.JAR -->

if <include name="*.jar"/> only includes the play-.jar it should work.

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

Referenced by