Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update maven-publish.yml #115

Open
wants to merge 61 commits into
base: main
Choose a base branch
from
Open

Update maven-publish.yml #115

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
61 commits
Select commit Hold shift + click to select a range
be484be
add first implementations of some annotation processing
carstenartur Oct 12, 2024
db54002
RunWith implemented
carstenartur Oct 15, 2024
b6050e5
first implementation of Assertions
carstenartur Oct 16, 2024
5d7ce06
cover more assertions in the implementation
carstenartur Oct 17, 2024
48f903c
implement static imports of assertion methods
carstenartur Oct 18, 2024
3474f3d
fix bug in import that causes static and normal import to be added
carstenartur Oct 18, 2024
d032478
consider 4 parameter case
carstenartur Oct 19, 2024
5b74616
fix explicit static import case
carstenartur Oct 19, 2024
dde7e92
Update .classpath
carstenartur Oct 19, 2024
96c93fa
fill out preview
carstenartur Oct 19, 2024
c83be40
add skeleton for rule test
carstenartur Oct 19, 2024
28fb796
add stub
carstenartur Oct 19, 2024
0f3756e
implement Rule TemporaryFolder
carstenartur Oct 20, 2024
d572153
add some fixes but ExternalResource still not working
carstenartur Oct 20, 2024
3bf6e83
fix spotbugs issue
carstenartur Oct 20, 2024
31ab10d
add rtstubs18
carstenartur Oct 20, 2024
6a9cdd5
add ExtensionContext
carstenartur Oct 21, 2024
87f4535
more fixes to ExternalResource
carstenartur Oct 22, 2024
932d537
cleanup code
carstenartur Oct 23, 2024
94cda28
more cleanup
carstenartur Oct 23, 2024
1e76a03
only formatting
carstenartur Oct 23, 2024
71c7c9a
pull methods up
carstenartur Oct 23, 2024
859ecf6
use toString()
carstenartur Oct 23, 2024
7997928
add test for already junit5 case
carstenartur Oct 24, 2024
012362d
Add support for Assume
carstenartur Oct 25, 2024
279dd51
add support for super calls
carstenartur Oct 26, 2024
cf77987
add context to super call
carstenartur Oct 26, 2024
f37e285
mostly formatting and a test
carstenartur Oct 26, 2024
247222d
fix jface migration
carstenartur Oct 27, 2024
eaa7934
extract some constants, formatting
carstenartur Oct 27, 2024
bf29b38
aggregate on AbstractTool
carstenartur Oct 27, 2024
a13eb85
simplify junit test setup
carstenartur Oct 27, 2024
c98aee3
fix spotbugs error
carstenartur Oct 27, 2024
6d0cc66
refactor to use public instead of protected for before and after
carstenartur Oct 27, 2024
3323b50
Support for assertSame and assertNotSame
carstenartur Oct 28, 2024
9d827ef
fix length of preview issue
carstenartur Oct 29, 2024
a0b46dc
add more testcases
carstenartur Oct 30, 2024
e920086
Dont create change on empty ExternalResource derived class
carstenartur Oct 30, 2024
807417f
Add assumeThat support
carstenartur Oct 31, 2024
af3be13
Add Assert.assertThat support
carstenartur Oct 31, 2024
8736b4e
test updating orbit target
carstenartur Nov 1, 2024
9e07490
test changing junit dependency
carstenartur Nov 1, 2024
051e431
add junit to product
carstenartur Nov 1, 2024
45f8917
remove junit from xml feature
carstenartur Nov 1, 2024
55a3c32
remove junit
carstenartur Nov 1, 2024
4977482
remove junit
carstenartur Nov 1, 2024
037c104
add some features to target and jupiter features to test commons
carstenartur Nov 1, 2024
e91489d
update to 2024-09
carstenartur Nov 1, 2024
50172b7
add more plugins to target
carstenartur Nov 1, 2024
f230011
test
carstenartur Nov 1, 2024
29c0c60
extend list of features in target and product
carstenartur Nov 3, 2024
ad23fab
add separate constants for each migration piece
carstenartur Nov 3, 2024
f7b69a9
test update 21
carstenartur Nov 4, 2024
7932f3f
Update maven-publish.yml
carstenartur Nov 5, 2024
bc303ff
Merge branch 'main' into carstenartur-patch-1
carstenartur Nov 17, 2024
d1d44fe
Merge branch 'main' into carstenartur-patch-1
carstenartur Nov 18, 2024
2889fd6
Merge branch 'main' into carstenartur-patch-1
carstenartur Nov 23, 2024
7f8377d
Merge branch 'main' into carstenartur-patch-1
carstenartur Nov 23, 2024
97041ed
Merge branch 'main' into carstenartur-patch-1
carstenartur Dec 5, 2024
2f4892b
Merge branch 'main' into carstenartur-patch-1
carstenartur Dec 8, 2024
d3a19dd
Merge branch 'main' into carstenartur-patch-1
carstenartur Dec 8, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .github/workflows/maven-publish.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,10 +17,10 @@ jobs:

