Skip to content
This repository has been archived by the owner on Jul 27, 2023. It is now read-only.

Use version range for referencing the parent pom #229

Closed
neeraj-laad opened this issue Aug 22, 2019 · 1 comment
Closed

Use version range for referencing the parent pom #229

neeraj-laad opened this issue Aug 22, 2019 · 1 comment
Milestone
Milestone-7

Comments

@neeraj-laad
Copy link
Contributor

Describe the bug
All maven stacks today use a parent tag to specify which parent pom (stack) to use. When the stack is updated today we are also updating the version of the pom and this means users's do not have the new pom installed in their man cache.

Could we allow a range to be used as parent to avoid local IDE issues? When running inside appsody, the stack always has the right version of pom installed anyway.
@ebullient ebullient mentioned this issue Aug 22, 2019
Merged
4 tasks
@neeraj-laad neeraj-laad added this to the Milestone-5 milestone Aug 28, 2019
@neeraj-laad neeraj-laad modified the milestones: Milestone-5, Milestone-6 Sep 5, 2019
@BarDweller BarDweller mentioned this issue Sep 9, 2019
Closed
6 tasks
@ebullient ebullient mentioned this issue Sep 11, 2019
Closed
This was referenced Sep 11, 2019
Merged
Merged
@neeraj-laad neeraj-laad modified the milestones: Milestone-6, Milestone-7 Sep 18, 2019
@neeraj-laad
Copy link
Contributor Author

All stacks except for quarkus have been updated. There is a separate issue for quarkus work #348

richard-trotter pushed a commit to richard-trotter/stacks that referenced this issue Feb 4, 2020
@groeges
Merge pull request appsody#229 from groeges/master-test-travis_wait
afd89fe 
Use new travis-wait-enhanced function
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
Milestone-7
Development

No branches or pull requests
1 participant
@neeraj-laad