GRECLIPSE
  1. GRECLIPSE
  2. GRECLIPSE-1200

maven: after a successful build, doing a mvn install fails with "The type package-info is already defined"

    Details

    • Type: Bug Bug
    • Status: Resolved Resolved
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 2.5.1Release
    • Fix Version/s: 2.5.2.Release
    • Component/s: Maven integration
    • Labels:
      None
    • Number of attachments :
      0

      Description

      when building a project that contains package-info.java files doing following command will fail compilation:

      mvn install //this will succeed
      mvn install //this will fail

      the workaround is always to do a mvn clean install

      the error you receive relates to the compiler thinking an existing package-info.java already exists.

      222. ERROR in C:\projects\kuali\KULRICE-5640\core\api\src\main\java\org\kuali\ri
      ce\core\api\util\package-info.java (at line 1)
      /*
      ^
      The type package-info is already defined

        Activity

        Hide
        Andrew Eisenberg added a comment -

        Thanks for following up. I am resolving this as fixed, but please re-open if this happens again.

        Show
        Andrew Eisenberg added a comment - Thanks for following up. I am resolving this as fixed, but please re-open if this happens again.
        Hide
        Travis added a comment -

        So does that mean it is fixed in trunk? I thought 2.5.1-1 was an older version that 2.5.1....

        Show
        Travis added a comment - So does that mean it is fixed in trunk? I thought 2.5.1-1 was an older version that 2.5.1....
        Hide
        Andrew Eisenberg added a comment -

        No, 2.5.1-1 is the next release after 2.5.1. Is that not considered a greater version in the maven world? I had assumed that the same rules would apply from the OSGi world, where 2.5.1 is less than 2.5.1.1.

        I am trying to find the maven documentation for version comparisons, but there is nothing that clearly states the rules. The closest I found is this, but even that is unclear about comparing these kinds of versions.
        http://mojo.codehaus.org/versions-maven-plugin/version-rules.html

        Well regardless when 2.5.2 comes out I will mark it as 2.5.2-01 just in case I need to put out other releases of the maven support between micro releases of Groovy-Eclipse.

        Show
        Andrew Eisenberg added a comment - No, 2.5.1-1 is the next release after 2.5.1. Is that not considered a greater version in the maven world? I had assumed that the same rules would apply from the OSGi world, where 2.5.1 is less than 2.5.1.1. I am trying to find the maven documentation for version comparisons, but there is nothing that clearly states the rules. The closest I found is this, but even that is unclear about comparing these kinds of versions. http://mojo.codehaus.org/versions-maven-plugin/version-rules.html Well regardless when 2.5.2 comes out I will mark it as 2.5.2-01 just in case I need to put out other releases of the maven support between micro releases of Groovy-Eclipse.
        Hide
        Travis added a comment -

        Yup you are right. See here for details: http://docs.codehaus.org/display/MAVEN/Versioning

        Show
        Travis added a comment - Yup you are right. See here for details: http://docs.codehaus.org/display/MAVEN/Versioning
        Hide
        Andrew Eisenberg added a comment -

        Still, I think it is better to be more explicit with version names and the next release will be 2.5.2-01.

        Show
        Andrew Eisenberg added a comment - Still, I think it is better to be more explicit with version names and the next release will be 2.5.2-01.

          People

          • Assignee:
            Andrew Eisenberg
            Reporter:
            Travis
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: