Ticket #161 (closed defect: wontfix)

Opened 9 years ago

Last modified 9 years ago

Maven: better Eclipse project metadata

Reported by: curtis Owned by: curtis
Priority: minor Milestone: biweekly-2011: Feb-14 to Feb-25
Component: Build System Version:
Severity: serious Keywords:
Cc: Blocked By:
Blocking:

Description (last modified by curtis) (diff)

We currently have one Eclipse project per component committed to the SVN repository. With Maven it is better not to do this, and instead allow people to use the m2eclipse plugin, or generate their own Eclipse projects with the eclipse:eclipse target. However, our project POMs should document the desired Eclipse configuration where applicable; in particular, project forks should suppress all Eclipse warnings.

Change History

comment:1 Changed 9 years ago by curtis

  • Description modified (diff)

comment:2 Changed 9 years ago by curtis

See  this page for documentation on the eclipse plugin's configuration options.

comment:3 Changed 9 years ago by curtis

  • Component changed from other to build

comment:4 Changed 9 years ago by curtis

  • Milestone changed from biweekly-2010: Sep-07 to Sep-17 to biweekly-2011: Jan-03 to Jan-14

comment:5 Changed 9 years ago by curtis

  • Status changed from new to closed
  • Resolution set to wontfix

It would be nice to eventually distribute some shared Eclipse configuration. But it is not a high priority. Further, the OME team has opted to not use Maven for Bio-Formats, which is where all the project forks currently live, so this task is now largely irrelevant.

Note: See TracTickets for help on using tickets.