DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • OpenAPI From Code With Spring and Java: A Recipe for Your CI
  • Tracking Dependencies Beyond the Build Stage
  • Automating Maven Dependency Upgrades Using AI
  • Web App Load Testing Using Maven Plugins for Apache JMeter, and Analyzing the Results

Trending

  • [closed] DZone's 2025 Developer Community Survey
  • Reactive Kafka With Spring Boot
  • The Developer's Guide to Context-Aware AI: When Your Code Documentation Becomes Intelligent
  • Product-Led Software Delivery: Intelligent Platforms for DevOps at Scale
  1. DZone
  2. Coding
  3. Java
  4. debugging fornax-oaw-m2-plugin maven plugin

debugging fornax-oaw-m2-plugin maven plugin

By 
Peter Butkovic user avatar
Peter Butkovic
·
May. 29, 13 · Interview
Likes (0)
Comment
Save
Tweet
Share
3.6K Views

Join the DZone community and get the full member experience.

Join For Free

Question: Do you need to debug maven plugin: fornax-oaw-m2-plugin ?

If so, go on reading.

You can find the basic info at their home page:

  • usage - http://fornax.itemis.de/confluence/display/fornax/Usage+%28TOM%29
  • advanced configuration - http://fornax.itemis.de/confluence/display/fornax/Configuration+%28TOM%29

However remote debugging topic is not covered there.

The problem with maven plugins might be, that sometimes it's not enough to debug maven run itself (as described in my previous post).

However merging information from the previous links with common remote debugging options I came to solution that simply works for me:

<build>
  <plugins>
    <plugin>
      <groupId>org.fornax.toolsupport</groupId>
      <artifactId>fornax-oaw-m2-plugin</artifactId>
      <version>2.1.1</version>
      <type>pom</type>
      <configuration>
        <!-- [BEGIN] debugging related section -->
        <jvmSettings>
          <jvmArgs>
            <jvmArg>-Xdebug</jvmArg>
            <jvmArg>-Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8100</jvmArg>
            <jvmArg>-Xnoagent</jvmArg>
            <jvmArg>-Djava.compiler=NONE</jvmArg>
          </jvmArgs>
        </jvmSettings>
        <!-- [END] debugging related section -->
      </configuration>
      <executions>
        <execution>
          <phase>generate-sources</phase>
          <goals>
            <goal>run-workflow</goal>
          </goals>
        </execution>
      </executions>
    </plugin>
  </plugins>
</build>

Please note that port to remotely connect to with debugger is 8100 in my sample. Feel free to adapt it based on your setup.

After using the configuration in your run, you should get to point where plugin run gets suspended and waits for remote debugger to connect (to find out how to remotelly debug, see some existing tutorial, like this one: https://dzone.com/articles/how-debug-remote-java-applicat).

That's it. Enjoy your debugging session.

This post is from pb's blog.

Apache Maven

Published at DZone with permission of Peter Butkovic. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • OpenAPI From Code With Spring and Java: A Recipe for Your CI
  • Tracking Dependencies Beyond the Build Stage
  • Automating Maven Dependency Upgrades Using AI
  • Web App Load Testing Using Maven Plugins for Apache JMeter, and Analyzing the Results

Partner Resources

×

Comments

The likes didn't load as expected. Please refresh the page and try again.

  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook