Changes between Initial Version and Version 1 of Ticket #1959


Ignore:
Timestamp:
Feb 22, 2019, 3:57:41 PM (5 years ago)
Author:
Dimitar Misev
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1959

    • Property Owner changed from Bang Pham Huu to ahambasan
    • Property Status new → assigned

  • Ticket #1959 – Description

    initial v1  
    1 For all Java applications which use Maven, it should have pom.xml only with input properties are passed from CMake, e.g:
     1All Java applications which use Maven have a template pom.xml.in, which is instantiated with values instead of @VARIABLE@ placeholders by cmake with such a command in CMakeLists.txt
     2{{{
     3configure_file(pom.xml.in "${CMAKE_CURRENT_SOURCE_DIR}/pom.xml" @ONLY)
     4}}}
     5Currently the following pom.xml.in exist in the repo:
     6{{{
     7./applications/RRasdaman/pom.xml.in
     8./applications/secore/pom.xml.in
     9./applications/petascope/petascope_main/pom.xml.in
     10./applications/petascope/petascope_core/pom.xml.in
     11./applications/petascope/pom.xml.in
     12./java/pom.xml.in
     13}}}
    214
    3 
     15Instead of configuring pom.xml.in into pom.xml, mvn can be executed to pass variable values directly to a pom.xml, e.g:
    416{{{
    517 COMMAND ${MAVEN_EXECUTABLE} -q install:install-file
    … …  
    921                             -Dversion=${PROJECT_VERSION}
    1022}}}
    11 
    1223and in pom.xml, it can define these properties such as:
    13 
    14 
    1524{{{
    1625<properties>
    … …  
    1827</properties>
    1928}}}
    20 
     29The goal of this ticket is to eliminate pom.xml.in and have only pom.xml