Our Rate of Change
JWare/AntXtras SAM is refactored and extended as the need arises. In particular, as new versions of Ant and AntXtras Foundation are released, SAM will change to remain up-to-date and to take advantage of new capabilities where feasible and worth the effort. We will always update SAM to fix critical bugs or packaging issues as soon as possible; however, because SAM is still making its way to its 1.0 release, all bug-fixes are rolled into the next point-release with no branching into maintenance releases (ie. we would not create an SAM v0.2.1 for bug-fixes, instead changes and bug-fixes would appear in v0.3).
Below we describe our (near) future plans generally. We estimate there will be three beta releases of SAM 0.1 before the final release; see details below. You can use the AntXtras Feature Requests Tracker to submit your own enhancement suggestions. We often reschedule features to the next major release if we decide there are enough new concepts and/or components for the release under construction. Items rescheduled in this manner have not fallen behind schedule per se, they’ve just been reprioritized with regards to the current release.
Planned SAM Extensions (Icon Key)
00. General
- Provide detailed examples of catalogs spanning multiple projects; in particular, a driver/client project use case. [???]
- Provide “one-off” URL handlers for resource: and cvs: as demonstration vehicles of base URLs. [???]
01. Build Iteration and Fixture Support
- Need to support classpath and classpathref parameters inside various file and/or resources loading components like <fixturedef> and <add-artifactdefs>. Would be nice if both classpaths and filepaths where supported. [0.1]
02. Antlib Library Management Service (ALMS)
- Ensure can download ARMs through base urls indicating http, https, and ftp sources. Also verify that basic authentication mechanisms work as expected. [0.2]
- Ensure there is straightforward way to map from a version-based repository where a single, maintained archive contains multiple ARM packages. Who is responsible for expanding the distributed archive into the ARM packages (which ALMS “downloads” to its working area)? [0.2]
- Implement some form of inheritance for module filters. [0.2]
- Extend base urls to handle 'mustexist' parameter at resolution time in particular <add-baseurls> should check this stuff! [???]
03. Artifact Definition Framework
- Add support for a "loctype" [=url|path] parameter for all chkdir task methods. [0.1]
- Enhance <artifactdef> to ensure it does not contain circular setup steps. [0.2]
- Enhance <parameter> to support the allowoverrides option. [0.2]
- Clarify difference between artifactdef presetdefs and the artifactdef value URI. [0.1rc]
- Need some way to configure an artifactdef catalog's cache policy. [0.2]
- How does the artifactdef's catalog's name get reflected in the generated presetdefs? Ideally to same-named artifactdefs from different catalogs should be somehow different(!). [???]
- Figure out if (and then how) artifactdef catalogs should be cloneable. [???]
04. Event Monitoring and Artifact Announcement
05. Support for other JWare/AntXtras-based Projects
06. In Need of Future JRE, Ant, and/or newer Third-Party Library
Status Icons Key
- Item is planned for some future iteration.
- Item design and implementation has started.
- Item has been completed and released to some milestone iteration.
- Item has fallen behind schedule (missed milestone).
- Item has been rescheduled to next major release.
- Item has fallen seriously behind schedule an is in danger of reverting to simply “planned” for a future iteration.
- Item has been cancelled permanently. (This status is shown for one full point release cycle; it is then removed along with item.)
|
