Versions Compared

Old Version 16

changes.mady.by.user Marshall Schor

Saved on

compared with

New Version 17

changes.mady.by.user Marshall Schor

Saved on

Key

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

...

  • separate "aggregate" and "super" poms
    • for super poms - put in containing super-poms project
    • for aggregate poms - just leave in flat organization - tools should now support this
  • scm element in pom needs to point to where this pom is, in the svn tree (to make releasing conventional)
  • change relative links in pom structure to assume the layout that m2eclipse would create
    • m2eclipse, when you say to Eclipse->import, say uimaj/trunk into workspace, checks out trunk as a uniquely name folder in the workspace, and then "imports" from there. If another trunk is imported, say, sandbox/trunk, into the workspace, then m2eclipse checks out that trunk under another uniquely named folder in the workspace.
    • Therefore, our convention for locating relative things (if we don't get them using repository dependencies) will be
      No Format
      
   arbitrary-top-working-copy-dir
      substitute-name-for-trunk  (maybe generated by m2eclipse)
         project1
         project2
         ...