#1246 ✓resolved
Ealden Escanan

play idealize in 1.2.4RC2 should also set ProjectRootManager

Reported by Ealden Escanan | November 13th, 2011 @ 01:18 PM | in 1.3 (closed)

Framework version:

  • Play 1.2.4 RC2
  • MacOS X 10.7.2

Reproduction steps:

  • Run play idealize
  • Load IPR into IDEA

Details:

I'm not sure if I should have added this to #1068. But since that was closed already I created a new one.

The IPR generated only sets the IML and not other settings. Once setting group is ProjectRootManager, which means that the 'Project SDK', 'Project language level', and 'Project compiler output' are not set. Attached is a screenshot with this settings window - I'm using IDEA 10.5.2 Ultimate.

The valid XML from Play 1.2.3 looks like this:

<component name="ProjectRootManager" version="2" languageLevel="JDK_1_6" assert-keyword="true" jdk-15="true" project-jdk-name="1.6" project-jdk-type="JavaSDK">
    <output url="file://$PROJECT_DIR$/out" />
</component>

I think output URL for 'Project compiler output' can be set safely, but languageLevel and project-jdk-name is dependent on each system. In MacOS X I only have 1.6, so I set this to 1.6 with 6.0 language level. I'm not sure if it is possible to determine this with the Python script.

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.

Attachments

Referenced by

Pages