Java library management with Maven and Gradle

In the last blog, I showed you some of the cases that uses the library in the Central Repository with Maven.  In the following test cases, I show you how the library can be incorporated into your project by using Maven (ComplexMaven) and Gradle (ComplexGradle).  The projects uses the library called Complex.  Complex is available from the Central Repository.  Maven and Gradle use different configuration files for library dependency.

In case with Maven, the library dependency is in the pom.xml file (POM file).  The file format goes as folllows:

 
        <dependency>
            <groupId>com.github.easai.math</groupId>
            <artifactId>Complex</artifactId>
            <version>0.0.1</version>
        </dependency>

If you are using Gradle, the configuration should be in the build.gradle file.

 
 compile group: 'com.github.easai.math', name: 'Complex', version:'0.0.1'

Now you can instantiate the Complex class.

 
 import com.github.easai.math.Complex;
...
    Complex c=new Complex(1.0,1.0);

You can download the entire projects from GitHub (ComplexMaven, ComplexGradle).

Comments

Post a Comment

Popular posts from this blog

Logging your Maven project with Logback

How do you trace your app?  Well, simple standard output is enough for simple applications.   What if, however, you'd want layered commeting/tracing?  Supposing, say, you do not want lengthy trace info for regular use of your app?  The error reports certainly should be distinguished from debugging info. Logback is a nice package that does the work.  Your app will emit any sort of messages, with proper labels (error, warning, info, debug, trace).  Load the library by editing pom.xml file.   < dependency > < groupId > ch.qos.logback </ groupId > < artifactId > logback-classic </ artifactId > < version > 1.2.2 </ version > </ dependency > The log file should be specified in logback.xml file.  The file should be under src/main/resources.   <? xml version = "1.0" encoding = "UTF-8" ?> <! DOCTYPE logback > < configuration > &
Read more

TreeEditor: Customizing Drag and Drop

JTree is a Java GUI component for tree structure.  The tree structure is represented by nodes ( DefaultMutableTreeNode ).  The path or the placement of the node in the tree is represented by TreePath . DefaultMutableTreeNode selectedNode = (DefaultMutableTreeNode) tree.getLastSelectedPathComponent(); Use TransferHandler for drag and drop.  Supposing a class derived from TransferHandler called MenuTransferHandler handles drag and drop, set the TransferHandler as follows: MenuTransferHandler handler = new MenuTransferHandler(); treeEditor . tree .setTransferHandler(handler); The copied new node should be generated at TransferHandler#createTransferable() .  Here shows the function copy() that may come in handy in writing createTransferable() .   copy() should be called recursively. private DefaultMutableTreeNode copy (TreeNode node) { DefaultMutableTreeNode newNode = new DefaultMutableTreeNode(node); if (!node.isLeaf()) { @Supp
Read more

Spring Tool Suite

The Spring Framework offers a safe webapp framework with integrated Hibernate style database mapping. With Spring Tool Suite, all the config parameter settings are taken care of. Using STS, you can start out writing the Spring app rıght away. A word of caution, it may demand JVM (32bit version). → Spring Tool Suite The default port number 8080. That can be set by specifying it in src/main/resources/application.properties file. server . port = 8090 Using STS, the database mapping called JPA is as simple as specifying in pom.xml. The mapped class should be specified by annotation. As for HTML pages, Thyme leaf is recommended and instead of JSP. < dependencies > < dependency > < groupId > org.springframework.boot </ groupId > < artifactId > spring-boot-starter-data-jpa </ artifactId > </ dependency > < dependency > < groupId > org.springframework.b
Read more