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

Branchout mvn -f pom.xml prevents pom-less mvn operations that need settings.xml from being conveniently run #84

Open
fredcooke opened this issue Aug 30, 2021 · 3 comments
Assignees

Comments

@fredcooke
Copy link
Collaborator

For example, mvn deploy:deploy-file does not require a pom.xml locally but does need settings depending upon to where you're trying to deploy.

Given that pom.xml is the default project object model and is used in the 5 9s cases in almost every maven project ever, why can we not rely on the default to use pom.xml instead of calling it explicitly when there are use cases that don't make sense to require it for that then force you to either manually run the command outside branchout (defeating the purpose) or create a fake pom with just parent and basics just to satisfy the requirement and let it run okay.

I never understood this, however it didn't cause me any trouble until recently, so I never complained about it (mentioned it a year or so back, but that's it).

Are there any valid reasons why we can't simply stop doing that?

@stickycode
Copy link
Member

stickycode commented Aug 30, 2021 via email

@fredcooke
Copy link
Collaborator Author

Okay, I see why it was added and also how to remove it without breaking that. I'll have a crack at some point. Cheers.

@fredcooke
Copy link
Collaborator Author

Sees like you never got the #82 build fixed though?

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

2 participants