User Story #128 (closed)
Opened 13 years ago
Closed 5 years ago
Get rid of omero.class in build
| Reported by: | sfrank | Owned by: | jamoore |
|---|---|---|---|
| Priority: | minor | Milestone: | 5.0.5 |
| Component: | Deployment | Keywords: | build, ant, omero.class |
| Cc: | Story Points: | n.a. | |
| Sprint: | n.a. | Importance: | n.a. |
| Total Remaining Time: | n.a. | Estimated Remaining Time: | n.a. |
Description
omero.class contains hardcoded references to libraries and adds another layer of configuration on top/underneath of ant - the jars referenced here should be moved into the regular build to remove the number of moving parts in the system and get back to a simple ant fulllbuild.
Change History (2)
comment:1 Changed 13 years ago by jmoore
- Milestone set to Unscheduled
- Summary changed from build:: Get rid of omero.class to Get rid of omero.class in build
comment:2 Changed 5 years ago by jamoore
- Milestone changed from Unscheduled to 5.0.5
- Resolution set to wontfix
- Status changed from new to closed
Keeping the class for easily launching without installing ant, but using ant does work again.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
The paths certainly need to get fixed, but there are several advantages of omero.class:
I realize that it complicates things for people who want to know what's going on, and we should continue to discuss, but for the people who don't want to know what's going on, omero.class makes things simpler, and we can more likely guarantee out-of-the-box success. (Windows users being an obvious exception. :) )
Other opinions?