steps:
- uses: actions/checkout@v4
- name: Set up JDK 11
- name: Set up JDK 21
uses: actions/setup-java@v4
with:
java-version: '11'
java-version: '21'
distribution: 'temurin'
cache: maven
server-id: github # Value of the distributionManagement/repository/id field of the pom.xml
Expand Down
295 changes: 148 additions & 147 deletions sandbox_product/sandbox.product
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,21 +1,22 @@
<?xml version="1.0" encoding="UTF-8"?>
<?pde version="3.5"?>

<product name="Sandbox Product" uid="sandbox.bundle.producteclipse" id="org.eclipse.platform.ide" application="org.sandbox.jdt.core.JavaCleanup" version="1.2.0.qualifier" type="features" includeLaunchers="false" autoIncludeRequirements="true">
<product name="Sandbox Product" uid="sandbox.bundle.producteclipse" id="org.eclipse.platform.ide" application="org.eclipse.ui.ide.workbench" version="1.2.0.qualifier" type="features" includeLaunchers="false" autoIncludeRequirements="true">


<configIni use="default">
</configIni>

<launcherArgs>
<programArgs>-clearPersistedState --launcher.defaultAction openFile --launcher.appendVmargs
</programArgs>
<vmArgs>-Xms512m
-Xmx1024m
-XX:+UseG1GC
-XX:+UseStringDeduplication
-Dosgi.requiredJavaVersion=21
-Dosgi.dataAreaRequiresExplicitInit=true
-Dorg.eclipse.swt.graphics.Resource.reportNonDisposed=true
<vmArgs>-Xms512m
-Xmx1024m
-XX:+UseG1GC
-XX:+UseStringDeduplication
-Dosgi.requiredJavaVersion=21
-Dosgi.dataAreaRequiresExplicitInit=true
-Dorg.eclipse.swt.graphics.Resource.reportNonDisposed=true
--add-modules=ALL-SYSTEM
</vmArgs>
<vmArgsMac>-Xdock:icon=../Resources/Eclipse.icns -XstartOnFirstThread -Dorg.eclipse.swt.internal.carbon.smallFonts
Expand Down Expand Up @@ -43,145 +44,145 @@
<license>
<url>http://eclipse.org/legal/epl/notice.php</url>
<text>
Eclipse Foundation Software User Agreement

November 22, 2017

Usage Of Content

THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION
AND/OR OTHER MATERIALS FOR OPEN SOURCE PROJECTS (COLLECTIVELY &amp;quot;CONTENT&amp;quot;). USE OF
THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS AGREEMENT AND/OR THE
TERMS AND CONDITIONS OF LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED
BELOW. BY USING THE CONTENT, YOU AGREE THAT YOUR USE OF THE CONTENT IS GOVERNED
BY THIS AGREEMENT AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE
AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW. IF YOU DO NOT AGREE TO THE
TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND CONDITIONS OF ANY
APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW, THEN YOU
MAY NOT USE THE CONTENT.

Applicable Licenses

Unless otherwise indicated, all Content made available by the Eclipse Foundation
is provided to you under the terms and conditions of the Eclipse Public License
Version 2.0 (&amp;quot;EPL&amp;quot;). A copy of the EPL is provided with this Content and is also
available at http://www.eclipse.org/legal/epl-2.0. For purposes of the EPL,
&amp;quot;Program&amp;quot; will mean the Content.

Content includes, but is not limited to, source code, object code, documentation
and other files maintained in the Eclipse Foundation source code repository
(&amp;quot;Repository&amp;quot;) in software modules (&amp;quot;Modules&amp;quot;) and made available as
downloadable archives (&amp;quot;Downloads&amp;quot;).

