Skip to content
This repository has been archived by the owner on Mar 21, 2022. It is now read-only.

Manage scope for pkg.name #1

Closed
cballesta opened this issue Oct 6, 2017 · 5 comments
Closed

Manage scope for pkg.name #1

cballesta opened this issue Oct 6, 2017 · 5 comments
Assignees

Comments

@cballesta
Copy link
Contributor

Hi,

Could you manage to automatically replace scope in the pkg.name by a valid string for sonar projectKey ?
Something like @neo9/n9-node-sonar-generate => neo9_n9-node-sonar-generate for example.
I don't want to fill the sonar.projectKey for each projects.
You would be very kind ;)

SonarQube Scanner error with "@neo9/n9-node-sonar-generate" value for projectKey :

ERROR: Error during SonarQube Scanner execution
ERROR: Validation of project reactor failed:
  o "@neo9/n9-node-sonar-generate" is not a valid project or module key. Allowed characters are alphanumeric, '-', '_', '.' and ':', with at least one non-digit.
ERROR: 
ERROR: Re-run SonarQube Scanner using the -X switch to enable full debug logging.
ERROR: SonarQube scanner exited with non-zero code: 1

Cheers mate !

@gaetansenn
Copy link

Hi @cballesta

What about @neo9/n9-node-sonar-generate -> neo9:n9-node-sonar-generate?

@cballesta
Copy link
Contributor Author

You read my mind, I hesitated with this format !
Go for it !

atinux added a commit that referenced this issue Oct 6, 2017
@atinux
Copy link
Contributor

atinux commented Oct 6, 2017

Done!

Thanks @gaetansenn for this idea and @cballesta for reporting this issue.

@atinux atinux closed this as completed Oct 6, 2017
@atinux atinux reopened this Oct 6, 2017
@atinux
Copy link
Contributor

atinux commented Oct 9, 2017

Fixed in v1.0.2

@atinux atinux closed this as completed Oct 9, 2017
@cballesta
Copy link
Contributor Author

Thanks !

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

No branches or pull requests

3 participants