Versions Compared


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


  • downloading the latest source code from the trunk of a plugin
  • building the plugin
  • creating JIRA issues
  • modifying the plugin source code
  • deploying the plugin to an internal repository for use within your company
  • creating patches and attaching to JIRA
  • applying patches retrieved from JIRA

Known Issues

Single Artifact can not be available on multiple repositories

See, a single artifact can not be available on multiple repositories.


The previous workaround was to suffix "-i" to the artifactId, which is a broken workaround as this makes a duplicate copy of the artifact with a different name and will cause two potentially incompatible libraries to be on the classpath. If you see any references to this workaround in this document please make corrections.

Long file names on Windows

Previous versions of this document recommended a naming convention like -INTERNAL-r<svn rev>-p<Patch Num>-p<Patch Num>... The problem is that this causes very long file names on windows and then when you run maven the java will fail with a general protection fault. Please ensure you dont use long version values.

Downloading the latest source code from the trunk of a plugin


  • Set the version to be -INTERNAL-r<svn version>-p<num>-p<num> instead of -SNAPSHOT. See Better Builds with Maven (June 2006) page 61 for an explanation of how version numbers are compared. e.g. if the version is 2.2-SNAPSHOT and the subversion repository when you checked out the plugin was at r485327 then set it to 2.2-INTERNAL-r485327. If you are have applied any patches then also include the patch numbers in the version id, e.g. the patches for bugs MECLIPSE-206 and MECLIPSE-31 have been applied then use -INTERNAL-r485327-pMECLIPSE-206-pMECLIPSE-31. Note: When the plugin is officially released as 2.2 the released version will be considered newer than your patched version and supersede supercede it. You will need to check if your patches have been applied in the release and if not then follow these instructions again. By including the patch numbers in the version id it will help you identify immediately what needs to get checked.