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 > < config...
Read more

Reading RSS in Java

In the previous article, I talked about XML.  It is a hierarchical structure of which each node is represented by <tag> enclosed tags.  The closing tag can either be </tag> or <tag /> format if there is no tags in it. RSS is a type of XML format that consists of pre-defined tags.  Here is how you read RSS feeds.  The structure is simple: the top node is "channel" and the articles are under "item" nodes.  Each "item" node contains nodes such as "title", "description", "link", and so on. The RSS reading code therefore is the same as in the way you read XML files.  I created a library called com.github.easai.text that can simplify the process pretty much.  Using the library, the procedure is abstracted and encapsulated.  So load:   < dependency > < groupId > com.github.easai </ groupId > < artifactId > text </ artifactId > < v...
Read more

JPopupMenu

Setting up a right click menu, or popup menu in Java is a tricky but simple procedure.  You would instantiate JPopupMenu, set JMenuItem, attach an ActionListener, set MouseListener.  The beauty of Java GUI structure is in that the listener can be set anywhere.  Any arbitrary component can implement the listener.  A JFrame can have a JPopupMenu and any component can set the MouseListener that set the popup.  And then any component can process the selected JMenuItem. Supposing say a JFrame has a JTable and a JTextArea.  You would want different JPopupMenu.  Each component can possess the JMenuPopup of its own, and the menu can invoke the function in JFrame and not only of JTable nor JTextArea. Which component should have the JPopupMenu (usually the sub-component but can be anywhere) determines what should implements the MouseListener.  The JMenuItem in the JPopupMenu should be 'listened' by an ActionListener that should process the demand. Her...
Read more