Details
-
Enhancement
-
Resolution: Done
-
Major
-
1.0.0.M2c
-
None
Description
I do see their point here, but it is also useful from our end to make sure we have good license coverage.
As as-* items are not likely to change drastically in the future perhaps we should remove it from them, and have it instead in something /aerogear repo specific. Perhaps the aerogear parent pom.xml if we create it.
This task is to determine if we should remove it, and if so where, if anywhere we should put it.
Attachments
Issue Links
- relates to
-
AEROGEAR-162 as-* archetype projects do not need the license.txt file
- Resolved
1.
|
evaluate an aerogear parent pom | Resolved | Jay Balunas |