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

[Fixed] Use relative path to working directory for maven wrapper command #890

Conversation

jbmgrtn
Copy link
Contributor

@jbmgrtn jbmgrtn commented Mar 9, 2022

Resolves #889

@pivotal-cla
Copy link

@jbmgrtn Please sign the Contributor License Agreement!

Click here to manually synchronize the status of this Pull Request.

See the FAQ for frequently asked questions.

@cf-gitbot
Copy link
Collaborator

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

@jbmgrtn
Copy link
Contributor Author

jbmgrtn commented Mar 9, 2022

Do I have to sign the CLA?
Is this considered as being an obvious fix?

@jbmgrtn
Copy link
Contributor Author

jbmgrtn commented Mar 9, 2022

Please be indulgent, I don't know Ruby nor the best practices and code guidelines on your project.
Anyway, this project is well organized and written so it was not that hard on my side to find where was the problem and came up with a fix.

@xtreme-shane-lattanzio
Copy link
Contributor

Hey @jbmgrtn and thanks for the PR! This looks good to me. As for ruby code cleanup, we actually run rubocop to do that. You can run rubocop in the root directory to see whats wrong or rubocop -a to have the issues auto fixed. Looking at the pipeline, the only issue is

Offenses:

lib/license_finder/package_managers/maven.rb:37:81: C: [Correctable] Style/Semicolon: Do not use semicolons to terminate expressions.
      wrapper = File.join(project_path, Platform.windows? ? 'mvnw.cmd' : 'mvnw');

I think the fix is trivial enough but to be safe, is it an issue to sign the CLA? It is basically just saying you do not own the change and are donating it to the project.

Once we have the pipeline green I'll merge this in!

1 similar comment
@xtreme-shane-lattanzio
Copy link
Contributor

Hey @jbmgrtn and thanks for the PR! This looks good to me. As for ruby code cleanup, we actually run rubocop to do that. You can run rubocop in the root directory to see whats wrong or rubocop -a to have the issues auto fixed. Looking at the pipeline, the only issue is

Offenses:

lib/license_finder/package_managers/maven.rb:37:81: C: [Correctable] Style/Semicolon: Do not use semicolons to terminate expressions.
      wrapper = File.join(project_path, Platform.windows? ? 'mvnw.cmd' : 'mvnw');

I think the fix is trivial enough but to be safe, is it an issue to sign the CLA? It is basically just saying you do not own the change and are donating it to the project.

Once we have the pipeline green I'll merge this in!

@jbmgrtn jbmgrtn force-pushed the fix/use_relative_path_to_working_directory_for_maven_wrapper_command branch from 9c64805 to 89a9253 Compare March 11, 2022 10:22
@pivotal-cla
Copy link

@jbmgrtn Thank you for signing the Contributor License Agreement!

@xtreme-shane-lattanzio xtreme-shane-lattanzio merged commit 298a733 into pivotal:master Mar 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Fail to detect Maven when using Maven Wrapper with aggregate paths on a Maven project in a subdirectory
4 participants