Adding Spring boot application as a dependency to another spring boot application

 The Spring Boot Maven and Gradle plugins both package our application as executable JARs – such a file can't be used in another project since class files are put into BOOT-INF/classes. This is not a bug, but a feature.

In order to share classes with another project, the best approach to take is to create a separate jar containing shared classes, then make it a dependency of all modules that rely on them.

But if that isn't possible, we can configure the plugin to generate a separate jar that can be used as a dependency.

Suppose we have two projects

1- general_definitions_app

2- cutstomer_service_app

we want to add "general_definitions_app" as a dependency to "cutstomer_service_app"

 Steps:

1- open  general_definitions_app , then open the pom.xml file

2- serach for the plugin "spring-boot-maven-plugin" and modify it to be 

<build>
        <plugins>
            <plugin>
                <groupId>org.springframework.boot</groupId>
                <artifactId>spring-boot-maven-plugin</artifactId>
                <configuration>
                    <classifier>exec</classifier>
                </configuration>
            </plugin>
        </plugins>
    </build>

we added <configuration>
                    <classifier>exec</classifier>
                </configuration>

to generate separate jar file with suffix "-exec"

3- click save

4- using CMD , go to the location of the  "general_definitions_app"

issue this command:

mvn clean

mvn install

this will install two separate jars in the local repos ".m2" folder in you machine, the first one is for the spring boot app , the second one will be used as dependencies in other projects

5- open the "cutstomer_service_app" , then open the pom.xml file

6- add dependencies. Example:

<dependency>
            <groupId>org.dhaman.opr</groupId>
            <artifactId>opr-gen-definitions</artifactId>
            <version>0.0.1-SNAPSHOT</version>
            <scope>compile</scope>
        </dependency>

7- update the depencencies

 

Comments

Post a Comment

Popular posts from this blog

Detail entity with row key null cannot find or invalidate its owning entity.

Image
in the model project go to the association. double click on the association and expand the behavior node under relationship tab. make sure that the primary key column is set to DBsequance, if you have a sequence on the database or a function that generate the db sequence from a trigger 3- check on composition association and cascade update key attribute 4- When an entity row is created it's row status is STATUS_NEW . This means row is added in the transaction's list of changes to be validated or posted or committed. This is fine and expected in most of the cases. However, during complex business objects like master-detail there comes the situation where you may want to turn off these validations until both master and detail are available. For such situations to remove the row from transactions's list of changes ADF exposes an api setNewRowStatus(ROW.STATUS_INITIALIZED). This is specifically helpful when master-detail association ...
Read more

Another user has changed the row with primary key oracle.jbo.Key[12 ].

Image
Try these solutions:  make sure that you check "refresh after insert" and refresh after update" for the primary key column in you entity object. in the application module tab Click the Properties tab and select jbo.locking.mode. Double click the “pessimistic”value next to the property to open the field editor and type “optimistic” over the value.Press enter. if error still exist then you must set "refresh after insert" and refresh after update" as true for all attributes in the entity object another way is to execute the View Object after the commit operation to bring back updated data to ViewObject. For this we need to override the  afterCommit()  of ViewObject class as follows:                  public void afterCommit(TransactionEvent){                         executeQuery();                  ...
Read more

setDomainEnv file in weblogic

@ECHO OFF @REM WARNING: This file is created by the Configuration Wizard. @REM Any changes to this script may be lost when adding extensions to this configuration. @REM ************************************************************************* @REM This script is used to setup the needed environment to be able to start Weblogic Server in this domain. @REM @REM This script initializes the following variables before calling commEnv to set other variables: @REM @REM WL_HOME         - The BEA home directory of your WebLogic installation. @REM JAVA_VM         - The desired Java VM to use. You can set this environment variable before calling @REM                   this script to switch between Sun or BEA or just have the default be set. @REM JAVA_HOME       - Location of the version of Java used to start WebLogic @REM                   ...
Read more