-
Notifications
You must be signed in to change notification settings - Fork 88
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
Avoid redundant versioning of devon4j itself and archetype #118
Labels
enhancement
New feature or request
SCM
Software-configuration-management (maven, travis, etc.)
security
template
maven-archetype to create new application.
Milestone
Comments
I see the following options:
|
hohwille
added a commit
to hohwille/devon4j
that referenced
this issue
Jul 5, 2019
…build devonfw#118: avoid redundant spring.boot.version devonfw#112: renamed test to ObjectMapperFactoryTest
hohwille
added a commit
that referenced
this issue
Jul 6, 2019
Merged
hohwille
pushed a commit
that referenced
this issue
Aug 13, 2019
IMHO all already done via first option. |
This was referenced Nov 28, 2019
hohwille
added a commit
to hohwille/devon4j
that referenced
this issue
Nov 29, 2019
hohwille
added a commit
that referenced
this issue
Dec 2, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
New feature or request
SCM
Software-configuration-management (maven, travis, etc.)
security
template
maven-archetype to create new application.
We have to maintain, update and fix versions often. In most cases we have trouble and issues because almost all versions are both in our devon4j parent POM as well as in the toplvel POM of the archetype.
The text was updated successfully, but these errors were encountered: