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

Bad version number for Aspectj library #36

Open
blcham opened this issue Feb 28, 2025 · 4 comments
Open

Bad version number for Aspectj library #36

blcham opened this issue Feb 28, 2025 · 4 comments
Assignees
@palagdan

Comments

@blcham
Copy link
Contributor

blcham commented Feb 28, 2025 •
edited
Loading

Image

In some cases mvn compile does not work.
@blcham
Copy link
Contributor Author

blcham commented Feb 28, 2025

@cipmo

@blcham blcham changed the title Bad version number for Aspectj Bad version number for Aspectj library Feb 28, 2025
@blcham
Copy link
Contributor Author

blcham commented Feb 28, 2025 •
edited
Loading

Same issue occurs in s-pipes. Maybe it is inherrited problem from s-pipes-foms.

@blcham
Copy link
Contributor Author

blcham commented Feb 28, 2025

@palagdan

@blcham
Copy link
Contributor Author

blcham commented Feb 28, 2025

Following commands might be useful while debugging:

  • mvn dependency:purge-local-repository
  • mvn clean install -Dmaven.repo.local=/path/to/new-folder
  • mvn spring-boot:run

@blcham blcham assigned palagdan and unassigned blcham Mar 6, 2025
@blcham blcham moved this to In progress in SPipes related projects Mar 6, 2025
@blcham blcham moved this from In progress to Todo in SPipes related projects Mar 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@palagdan palagdan

Labels
None yet
Projects
SPipes related projects
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
3 participants
@blcham @palagdan @cipmo