[jira] [Commented] (MNG-6425) Maven inserts incorrect version metadata when 'artifactory matrix parameters' are used.
[
https://issues.apache.org/jira/browse/MNG-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16510273#comment-16510273
]
Michael Osipov commented on MNG-6425:
-
Alright, will wait for your test.
> Maven inserts incorrect version metadata when 'artifactory matrix parameters'
> are used.
> ---
>
> Key: MNG-6425
> URL: https://issues.apache.org/jira/browse/MNG-6425
> Project: Maven
> Issue Type: Bug
> Components: Deployment
>Affects Versions: 3.5.3
> Environment: Linux, Windows
>Reporter: George Lianeris
>Priority: Major
> Attachments: MNG-6425-wirelog-full.log, MNG-6425-wirelog.log,
> MNG-6425.log
>
>
> When using artifactory matrix parameters as per
> [Artifactory Matrix
> Parameters|https://www.jfrog.com/confluence/display/RTF/Using+Properties+in+Deployment+and+Resolution#UsingPropertiesinDeploymentandResolution-IntroducingMatrixParameters]
> and they are added to the command line like so:
> mvn -Psomeprofile package deploy:deploy
> -DaltDeploymentRepository=central::default::[https://artifactory.my.co/artifactory/myco-dev;artifactory.licenses=myco]
> The metadata.xml for the artifact (not the version beneath it) acquires
> incorrectly calculated version values on the *second* run.
> What it should be:
> {code:xml}
>
>
> com.myco.foo
> bar
>
>
> 1.0.0-SNAPSHOT
>
> 20180611143540
>
>
> {code}
>
> What it is (more or less):
> {code:xml}
>
>
> com.myco.foo
> bar
>
> *1.0.0*
> *1.0.0*
>
> *1.0.0*
> 1.0.0-SNAPSHOT
>
> 20180611143540
>
>
> {code}
>
> Note that version 1.0.0 does not exist and was never built. This makes it
> impossible to use the artifactory matrix parameters.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6425) Maven inserts incorrect version metadata when 'artifactory matrix parameters' are used.
[
https://issues.apache.org/jira/browse/MNG-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16510266#comment-16510266
]
George Lianeris commented on MNG-6425:
--
So, there are NO release versions of this artifact at all. I never built any,
and they don't exist anywhere except for the metadata.
Please keep in mind that the very first upload generates a correct-ish file,
without the latest/release tags.
I agree that this is very fishy - these versions are coming seemingly from
nowhere. I agree that this may be an artifactory bug, but I don't know how to
diagnose this. If artifactory is serving up an incorrect file that would
explain things: 1.0.4 is already 'latest'.
I will run another trial tomorrow, specifically so we can see when '1.0.5'
decides to appear - however, I am quite certain that the previous version of
this metadata simply lacked any reference to version 1.0.4 whatsoever - that
snapshot was created only when I manually changed the POM version and pushed it
to the build system.
The fact that we have a 'get' which already provides an incorrect file makes
it look like this is an artifactory bug to me.
> Maven inserts incorrect version metadata when 'artifactory matrix parameters'
> are used.
> ---
>
> Key: MNG-6425
> URL: https://issues.apache.org/jira/browse/MNG-6425
> Project: Maven
> Issue Type: Bug
> Components: Deployment
>Affects Versions: 3.5.3
> Environment: Linux, Windows
>Reporter: George Lianeris
>Priority: Major
> Attachments: MNG-6425-wirelog-full.log, MNG-6425-wirelog.log,
> MNG-6425.log
>
>
> When using artifactory matrix parameters as per
> [Artifactory Matrix
> Parameters|https://www.jfrog.com/confluence/display/RTF/Using+Properties+in+Deployment+and+Resolution#UsingPropertiesinDeploymentandResolution-IntroducingMatrixParameters]
> and they are added to the command line like so:
> mvn -Psomeprofile package deploy:deploy
> -DaltDeploymentRepository=central::default::[https://artifactory.my.co/artifactory/myco-dev;artifactory.licenses=myco]
> The metadata.xml for the artifact (not the version beneath it) acquires
> incorrectly calculated version values on the *second* run.
> What it should be:
> {code:xml}
>
>
> com.myco.foo
> bar
>
>
> 1.0.0-SNAPSHOT
>
> 20180611143540
>
>
> {code}
>
> What it is (more or less):
> {code:xml}
>
>
> com.myco.foo
> bar
>
> *1.0.0*
> *1.0.0*
>
> *1.0.0*
> 1.0.0-SNAPSHOT
>
> 20180611143540
>
>
> {code}
>
> Note that version 1.0.0 does not exist and was never built. This makes it
> impossible to use the artifactory matrix parameters.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6425) Maven inserts incorrect version metadata when 'artifactory matrix parameters' are used.
[
https://issues.apache.org/jira/browse/MNG-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16510229#comment-16510229
]
Michael Osipov commented on MNG-6425:
-
Something if fishy about your metadata: look at line 1968:
{{[DEBUG] http-outgoing-1 >> "GET
/artifactory/myco-unrestricted-dev;artifactory.licenses=myco/com/myco/idsys/test/library1/maven-metadata.xml
HTTP/1.1[\r][\n]"}} with the content
{code:xml}
[DEBUG] http-outgoing-1 << "[\n]"
[DEBUG] http-outgoing-1 << "[\n]"
[DEBUG] http-outgoing-1 << " com.myco.idsys.test[\n]"
[DEBUG] http-outgoing-1 << " library1[\n]"
[DEBUG] http-outgoing-1 << " 1.0.0[\n]"
[DEBUG] http-outgoing-1 << " [\n]"
[DEBUG] http-outgoing-1 << "1.0.4[\n]"
[DEBUG] http-outgoing-1 << "1.0.4[\n]"
[DEBUG] http-outgoing-1 << "[\n]"
[DEBUG] http-outgoing-1 << " 1.0.0[\n]"
[DEBUG] http-outgoing-1 << " 1.0.1[\n]"
[DEBUG] http-outgoing-1 << " 1.0.2[\n]"
[DEBUG] http-outgoing-1 << " 1.0.3[\n]"
[DEBUG] http-outgoing-1 << " 1.0.4[\n]"
[DEBUG] http-outgoing-1 << "[\n]"
[DEBUG] http-outgoing-1 << "20180612142911[\n]"
[DEBUG] http-outgoing-1 << " [\n]"
[DEBUG] http-outgoing-1 << "[\n]"
{code}
but you are uploading version 1.0.4-SNAPSHOT. Now line 2316
{{[DEBUG] http-outgoing-1 >> PUT
/artifactory/myco-unrestricted-dev;artifactory.licenses=myco/com/myco/idsys/test/library1/maven-metadata.xml
HTTP/1.1}}
with
{code:xml}
[DEBUG] http-outgoing-1 >> "[\n]"
[DEBUG] http-outgoing-1 >> "[\n]"
[DEBUG] http-outgoing-1 >> " com.myco.idsys.test[\n]"
[DEBUG] http-outgoing-1 >> " library1[\n]"
[DEBUG] http-outgoing-1 >> " [\n]"
[DEBUG] http-outgoing-1 >> "1.0.4[\n]"
[DEBUG] http-outgoing-1 >> "1.0.4[\n]"
[DEBUG] http-outgoing-1 >> "[\n]"
[DEBUG] http-outgoing-1 >> " 1.0.0[\n]"
[DEBUG] http-outgoing-1 >> " 1.0.1[\n]"
[DEBUG] http-outgoing-1 >> " 1.0.2[\n]"
[DEBUG] http-outgoing-1 >> " 1.0.3[\n]"
[DEBUG] http-outgoing-1 >> " 1.0.4[\n]"
[DEBUG] http-outgoing-1 >> " 1.0.4-SNAPSHOT[\n]"
[DEBUG] http-outgoing-1 >> "[\n]"
[DEBUG] http-outgoing-1 >> "20180612142913[\n]"
[DEBUG] http-outgoing-1 >> " [\n]"
[DEBUG] http-outgoing-1 >> "[\n]"
{code}
Why is 1.0.4 released you are uploading 1.0.4-SNAPSHOT? Where do the versions
come from? Have you tried to refresh metadata in Arifactory? This does work in
Nexus, for instance.
> Maven inserts incorrect version metadata when 'artifactory matrix parameters'
> are used.
> ---
>
> Key: MNG-6425
> URL: https://issues.apache.org/jira/browse/MNG-6425
> Project: Maven
> Issue Type: Bug
> Components: Deployment
>Affects Versions: 3.5.3
> Environment: Linux, Windows
>Reporter: George Lianeris
>Priority: Major
> Attachments: MNG-6425-wirelog-full.log, MNG-6425-wirelog.log,
> MNG-6425.log
>
>
> When using artifactory matrix parameters as per
> [Artifactory Matrix
> Parameters|https://www.jfrog.com/confluence/display/RTF/Using+Properties+in+Deployment+and+Resolution#UsingPropertiesinDeploymentandResolution-IntroducingMatrixParameters]
> and they are added to the command line like so:
> mvn -Psomeprofile package deploy:deploy
> -DaltDeploymentRepository=central::default::[https://artifactory.my.co/artifactory/myco-dev;artifactory.licenses=myco]
> The metadata.xml for the artifact (not the version beneath it) acquires
> incorrectly calculated version values on the *second* run.
> What it should be:
> {code:xml}
>
>
> com.myco.foo
> bar
>
>
> 1.0.0-SNAPSHOT
>
> 20180611143540
>
>
> {code}
>
> What it is (more or less):
> {code:xml}
>
>
> com.myco.foo
> bar
>
> *1.0.0*
> *1.0.0*
>
> *1.0.0*
> 1.0.0-SNAPSHOT
>
> 20180611143540
>
>
> {code}
>
> Note that version 1.0.0 does not exist and was never built. This makes it
> impossible to use the artifactory matrix parameters.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6425) Maven inserts incorrect version metadata when 'artifactory matrix parameters' are used.
[
https://issues.apache.org/jira/browse/MNG-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16509928#comment-16509928
]
Michael Osipov commented on MNG-6425:
-
Thanks, I will have a look at it a bit later today.
> Maven inserts incorrect version metadata when 'artifactory matrix parameters'
> are used.
> ---
>
> Key: MNG-6425
> URL: https://issues.apache.org/jira/browse/MNG-6425
> Project: Maven
> Issue Type: Bug
> Components: Deployment
>Affects Versions: 3.5.3
> Environment: Linux, Windows
>Reporter: George Lianeris
>Priority: Major
> Attachments: MNG-6425-wirelog-full.log, MNG-6425-wirelog.log,
> MNG-6425.log
>
>
> When using artifactory matrix parameters as per
> [Artifactory Matrix
> Parameters|https://www.jfrog.com/confluence/display/RTF/Using+Properties+in+Deployment+and+Resolution#UsingPropertiesinDeploymentandResolution-IntroducingMatrixParameters]
> and they are added to the command line like so:
> mvn -Psomeprofile package deploy:deploy
> -DaltDeploymentRepository=central::default::[https://artifactory.my.co/artifactory/myco-dev;artifactory.licenses=myco]
> The metadata.xml for the artifact (not the version beneath it) acquires
> incorrectly calculated version values on the *second* run.
> What it should be:
> {code:xml}
>
>
> com.myco.foo
> bar
>
>
> 1.0.0-SNAPSHOT
>
> 20180611143540
>
>
> {code}
>
> What it is (more or less):
> {code:xml}
>
>
> com.myco.foo
> bar
>
> *1.0.0*
> *1.0.0*
>
> *1.0.0*
> 1.0.0-SNAPSHOT
>
> 20180611143540
>
>
> {code}
>
> Note that version 1.0.0 does not exist and was never built. This makes it
> impossible to use the artifactory matrix parameters.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6425) Maven inserts incorrect version metadata when 'artifactory matrix parameters' are used.
[
https://issues.apache.org/jira/browse/MNG-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16509883#comment-16509883
]
George Lianeris commented on MNG-6425:
--
Full log attached.
> Maven inserts incorrect version metadata when 'artifactory matrix parameters'
> are used.
> ---
>
> Key: MNG-6425
> URL: https://issues.apache.org/jira/browse/MNG-6425
> Project: Maven
> Issue Type: Bug
> Components: Deployment
>Affects Versions: 3.5.3
> Environment: Linux, Windows
>Reporter: George Lianeris
>Priority: Major
> Attachments: MNG-6425-wirelog-full.log, MNG-6425-wirelog.log,
> MNG-6425.log
>
>
> When using artifactory matrix parameters as per
> [Artifactory Matrix
> Parameters|https://www.jfrog.com/confluence/display/RTF/Using+Properties+in+Deployment+and+Resolution#UsingPropertiesinDeploymentandResolution-IntroducingMatrixParameters]
> and they are added to the command line like so:
> mvn -Psomeprofile package deploy:deploy
> -DaltDeploymentRepository=central::default::[https://artifactory.my.co/artifactory/myco-dev;artifactory.licenses=myco]
> The metadata.xml for the artifact (not the version beneath it) acquires
> incorrectly calculated version values on the *second* run.
> What it should be:
> {code:xml}
>
>
> com.myco.foo
> bar
>
>
> 1.0.0-SNAPSHOT
>
> 20180611143540
>
>
> {code}
>
> What it is (more or less):
> {code:xml}
>
>
> com.myco.foo
> bar
>
> *1.0.0*
> *1.0.0*
>
> *1.0.0*
> 1.0.0-SNAPSHOT
>
> 20180611143540
>
>
> {code}
>
> Note that version 1.0.0 does not exist and was never built. This makes it
> impossible to use the artifactory matrix parameters.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6425) Maven inserts incorrect version metadata when 'artifactory matrix parameters' are used.
[
https://issues.apache.org/jira/browse/MNG-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16509875#comment-16509875
]
Michael Osipov commented on MNG-6425:
-
Can you also please share what is downloaded from Artifactory?
> Maven inserts incorrect version metadata when 'artifactory matrix parameters'
> are used.
> ---
>
> Key: MNG-6425
> URL: https://issues.apache.org/jira/browse/MNG-6425
> Project: Maven
> Issue Type: Bug
> Components: Deployment
>Affects Versions: 3.5.3
> Environment: Linux, Windows
>Reporter: George Lianeris
>Priority: Major
> Attachments: MNG-6425-wirelog.log, MNG-6425.log
>
>
> When using artifactory matrix parameters as per
> [Artifactory Matrix
> Parameters|https://www.jfrog.com/confluence/display/RTF/Using+Properties+in+Deployment+and+Resolution#UsingPropertiesinDeploymentandResolution-IntroducingMatrixParameters]
> and they are added to the command line like so:
> mvn -Psomeprofile package deploy:deploy
> -DaltDeploymentRepository=central::default::[https://artifactory.my.co/artifactory/myco-dev;artifactory.licenses=myco]
> The metadata.xml for the artifact (not the version beneath it) acquires
> incorrectly calculated version values on the *second* run.
> What it should be:
> {code:xml}
>
>
> com.myco.foo
> bar
>
>
> 1.0.0-SNAPSHOT
>
> 20180611143540
>
>
> {code}
>
> What it is (more or less):
> {code:xml}
>
>
> com.myco.foo
> bar
>
> *1.0.0*
> *1.0.0*
>
> *1.0.0*
> 1.0.0-SNAPSHOT
>
> 20180611143540
>
>
> {code}
>
> Note that version 1.0.0 does not exist and was never built. This makes it
> impossible to use the artifactory matrix parameters.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6425) Maven inserts incorrect version metadata when 'artifactory matrix parameters' are used.
[
https://issues.apache.org/jira/browse/MNG-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16509694#comment-16509694
]
George Lianeris commented on MNG-6425:
--
Hi Michael,
I am inclined to agree with you, but to my surprise the wire log appears to
say otherwise. I have attached the relevant section of the log.
> Maven inserts incorrect version metadata when 'artifactory matrix parameters'
> are used.
> ---
>
> Key: MNG-6425
> URL: https://issues.apache.org/jira/browse/MNG-6425
> Project: Maven
> Issue Type: Bug
> Components: Deployment
>Affects Versions: 3.5.3
> Environment: Linux, Windows
>Reporter: George Lianeris
>Priority: Major
> Attachments: MNG-6425-wirelog.log, MNG-6425.log
>
>
> When using artifactory matrix parameters as per
> [Artifactory Matrix
> Parameters|https://www.jfrog.com/confluence/display/RTF/Using+Properties+in+Deployment+and+Resolution#UsingPropertiesinDeploymentandResolution-IntroducingMatrixParameters]
> and they are added to the command line like so:
> mvn -Psomeprofile package deploy:deploy
> -DaltDeploymentRepository=central::default::[https://artifactory.my.co/artifactory/myco-dev;artifactory.licenses=myco]
> The metadata.xml for the artifact (not the version beneath it) acquires
> incorrectly calculated version values on the *second* run.
> What it should be:
> {code:xml}
>
>
> com.myco.foo
> bar
>
>
> 1.0.0-SNAPSHOT
>
> 20180611143540
>
>
> {code}
>
> What it is (more or less):
> {code:xml}
>
>
> com.myco.foo
> bar
>
> *1.0.0*
> *1.0.0*
>
> *1.0.0*
> 1.0.0-SNAPSHOT
>
> 20180611143540
>
>
> {code}
>
> Note that version 1.0.0 does not exist and was never built. This makes it
> impossible to use the artifactory matrix parameters.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6425) Maven inserts incorrect version metadata when 'artifactory matrix parameters' are used.
[
https://issues.apache.org/jira/browse/MNG-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16509579#comment-16509579
]
Michael Osipov commented on MNG-6425:
-
The log itself looks fine to me, thank you. Please enable wire log too. Check
wether the uploaded file does already contain the erronous content. Please also
try Maven from master.
> Maven inserts incorrect version metadata when 'artifactory matrix parameters'
> are used.
> ---
>
> Key: MNG-6425
> URL: https://issues.apache.org/jira/browse/MNG-6425
> Project: Maven
> Issue Type: Bug
> Components: Deployment
>Affects Versions: 3.5.3
> Environment: Linux, Windows
>Reporter: George Lianeris
>Priority: Major
> Attachments: MNG-6425.log
>
>
> When using artifactory matrix parameters as per
> [Artifactory Matrix
> Parameters|https://www.jfrog.com/confluence/display/RTF/Using+Properties+in+Deployment+and+Resolution#UsingPropertiesinDeploymentandResolution-IntroducingMatrixParameters]
> and they are added to the command line like so:
> mvn -Psomeprofile package deploy:deploy
> -DaltDeploymentRepository=central::default::[https://artifactory.my.co/artifactory/myco-dev;artifactory.licenses=myco]
> The metadata.xml for the artifact (not the version beneath it) acquires
> incorrectly calculated version values on the *second* run.
> What it should be:
> {code:xml}
>
>
> com.myco.foo
> bar
>
>
> 1.0.0-SNAPSHOT
>
> 20180611143540
>
>
> {code}
>
> What it is (more or less):
> {code:xml}
>
>
> com.myco.foo
> bar
>
> *1.0.0*
> *1.0.0*
>
> *1.0.0*
> 1.0.0-SNAPSHOT
>
> 20180611143540
>
>
> {code}
>
> Note that version 1.0.0 does not exist and was never built. This makes it
> impossible to use the artifactory matrix parameters.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6425) Maven inserts incorrect version metadata when 'artifactory matrix parameters' are used.
[
https://issues.apache.org/jira/browse/MNG-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16508881#comment-16508881
]
George Lianeris commented on MNG-6425:
--
Thank You.
Take two. Please let me know if more logging is required.
> Maven inserts incorrect version metadata when 'artifactory matrix parameters'
> are used.
> ---
>
> Key: MNG-6425
> URL: https://issues.apache.org/jira/browse/MNG-6425
> Project: Maven
> Issue Type: Bug
> Components: Deployment
>Affects Versions: 3.5.3
> Environment: Linux, Windows
>Reporter: George Lianeris
>Priority: Major
> Attachments: MNG-6425.log
>
>
> When using artifactory matrix parameters as per
> [Artifactory Matrix
> Parameters|https://www.jfrog.com/confluence/display/RTF/Using+Properties+in+Deployment+and+Resolution#UsingPropertiesinDeploymentandResolution-IntroducingMatrixParameters]
> and they are added to the command line like so:
> mvn -Psomeprofile package deploy:deploy
> -DaltDeploymentRepository=central::default::[https://artifactory.my.co/artifactory/myco-dev;artifactory.licenses=myco]
> The metadata.xml for the artifact (not the version beneath it) acquires
> incorrectly calculated version values on the *second* run.
>
> What it should be:
>
>
> com.myco.foo
> bar
>
>
> 1.0.0-SNAPSHOT
>
> 20180611143540
>
>
>
> What it is (more or less):
>
>
> com.myco.foo
> bar
>
> *{{1.0.0}}*
> *{{1.0.0}}*
>
> *1.0.0*
> 1.0.0-SNAPSHOT
>
> 20180611143540
>
>
>
> Note that version 1.0.0 does not exist and was never built. This makes it
> impossible to use the artifactory matrix parameters.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6425) Maven inserts incorrect version metadata when 'artifactory matrix parameters' are used.
[
https://issues.apache.org/jira/browse/MNG-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16508764#comment-16508764
]
Michael Osipov commented on MNG-6425:
-
Here is the config file:
https://github.com/apache/maven/blob/master/apache-maven/src/conf/logging/simplelogger.properties
Your properties are only partially correct. I do not see any HttpClient
logging. Please revise your config and retry.
> Maven inserts incorrect version metadata when 'artifactory matrix parameters'
> are used.
> ---
>
> Key: MNG-6425
> URL: https://issues.apache.org/jira/browse/MNG-6425
> Project: Maven
> Issue Type: Bug
> Components: Deployment
>Affects Versions: 3.5.3
> Environment: Linux, Windows
>Reporter: George Lianeris
>Priority: Major
> Attachments: MNG-6425.log
>
>
> When using artifactory matrix parameters as per
> [Artifactory Matrix
> Parameters|https://www.jfrog.com/confluence/display/RTF/Using+Properties+in+Deployment+and+Resolution#UsingPropertiesinDeploymentandResolution-IntroducingMatrixParameters]
> and they are added to the command line like so:
> mvn -Psomeprofile package deploy:deploy
> -DaltDeploymentRepository=central::default::[https://artifactory.my.co/artifactory/myco-dev;artifactory.licenses=myco]
> The metadata.xml for the artifact (not the version beneath it) acquires
> incorrectly calculated version values on the *second* run.
>
> What it should be:
>
>
> com.myco.foo
> bar
>
>
> 1.0.0-SNAPSHOT
>
> 20180611143540
>
>
>
> What it is (more or less):
>
>
> com.myco.foo
> bar
>
> *{{1.0.0}}*
> *{{1.0.0}}*
>
> *1.0.0*
> 1.0.0-SNAPSHOT
>
> 20180611143540
>
>
>
> Note that version 1.0.0 does not exist and was never built. This makes it
> impossible to use the artifactory matrix parameters.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6425) Maven inserts incorrect version metadata when 'artifactory matrix parameters' are used.
[
https://issues.apache.org/jira/browse/MNG-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16508757#comment-16508757
]
George Lianeris commented on MNG-6425:
--
The above run caused the following to happen on the second run (again, 1.0.0
release does not exist).
com.myco.idsys.test
library1
1.0.0
1.0.0
1.0.0
1.0.0-SNAPSHOT
20180611205743
For this run, the only difference to the previous is that I committed a change
to the POM version:
com.myco.idsys.test
library1
1.0.1
1.0.1
1.0.0
1.0.1
1.0.1-SNAPSHOT
20180611210923
> Maven inserts incorrect version metadata when 'artifactory matrix parameters'
> are used.
> ---
>
> Key: MNG-6425
> URL: https://issues.apache.org/jira/browse/MNG-6425
> Project: Maven
> Issue Type: Bug
> Components: Deployment
>Affects Versions: 3.5.3
> Environment: Linux, Windows
>Reporter: George Lianeris
>Priority: Major
> Attachments: MNG-6425.log
>
>
> When using artifactory matrix parameters as per
> [Artifactory Matrix
> Parameters|https://www.jfrog.com/confluence/display/RTF/Using+Properties+in+Deployment+and+Resolution#UsingPropertiesinDeploymentandResolution-IntroducingMatrixParameters]
> and they are added to the command line like so:
> mvn -Psomeprofile package deploy:deploy
> -DaltDeploymentRepository=central::default::[https://artifactory.my.co/artifactory/myco-dev;artifactory.licenses=myco]
> The metadata.xml for the artifact (not the version beneath it) acquires
> incorrectly calculated version values on the *second* run.
>
> What it should be:
>
>
> com.myco.foo
> bar
>
>
> 1.0.0-SNAPSHOT
>
> 20180611143540
>
>
>
> What it is (more or less):
>
>
> com.myco.foo
> bar
>
> *{{1.0.0}}*
> *{{1.0.0}}*
>
> *1.0.0*
> 1.0.0-SNAPSHOT
>
> 20180611143540
>
>
>
> Note that version 1.0.0 does not exist and was never built. This makes it
> impossible to use the artifactory matrix parameters.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6425) Maven inserts incorrect version metadata when 'artifactory matrix parameters' are used.
[
https://issues.apache.org/jira/browse/MNG-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16508749#comment-16508749
]
George Lianeris commented on MNG-6425:
--
Thank you; the log is attached. Please let me know if Ithis was done correctly
- the configuration I used is:
# === Maven 3.1.x+ section
# http://maven.apache.org/maven-logging.html Default Overrides
org.slf4j.simpleLogger.defaultLogLevel=trace
org.slf4j.simpleLogger.showDateTime=true
org.slf4j.simpleLogger.showThreadName=true
org.slf4j.simpleLogger.showLogName=true
org.slf4j.simpleLogger.logFile=System.out
org.slf4j.simpleLogger.levelInBrackets=true
org.slf4j.simpleLogger.log.Sisu=info
org.slf4j.simpleLogger.warnLevelString=DEBUG
# HTTP logging overrides
org.slf4j.simpleLogger.log.org.apache.http=DEBUG
org.slf4j.simpleLogger.log.org.apache.http.wire=ERROR
org.slf4j.simplelogger.log.org.apache.maven.wagon.providers.http=DEBUG
org.slf4j.simplelogger.log.org.apache.maven.wagon.providers.http.httpclient.wire=ERROR
> Maven inserts incorrect version metadata when 'artifactory matrix parameters'
> are used.
> ---
>
> Key: MNG-6425
> URL: https://issues.apache.org/jira/browse/MNG-6425
> Project: Maven
> Issue Type: Bug
> Components: Deployment
>Affects Versions: 3.5.3
> Environment: Linux, Windows
>Reporter: George Lianeris
>Priority: Major
> Attachments: MNG-6425.log
>
>
> When using artifactory matrix parameters as per
> [Artifactory Matrix
> Parameters|https://www.jfrog.com/confluence/display/RTF/Using+Properties+in+Deployment+and+Resolution#UsingPropertiesinDeploymentandResolution-IntroducingMatrixParameters]
> and they are added to the command line like so:
> mvn -Psomeprofile package deploy:deploy
> -DaltDeploymentRepository=central::default::[https://artifactory.my.co/artifactory/myco-dev;artifactory.licenses=myco]
> The metadata.xml for the artifact (not the version beneath it) acquires
> incorrectly calculated version values on the *second* run.
>
> What it should be:
>
>
> com.myco.foo
> bar
>
>
> 1.0.0-SNAPSHOT
>
> 20180611143540
>
>
>
> What it is (more or less):
>
>
> com.myco.foo
> bar
>
> *{{1.0.0}}*
> *{{1.0.0}}*
>
> *1.0.0*
> 1.0.0-SNAPSHOT
>
> 20180611143540
>
>
>
> Note that version 1.0.0 does not exist and was never built. This makes it
> impossible to use the artifactory matrix parameters.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6425) Maven inserts incorrect version metadata when 'artifactory matrix parameters' are used.
[
https://issues.apache.org/jira/browse/MNG-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16508655#comment-16508655
]
Michael Osipov commented on MNG-6425:
-
Debug log with HttpClient debug log please.
> Maven inserts incorrect version metadata when 'artifactory matrix parameters'
> are used.
> ---
>
> Key: MNG-6425
> URL: https://issues.apache.org/jira/browse/MNG-6425
> Project: Maven
> Issue Type: Bug
> Components: Deployment
>Affects Versions: 3.5.3
> Environment: Linux, Windows
>Reporter: George Lianeris
>Priority: Major
>
> When using artifactory matrix parameters as per
> [Artifactory Matrix
> Parameters|https://www.jfrog.com/confluence/display/RTF/Using+Properties+in+Deployment+and+Resolution#UsingPropertiesinDeploymentandResolution-IntroducingMatrixParameters]
> and they are added to the command line like so:
> mvn -Psomeprofile package deploy:deploy
> -DaltDeploymentRepository=central::default::[https://artifactory.my.co/artifactory/myco-dev;artifactory.licenses=myco]
> The metadata.xml for the artifact (not the version beneath it) acquires
> incorrectly calculated version values on the *second* run.
>
> What it should be:
>
>
> com.myco.foo
> bar
>
>
> 1.0.0-SNAPSHOT
>
> 20180611143540
>
>
>
> What it is (more or less):
>
>
> com.myco.foo
> bar
>
> *{{1.0.0}}*
> *{{1.0.0}}*
>
> *1.0.0*
> 1.0.0-SNAPSHOT
>
> 20180611143540
>
>
>
> Note that version 1.0.0 does not exist and was never built. This makes it
> impossible to use the artifactory matrix parameters.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
