Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Add a distributionManagement section (or overwrite the existing section). As this is an internal release it will go to your internal_plugins repository, if you forget to do this you will be attempting to release into the maven repositories which you don't have access to.
    Code Block
    languagexml
      ...
      <distributionManagement>
        <repository>
          <id>internal._plugins</id>
          <name>Internal Plugin Repository</name>
          <url>
            scp://NUCLEUS/path/to/maven2_repositories/internal_plugins
          </url>
        </repository>
      </distributionManagement>  
    

...

Each dependency and parent pom that is promoted to INTERNAL needs to be deployed to your internal repository via mvn deploy, you must do this depth first so that the pom you are deploying has no SNAPTSHOT dependencies.

Once all depeencies dependencies and parents have been deployed you can now deploy your changes to the plugin to your internal repository via mvn deploy.