Ok, I'll write this a last time as I do feel like we're going in circles and will from now on not participate in any discussion involving releasing on a CI server.
A correct Maven release would use (There will be some additional profiles to activate to include all modules) 1) the "mvn release:branch" call in order to create the branch and bump the version of develop to the next version. 2) the "mvn release:prepare" to change the pom to the release version, set the timestamp in the pom (for reproducible builds) build ... if all tests are good, commit the changes, tag this commit, update the poms to the next development version, commit those changes and push everything. 3) the "mvn release:perform" which will checkout the tagged version build everything with the "apache-release" profile turned on (Which causes the source.jars, Javadoc.jars, hashes and gpg singatures to be created as well as the assembly) This also deploys the built artifacts to Nexus. Most of that you are already doing on the CI server however you're not letting it do all automatically (For lack of credentials) But ... if you would just be doing those steps on the RM machine. Chris Am 26.03.20, 05:54 schrieb "Alex Harui" <[email protected]>: On 3/25/20, 4:46 PM, "Carlos Rovira" <[email protected]> wrote: > What I want to know is what the Maven commands should be to create a > release in this "conventional process" you are referring to. > If you want to know what's the conventional maven process is, I think I can ask Chris if he wants to work with me on that process, since he already did many other Apache projects, we can expect the process is what is needed for us to. But just expect that will be a series of standard maven commands (prepare, release,...), so nothing strange at all (I expect). Do you want us to do that? Yes. I want to know what the series of standard Maven commands are. Then we can figure out how to convert them to run on the CI server. -Alex Thanks > > Maybe someone else can explain better than me. > > -Alex > > On 3/25/20, 2:22 PM, "Carlos Rovira" <[email protected]> wrote: > > Hi Alex, > > El mié., 25 mar. 2020 a las 21:26, Alex Harui > (<[email protected]>) > escribió: > > > Carlos, > > > > I'm pretty sure that part of the "conventional process" you want to > try > > requires filling the staging repo from a local machine. > > > > This is what we already did. If you go to [1] will see [2]. That was > the > upload of compiler to the staging repo. When trying to do the same for > typedefs it failed when trying to fill repo from local machine. I think > Chris or I should not take more time in trying to fix Ant scripts that > are > failing. > > Thanks > > [1] > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2F%23stagingRepositories&data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&sdata=qSFTmdvxYB8fK%2FKM5kAd%2Bzslsl0fNxUJi%2BybUIleIUY%3D&reserved=0 > [2] > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fimgur.com%2Fa%2Fw4az7pD&data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&sdata=mOv7%2BFzO764iEkXZgA3DiGEdeRaXQrLp%2Fgq8g%2BOkjt0%3D&reserved=0 > > > > > > > > -- > > Carlos Rovira > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&sdata=96pUSZqS1Sc%2FJ4%2BvUUIFpcKEW4b2DAj2FJjCvc9eW2k%3D&reserved=0 > > > > > > > > > > > -- Carlos Rovira https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C821c810ff88f4f3371a608d7d116c8e0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637207768101866118&sdata=96pUSZqS1Sc%2FJ4%2BvUUIFpcKEW4b2DAj2FJjCvc9eW2k%3D&reserved=0
