Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #868 (closed)

Opened 12 years ago

Closed 10 years ago

Simplify blitz build experience

Reported by: jamoore Owned by: jamoore
Priority: minor Milestone: OMERO-Beta4
Component: Deployment Version: 3.0-M1
Keywords: build Cc: dzmacdonald
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.

Description

Currently, building blitz is less than simple. It was originally designed to only be run by those who really wanted it. Now that more people are intereseted, the barrier to entry must be lowered.

  • ant nomake noear dist
  • chmod a+x dist/blitz
  • ...

Change History (3)

comment:1 Changed 11 years ago by jmoore

  • Type changed from User Story to Task

comment:2 Changed 11 years ago by jmoore

Combining other tickets:

  • #639 Currently, the ice code generation often triggers full compile cycles in both Java and C++, making development very slow. See also #629.
  • #869 Currently, after building, another call to build will take a significant amount of time, not the least of which is parsing Ivy files and preparing the classpath. One simple optimization would be to wait for ivy configuration until a compile is needed.

comment:3 Changed 10 years ago by jmoore

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

"ant" is now sufficient to have a working blitz under dist/. Seems sufficient.

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.75039 sec.)

© 2000-2014 University of Dundee & Open Microscopy Environment. Creative Commons Attribution 3.0 Unported License
OME source code is available under the GNU General public license or through commercial license from Glencoe Software

We're Hiring!