[jira] [Commented] (MNG-6694) generated maven-metadata.xml gives wrong snapshot version

[ https://issues.apache.org/jira/browse/MNG-6694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883636#comment-16883636 ] Rik Schaaf commented on MNG-6694: - It is not easy to reproduce, since it probably only happ

[jira] [Comment Edited] (MNG-6694) generated maven-metadata.xml gives wrong snapshot version

[ https://issues.apache.org/jira/browse/MNG-6694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16880117#comment-16880117 ] Rik Schaaf edited comment on MNG-6694 at 7/8/19 8:31 AM: - That is a

[jira] [Commented] (MNG-6694) generated maven-metadata.xml gives wrong snapshot version

[ https://issues.apache.org/jira/browse/MNG-6694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16880117#comment-16880117 ] Rik Schaaf commented on MNG-6694: - That is a google analytics opt-out I think. > generated

[jira] [Updated] (MNG-6694) generated maven-metadata.xml gives wrong snapshot version

[ https://issues.apache.org/jira/browse/MNG-6694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rik Schaaf updated MNG-6694: Description: I build and deploy my maven project today, but when trying to use that deployed version (deploy

[jira] [Commented] (MNG-6694) generated maven-metadata.xml gives wrong snapshot version

[ https://issues.apache.org/jira/browse/MNG-6694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16875751#comment-16875751 ] Rik Schaaf commented on MNG-6694: - It feels like it is caused by not reusing the same date

[jira] [Created] (MNG-6694) generated maven-metadata.xml gives wrong snapshot version

Rik Schaaf created MNG-6694: --- Summary: generated maven-metadata.xml gives wrong snapshot version Key: MNG-6694 URL: https://issues.apache.org/jira/browse/MNG-6694 Project: Maven Issue Type: Bug

[jira] [Created] (MNG-6690) Child pom doesn't use the plugin version specified in the parent pom plugin management

Rik Schaaf created MNG-6690: --- Summary: Child pom doesn't use the plugin version specified in the parent pom plugin management Key: MNG-6690 URL: https://issues.apache.org/jira/browse/MNG-6690 Project: Maven

[jira] [Comment Edited] (MNG-6578) revision property not resolved when the root module isnt the ancestor of a submodule

[ https://issues.apache.org/jira/browse/MNG-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16752369#comment-16752369 ] Rik Schaaf edited comment on MNG-6578 at 1/25/19 3:54 PM: -- I have

[jira] [Comment Edited] (MNG-6578) revision property not resolved when the root module isnt the ancestor of a submodule

[ https://issues.apache.org/jira/browse/MNG-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16752369#comment-16752369 ] Rik Schaaf edited comment on MNG-6578 at 1/25/19 3:54 PM: -- I have

[jira] [Commented] (MNG-6578) revision property not resolved when the root module isnt the ancestor of a submodule

[ https://issues.apache.org/jira/browse/MNG-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16752369#comment-16752369 ] Rik Schaaf commented on MNG-6578: - I have a feeling that it is not a bug per se, but just a

[jira] [Updated] (MNG-6578) revision property not resolved when the root module isnt the ancestor of a submodule

[ https://issues.apache.org/jira/browse/MNG-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rik Schaaf updated MNG-6578: Issue Type: New Feature (was: Bug) > revision property not resolved when the root module isnt the ancestor o

[jira] [Created] (MNG-6578) revision property not resolved when the root module isnt the ancestor of a submodule

Rik Schaaf created MNG-6578: --- Summary: revision property not resolved when the root module isnt the ancestor of a submodule Key: MNG-6578 URL: https://issues.apache.org/jira/browse/MNG-6578 Project: Maven

[jira] [Commented] (MNG-6564) Lack of ability to overwrite properties of specified dependencies

[ https://issues.apache.org/jira/browse/MNG-6564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16742570#comment-16742570 ] Rik Schaaf commented on MNG-6564: - That depends on what the intended behaviour was before o

[jira] [Updated] (MNG-6564) Lack of ability to overwrite properties of specified dependencies

[ https://issues.apache.org/jira/browse/MNG-6564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rik Schaaf updated MNG-6564: Description: For example, if I want to update the flyway version to 4.2.0 in spring boot 1.5 (by default Fly

[jira] [Commented] (MNG-6564) Lack of ability to overwrite properties of specified dependencies

[ https://issues.apache.org/jira/browse/MNG-6564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16742032#comment-16742032 ] Rik Schaaf commented on MNG-6564: - I found an old forum thread that describes the same issu

[jira] [Updated] (MNG-6564) Lack of ability to overwrite properties of specified dependencies

[ https://issues.apache.org/jira/browse/MNG-6564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rik Schaaf updated MNG-6564: Description: For example, if I want to update the flyway version to 4.2.0 in spring boot 1.5 (by default Fly

[jira] [Created] (MNG-6564) Lack of ability to overwrite properties of specified dependencies

Rik Schaaf created MNG-6564: --- Summary: Lack of ability to overwrite properties of specified dependencies Key: MNG-6564 URL: https://issues.apache.org/jira/browse/MNG-6564 Project: Maven Issue Type