← Back to issue list

Use craft-application lifecycle commands

View original Github issue

Metadata

Project
charmcraft
Number
#1532
Type
issue
State
closed
Author
lengau
Labels
Created
Updated
Closed

Current evaluation

Closed without a documented fix or merge. Likely abandoned or superseded by upstream craft-application updates, as no resolution details were provided in the issue thread.

Suggested action:

No scores available.

Issue body

### What needs to get done Except for `pack` and possibly `clean` (for backwards compatibility), we don't need to define our own lifecycle commands. The commands we do need to modify for charmcraft should, if possible, use the lifecycle commands' extensible interface. ### Why it needs to get done These commands are cruft and will begin to diverge from other craft applications.

Evaluation history

Date Model Scores Action Summary
qwen3.6-35b-a3b-mtp-q6 Closed without a documented fix or merge. Likely abandoned or superseded by upstream craft-application updates, as no resolution details were provided in the issue thread.
qwen/qwen3.6-35b-a3b Closed and abandoned. The proposal to replace custom lifecycle commands with craft-application equivalents was logged as Jira ticket CRAFT-2512 but never implemented or merged.
qwen/qwen3.6-35b-a3b Closed and deferred to internal tracking ticket CRAFT-2512. The task to replace custom lifecycle commands with craft-application equivalents, excluding pack and clean, remains unimplemented.
qwen/qwen3.6-35b-a3b Closed without implementation. The proposal to replace custom lifecycle commands with craft-application equivalents was abandoned or deferred, with no resolution or merge details provided.
qwen3.6-35b-a3b-mtp-q6 Closed and abandoned on GitHub. An automated bot migrated the request to internal Jira ticket CRAFT-2512. No code changes, merges, or further repository discussion occurred.
qwen3.6-35b-a3b-mtp-q6 Closed and superseded by an automatic sync to internal Jira ticket CRAFT-2512. No GitHub resolution, merge, or code changes were implemented.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#4742 Migrate commands to craft-application command snapcraft closed Closed without implementation. The commands were not migrated to craft-application, and no resolution details were provided. The issue appears abandoned or superseded.
81%
#1412 Use upstream craft-application lifecycle commands charmcraft closed Closed without implementation. The proposal to replace custom lifecycle commands with upstream craft-application equivalents and deprecate --base-index was abandoned or superseded by upstream updates. No related pull requests were created.
79%
#359 Migrate remaining lifecycle commands to craft-application rockcraft closed Closed as abandoned. No pull requests or comments were created, indicating the migration of remaining lifecycle commands was not completed and superseded by later development.
78%
#360 Migrate non-lifecycle commands to craft-application rockcraft closed Closed without a documented resolution. Implementation discussion noted changing the InitCommand superclass from BaseCommand to AppCommand within craft-application. The migration remains unimplemented and effectively abandoned.
78%
#4468 feature/craft-application: migrate version command snapcraft closed Closed without comments or linked resolution. The version command migration to craft-application appears abandoned or superseded by subsequent refactoring. No merge or fix details were recorded.
77%
#271 Craft-application reading craft-archives version craft-application closed Closed without resolution or fix. The report highlighted a version fallback bug but received no developer response beyond a Jira sync notification. The issue appears abandoned due to prolonged inactivity.
75%
#1153 Move the init command to craft-application charmcraft closed Closed without implementation. The migration of the init command to craft-application was abandoned or superseded, with no comments or merge details recorded.
74%