-
Notifications
You must be signed in to change notification settings - Fork 751
fix(amazonq): setMaven correctly #6384
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
Conversation
|
| await setMaven() | ||
| const versionInfo = await getVersionData() | ||
| const mavenVersionInfoMessage = `${versionInfo[0]} (${transformByQState.getMavenName()})` | ||
| telemetry.record({ buildSystemVersion: mavenVersionInfoMessage }) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was always recording [undefined, undefined] since the user hasn't selected a project to transform at this point. Plus, we already emit this in the totalRunTime metric at the very end of a transformation anyway.
| } | ||
|
|
||
| export async function prepareProjectDependencies(dependenciesFolder: FolderInfo, rootPomPath: string) { | ||
| await setMaven() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Better to set the Maven to use (mvn, mvnw, mvnw.cmd) just before the local build happens to ensure we're using the correct Maven executable.
| }) | ||
| } | ||
| transformByQState.setPolledJobStatus(status) | ||
| getLogger().info(`CodeTransformation: polled job status = ${status}`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FYI: getLogger() now has a "topic" feature so you can do this at the top of the module:
const logger = getLogger('CodeTransformation')
then logger.info() will prepend the topic name.
## Problem `setMaven` is being executed unnecessarily. ## Solution Move the call to happen just before the local build starts.
## Problem `setMaven` is being executed unnecessarily. ## Solution Move the call to happen just before the local build starts.
## Problem `setMaven` is being executed unnecessarily. ## Solution Move the call to happen just before the local build starts.
## Problem `setMaven` is being executed unnecessarily. ## Solution Move the call to happen just before the local build starts.
Problem
setMavenis being executed unnecessarily.Solution
Move the call to happen just before the local build starts.
feature/xbranches will not be squash-merged at release time.