my-common | A CommonJS-like script/module loader | Awesome List library

now AWS have new sercvice (codeartifact), so I do not use S3.

step 1: Update aws cli

step 2: Create aws codeartifact

• Repository name (my-repo)

• Domain (my-domain)

step 3: Edit my module

The problem is clearly stated in the error message:

Failure to find groud-id:parent-id:pom:4.0.0 in file://D:\dev-customers\customer\workspace\parent-id\my-module-1/../repo

This means that didn't do a mvn install for the parent pom. That needs to be in a repository to be able to correctly resolve dependencies for the common module.

If you do a mvn install from the parent directory, it will first install the parent pom and then all child modules as described by the modules:

Micrometer uses MeterFilters registered with a MeterRegistry to modified the meters that are registered. The modifications include the ability to map a meter's ID to something different.

In Spring Boot, you can use a MeterRegistryCustomizer bean to add a MeterFilter to a registry. You can use generics to work with a registry of a specific type, for example MeterRegistryCustomizer for a customizer that is only interested in customizing the Datadog registry.

Putting this together, you can map the ID of the http.server.request meter to i.want.to.be.different using the following bean:

To long for comment. Lacking your data, this code may be a bit of a shot into the dark. Try something like this:

I've pushed working example demo code here https://github.com/swapnil-kotwal-sp/basic-demo

I also able to fix my business project issue during instrumentation, the problem was with below pice of code.

I found out what my problems were:

1. I needed to use the useClass property instead of the useValue property. useClass expects a constructor (or factory function) while the useValue property expects a simple object.
2. In the deps section you are basically overriding what values you want to pass into the constructor for the service. So, in my case, I had the 'TokenHttpService' injected but no logger, so my service threw an error when it tried to call this.logger.debug. After adding NGXLogger to the deps array the service worked flawlessly.

Here's my final providers array:

So it turns out that the error was that when moving to the separate package, I added the component to an index file that reexported the component. But by doing so, I made it cease to be a default export. Kind of obvios in hindsight. So the fix was to wrap the name of the component name in curly braces so to import the actual named component, like this:

import { Loader }from "my-common-components";

and that's it. I hope I saved someone from making the same mistake, as when searching I found lots of places describing the same error but caused by different roots, like the Typescript version and wrong required instructions.

Based on your demo project, I was able to duplicate your error. That said, here are the revised changes I made, after my first failed attempt, to be able to build the project:

1. I added the maven-compiler-plugin version 3.8.0 to all the modules. You need a version of 3.7 or higher to compile modules with Maven - at least that's the warning NetBeans showed. Since there is no harm, I added the pluging to both the common and implementation modules' POM files: