[Git][java-team/jboss-classfilewriter][master] 6 commits: New upstream version 1.3.1
Markus Koschany (@apo)
gitlab at salsa.debian.org
Fri Jan 3 19:53:06 GMT 2025
Markus Koschany pushed to branch master at Debian Java Maintainers / jboss-classfilewriter
Commits:
d25e4008 by Markus Koschany at 2025-01-03T20:47:19+01:00
New upstream version 1.3.1
- - - - -
ace9a20e by Markus Koschany at 2025-01-03T20:47:19+01:00
Update upstream source from tag 'upstream/1.3.1'
Update to upstream version '1.3.1'
with Debian dir be7aaa35eadc251e9d61c1ebf232cc8459a11091
- - - - -
5fe71eb0 by Markus Koschany at 2025-01-03T20:48:28+01:00
Update copyright years
- - - - -
eabc7f04 by Markus Koschany at 2025-01-03T20:48:42+01:00
Declare compliance with Debian Policy 4.7.0.
- - - - -
39f43c03 by Markus Koschany at 2025-01-03T20:49:20+01:00
Remove README.source
- - - - -
ebc7fb1e by Markus Koschany at 2025-01-03T20:49:56+01:00
Update changelog
- - - - -
15 changed files:
- + .github/dependabot.yml
- .github/workflows/ci.yml
- + CODEOWNERS
- + CODE_OF_CONDUCT.md
- + CONTRIBUTING.md
- + LICENSE.txt
- − README
- + README.md
- + SECURITY.md
- − debian/README.source
- debian/changelog
- debian/control
- debian/copyright
- pom.xml
- src/main/java/org/jboss/classfilewriter/util/Signatures.java
Changes:
=====================================
.github/dependabot.yml
=====================================
@@ -0,0 +1,16 @@
+# To get started with Dependabot version updates, you'll need to specify which
+# package ecosystems to update and where the package manifests are located.
+# Please see the documentation for all configuration options:
+# https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
+
+version: 2
+updates:
+ - package-ecosystem: "maven"
+ directory: "/"
+ schedule:
+ interval: "daily"
+ open-pull-requests-limit: 10
+ - package-ecosystem: "github-actions"
+ directory: "/"
+ schedule:
+ interval: "daily"
=====================================
.github/workflows/ci.yml
=====================================
@@ -9,15 +9,15 @@ on:
jobs:
build-test-matrix:
- name: ${{ matrix.impl}}-${{ matrix.jdk }}-${{ matrix.os }}
+ name: ${{ matrix.jdk-distribution }}-${{ matrix.jdk-version }}-${{ matrix.os }}
runs-on: ${{ matrix.os }}
timeout-minutes: 10
strategy:
fail-fast: false
matrix:
- os: [ubuntu-20.04, windows-latest]
- jdk: [11, 17]
- impl: [hotspot, openj9]
+ os: [ubuntu-latest, windows-latest]
+ jdk-distribution: [temurin, adopt-openj9]
+ jdk-version: [11, 17]
steps:
- name: Configure runner - Linux
if: contains(matrix.os, 'ubuntu')
@@ -30,16 +30,16 @@ jobs:
echo '127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4' > %SystemRoot%\System32\drivers\etc\hosts
echo '::1 localhost localhost.localdomain localhost6 localhost6.localdomain6' >> %SystemRoot%\System32\drivers\etc\hosts
shell: cmd
- - uses: actions/checkout at v2
- - name: Set up JDK ${{ matrix.jdk }}
- uses: AdoptOpenJDK/install-jdk at v1
+ - uses: actions/checkout at v4
+ - name: Set up JDK ${{ matrix.jdk-distribution }} ${{ matrix.jdk-version }}
+ uses: actions/setup-java at v4
with:
- version: ${{ matrix.jdk }}
- impl: ${{ matrix.impl }}
+ distribution: ${{ matrix.jdk-distribution }}
+ java-version: ${{ matrix.jdk-version }}
- name: Run Tests
run: mvn -ntp -U -B -fae clean install
- - uses: actions/upload-artifact at v2
+ - uses: actions/upload-artifact at v4
if: failure()
with:
- name: surefire-reports-${{ matrix.openjdk}}-${{ matrix.jdk }}-${{ matrix.os }}
+ name: surefire-${{ matrix.jdk-distribution }}-${{ matrix.jdk-version }}-${{ matrix.os }}
path: '**/surefire-reports/*.txt'
=====================================
CODEOWNERS
=====================================
@@ -0,0 +1 @@
+ at ropalka
=====================================
CODE_OF_CONDUCT.md
=====================================
@@ -0,0 +1,42 @@
+## JBoss Class File Writer Community Code of Conduct v1.0
+
+### Contributor Code of Conduct
+
+As contributors and maintainers of this project, and in the interest of fostering
+an open and welcoming community, we pledge to respect all people who contribute
+through reporting issues, posting feature requests, updating documentation,
+submitting pull requests or patches, and other activities.
+
+We are committed to making participation in this project a harassment-free experience for
+everyone, regardless of level of experience, gender, gender identity and expression,
+sexual orientation, disability, personal appearance, body size, race, ethnicity, age,
+religion, or nationality.
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery
+* Personal attacks
+* Trolling or insulting/derogatory comments
+* Public or private harassment
+* Publishing other's private information, such as physical or electronic addresses, without explicit permission
+* Other unethical or unprofessional conduct.
+
+Project maintainers have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are not
+aligned to this Code of Conduct. By adopting this Code of Conduct, project maintainers
+commit themselves to fairly and consistently applying these principles to every aspect
+of managing this project. Project maintainers who do not follow or enforce the Code of
+Conduct may be permanently removed from the project team.
+
+This code of conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community.
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by
+contacting a JBoss Class File Writer project lead, Richard Opalka <ropalka at redhat.com>.
+
+
+This Code of Conduct is adapted from the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md) which is
+adapted from the Contributor Covenant
+(http://contributor-covenant.org), version 1.2.0, available at
+http://contributor-covenant.org/version/1/2/0/
+
=====================================
CONTRIBUTING.md
=====================================
@@ -0,0 +1,130 @@
+First off, thank you for considering contributing to JBoss Class File Writer project. It's people like you that make JBoss Class File Writer such a great library. JBoss Class File Writer is an open source project and contributions from our community are more than welcome! There are many ways to contribute, from writing tutorials or blog posts, improving the documentation, submitting bug reports and feature requests or writing code which can be incorporated into JBoss Class File Writer itself.
+
+We expect all contributors and users to follow our [Code of Conduct](CODE_OF_CONDUCT.md) when communicating through project channels. These include, but are not limited to: chat, issues, code.
+
+All recent development happens in the branch `main`. There are additional [branches](https://github.com/jbossas/jboss-classfilewriter/branches) mainly used for maintenance.
+
+# One time setup
+
+## Create a GitHub account
+
+If you don't have one already, head to https://github.com/
+
+## Fork JBoss Class File Writer
+
+Fork https://github.com/jbossas/jboss-classfilewriter into your GitHub account.
+
+## Clone your newly forked repository onto your local machine
+
+```bash
+git clone git at github.com:[your username]/jboss-classfilewriter.git
+cd jboss-classfilewriter
+```
+
+## Add a remote reference to upstream
+
+This makes it easy to pull down changes in the project over time
+
+```bash
+git remote add upstream git://github.com/jbossas/jboss-classfilewriter.git
+```
+
+# Development Process
+
+This is the typical process you would follow to submit any changes to JBoss Class File Writer.
+
+## Pulling updates from upstream
+
+```bash
+git pull --rebase upstream main
+```
+
+> Note that --rebase will automatically move your local commits, if you have
+> any, on top of the latest branch you pull from.
+> If you don't have any commits it is safe to leave off, but for safety it
+> doesn't hurt to use it each time just in case you have a commit you've
+> forgotten about!
+
+## Discuss your planned changes (if you want feedback)
+
+ * JBoss Class File Writer Issue Tracker - https://github.com/jbossas/jboss-classfilewriter/issues
+ * Zulip - https://wildfly.zulipchat.com/#narrow/stream/174184-wildfly-developers
+
+## Create a simple topic branch to isolate your work (recommended)
+
+```bash
+git checkout -b my_cool_feature
+```
+
+## Make the changes
+
+Make whatever code changes, including new tests to verify your change, are necessary and ensure that the build and tests pass.
+
+```bash
+mvn clean install
+```
+
+> If you're making non code changes, the above step is not required.
+
+## Commit changes
+
+Add whichever files were changed into 'staging' before performing a commit:
+
+```bash
+git commit
+```
+
+## Rebase changes against main
+
+Once all your commits for the issue have been made against your local topic branch, we need to rebase it against branch main in upstream to ensure that your commits are added on top of the current state of main. This will make it easier to incorporate your changes into the main branch, especially if there has been any significant time passed since you rebased at the beginning.
+
+```bash
+git pull --rebase upstream main
+```
+
+## Push to your repo
+
+Now that you've synced your topic branch with upstream, it's time to push it to your GitHub repo.
+
+```bash
+git push origin my_cool_feature
+```
+
+## Getting your changes merged into upstream, a pull request
+
+Now your updates are in your GitHub repo, you will need to notify the project that you have code/docs for inclusion.
+
+ * Send a pull request, by clicking the pull request link while in your repository fork
+ * After review a maintainer will merge your pull request, update/resolve associated issues, and reply when complete
+ * Lastly, switch back to branch main from your topic branch and pull the updates
+
+```bash
+git checkout main
+git pull upstream main
+```
+
+ * You may also choose to update your origin on GitHub as well
+
+```bash
+git push origin
+```
+
+## Some tips
+
+Here are some tips on increasing the chance that your pull request is accepted:
+
+ * Write a [good commit message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
+ * Include tests that fail without your code, and pass with it
+
+# Issues
+
+JBoss Class File Writer uses github issues to manage issues. All issues can be found [here](https://github.com/jbossas/jboss-classfilewriter/issues).
+
+To create a new issue, comment on an existing issue, or assign an issue to yourself, you'll need to first [create a github account](https://github.com/).
+
+## Good First Issues
+
+Want to contribute to JBoss Class File Writer but aren't quite sure where to start? Check out our issues with the `good-first-issue` label. These are a triaged set of issues that are great for getting started on our project. These can be found [here](https://github.com/jbossas/jboss-classfilewriter/issues?q=is%3Aissue+is%3Aopen+label%3A%22good-first-issue%22).
+
+Once you have selected an issue you'd like to work on, make sure it's not already assigned to someone else. To assign an issue to yourself, simply click on "Start Progress". This will automatically assign the issue to you.
+
=====================================
LICENSE.txt
=====================================
@@ -0,0 +1,202 @@
+
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
=====================================
README deleted
=====================================
=====================================
README.md
=====================================
@@ -0,0 +1,26 @@
+## JBoss Class File Writer
+
+JBoss Class File Writer is a byte code manipulating library used by EJB subsytem in [WildFly](https://github.com/wildfly/wildfly) project.
+
+## Building
+
+Prerequisites:
+
+* JDK 11 or newer - check `java -version`
+* Maven 3.6.0 or newer - check `mvn -v`
+
+To build with your own Maven installation:
+
+ mvn install
+
+## Issue tracker
+
+All issues can be reported at https://github.com/jbossas/jboss-classfilewriter/issues
+
+## Code
+
+All code can be found at https://github.com/jbossas/jboss-classfilewriter
+
+## License
+
+All code distributed under [ASL 2.0](LICENSE.txt).
=====================================
SECURITY.md
=====================================
@@ -0,0 +1,11 @@
+# Security Policy
+
+## Security Contacts and Procedures
+
+JBoss Class File Writer community takes security very seriously, and we aim to take immediate action to address serious security-related problems that involve our products or services.
+
+Please report any suspected security vulnerability in this project to Red Hat Product Security at secalert at redhat.com. You can use our GPG key to communicate with us securely.
+
+To report an issue in any Red Hat branded website or online service, please contact Red Hat Information Security at site-security at redhat.com.
+https://access.redhat.com/security/team/contact
+
=====================================
debian/README.source deleted
=====================================
@@ -1,9 +0,0 @@
-Information about jboss-classfilewriter
----------------------------------------
-
-This package was debianized using the mh_make command
-from the maven-debian-helper package.
-
-The build system uses Maven but prevents it from downloading
-anything from the Internet, making the build compliant with
-the Debian policy.
=====================================
debian/changelog
=====================================
@@ -1,3 +1,11 @@
+jboss-classfilewriter (1.3.1-1) unstable; urgency=medium
+
+ * New upstream version 1.3.1.
+ * Declare compliance with Debian Policy 4.7.0.
+ * Remove README.source.
+
+ -- Markus Koschany <apo at debian.org> Fri, 03 Jan 2025 20:49:40 +0100
+
jboss-classfilewriter (1.3.0-1) unstable; urgency=medium
* New upstream version 1.3.0. Supports OpenJDK 17. (Closes: #1012081)
=====================================
debian/control
=====================================
@@ -12,7 +12,7 @@ Build-Depends:
libmaven-javadoc-plugin-java,
libmaven-bundle-plugin-java,
maven-debian-helper (>= 1.5)
-Standards-Version: 4.6.1
+Standards-Version: 4.7.0
Vcs-Git: https://salsa.debian.org/java-team/jboss-classfilewriter.git
Vcs-Browser: https://salsa.debian.org/java-team/jboss-classfilewriter
Homepage: https://github.com/jbossas/jboss-classfilewriter
=====================================
debian/copyright
=====================================
@@ -3,11 +3,11 @@ Upstream-Name: classfilewriter
Source: https://github.com/jbossas/jboss-classfilewriter
Files: *
-Copyright: 2015-2022, Stuart Douglas <sdouglas at redhat.com>
+Copyright: 2015-2024, Stuart Douglas <sdouglas at redhat.com>
License: Apache-2.0
Files: debian/*
-Copyright: 2015-2022, Markus Koschany <apo at debian.org>
+Copyright: 2015-2025, Markus Koschany <apo at debian.org>
License: Apache-2.0
License: Apache-2.0
=====================================
pom.xml
=====================================
@@ -4,12 +4,12 @@
<parent>
<groupId>org.jboss</groupId>
<artifactId>jboss-parent</artifactId>
- <version>39</version>
+ <version>43</version>
</parent>
<groupId>org.jboss.classfilewriter</groupId>
<artifactId>jboss-classfilewriter</artifactId>
- <version>1.3.0.Final</version>
+ <version>1.3.1.Final</version>
<packaging>jar</packaging>
<description>A bytecode writer that creates .class files at runtime</description>
@@ -62,15 +62,20 @@
<plugin>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
- <version>3.3.0</version>
+ <version>5.1.9</version>
<extensions>true</extensions>
<configuration>
<instructions>
+ <Automatic-Module-Name>org.jboss.classfilewriter</Automatic-Module-Name>
<Bundle-SymbolicName>${project.artifactId}</Bundle-SymbolicName>
<Bundle-Version>${project.version}</Bundle-Version>
<Export-Package>
org.jboss.classfilewriter.*;version=${project.version}
</Export-Package>
+ <Import-Package>
+ !java.*,
+ *
+ </Import-Package>
</instructions>
</configuration>
<executions>
=====================================
src/main/java/org/jboss/classfilewriter/util/Signatures.java
=====================================
@@ -1,13 +1,14 @@
/*
- * JBoss, Home of Professional Open Source
- * Copyright 2015, Red Hat, Inc., and individual contributors
- * by the @authors tag. See the copyright.txt in the distribution for a
- * full listing of individual contributors.
+ * JBoss, Home of Professional Open Source.
+ *
+ * Copyright 2015 Red Hat, Inc.
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
- * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
View it on GitLab: https://salsa.debian.org/java-team/jboss-classfilewriter/-/compare/8b9dbcd06db6de40a402f995274811333221a1be...ebc7fb1e61fe274567f49b6482f514c9263971d9
--
View it on GitLab: https://salsa.debian.org/java-team/jboss-classfilewriter/-/compare/8b9dbcd06db6de40a402f995274811333221a1be...ebc7fb1e61fe274567f49b6482f514c9263971d9
You're receiving this email because of your account on salsa.debian.org.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-java-commits/attachments/20250103/4c7629d9/attachment.htm>
More information about the pkg-java-commits
mailing list