Re: Maven Artifacts not consumable after Introducing ci-friendly approach - revision tag

2020-06-17 Thread Hanish Bansal
Yes, the issue was coming due to shade plugin. By using the option falsein shade plugin configuration solved my issue. On Wed, Jun 17, 2020 at 12:58 AM Francois Marot wrote: > beware of a caveat when using flatten and shade plugins: > https://github.com/mojohaus/flatten-maven-plugin/issues/100

Re: Maven Artifacts not consumable after Introducing ci-friendly approach - revision tag

2020-06-16 Thread Francois Marot
beware of a caveat when using flatten and shade plugins: https://github.com/mojohaus/flatten-maven-plugin/issues/100 & https://stackoverflow.com/questions/52552329/use-maven-flatten-plugin-and-maven-shade-plugin-at-the-same-time Basically you have to make sure that flatten is plugged AFTER shade

Re: Maven Artifacts not consumable after Introducing ci-friendly approach - revision tag

2020-06-15 Thread Hanish Bansal
Still facing the same issue. Child project1 has shade plugin dependency in pom.xml. *Steps to reproduce the error:* 1. Compile external project https://github.com/hanishbansal/external-common , this is some external project in which we can not change anything. 2. Our project "test-parent" has

Re: Maven Artifacts not consumable after Introducing ci-friendly approach - revision tag

2020-06-14 Thread Hanish Bansal
Hi All, Thanks for your response. I have replicated the same issue as mentioned in below steps: 1. Compile external project https://github.com/hanishbansal/external-common , this is some external project in which we can not change anything. 2. Our project "test-parent" has dependency of

Re: Maven Artifacts not consumable after Introducing ci-friendly approach - revision tag

2020-06-13 Thread Tomo Suzuki
Hi Hanish, I see child1 in my Maven local repository cannot resolve the $version to refer to its parent, because $version is defined at the parent (the error message below). How about specifying the concrete version when specifying parent? While you might not like that the version value will

Re: Maven Artifacts not consumable after Introducing ci-friendly approach - revision tag

2020-06-13 Thread Francois Marot
Hello, I can confirm that you sample project works as intended once you add the missing configuration for the flatten plugin. Without it the pom.xml installed in your local repo are not correct because of the placeholders in the . I just copy pasted the content as explained here:

Re: Maven Artifacts not consumable after Introducing ci-friendly approach - revision tag

2020-06-12 Thread Hanish Bansal
Hi Team, I have pushed a sample minimal project in git at the following link https://github.com/hanishbansal/test-parent Project Structure: test-parent - child1 - child2 child2 project has dependency of child1 project. Steps to Reproduce the error: 1.

Re: Maven Artifacts not consumable after Introducing ci-friendly approach - revision tag

2020-06-12 Thread Hanish Bansal
Hi Team, I have pushed sample minimal project in git at following link https://github.com/hanishbansal/test-parent Also attached the same code as zip file. Steps to Reproduce the error: 1. Compile test-parent project with goal "clean install". It will compile and install all child projects. 2.

Re: Maven Artifacts not consumable after Introducing ci-friendly approach - revision tag

2020-06-12 Thread Tomo Suzuki
I suspect typo in child module name. Do you want to share minimum reproducible project? On Fri, Jun 12, 2020 at 07:17 Hanish Bansal wrote: > Yes, that has been already tried. I have installed child modules separately > but if there is any child module (e.g. child2) has dependency of other >

Re: Maven Artifacts not consumable after Introducing ci-friendly approach - revision tag

2020-06-12 Thread Hanish Bansal
Yes, that has been already tried. I have installed child modules separately but if there is any child module (e.g. child2) has dependency of other child module child1 then I am not able to compile child2 project. On Fri, Jun 12, 2020 at 3:39 PM Tomo Suzuki wrote: > (Assuming yy-utils is the one

Re: Maven Artifacts not consumable after Introducing ci-friendly approach - revision tag

2020-06-12 Thread Tomo Suzuki
(Assuming yy-utils is the one of the child project) Run ”mvn install” in yy-utils module first. On Fri, Jun 12, 2020 at 01:56 Hanish Bansal wrote: > Hi All, > > We have maven Multi Module Project, where we have recently implemented > version control process as mentioned in below documentation