- Content may be structured and packaged into modules to facilitate
delivering, extending, and upgrading the Content. Typical modules may
include plug-ins (&amp;quot;Plug-ins&amp;quot;), plug-in fragments (&amp;quot;Fragments&amp;quot;), and
features (&amp;quot;Features&amp;quot;).
- Each Plug-in or Fragment may be packaged as a sub-directory or JAR
(Java&amp;#8482; ARchive) in a directory named &amp;quot;plugins&amp;quot;.
- A Feature is a bundle of one or more Plug-ins and/or Fragments and
associated material. Each Feature may be packaged as a sub-directory in a
directory named &amp;quot;features&amp;quot;. Within a Feature, files named &amp;quot;feature.xml&amp;quot; may
contain a list of the names and version numbers of the Plug-ins and/or
Fragments associated with that Feature.
- Features may also include other Features (&amp;quot;Included Features&amp;quot;). Within a
Feature, files named &amp;quot;feature.xml&amp;quot; may contain a list of the names and
version numbers of Included Features.

The terms and conditions governing Plug-ins and Fragments should be contained in
files named &amp;quot;about.html&amp;quot; (&amp;quot;Abouts&amp;quot;). The terms and conditions governing Features
and Included Features should be contained in files named &amp;quot;license.html&amp;quot;
(&amp;quot;Feature Licenses&amp;quot;). Abouts and Feature Licenses may be located in any
directory of a Download or Module including, but not limited to the following
locations:

- The top-level (root) directory
- Plug-in and Fragment directories
- Inside Plug-ins and Fragments packaged as JARs
- Sub-directories of the directory named &amp;quot;src&amp;quot; of certain Plug-ins
- Feature directories

Note: if a Feature made available by the Eclipse Foundation is installed using
the Provisioning Technology (as defined below), you must agree to a license
(&amp;quot;Feature Update License&amp;quot;) during the installation process. If the Feature
contains Included Features, the Feature Update License should either provide you
with the terms and conditions governing the Included Features or inform you
where you can locate them. Feature Update Licenses may be found in the &amp;quot;license&amp;quot;
property of files named &amp;quot;feature.properties&amp;quot; found within a Feature. Such
Abouts, Feature Licenses, and Feature Update Licenses contain the terms and
conditions (or references to such terms and conditions) that govern your use of
the associated Content in that directory.

THE ABOUTS, FEATURE LICENSES, AND FEATURE UPDATE LICENSES MAY REFER TO THE EPL
OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS. SOME OF THESE
OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):

