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.

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

Fix #203: Have org.apache.commons.lang in targets #205

Merged

Conversation

Bananeweizen
Copy link
Contributor

The POM repositories and the Eclipse targets are somewhat out of sync.
As a quickfix just add the missing bundle to the Eclipse target. In the
long run I suggest to use a .target file in the Maven build, too,
instead of fetching whatever is available on the repository URLs.

The POM repositories and the Eclipse targets are somewhat out of sync.
As a quickfix just add the missing bundle to the Eclipse target. In the
long run I suggest to use a .target file in the Maven build, too,
instead of fetching whatever is available on the repository URLs.
@vorburger
Copy link
Member

In the long run I suggest to use a .target file in the Maven build, too

or the other way around? I last did this kind of stuff about 5 ago, and forgot the details, but Oomph had these "Targlets" which, from what little I remember, were an alternative to, and better than, checked in .target files? Others may know more about this... The Oomph Wiki may even have some doc, I think I may have actually contributed some of that back at the time. I won't be able to help with this though, sorry. (And this may be best discussed in a new issue with others; closing this.)

@vorburger vorburger merged commit 2cc383b into m2e-code-quality:develop Feb 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants