[jira] [Updated] (MRELEASE-1061) Not able to stop version increment in pom.xml with the release prepare

2022-01-01 Thread Michael Osipov (Jira)


 [ 
https://issues.apache.org/jira/browse/MRELEASE-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov updated MRELEASE-1061:
-
Issue Type: New Feature  (was: Bug)

> Not able to stop version increment in pom.xml with the release prepare 
> ---
>
> Key: MRELEASE-1061
> URL: https://issues.apache.org/jira/browse/MRELEASE-1061
> Project: Maven Release Plugin
>  Issue Type: New Feature
>  Components: prepare
>Affects Versions: 2.5.3
>Reporter: Nikunj Ramani
>Priority: Major
>
> Hello Team,
> Here is my requirement:
> I have two profiles (32 Bit and 64 Bit) in my pom.xml. And I want them to be 
> executed one by one and expecting (tasks release prepare and release perform) 
> them to push build artifacts in artifact repository.
>  * Expected points :
>  ** For 32 Bit and 64 Bit separate .jar will be created with the same version 
> (1.0) as per below expected directory structure.
> -->ABC
>     --> 32 Bit
>             --> 1.0
>                      ABC_32Bit-1.0.jar
>     --> 64 Bit
>            --> 1.0
>                   ABC_64Bit-1.0.jar
>  * Problem facing : 
>  ** We have a Bamboo plan with two tasks. 
>  ** 1. for 32 Bit -->release:prepare release:perform -P "32Bit,!64Bit" 
>  ** 2. for 64 Bit -->release:prepare release:perform -P "!32Bit,64Bit" 
>  ** But, when task 1 for 32 Bit is getting executed it increment the version 
> number (2.0) in pom.xml file. Pushes the builds in artifacts repository with 
> the notation (ABC_32Bit-1.0.jar)
>  ** 64 Bit task uses that newly updated pom.xml file with (2.0), it creates 
> build on that version. And updates the version (3.0) in pom.xml file. Pushes 
> the builds in artifacts repository with the notation (ABC_64Bit-2.0.jar)
>  ** So, finally we get directory structure as below, which is not expected.
> --> ABC    
>      --> 32 Bit
>             --> 1.0
>                      ABC_32Bit-1.0.jar
>       --> 64 Bit
>              --> 2.0
>                   ABC_64Bit-2.0.jar
> I have even tried to use release:rollback command in between above mentioned 
> tasks. After executing 32 Bit task to make pom.xml file fresh (before 
> executing 32 Bit profile) for executing 64 Bit profile to avoid version 
> increment in pom.xml. 
>  Again it is not working and giving error as "cannot restore from a missing 
> backup POM" 
>  * 1. for 32 Bit -->release:prepare release:perform -P "32Bit,!64Bit" 
>  * 2. release:rollback
>  * 3. for 64 Bit -->release:prepare release:perform -P "!32Bit,64Bit"
> Hope you guys got my problem. If not feel free to open discussion.
> Thanks



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Updated] (MRELEASE-1061) Not able to stop version increment in pom.xml with the release prepare

2021-03-01 Thread Nikunj Ramani (Jira)


 [ 
https://issues.apache.org/jira/browse/MRELEASE-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nikunj Ramani updated MRELEASE-1061:

Description: 
Hello Team,

Here is my requirement:

I have two profiles (32 Bit and 64 Bit) in my pom.xml. And I want them to be 
executed one by one and expecting (tasks release prepare and release perform) 
them to push build artifacts in artifact repository.
 * Expected points :
 ** For 32 Bit and 64 Bit separate .jar will be created with the same version 
(1.0) as per below expected directory structure.

-->ABC

    --> 32 Bit

            --> 1.0
                     ABC_32Bit-1.0.jar
    --> 64 Bit

           --> 1.0

                  ABC_64Bit-1.0.jar
 * Problem facing : 
 ** We have a Bamboo plan with two tasks. 
 ** 1. for 32 Bit -->release:prepare release:perform -P "32Bit,!64Bit" 
 ** 2. for 64 Bit -->release:prepare release:perform -P "!32Bit,64Bit" 
 ** But, when task 1 for 32 Bit is getting executed it increment the version 
number (2.0) in pom.xml file. Pushes the builds in artifacts repository with 
the notation (ABC_32Bit-1.0.jar)
 ** 64 Bit task uses that newly updated pom.xml file with (2.0), it creates 
build on that version. And updates the version (3.0) in pom.xml file. Pushes 
the builds in artifacts repository with the notation (ABC_64Bit-2.0.jar)
 ** So, finally we get directory structure as below, which is not expected.

--> ABC    

     --> 32 Bit

            --> 1.0
                     ABC_32Bit-1.0.jar
      --> 64 Bit

             --> 2.0

                  ABC_64Bit-2.0.jar

I have even tried to use release:rollback command in between above mentioned 
tasks. After executing 32 Bit task to make pom.xml file fresh (before executing 
32 Bit profile) for executing 64 Bit profile to avoid version increment in 
pom.xml. 
 Again it is not working and giving error as "cannot restore from a missing 
backup POM" 
 * 1. for 32 Bit -->release:prepare release:perform -P "32Bit,!64Bit" 
 * 2. release:rollback
 * 3. for 64 Bit -->release:prepare release:perform -P "!32Bit,64Bit"

Hope you guys got my problem. If not feel free to open discussion.

Thanks

  was:
Hello Team,

Here is my requirement:

I have two profiles (32 Bit and 64 Bit) in my pom.xml. And I want them to be 
executed one by one and expecting (tasks release prepare and release perform) 
them to push build artifacts in artifact repository.
 * Expected points :
 ** For 32 Bit and 64 Bit separate .jar will be created with the same version 
(1.0) as per below expected notation.

-->ABC

    --> 32 Bit

            --> 1.0
                    ABC_32Bit-1.0.jar
   --> 64 Bit

           --> 1.0

                  ABC_64Bit-1.0.jar
 * Problem facing : 
 ** We have a Bamboo plan with two tasks. 
 ** 1. for 32 Bit -->release:prepare release:perform -P "32Bit,!64Bit" 
 ** 2. for 64 Bit -->release:prepare release:perform -P "!32Bit,64Bit" 
 ** But, when task 1 for 32 Bit is getting executed it increment the version 
number (2.0) in pom.xml file. Pushes the builds in artifacts repository with 
the notation (ABC_32Bit-1.0.jar)
 ** 64 Bit task uses that newly updated pom.xml file with (2.0), it creates 
build on that version. And updates the version (3.0) in pom.xml file. Pushes 
the builds in artifacts repository with the notation (ABC_64Bit-2.0.jar)
 ** So, we finally we get the structure as below, which is not expected.
 ** -->ABC

    --> 32 Bit

            --> 1.0
                    ABC_32Bit-1.0.jar
   --> 64 Bit

             --> 2.0

                  ABC_64Bit-2.0.jar

I have even tried to use release:rollback command in between above mentioned 
tasks. After executing 32 Bit task to make pom.xml file fresh (before executing 
32 Bit profile) for executing 64 Bit profile to avoid version increment in 
pom.xml. 
Again it is not working and giving error as "cannot restore from a missing 
backup POM" 
 * 1. for 32 Bit -->release:prepare release:perform -P "32Bit,!64Bit" 
 * 2. release:rollback
 * 3. for 64 Bit -->release:prepare release:perform -P "!32Bit,64Bit"

Hope you guys got my problem. If not feel free to open discussion.

Thanks


> Not able to stop version increment in pom.xml with the release prepare 
> ---
>
> Key: MRELEASE-1061
> URL: https://issues.apache.org/jira/browse/MRELEASE-1061
> Project: Maven Release Plugin
>  Issue Type: Bug
>  Components: prepare
>Affects Versions: 2.5.3
>Reporter: Nikunj Ramani
>Priority: Major
>
> Hello Team,
> Here is my requirement:
> I have two profiles (32 Bit and 64 Bit) in my pom.xml. And I want them to be 
> executed one by one and expecting (tasks release prepare and release perform) 
> them to push build artifacts in artifact repository.
>  * Expected points :
>  ** For 32 Bit and 64 Bit separate .jar will be created