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

Pax runner folder not cleaned one pax:provision [PAXCONSTRUCT-121] #133

Open
ops4j-issues opened this issue Aug 20, 2009 · 1 comment
Open
Labels

Comments

@ops4j-issues
Copy link

Anders Storsveen created PAXCONSTRUCT-121

Sometimes I have to manually remove the runner folder, especially if I have updated some dependencies that is pulled in.


Votes: 0, Watches: 0

@ops4j-issues
Copy link
Author

Stuart McCulloch commented

pax:provision invokes pax-runner with the --overwriteUserBundles option, which means any user bundles are automatically updated, so you shouldn't really need to remove the whole runner folder (also removing the whole folder would potentially cause all the system bundles to be re-downloaded).

Can you provide more information about your setup and describe what exactly happens if you don't manually remove the runner folder?

Note you can use the pax:clean maven goal to remove the runner folder if its really necessary see also PAXCONSTRUCT-115

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

No branches or pull requests

1 participant