- Eclipse Public License Version 1.0 (available at
http://www.eclipse.org/legal/epl-v10.html)
- Eclipse Distribution License Version 1.0 (available at
http://www.eclipse.org/licenses/edl-v1.0.html)
- Common Public License Version 1.0 (available at
http://www.eclipse.org/legal/cpl-v10.html)
- Apache Software License 1.1 (available at
http://www.apache.org/licenses/LICENSE)
- Apache Software License 2.0 (available at
http://www.apache.org/licenses/LICENSE-2.0)
- Mozilla Public License Version 1.1 (available at
http://www.mozilla.org/MPL/MPL-1.1.html)

IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR TO
USE OF THE CONTENT. If no About, Feature License, or Feature Update License is
provided, please contact the Eclipse Foundation to determine what terms and
conditions govern that particular Content.

Use of Provisioning Technology

The Eclipse Foundation makes available provisioning software, examples of which
include, but are not limited to, p2 and the Eclipse Update Manager
(&amp;quot;Provisioning Technology&amp;quot;) for the purpose of allowing users to install
software, documentation, information and/or other materials (collectively
&amp;quot;Installable Software&amp;quot;). This capability is provided with the intent of allowing
such users to install, extend and update Eclipse-based products. Information
about packaging Installable Software is available at
http://eclipse.org/equinox/p2/repository_packaging.html (&amp;quot;Specification&amp;quot;).

You may use Provisioning Technology to allow other parties to install
Installable Software. You shall be responsible for enabling the applicable
license agreements relating to the Installable Software to be presented to, and
accepted by, the users of the Provisioning Technology in accordance with the
Specification. By using Provisioning Technology in such a manner and making it
available in accordance with the Specification, you further acknowledge your
agreement to, and the acquisition of all necessary rights to permit the
following:

1. A series of actions may occur (&amp;quot;Provisioning Process&amp;quot;) in which a user may
execute the Provisioning Technology on a machine (&amp;quot;Target Machine&amp;quot;) with the
intent of installing, extending or updating the functionality of an
Eclipse-based product.
2. During the Provisioning Process, the Provisioning Technology may cause third
party Installable Software or a portion thereof to be accessed and copied to
the Target Machine.
3. Pursuant to the Specification, you will provide to the user the terms and
conditions that govern the use of the Installable Software (&amp;quot;Installable
Software Agreement&amp;quot;) and such Installable Software Agreement shall be
accessed from the Target Machine in accordance with the Specification. Such
Installable Software Agreement must inform the user of the terms and
conditions that govern the Installable Software and must solicit acceptance
by the end user in the manner prescribed in such Installable
Software Agreement. Upon such indication of agreement by the user, the
provisioning Technology will complete installation of the
Installable Software.

Cryptography

Content may contain encryption software. The country in which you are currently
may have restrictions on the import, possession, and use, and/or re-export to
another country, of encryption software. BEFORE using any encryption software,
please check the country&amp;apos;s laws, regulations and policies concerning the import,
possession, or use, and re-export of encryption software, to see if this is
permitted.

Java and all Java-based trademarks are trademarks of Oracle Corporation in the
Eclipse Foundation Software User Agreement
November 22, 2017
Usage Of Content
THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION
AND/OR OTHER MATERIALS FOR OPEN SOURCE PROJECTS (COLLECTIVELY &amp;quot;CONTENT&amp;quot;). USE OF
THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS AGREEMENT AND/OR THE
TERMS AND CONDITIONS OF LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED
BELOW. BY USING THE CONTENT, YOU AGREE THAT YOUR USE OF THE CONTENT IS GOVERNED
BY THIS AGREEMENT AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE
AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW. IF YOU DO NOT AGREE TO THE
TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND CONDITIONS OF ANY
APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW, THEN YOU
MAY NOT USE THE CONTENT.
Applicable Licenses
Unless otherwise indicated, all Content made available by the Eclipse Foundation
is provided to you under the terms and conditions of the Eclipse Public License
Version 2.0 (&amp;quot;EPL&amp;quot;). A copy of the EPL is provided with this Content and is also
available at http://www.eclipse.org/legal/epl-2.0. For purposes of the EPL,
&amp;quot;Program&amp;quot; will mean the Content.
Content includes, but is not limited to, source code, object code, documentation
and other files maintained in the Eclipse Foundation source code repository
(&amp;quot;Repository&amp;quot;) in software modules (&amp;quot;Modules&amp;quot;) and made available as
downloadable archives (&amp;quot;Downloads&amp;quot;).
- Content may be structured and packaged into modules to facilitate
delivering, extending, and upgrading the Content. Typical modules may
include plug-ins (&amp;quot;Plug-ins&amp;quot;), plug-in fragments (&amp;quot;Fragments&amp;quot;), and
features (&amp;quot;Features&amp;quot;).
- Each Plug-in or Fragment may be packaged as a sub-directory or JAR
(Java&amp;#8482; ARchive) in a directory named &amp;quot;plugins&amp;quot;.
- A Feature is a bundle of one or more Plug-ins and/or Fragments and
associated material. Each Feature may be packaged as a sub-directory in a
directory named &amp;quot;features&amp;quot;. Within a Feature, files named &amp;quot;feature.xml&amp;quot; may
contain a list of the names and version numbers of the Plug-ins and/or
Fragments associated with that Feature.
- Features may also include other Features (&amp;quot;Included Features&amp;quot;). Within a
Feature, files named &amp;quot;feature.xml&amp;quot; may contain a list of the names and
version numbers of Included Features.
The terms and conditions governing Plug-ins and Fragments should be contained in
files named &amp;quot;about.html&amp;quot; (&amp;quot;Abouts&amp;quot;). The terms and conditions governing Features
and Included Features should be contained in files named &amp;quot;license.html&amp;quot;
(&amp;quot;Feature Licenses&amp;quot;). Abouts and Feature Licenses may be located in any
directory of a Download or Module including, but not limited to the following
locations:
- The top-level (root) directory
- Plug-in and Fragment directories
- Inside Plug-ins and Fragments packaged as JARs
- Sub-directories of the directory named &amp;quot;src&amp;quot; of certain Plug-ins
- Feature directories
Note: if a Feature made available by the Eclipse Foundation is installed using
the Provisioning Technology (as defined below), you must agree to a license
(&amp;quot;Feature Update License&amp;quot;) during the installation process. If the Feature
contains Included Features, the Feature Update License should either provide you
with the terms and conditions governing the Included Features or inform you
where you can locate them. Feature Update Licenses may be found in the &amp;quot;license&amp;quot;
property of files named &amp;quot;feature.properties&amp;quot; found within a Feature. Such
Abouts, Feature Licenses, and Feature Update Licenses contain the terms and
conditions (or references to such terms and conditions) that govern your use of
the associated Content in that directory.
THE ABOUTS, FEATURE LICENSES, AND FEATURE UPDATE LICENSES MAY REFER TO THE EPL
OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS. SOME OF THESE
OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):
- Eclipse Public License Version 1.0 (available at
http://www.eclipse.org/legal/epl-v10.html)
- Eclipse Distribution License Version 1.0 (available at
http://www.eclipse.org/licenses/edl-v1.0.html)
- Common Public License Version 1.0 (available at
http://www.eclipse.org/legal/cpl-v10.html)
- Apache Software License 1.1 (available at
http://www.apache.org/licenses/LICENSE)
- Apache Software License 2.0 (available at
http://www.apache.org/licenses/LICENSE-2.0)
- Mozilla Public License Version 1.1 (available at
http://www.mozilla.org/MPL/MPL-1.1.html)
IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR TO
USE OF THE CONTENT. If no About, Feature License, or Feature Update License is
provided, please contact the Eclipse Foundation to determine what terms and
conditions govern that particular Content.
Use of Provisioning Technology
The Eclipse Foundation makes available provisioning software, examples of which
include, but are not limited to, p2 and the Eclipse Update Manager
(&amp;quot;Provisioning Technology&amp;quot;) for the purpose of allowing users to install
software, documentation, information and/or other materials (collectively
&amp;quot;Installable Software&amp;quot;). This capability is provided with the intent of allowing
such users to install, extend and update Eclipse-based products. Information
about packaging Installable Software is available at
http://eclipse.org/equinox/p2/repository_packaging.html (&amp;quot;Specification&amp;quot;).
You may use Provisioning Technology to allow other parties to install
Installable Software. You shall be responsible for enabling the applicable
license agreements relating to the Installable Software to be presented to, and
accepted by, the users of the Provisioning Technology in accordance with the
Specification. By using Provisioning Technology in such a manner and making it
available in accordance with the Specification, you further acknowledge your
agreement to, and the acquisition of all necessary rights to permit the
following:
1. A series of actions may occur (&amp;quot;Provisioning Process&amp;quot;) in which a user may
execute the Provisioning Technology on a machine (&amp;quot;Target Machine&amp;quot;) with the
intent of installing, extending or updating the functionality of an
Eclipse-based product.
2. During the Provisioning Process, the Provisioning Technology may cause third
party Installable Software or a portion thereof to be accessed and copied to
the Target Machine.
3. Pursuant to the Specification, you will provide to the user the terms and
conditions that govern the use of the Installable Software (&amp;quot;Installable
Software Agreement&amp;quot;) and such Installable Software Agreement shall be
accessed from the Target Machine in accordance with the Specification. Such
Installable Software Agreement must inform the user of the terms and
conditions that govern the Installable Software and must solicit acceptance
by the end user in the manner prescribed in such Installable
Software Agreement. Upon such indication of agreement by the user, the
provisioning Technology will complete installation of the
Installable Software.
Cryptography
Content may contain encryption software. The country in which you are currently
may have restrictions on the import, possession, and use, and/or re-export to
another country, of encryption software. BEFORE using any encryption software,
please check the country&amp;apos;s laws, regulations and policies concerning the import,
possession, or use, and re-export of encryption software, to see if this is
permitted.
Java and all Java-based trademarks are trademarks of Oracle Corporation in the
United States, other countries, or both.
</text>
</license>
Expand Down
Loading
Loading