title: How do I get IntelliJ to recognise resource bundle when compiling?
body: <p>Ok, first up I am almost completely unfamiliar with Java and Java tooling.</p>
  
  <p>I am attempting to contribute a bugfix to a Jenkins <a href="https://github.com/jenkinsci/copyartifact-plugin" rel="nofollow">plugin</a>.  Code-wise the fix is simple, my problem is in trying to compile the project and run the tests locally.</p>
  
  <p>I have installed IntelliJ IDEA 15CE and started a new project, pointing it to my local clone of the plugin repo.</p>
  
  <p>It has gone away and 'downloaded the internet' in terms of Maven dependencies. Mostly everything looks ok. What I want to do is to run the tests...</p>
  
  <p>If I right-click at the root of the project and select 'Run All Tests' I get the error:</p>
  
  <pre><code>Error:(115, 29) java: cannot find symbol
    symbol:   variable Messages
    location: class hudson.plugins.copyartifact.BuildSelector
  </code></pre>
  
  <p>The source of this error is a line:</p>
  
  <pre><code> console.println(Messages.CopyArtifact_MissingSrcArtifacts(srcDir));
  </code></pre>
  
  <p><a href="https://github.com/jenkinsci/copyartifact-plugin/blob/master/src/main/java/hudson/plugins/copyartifact/BuildSelector.java#L115" rel="nofollow">https://github.com/jenkinsci/copyartifact-plugin/blob/master/src/main/java/hudson/plugins/copyartifact/BuildSelector.java#L115</a></p>
  
  <p>As far as I can tell the <code>Messages</code> symbol should resolve to this properties file:<br>
  <a href="https://github.com/jenkinsci/copyartifact-plugin/blob/master/src/main/resources/hudson/plugins/copyartifact/Messages.properties" rel="nofollow">https://github.com/jenkinsci/copyartifact-plugin/blob/master/src/main/resources/hudson/plugins/copyartifact/Messages.properties</a><br>
  ...which IDEA recognises as a 'Resource Bundle' in the project tree view.</p>
  
  <p>But it doesn't seem to recognise it when compiling the project.</p>
  
  <p>I have no idea where to start fixing this. The tests run fine if I push a commit to a pull request on GitHub and let the cloudbees.com Jenkins server run them, but I'd like to be able to test stuff locally first.</p>