+1 

Testing git tag on macOS 12.3 with Java 8  and 17.


TY


Arturo Bernal
arturobern...@yahoo.com



> On 14 May 2022, at 16:52, Andreas Lehmkuehler <andr...@lehmi.de> wrote:
> 
> Hi,
> 
> here is my +1 (non-binding as I'm not a commons PMC member)
> 
> I've succesfully build the alpha release using
> 
> mvn clean install site
> 
> Apache Maven 3.6.3 (Red Hat 3.6.3-13)
> Java version: 11.0.15, vendor: Red Hat, Inc., runtime: 
> /usr/lib/jvm/java-11-openjdk-11.0.15.0.10-1.fc35.x86_64
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "linux", version: "5.17.5-200.fc35.x86_64", arch: "amd64", family: 
> "unix"
> 
> Thanks to all who made this possible!
> 
> Cheers
> Andreas
> 
> 
> 
> Am 13.05.22 um 14:02 schrieb Bruno Kinoshita:
>> We have fixed quite a few bugs and added some significant enhancements
>> since Apache Commons Imaging 1.0-alpha2 was released, so I would like to
>> release Apache Commons Imaging 1.0-alpha3.
>> Apache Commons Imaging 1.0-alpha3 RC2 is available for review here:
>>     https://dist.apache.org/repos/dist/dev/commons/imaging/1.0-alpha3-RC2
>> (svn revision 54488)
>> The Git tag commons-imaging-1.0-alpha3-RC2 commit for this RC is
>> bef4caa54f8e736644f3d5bb4658d5c3c95ec70a which you can browse here:
>> https://gitbox.apache.org/repos/asf?p=commons-imaging.git;a=commit;h=bef4caa54f8e736644f3d5bb4658d5c3c95ec70a
>> You may checkout this tag using:
>>     git clone https://gitbox.apache.org/repos/asf/commons-imaging.git
>> --branch commons-imaging-1.0-alpha3-RC2 commons-imaging-1.0-alpha3-RC2
>> Maven artifacts are here:
>> https://repository.apache.org/content/repositories/orgapachecommons-1587/org/apache/commons/commons-imaging/1.0-alpha3/
>> These are the artifacts and their hashes:
>> #Release SHA-512s
>> #Fri May 13 23:32:54 NZST 2022
>> commons-imaging-1.0-alpha3-tests.jar=6fad2edc85f4428de195e2dafe5b3cc2be19307b8b1dcc00c6ceaa92eb7767cfb4621c9a3a7c433e1486997f11f05114c04275a8129fe5f15999f1414baa9041
>> commons-imaging-1.0-alpha3-sources.jar=5e2f5ad8c6d9b988569793e707926d40498dbc07f7404027d67ec67fa061e1aea9947f7d05a9cf60290326689c6296287055e8b9f334426ebab76620152fff1e
>> commons-imaging-1.0-alpha3-bin.zip=bdf53a57521aea0c11c20e0884cbb68cc756ebee34f0d48319816333e600777caf04ded543a4f2560d1adef7dd2993c0cc9b4e32e3db6d024a950650222cc277
>> commons-imaging-1.0-alpha3-src.zip=73511d7068a665471805af6a832b26fa5f2f32ea1a716c0cac9a5b3a2d47cfd2e343b35a2ae79d29fa22dc54586be274c4500d209e057a544776b8f0e77cb7cb
>> commons-imaging-1.0-alpha3-javadoc.jar=624c8cafa60159be44392c51e515617548526fbe40b56f45d3f0ccc83f220a59145de474d6428e5ede383f536a18ccd4382c7673d0a14ba3b9d9cd82db4ffe6e
>> commons-imaging-1.0-alpha3-test-sources.jar=a5204a827e9d5b8fa1d98967f7b416c9a1af81eb0d9009fc0159447dbdab56e18cdaaaf10ea50b0dfc941f6668f21df1c1a49df1c051dd8cda79a3e3f00c0572
>> commons-imaging-1.0-alpha3-bin.tar.gz=877c1b28fe8fd82207d6873673e23b3ced73f09c9bd20fcfe35ff72be8480e1d0558f966fdbdd25dacef92fca02643b0cd0cdb27928914a77fad65dd47feea7d
>> commons-imaging-1.0-alpha3-src.tar.gz=16300adb5873fef464bedfdce7e1368f52add8d33087f059667840880b8666024feeecdb278a53d5c3d8e76d01ab921ea146d41ca688757f0cf0c2f2b32b0d53
>> I have tested this with ***'mvn clean install site'*** using:
>> ***
>> Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0)
>> Maven home: /opt/apache-maven-3.8.5
>> Java version: 11.0.15, vendor: Private Build, runtime:
>> /usr/lib/jvm/java-11-openjdk-amd64
>> Default locale: en_US, platform encoding: UTF-8
>> OS name: "linux", version: "5.4.0-110-generic", arch: "amd64", family:
>> "unix"
>> ***
>> Details of changes since 1.0-alpha2 are in the release notes:
>> https://dist.apache.org/repos/dist/dev/commons/imaging/1.0-alpha3-RC2/RELEASE-NOTES.txt
>> https://dist.apache.org/repos/dist/dev/commons/imaging/1.0-alpha3-RC2/site/changes-report.html
>> Site:
>> https://dist.apache.org/repos/dist/dev/commons/imaging/1.0-alpha3-RC2/site/index.html
>>     (note some *relative* links are broken and the 1.0-alpha3 directories
>> are not yet created - these will be OK once the site is deployed.)
>> CLIRR and JApiCmp reports are not being used during the alpha releases, but
>> will be used again in the
>> 1.0 release (alpha3 is expected to be the last 1.0 alpha release.)
>> RAT Report:
>> https://dist.apache.org/repos/dist/dev/commons/imaging/1.0-alpha3-RC2/site/rat-report.html
>> KEYS:
>>   https://www.apache.org/dist/commons/KEYS
>> Please review the release candidate and vote.
>> This vote will close no sooner than 72 hours from now.
>>   [ ] +1 Release these artifacts
>>   [ ] +0 OK, but...
>>   [ ] -0 OK, but really should fix...
>>   [ ] -1 I oppose this release because...
>> Thank you,
>> Bruno P. Kinoshita,
>> Release Manager (using key 33C6E01240C5468C2B7A556954E2764B48A42DF0)
>> The following is intended as a helper and refresher for reviewers.
>> Validating a release candidate
>> ==============================
>> These guidelines are NOT complete.
>> Requirements: Git, Java, Maven.
>> You can validate a release from a release candidate (RC) tag as follows.
>> 1) Clone and checkout the RC tag
>> git clone https://gitbox.apache.org/repos/asf/commons-imaging.git --branch
>> commons-imaging-1.0-alpha3-RC2 commons-imaging-1.0-alpha3-RC2
>> cd commons-imaging-1.0-alpha3-RC2
>> 2) Check Apache licenses
>> This step is not required if the site includes a RAT report page which you
>> then must check.
>> mvn apache-rat:check
>> 3) Check binary compatibility
>> Older components still use Apache Clirr:
>> This step is not required if the site includes a Clirr report page which
>> you then must check.
>> mvn clirr:check
>> Newer components use JApiCmp with the japicmp Maven Profile:
>> This step is not required if the site includes a JApiCmp report page which
>> you then must check.
>> mvn install -DskipTests -P japicmp japicmp:cmp
>> 4) Build the package
>> mvn -V clean package
>> You can record the Maven and Java version produced by -V in your VOTE reply.
>> To gather OS information from a command line:
>> Windows: ver
>> Linux: uname -a
>> 5) Build the site for a single module project
>> Note: Some plugins require the components to be installed instead of
>> packaged.
>> mvn site
>> Check the site reports in:
>> - Windows: target\site\index.html
>> - Linux: target/site/index.html
>> 6) Build the site for a multi-module project
>> mvn site
>> mvn site:stage
>> Check the site reports in:
>> - Windows: target\site\index.html
>> - Linux: target/site/index.html
>> -the end-
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to