Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-28242

Missing class hudson.scm.cvs.Messages

    Details

    • Similar Issues:

      Description

      hudson.scm.CvsModule has an import line and requires the following class but it is not included in the source provided
      {{import hudson.scm.cvs.Messages; }}

      The class is also used in lines such as :
      {{ return FormValidation.error(hudson.scm.cvs.Messages.CVSSCM_MissingRemoteName());}}

        Attachments

          Activity

          Hide
          albers Harald Albers added a comment - - edited

          hudson.scm.cvs.Messages is generated from properties files and therefore not included in the sources.
          mvn generate-sources will place it in target/generated-sources/localizer.
          If your IDE cannot spot it, you will have to manually add this directory it to the classpath.

          I verified that the plugin version that currently ships with Jenkins actually contains the class file.

          Show
          albers Harald Albers added a comment - - edited hudson.scm.cvs.Messages is generated from properties files and therefore not included in the sources. mvn generate-sources will place it in target/generated-sources/localizer . If your IDE cannot spot it, you will have to manually add this directory it to the classpath. I verified that the plugin version that currently ships with Jenkins actually contains the class file.
          Hide
          danielbeck Daniel Beck added a comment -

          Looks like Not A Defect to me. My guess is this only affects IDEs that cannot handle Maven. Harald WDYT?

          Show
          danielbeck Daniel Beck added a comment - Looks like Not A Defect to me. My guess is this only affects IDEs that cannot handle Maven. Harald WDYT?
          Hide
          albers Harald Albers added a comment -

          @Daniel yes, definitely an IDE issue.

          The Eclipse story is: target/generated-sources/localizer is only recognized as a classpath member if you have m2e connector for build-helper-maven-plugin installed and a plugin adds this path as a source via build-helper-maven-plugin. For other plugins you have to add the directory manually.

          I suggest we wait a little longer to give the reporter time to respond before closing the issue.

          Show
          albers Harald Albers added a comment - @Daniel yes, definitely an IDE issue. The Eclipse story is: target/generated-sources/localizer is only recognized as a classpath member if you have m2e connector for build-helper-maven-plugin installed and a plugin adds this path as a source via build-helper-maven-plugin . For other plugins you have to add the directory manually. I suggest we wait a little longer to give the reporter time to respond before closing the issue.
          Hide
          simons_orw Simon Springall added a comment -

          Thanks very much for the fast answer! I can't test right now, but I'm sure this will solve it.
          I am using IntelliJ version 12 and built using maven plugin in IntelliJ but perhaps maven is not configured correctly.

          Show
          simons_orw Simon Springall added a comment - Thanks very much for the fast answer! I can't test right now, but I'm sure this will solve it. I am using IntelliJ version 12 and built using maven plugin in IntelliJ but perhaps maven is not configured correctly.
          Hide
          albers Harald Albers added a comment -

          Closing because it is an IDE configuration issue.

          Show
          albers Harald Albers added a comment - Closing because it is an IDE configuration issue.

            People

            • Assignee:
              albers Harald Albers
              Reporter:
              simons_orw Simon Springall
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: