I think there are some rules in the maven-enforcer-plugin that might be
able to help you there (I'm on my phone now, so I can't say for sure).
Am Freitag, 22. Januar 2016 schrieb Alexander Kriegisch :
> Okay, I just found a subtle problem: One of my co-workers has added a
> slightly older
Yesterday I rolled another release and again the artifacts were not uploaded. I
cannot share my build log because it contains internal information, but what I
can say is that for each single module I see in the log:
Deploying at end
Then at the end of the successful mvn release:perform build,
Okay, I just found a subtle problem: One of my co-workers has added a slightly
older version of the deploy plugin (2.8.1 instead of 2.8.2) to a new
pluginManagement section in one of our submodules. Somehow this broke
deployAtEnd not just for that submodule but for all modules. When I removed
Hi,
can you test if a simple mvn deploy will work correctly or is it only
related during the release ? Has release plugin somehow configured
(preparationGoals something llike this? )?
Kind regards
Karl Heinz Marbaise
On 1/22/16 2:11 PM, Alexander Kriegisch wrote:
Yesterday I rolled another
Hi Alexander,
On 1/9/16 2:13 PM, Alexander Kriegisch wrote:
Hi community.
This inquiry relates to
[1] https://issues.apache.org/jira/browse/MRELEASE-664
[2] https://issues.apache.org/jira/browse/MDEPLOY-157
[3] https://issues.apache.org/jira/browse/MINSTALL-93
[4]
Hi community.
This inquiry relates to
[1] https://issues.apache.org/jira/browse/MRELEASE-664
[2] https://issues.apache.org/jira/browse/MDEPLOY-157
[3] https://issues.apache.org/jira/browse/MINSTALL-93
[4] https://issues.apache.org/jira/browse/MDEPLOY-168
where [2] and [3] are kinda
