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

Feature/315 configure global outputfolder #316

Closed
wants to merge 2 commits into
base: version-3.2-release-branch
from

Conversation

Projects
None yet
3 participants
@alexnederlof
Member

alexnederlof commented Jul 16, 2013

Set the output folder in the crawljax configuration for all plugins

Fixes #315

@amesbah amesbah closed this Jul 16, 2013

@jeremyhewett

This comment has been minimized.

Show comment
Hide comment
@jeremyhewett

jeremyhewett Jul 23, 2013

Contributor

Hi Alex, does this mean all plugins will output to the same folder? For the web ui I think it makes more sense to give each plugin its own output folder but then that doesn't really fit this pattern anymore. For now I've changed the web-ui-plugin-tests branch back to passing a HostInterface to the plugin which specifies both the output directory and the parameters. We might need to discuss how to merge these two ideas.

Contributor

jeremyhewett commented on ab9390f Jul 23, 2013

Hi Alex, does this mean all plugins will output to the same folder? For the web ui I think it makes more sense to give each plugin its own output folder but then that doesn't really fit this pattern anymore. For now I've changed the web-ui-plugin-tests branch back to passing a HostInterface to the plugin which specifies both the output directory and the parameters. We might need to discuss how to merge these two ideas.

This comment has been minimized.

Show comment
Hide comment
@alexnederlof

alexnederlof Jul 24, 2013

Member

No my idea is to give a general output folder. In that folder, all other plugins can claim their own folder. The advantage here is that the user can specify in one place where he wants everything to go.

Member

alexnederlof replied Jul 24, 2013

No my idea is to give a general output folder. In that folder, all other plugins can claim their own folder. The advantage here is that the user can specify in one place where he wants everything to go.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment