NOTICE! This is a static HTML version of a legacy ImageJ Trac ticket.

The ImageJ project now uses GitHub Issues for issue tracking.

Please file all new issues there.

Ticket #1350 (closed defect: fixed)

Opened 2012-07-19T21:54:40-05:00

Last modified 2012-07-20T13:30:10-05:00

Force m2e to respect our buildnumber settings

Reported by: dscho Owned by: dscho
Priority: major Milestone: imagej2-b4-plugins
Component: Other Version:
Severity: serious Keywords: m2e eclipse
Cc: Blocked By:
Blocking: #1348


At some stage, the Implementation-Build: tag in the manifests of our .jar files was lost.

Change History

comment:1 Changed 2012-07-19T21:56:15-05:00 by dscho

I tracked it down to Eclipse's m2e not executing the buildnumber plugin anymore. They consider it a bugfix. I forced the behavior back to the old one (IIUC it worked with m2e 0.12 but was broken with m2e 1.0) by adding a life cycle mapping to the top-level .pom.

However, I think this improvement should go into scijava, but I will not make that decision alone.

comment:2 Changed 2012-07-20T13:30:10-05:00 by dscho

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

Fixed in 4d1d0afe2da25d207c2448a6294c37dd580acad0. (Corresponding commit in scijava-common:

Last edited 2012-07-20T13:38:09-05:00 by dscho