GMaven (OLD... DO NOT USE)
  1. GMaven (OLD... DO NOT USE)
  2. MGROOVY-164

jvm enforcer too strict + shitty plugin not found

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.0-rc-4
    • Fix Version/s: 1.0-rc-4
    • Component/s: None
    • Labels:
      None
    • Environment:
      linux
    • Number of attachments :
      0

      Description

      I checked out the source today so I could fix MGROOVY-144 and got this:

      [INFO] [enforcer:enforce

      {execution: default}

      ]
      [WARNING] Rule 0: org.apache.maven.plugin.enforcer.RequireJavaVersion failed with message: Detected JDK Version: 1.6.0-3 is not in the allowed range [1.4,1.6).

      Commenting out the enforcer in the pom.xml allowed me to build up until ...

      Project ID: org.codehaus.mojo:shitty-maven-plugin

      Reason: POM 'org.codehaus.mojo:shitty-maven-plugin' not found in repository: Unable to download the artifact from any repository

      org.codehaus.mojo:shitty-maven-plugin:pom:1.0-alpha-4-SNAPSHOT

      from the specified remote repositories:
      codehaus.org (http://snapshots.repository.codehaus.org),
      central (http://repo1.maven.org/maven2)
      for project org.codehaus.mojo:shitty-maven-plugin

      From the shitty site, seems like the latest version is 1.0-alpha-2-SNAPSHOT. Changing the pom.xml to this worked:

      <plugin>
      <groupId>org.codehaus.mojo</groupId>
      <artifactId>shitty-maven-plugin</artifactId>
      <version>1.0-alpha-2-SNAPSHOT</version>
      </plugin>

      Cool project btw

        Activity

        Hide
        Jason Dillon added a comment -

        I've moved back to the latest shitty release, and you can use -Denforcer.skip=true to bypass the check.

        Show
        Jason Dillon added a comment - I've moved back to the latest shitty release, and you can use -Denforcer.skip=true to bypass the check.
        Hide
        Brian Fox added a comment -

        FWIW, the enforcer is not choking on the -3 part, but is enforcing the rule that says 1.4 >=x < 1.6 so he's really saying 1.6 is not allowed (not sure why)

        Show
        Brian Fox added a comment - FWIW, the enforcer is not choking on the -3 part, but is enforcing the rule that says 1.4 >=x < 1.6 so he's really saying 1.6 is not allowed (not sure why)
        Hide
        Jason Dillon added a comment -

        Right, I have not done much work with 1.6 so I've no idea how that builds, so I limit the build to 1.4 && 1.5.

        Show
        Jason Dillon added a comment - Right, I have not done much work with 1.6 so I've no idea how that builds, so I limit the build to 1.4 && 1.5.

          People

          • Assignee:
            Jason Dillon
            Reporter:
            robert lazarski
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: