Difference between revisions of "IAM Moving from Google Code"

From Eclipsepedia

Jump to: navigation, search
(comment on search.core)
Line 7: Line 7:
 
** org.devzuz.q.maven to org.eclipse.iam.core in the org.devzuz.q.maven.core plugin
 
** org.devzuz.q.maven to org.eclipse.iam.core in the org.devzuz.q.maven.core plugin
 
** org.eclipse.iam.search or org.eclipse.iam.search.core ?
 
** org.eclipse.iam.search or org.eclipse.iam.search.core ?
 +
*** ''amuino'': This is interesting, but I don't think it is needed as part of the move. In the same line, buckminster integration needs to be split in `core` and `ui`. ← we need another way of tracking this (bugs?).
  
 
* Support legacy naming
 
* Support legacy naming

Revision as of 14:50, 5 November 2008

< To: IAM

Tasks to do

  • Rename in packages/files
    • org.devzuz.q.maven to org.eclipse.iam
    • org.devzuz.q.maven to org.eclipse.iam.core in the org.devzuz.q.maven.core plugin
    • org.eclipse.iam.search or org.eclipse.iam.search.core ?
      • amuino: This is interesting, but I don't think it is needed as part of the move. In the same line, buckminster integration needs to be split in `core` and `ui`. ← we need another way of tracking this (bugs?).
  • Support legacy naming
    • classpath container
    • nature
    • builder
    • markers
    • what else?
  • Make uniform use of the maven conventions (some projects have source code on src, some on src/main/java)
  • Rename the plug-in "org.eclipse.iam.maven.dependencyviewer" to "org.eclipse.iam.maven.dependency.viewer" (i.e. split that last segment in two)
    • This is to match the dependency.analisys plug-in. It makes sense to have them sharing the same naming scheme.
  • Related to the previous one, move the org.devzuz.q.maven.dependency.* in the dependency viewer to org.eclipse.iam.dependency.viewer (insert the "viewer" segment that is currently missing).