there is no problem in pushing the parent pom, just didn't want to have
many packages/pom in maven leading to confusion.
Do you see any issues?
On Wed, Jun 6, 2018 at 9:06 AM, Karl Heinz Marbaise
wrote:
> Hi,
>
> On 30/05/18 20:44, Naveen Swamy wrote:
>
>> Hi, I am trying to refactor our maven p
Hi,
On 30/05/18 20:44, Naveen Swamy wrote:
Hi, I am trying to refactor our maven packages, we were publishing way too
many packages and I am fat jar which contains everything because that's how
our users use.
We are testing the package on the staging repo and running into issues
where it is ask
Thanks Francois, I thought It would be cumbersome and probably confusing
users to publish poms and ended up using the flatten-maven-plugin and it
works fine now. Thanks, Naveen
On Thu, May 31, 2018 at 12:36 PM, Francois MAROT
wrote:
> Hi,
>
> I have the same "problem" here which is not really a
Hi,
I have the same "problem" here which is not really a problem: I deploy the
parent pom (and the parent's parent and so on) and voila. As parent are only
pom, no real package or jars, this not really a problem.
But I think the Flatten Maven Plugin
https://www.mojohaus.org/flatten-maven-plugin/ m
Hi, I am trying to refactor our maven packages, we were publishing way too
many packages and I am fat jar which contains everything because that's how
our users use.
We are testing the package on the staging repo and running into issues
where it is asking for the parent pom file.
I wanted to know
