Stephan Leicht Vogt
Stephan Leicht Vogt
I'd like that. It confused me and my colleagues a lot having two similar projects. I currently use the merge-request-builder but also used in another project the GitLab-Plugin.
I finally could reproduce my initial problem. It happens if the profile with dependency is located in a parent project. See PR #21.
Additionally: In the docs for the property `embedBuildProfileDependencies` it is written that leaving this to `false` _all profiles will stay in the flattened-pom_. So I would expect to see the...
I'll rebase it right away to resolve the merge conflicts. @filiphr Is then something still missing in this PR for it to get merged?
Is this still under discussion? Can I help in any way?
it is still missing in jcenter and unfortunately the build ends in a 'Read timed out' instead of trying to load the plugin from maven central.
I tried to contact @srs via mail. Let's see if and what he'll answer.
Sorry that I didn't get back. @srs did answer me that the project isn't dead and that he would be happy if someone would help manage it. I offered him...
And where can I open a ticket for the `legacy-jre-target`?
That sounds reasonable. Can you give a link to your fork? Has @altercation any objection to this?