Age | Commit message (Collapse) | Author | Files | Lines |
|
Former-commit-id: 16cb8a0af0c8bb1efd1e26f0b9aeb7e1fec36dc0
|
|
onap jenkins use maven-assembly-plugin 2.2-beta-5. without fix, local build use
maven-assembly-plugin 2.4.1 and build fails as:
Assembly is incorrectly configured: null.
to fix local build issue:
1. update to maven-assembly-plugin 2.6
2. add AssemblyId configuration which is needed for assembly >= 2.2
Change-Id: I7b0b4ac61351704b4beab073dda5779d6b6e6152
Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
Former-commit-id: 6485eecefff83d76557aa8aaf33d273d5033d967
|
|
Change-Id: Ida725825312f9be2349cf1a1562c122e61efbcaa
Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
Former-commit-id: 53d11b9c8fa4a13c58f5b248998e9f8ce818e12a
|
|
Starting in version 2.2, maven-assembly-plugin
requires an id tag in the assembly descriptor xmls.
This patch allows the project to be built in
environments that use newer versions of
maven-assembly-plugin.
For details, see:
https://issues.apache.org/jira/browse/MASSEMBLY-517
Change-Id: I95df31b2eb880eb6d2a466eafcc57206f9d3d516
Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
Former-commit-id: 59263d726d0c6811c7608a0cbbbff18f74aa8c22
|
|
Problem seems to be related to version of exec-maven-plugin - version 1.5.0 seems to work correctly
Change-Id: Iafde699687fb06ea1dfd9fa06b04668022007345
Signed-off-by: Timoney, Daniel (dt5972) <dtimoney@att.com>
Former-commit-id: 660e02d8d1fc4a06e756c068f36f9bf74aba3199
|
|
Change-Id: I7ab579fd0d206bf356f36d52dcdf4f71f1fa2680
Signed-off-by: Timoney, Daniel (dt5972) <dtimoney@att.com>
Former-commit-id: 2a9f0edd09581f907e62ec4689b5ac94dd5382ba
|