Page tree
Skip to end of metadata
Go to start of metadata
Purpose

This page explains how to reproduce issues using the JEE Maven Http Extractor.

The Maven HTTP Extractor is always associated with Files on your file system package for which Maven alerts have been raised.

Applicable in CAST Version
Release
Yes/No
8.3.x(tick)
8.2.x(tick)
8.1.x(tick)
8.0.x(tick)
Applicable RDBMS
RDBMS
Yes/No
Oracle Server(tick)
Microsoft SQL Server(tick)
CSS2(tick)
Action plan

Perform the following steps to reproduce JEE Maven Http Extractor user issues:

  1. In order to proceed with the below steps, get the Relevant Input (source code is not required since it is a J2EE Maven source code)
  2. Reproduce the alerts logged during the Java source code packaging by following the process in the page Delivery Manager Tool - Information - How to reproduce a DMT issue in Discovery Selection or Validation steps
  3. Check that the maven http url configured in the Maven HTTP package by the user is accessible from your machine by using an Internet browser.
  4. If the http url is accessible :
    1. Create an Automated extraction of required jar files > Maven HTTP repository package and use the customer http url.
    2. Package the full version without forcing the extraction.
  5. If the http url is not accessible :
    1. Retrieve from the relevant input the Maven HTTP repository package the file <APPLICATION UUID>/<VERSION UUID>/<Maven Http repository PACKAGE UUID>/sources. CastSourceTreeDump as described in the page Delivery Manager Tool - Information - DELIVERY Folder Structure and Contents.
      In the index.xml file at the package level, the type name of the Maven Http repository is : dmtdevjeemavenresourcesextractor.MavenResourceFilesPackage :




    2. Create on your local machine a folder named MAVEN HTTP REPO.


    3. Use the tool CASTFolderTreeBuilder to generate a local MAVEN Repository using as source file the file  sources.CastSourceTreeDump:

    4. Create an Automated extraction of required jar files > Maven repository on your file system package
    5. The url must point to the folder MAVEN HTTP REPO you have created

    6. Package the full version without forcing the extraction.




  • No labels