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

Jump to bottom

Use JDT jars from maven central rather than packaging our own #10026

Closed
niloc132 opened this issue Nov 1, 2024 · 0 comments · Fixed by #10082
Closed

Use JDT jars from maven central rather than packaging our own #10026

niloc132 opened this issue Nov 1, 2024 · 0 comments · Fixed by #10082

Comments

@niloc132
Copy link
Member

niloc132 commented Nov 1, 2024 •
edited
Loading

Will help avoid issues like #10025.

A necessary component for #10011.

Light testing seems to suggest that

            <dependency>
                <groupId>org.eclipse.jdt</groupId>
                <artifactId>org.eclipse.jdt.core</artifactId>
                <version>3.32.0</version>
            </dependency>

functions the same as our re-packaged jars, and repackaging may no longer be required at all.
@niloc132 niloc132 mentioned this issue Nov 30, 2024
Closed
@niloc132 niloc132 mentioned this issue Dec 20, 2024
Open
vegegoku added a commit to vegegoku/tools that referenced this issue Jan 9, 2025
@vegegoku
Update jdt
f65c0ed 
Use JDT jars from maven central rather than packaging our own

related to gwtproject/gwt#10026
@vegegoku vegegoku mentioned this issue Jan 9, 2025
Merged
vegegoku added a commit to vegegoku/gwt that referenced this issue Jan 9, 2025
@vegegoku
Update JDT
c6fb281 
Use JDT jars from maven central rather than packaging our own

Fix gwtproject#10026
vegegoku added a commit to vegegoku/gwt that referenced this issue Jan 9, 2025
@vegegoku
Update JDT
ea32cc4 
Use JDT jars from maven central rather than packaging our own

Fix gwtproject#10026
@vegegoku vegegoku mentioned this issue Jan 9, 2025
Merged
vegegoku added a commit to vegegoku/gwt that referenced this issue Jan 9, 2025
@vegegoku
Update JDT
eef092a 
Use JDT jars from maven central rather than packaging our own

Fix gwtproject#10026
vegegoku added a commit to vegegoku/gwt that referenced this issue Feb 9, 2025
@vegegoku
Update JDT
ca58ab0 
Use JDT jars from maven central rather than packaging our own

Fix gwtproject#10026
vegegoku added a commit to vegegoku/gwt that referenced this issue Feb 9, 2025
@vegegoku
Update JDT
202dfb8 
update JDT dependencies to be similar to what we get from maven.

Fix gwtproject#10026
vegegoku added a commit to vegegoku/gwt that referenced this issue Feb 9, 2025
@vegegoku
Update JDT
6a13ad1 
update JDT dependencies to be similar to what we get from maven.

Fix gwtproject#10026
vegegoku added a commit to vegegoku/gwt that referenced this issue Feb 12, 2025
@vegegoku
Update JDT
c834a98 
update JDT dependencies to be similar to what we get from maven.

Fix gwtproject#10026
niloc132 pushed a commit to gwtproject/tools that referenced this issue Feb 12, 2025
@vegegoku
Update JDT to 3.33.0 (#35)
1b06a1a 
Use JDT jars from maven central rather than packaging our own.

Related to gwtproject/gwt#10026
vegegoku added a commit to vegegoku/gwt that referenced this issue Feb 18, 2025
@vegegoku
Update JDT
0895c05 
revert the build action workaround

Fix gwtproject#10026
niloc132 pushed a commit that referenced this issue Feb 19, 2025
@vegegoku
Update to JDT 3.33 (#10082)
a339938 
Use JDT jars from maven central rather than packaging our own.

Fix #10026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update JDT vegegoku/gwt
1 participant
@niloc132