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 #1602 (closed defect: fixed)

Opened 2012-12-11T14:01:04-06:00

Last modified 2013-01-09T09:53:13-06:00 does not deploy POMs

Reported by: curtis Owned by: dscho
Priority: major Milestone: imagej2-b7-ndim-data
Component: Build System Version:
Severity: serious Keywords:
Cc: Blocked By:
Blocking: #1608


Jenkins  deployed the 2.0.0-beta5 release for us, but that job uses, which skips POM deployment. However, we must deploy the POMs for our releases to be valid and usable.

For 2.0.0-beta5 I deployed the POMs manually (mvn deploy in strategic places) but it would be best to fix to do the right thing.

Change History

comment:1 Changed 2012-12-11T14:14:51-06:00 by curtis

This problem shed some light on the fact that the  ImageJ job was doing too much by doubling as our release job. It runs unit tests, does performance analysis, and triggers downstream builds  ImageJ-style and [ ImageJ-tutorials), none of which make sense when building the release.

So I created a new parameterized  ImageJ-release job just for that, which is stripped down. It also builds all the UIs (-P all), which the regular ImageJ job does not do, which kept artifacts like ij-ui-awt from ever being released.

I removed the branch parameter from the ImageJ job, since it is no longer necessary.

And I updated the `release-steps.txt` accordingly too.

Last edited 2012-12-11T14:15:24-06:00 by curtis

comment:2 Changed 2012-12-27T11:13:57-06:00 by curtis

  • Blocking 1608 added

comment:3 Changed 2012-12-27T11:14:14-06:00 by curtis

  • Milestone changed from imagej2-b6-legacy to imagej2-b7-ndim-data

comment:4 Changed 2013-01-09T09:53:13-06:00 by dscho

  • Status changed from new to closed
  • Resolution set to fixed
Last edited 2013-01-09T09:53:34-06:00 by dscho