Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review concept of optional dependencies #53

Open
FRosner opened this issue Aug 14, 2014 · 1 comment
Open

Review concept of optional dependencies #53

FRosner opened this issue Aug 14, 2014 · 1 comment
Milestone

Comments

@FRosner
Copy link
Collaborator

FRosner commented Aug 14, 2014

Problem

Currently, optional dependencies only influence the way a command graph is built from an XML catalog. If an optional dependency is missing in the catalog, the parsing will continue.

We might want to remove this to require catalogs that are properly set up. It is also considerable to rethink the influence of failing optional dependencies during execution. Maybe we don't need to abort the execution in that case.

@FRosner FRosner added this to the 2.0 milestone Aug 14, 2014
@FRosner
Copy link
Collaborator Author

FRosner commented Aug 14, 2014

@Husterknupp please include a comment with a reference to this ticket in the place you add this exceptional parsing (CommandMananger.of()) or something.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant