I had previously published a post; IIB (v9 and v10) Continuous Integration using Maven and Jenkins. This post is in continuation to that to explain the steps for performing a similar implementation for ACE v11.
The Maven plugin for IIB (iib-maven-plugin) has been enhanced and renamed to ace-maven-plugin for ACE. The plugin supports:-

  1. Building applications and services with referenced static library projects
  2. Building shared libraries independently
  3. Building newly introduced Policy projects independently

Note that the Shared libraries and Policy projects should be deployed before the referencing application/service can be deployed.
Note that the iib-maven-plugin was originally taken from GitHub and was enhanced for IIB v9 & v10.

This CI framework for ACE, built using Maven, Nexus, and Jenkins, can further be enhanced to deploy ACE in a microservices architecture pattern using Docker and Kubernetes. This is out of scope for this article.

In this article I will explain how to build an ACE v11 (App Connect Enterprise v11) project and deploy the bar file to target the Integration Server using Maven and Jenkins.
Here I will take a basic scenario and will explain all the steps. You should be able to use this information to build the CI infrastructure for ACE in your enterprise.

Scenario

Build ACE v11 projects
Create BAR file with all referenced libraries/projects/jars
Overwrite BAR file Node properties and User Defined Properties using Properties file
Deploy this BAR file on target Integration Server

Environment

ACE v11.0.0.4
Maven 3.2.1
Jenkins 2.73.3
ace-maven-plugin
Maven Eclipse Plugin (m2e) v1.5.1
Visual SVN server 3.9.3

Operating System

Windows 10

Step 1: Install ACE v11 runtime and Toolkit.

Make sure that the ACE v11 runtime and Toolkit are installed on your Build server. I assume this is already in place.

Step 2: Install Maven.

I have used the Maven version 3.2.1 here. You may install the latest Maven version. If you are new to Maven, don’t worry. It’s a very simple installation. Below are the steps to do it:

  1. Download Maven Binary Zip archive from https://maven.apache.org/download.cgi
  2. Extract the distribution archive in any directory.
  3. Ensure that you have JDK8 installed and that the JAVA_HOME environment variable is set & points to your JDK installation.
  4. Add the bin directory of the created Maven directory to the PATH environment variable.
  5. Confirm with mvn -v in a new shell. The result should look similar to:


  6. Optionally you can change the local repository location in Maven settings.xml. You can find settings.xml in the ‘conf’ directory inside your Maven installation directory.

Below is the sample settings.xml used for testing. You would need to update the repository & paths with respect to your environment:
Settings

Step 3: Install ace-maven-plugin.

You can download the ace-maven-plugin jar file from the location below:
ace-maven-plugin

Run the Maven install command below to install the plugin in your local repository.

mvn install:install-file -Dfile=ace-maven-plugin.jar -DgroupId=ibm.maven.plugins -DartifactId=ace-maven-plugin -Dversion=11.9.6 -Dpackaging=jar

If you want to deploy the plugin to a remote repository e.g. a Nexus repository, use the mvn deploy command.

Alternately you can download the plugin source code from the location below:
ace-maven-plugin-source

After you download this plugin, unzip the file in any directory. Go to the POM.xml of the plugin and make sure to update the repository paths relevant to your environment. Also you can update the path below; however make sure that the path specified in this ‘workingDirectory’ exists in order to compile the plugin:

<configuration><workingDirectory>C:\releases\MavenPlugins\ace-maven-plugin</workingDirectory></configuration>

You can install this plugin in the central repository of your enterprise. Here we will install it locally.
Open the command prompt and go to the directory where you extracted it. Navigate to the directory where the POM file is present and run the command “mvn clean install”. You may update the version of the plugin in POM.xml before running this command so that the appropriate version number for the plugin is reflected.


Step 4: Convert ACE project to Maven project.

ACE projects are nothing but Eclipse projects. You can convert them to a Maven project using the command line or you can use an m2e plugin to use the ACE toolkit for project conversion. My recommendation is to:

  • Manage application/services as Maven projects. Static library projects should not be converted to Maven projects. During the build, Jenkins or some script can copy the dependent static libraries to the workspace for successful build and bar creation.
  • Shared library projects and Policy projects should be converted to Maven projects and be built/deployed independently.

Here we will use an m2e plugin. Follow the steps below to install the m2e plugin on your ACE toolkit:

  1. Go to Help –> Install New Software
  2. If not already there, add the site http://download.eclipse.org/releases/luna/
  3. Make sure you uncheck the check-box ‘Show only the latest versions of software available’. Install m2e-Maven Integration for Eclipse 1.5.1 and m2e-slf4j over logback logging v1.5.1

  4. m2e-plugin

  5. Complete the installation and restart the ACE toolkit.
  6. Now change the settings in your toolkit to refer to Custom Maven installation instead of Embedded installation. Go to Window–>Preferences–>Maven–>Installations. Add the maven installation directory. If you want to keep using embedded installation, only update the the paths of the settings file.

  7. settings-file

  8. Now checkout the ACE project into your ACE toolkit. Right click on the project –> Configure –> Convert to Maven project.

  9. convert-to-maven-prj

  10. Provide the groupId, artifcatId and Version and select packaging as ‘pom’.

  11. convert-pom

  12. Click on Finish.

Now we need to make configurations in the POM file. This POM is referencing to some variables from the Maven settings file. Below is a complete sample POM for the project I created:
application-pom

Note that I have changed the packaging to ‘ace-bar’.

<groupId>com.anand.test</groupId><artifactId>Test.Application</artifactId><version>1.0.07-SNAPSHOT</version><packaging>ace-bar</packaging><name>${project.artifactId}</name>

Now look at the Configuration block.
toolkitInstallDir: Path of the ACE toolkit installation directory.
barName: Absolute path for bar file.
workspace: Absolute path for workspace.
versionString: Will be appended to Application name in bar file.
cleanBuild: default value is ‘true’.
deployAsSource: default value is ‘true’.
esql21: default value is false. If you are compiling mqsi2.1 esql file then it should be set to true.
applicationName: Name of applications to be included in bar file separated by space.
configPropFileDirectory: Absolute path for properties file to override bar file (UDPs and Node properties). If you are creating a PolicyProject or Shared library where property overriding is not applicable, you should either remove it or keep the empty tag for it.
defaultPropertiesFile: Absolute path for properties file where the plugin dumps all the properties for internal use.
debugWorkspace: Make this ‘true’.
applyBarOverride: ‘true’. If property overriding is not applicable, make it ‘false’.

Make sure that you have updated the repository paths as applicable to your environment. Keep the other settings the same as those in the sample POM.
Now your ACE Maven project is ready to compile. Make sure that the referenced projects are present in ‘workspace’. You can copy referenced library projects into workspace using a Jenkins pre-build step.

Step 5: Setup Jenkins.

Now let us setup Jenkins and trigger the ACE Build from Jenkins.
You can just download the Jenkins WAR and use it with Tomcat or any other server. Here I will use a Windows installer and setup Jenkins as a Windows service.
Download the Windows installer from the url below:

http://jenkins-ci.org/content/thank-you-downloading-windows-installer

The installation is straightforward. Once installation is complete, you can access Jenkins using the url below:
http://localhost:8080

You can do access configuration in Jenkins using LDAP or AD server or local access setup. This part is not in scope of this article. We can continue without doing this access setup.

Go to ‘Manage Jenkins’ –> Configure System
Set ‘Workspace root directory’ and ‘Build record root directory’ as below:

jenkins-workspace
Workspace Root Directory: ${ITEM_ROOTDIR}/workspace
Build Record Root Directory: ${ITEM_ROOTDIR}/builds

If you are using newer version of Jenkins, both these variables have been moved to the Jenkins configuration file. Make sure to update them.

  1. Go to ‘Manage Jenkins’ –> Global tool configuration
  2. Set the Maven Configuration.

  3. jenkins-maven

  4. Give the path to settings.xml
  5. Also add JDK installation for Jenkins.
  6. jenkins-jdk

  7. Save it and exit.

Step 6: Setup Jenkins job to build and deploy ACE Bar.

  1. Click on ‘New Item’ and give a name to the Jenkins job, the same as the corresponding Application/Service/Library/PolicyProject. Select the check-box ‘maven-project’ and click ‘Ok’.
  2. Now the Configuration page is open. We need to provide the configuration here. Give the SVN path of the application/library project

  3. jenkins-svn-step

    Note the value of ‘Local module directory’: ${JOB_NAME}

  4. If there are referenced libraries, make sure to add a pre-build step to copy artifacts from library projects (static and shared). You would create a library project as a ‘freestyle’ project and archive all its artifacts so that they can be copied to the workspace when building the application/service.
  5. Update the Build section as below:

  6. jenkins-build-step

  7. Set the deployment command or batch file having deployment command.

  8. jenkins-deployment-step

  9. Save the configuration.

You can do other additional configurations as per your requirement.
Now you are all set to trigger your build.

I triggered the Jenkins job and it built the bar file, overridden a node property using the properties file and deployed this new bar file to the target integration server. Attached is the sample properties file:
Sample Properties File

Note that this property file has been put inside ACE application/service at the path configured in the POM file (${basedir}\properties)

PropertiesFile

The Output of the Build.

Console Output
Started by user Anand Awasthi
Building in workspace E:\DevOps\Jenkins\jobs\Test.Application\workspace
Checking out a fresh workspace because E:\DevOps\Jenkins\jobs\Test.Application\workspace\Test.Application doesn’t exist
Cleaning local Directory Test.Application
Checking out https://desktop-s0joekp/svn/SourceCode/Test.Application/trunk/Test.Application at revision ‘2019-04-10T02:34:33.566 +0530’ –quiet
Using sole credentials aawasti/****** in realm ‘ VisualSVN Server’
At revision 176

No changes for https://desktop-s0joekp/svn/SourceCode/Test.Application/trunk/Test.Application since the previous build
Parsing POMs
Established TCP socket on 59732
[Test.Application] $ “C:\Program Files\Java\jdk1.8.0_171/bin/java” -cp E:\DevOps\Jenkins\plugins\maven-plugin\WEB-INF\lib\maven32-agent-1.12.jar;E:\DevOps\apache-maven-3.2.1\boot\plexus-classworlds-2.5.1.jar;E:\DevOps\apache-maven-3.2.1/conf/logging jenkins.maven3.agent.Maven32Main E:\DevOps\apache-maven-3.2.1 E:\DevOps\Jenkins\war\WEB-INF\lib\remoting-3.10.2.jar E:\DevOps\Jenkins\plugins\maven-plugin\WEB-INF\lib\maven32-interceptor-1.12.jar E:\DevOps\Jenkins\plugins\maven-plugin\WEB-INF\lib\maven3-interceptor-commons-1.12.jar 59732
<===[JENKINS REMOTING CAPACITY]===>channel started
Executing Maven: -B -f E:\DevOps\Jenkins\jobs\Test.Application\workspace\Test.Application\pom.xml -s E:\DevOps\apache-maven-3.2.1\conf\settings.xml -gs E:\DevOps\apache-maven-3.2.1\conf\settings.xml clean package
[INFO] Scanning for projects…
[INFO] [INFO] Using the builder org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder with a thread count of 1
[INFO] [INFO] ————————————————————————
[INFO] Building Test.Application 1.0.07-SNAPSHOT
[INFO] ————————————————————————
[INFO] [INFO] — maven-clean-plugin:2.5:clean (default-clean) @ Test.Application —
[INFO] [INFO] — ace-maven-plugin:11.9.5.1:prepare-bar-build-workspace (default-prepare-bar-build-workspace) @ Test.Application —
[INFO] [INFO] — ace-maven-plugin:11.9.5.1:validate-bar-build-workspace (default-validate-bar-build-workspace) @ Test.Application —
[INFO] [INFO] — ace-maven-plugin:11.9.5.1:create-bar (default-create-bar) @ Test.Application —
[INFO] Creating bar file: E:\DevOps\Jenkins\jobs\Test.Application\workspace\Test.Application\target\ace\Test.Application.bar
[INFO] executeMqsiCreateBar command: “E:\IBM\ACE\11.0.0.4\tools\mqsicreatebar” -data E:\DevOps\Jenkins\jobs\Test.Application\workspace -b E:\DevOps\Jenkins\jobs\Test.Application\workspace\Test.Application\target\ace\Test.Application.bar -cleanBuild -a Test.Application -deployAsSource -trace -v E:\DevOps\Jenkins\jobs\Test.Application\workspace\Test.Application\target\createbartrace.txt
[INFO] [INFO] E:\DevOps\Jenkins\jobs\Test.Application\workspace>”E:\IBM\ACE\11.0.0.4\tools\mqsicreatebar” -data E:\DevOps\Jenkins\jobs\Test.Application\workspace -b E:\DevOps\Jenkins\jobs\Test.Application\workspace\Test.Application\target\ace\Test.Application.bar -cleanBuild -a Test.Application -deployAsSource -trace -v E:\DevOps\Jenkins\jobs\Test.Application\workspace\Test.Application\target\createbartrace.txt
[INFO] Command log file is set to: E:\DevOps\Jenkins\jobs\Test.Application\workspace\Test.Application\target\createbartrace.txt
[INFO] BIP0986I Command completed successfully.
[INFO] [INFO] [INFO] [INFO] [INFO] Classloaders are not in use. The following jars will be removed from the bar file: **/javacompute_**.jar,**/jplugin2_**.jar
[INFO] [INFO] — ace-maven-plugin:11.9.5.1:validate-configurable-properties (default-validate-configurable-properties) @ Test.Application —
[WARNING] File encoding has not been set, using platform encoding Cp1252, i.e. build is platform dependent!
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory E:\DevOps\Jenkins\jobs\Test.Application\workspace\Test.Application\src\main\resources
[WARNING] File encoding has not been set, using platform encoding Cp1252, i.e. build is platform dependent!
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory E:\DevOps\Jenkins\jobs\Test.Application\workspace\Test.Application\src\test\resources
[INFO] Reading bar file: E:\DevOps\Jenkins\jobs\Test.Application\workspace\Test.Application\target\ace\Test.Application.bar
[INFO] mqsireadbar complete
[INFO] Writing configurable properties to: E:\DevOps\Jenkins\jobs\Test.Application\workspace\Test.Application\target\ace\Test.Application.properties
[INFO] Validating properties files
[INFO] E:\DevOps\Jenkins\jobs\Test.Application\workspace\Test.Application\properties\DEV.properties
[INFO] Applying properties files as bar file overrides
[INFO] E:\DevOps\Jenkins\jobs\Test.Application\workspace\Test.Application\properties\DEV.properties
[INFO] [INFO] E:\DevOps\Jenkins\jobs\Test.Application\workspace\Test.Application>mqsiprofile && mqsiapplybaroverride -b E:\DevOps\Jenkins\jobs\Test.Application\workspace\Test.Application\target\ace\Test.Application.bar -o E:\DevOps\Jenkins\jobs\Test.Application\workspace\Test.Application\target\ace\DEV_1.0.07-SNAPSHOT.bar -p E:\DevOps\Jenkins\jobs\Test.Application\workspace\Test.Application\properties\DEV.properties -k Test.Application -r -v E:\DevOps\Jenkins\jobs\Test.Application\workspace\Test.Application\target\applybaroverridetrace-DEV.txt
[INFO] [INFO] MQSI 11.0.0.4
[INFO] E:\IBM\ACE\11.0.0.4\server
[INFO] [INFO] BIP1138I: Applying overrides using runtime mqsiapplybaroverride…
[INFO] BIP1140I: Overriding property Test_Flow#Result with ‘Hi From DEV service’ in ‘Test.Application.appzip/META-INF/broker.xml’ …
[INFO] BIP1143I: Saving Bar file E:\DevOps\Jenkins\jobs\Test.Application\workspace\Test.Application\target\ace\DEV_1.0.07-SNAPSHOT.bar…
[INFO] [INFO] BIP8071I: Successful command completion.
[INFO] [INFO] — ace-maven-plugin:11.9.5.1:clean-bar-build-workspace (default-clean-bar-build-workspace) @ Test.Application —
[INFO] debugWorkspace enabled – workspace will not be cleaned
[INFO] [INFO] — ace-maven-plugin:11.9.5.1:validate-classloader-approach (default-validate-classloader-approach) @ Test.Application —
[INFO] Reading configurable properties from: E:\DevOps\Jenkins\jobs\Test.Application\workspace\Test.Application\target\ace\Test.Application.properties
[INFO] [INFO] — ace-maven-plugin:11.9.5.1:package-ace-bar (default-package-ace-bar) @ Test.Application —
[INFO] Building zip: E:\DevOps\Jenkins\jobs\Test.Application\workspace\Test.Application\target\Test.Application-1.0.07-SNAPSHOT.zip
[INFO] ————————————————————————
[INFO] BUILD SUCCESS
[INFO] ————————————————————————
[INFO] Total time: 01:16 min
[INFO] Finished at: 2019-04-10T02:35:56+05:30
[INFO] Final Memory: 22M/279M
[INFO] ————————————————————————
[JENKINS] Archiving E:\DevOps\Jenkins\jobs\Test.Application\workspace\Test.Application\pom.xml to com.anand.test/Test.Application/1.0.07-SNAPSHOT/Test.Application-1.0.07-SNAPSHOT.pom
[JENKINS] Archiving E:\DevOps\Jenkins\jobs\Test.Application\workspace\Test.Application\target\Test.Application-1.0.07-SNAPSHOT.zip to com.anand.test/Test.Application/1.0.07-SNAPSHOT/Test.Application-1.0.07-SNAPSHOT.zip
channel stopped
[workspace] $ cmd /c call C:\WINDOWS\TEMP\jenkins7115708312255015150.bat
E:\DevOps\Jenkins\jobs\Test.Application\workspace>mqsiprofile && mqsideploy -i localhost -p 7601 -a E:\DevOps\Jenkins\jobs\Test.Application\workspace\Test.Application\target\ace\DEV_1.0.07-SNAPSHOT.bar

MQSI 11.0.0.4
E:\IBM\ACE\11.0.0.4\server

BIP1040I: Deploying BAR file ‘E:\DevOps\Jenkins\jobs\Test.Application\workspace\Test.Application\target\ace\DEV_1.0.07-SNAPSHOT.bar’ to integration server ‘anand’ …
BIP9332I: Application ‘Test.Application’ has been changed successfully.
BIP1092I: The deployment request was processed successfully.
[WS-CLEANUP] Deleting project workspace…
[WS-CLEANUP] Deferred wipeout is used…
[WS-CLEANUP] done
Finished: SUCCESS

14 comments on"IBM ACE v11 Continuous Integration-Maven-Jenkins"

  1. FranRouss10 May 10, 2019

    I am have a error in my laptop with Window 10 64bit, when execute “mvn clear install” in the the CLI in the directory of project aplication of the toolkit ACE. I execute all step until the step 4 and later execute “mvn clear install”, later generate me the next error in the console:

    [ERROR] Failed to execute goal ibm.maven.plugins:ace-maven-plugin:11.9.6:prepare-bar-build-workspace (default-prepare-bar-build-workspace) on project BG_ESB_AfiliacionUsuario_SEN: Execution default-prepare-bar-build-workspace of goal ibm.maven.plugins:ace-maven-plugin:11.9.6:prepare-bar-build-workspace failed: A required class was missing while executing ibm.maven.plugins:ace-maven-plugin:11.9.6:prepare-bar-build-workspace: org/twdata/maven/mojoexecutor/MojoExecutor
    [ERROR] —————————————————–
    [ERROR] realm = extension>ibm.maven.plugins:ace-maven-plugin:11.9.6
    [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
    [ERROR] urls[0] = file:/C:/Users/Soaint1/.m2/repository/ibm/maven/plugins/ace-maven-plugin/11.9.6/ace-maven-plugin-11.9.6.jar
    [ERROR] urls[1] = file:/C:/Users/Soaint1/.m2/repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
    [ERROR] Number of foreign imports: 1
    [ERROR] import: Entry[import from realm ClassRealm[maven.api, parent: null]]
    [ERROR]
    [ERROR] —————————————————–
    [ERROR] : org.twdata.maven.mojoexecutor.MojoExecutor
    [ERROR] -> [Help 1]
    org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal ibm.maven.plugins:ace-maven-plugin:11.9.6:prepare-bar-build-workspace (default-prepare-bar-build-workspace) on project BG_ESB_AfiliacionUsuario_SEN: Execution default-prepare-bar-build-workspace of goal ibm.maven.plugins:ace-maven-plugin:11.9.6:prepare-bar-build-workspace failed: A required class was missing while executing ibm.maven.plugins:ace-maven-plugin:11.9.6:prepare-bar-build-workspace: org/twdata/maven/mojoexecutor/MojoExecutor

    —————————————————–
    realm = extension>ibm.maven.plugins:ace-maven-plugin:11.9.6
    strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
    urls[0] = file:/C:/Users/Soaint1/.m2/repository/ibm/maven/plugins/ace-maven-plugin/11.9.6/ace-maven-plugin-11.9.6.jar
    urls[1] = file:/C:/Users/Soaint1/.m2/repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
    Number of foreign imports: 1
    import: Entry[import from realm ClassRealm[maven.api, parent: null]]

    —————————————————–

    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
    at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:498)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
    Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-prepare-bar-build-workspace of goal ibm.maven.plugins:ace-maven-plugin:11.9.6:prepare-bar-build-workspace failed: A required class was missing while executing ibm.maven.plugins:ace-maven-plugin:11.9.6:prepare-bar-build-workspace: org/twdata/maven/mojoexecutor/MojoExecutor

    • AnandAwasthi May 13, 2019

      It looks like maven could not download few dependencies for some reason. Please run the command with “-X” parameter as below:
      “mvn clean install -X”
      It should show you more details and the dependencies that couldn’t be downloaded. You might need to download the dependencies manually and install them locally or deploy to your organizations nexus repository.

      • FranRouss10 May 13, 2019

        The dependencies that were missing in the nexus already add them, as also the MojoExecutor was added in the Nexus Maven repository of the company. And error message that I show you is from the output with the expression ‘-X’ in the command ‘mvn clean install’

        • AnandAwasthi May 14, 2019

          Please confirm that you followed below steps:
          1) Install ace-maven-plugin using mvn install or deploy command
          2) Your maven project ‘BG_ESB_AfiliacionUsuario_SEN’ and referenced ACE projects (library/java) are checked-out in the workspace
          3) To build the project ‘BG_ESB_AfiliacionUsuario_SEN’, run ‘mvn clean package -X’ command.

          Please share the output of step 3.

          • FranRouss10 May 14, 2019

            Ya logre corregirlo, me baje el codigo del ace-maven-plugin y en el tag , agregue la url de mi repositorio central como estaba en settings.xml del Maven local. Construi el archivo .jar, y lo agrege en nexus de la empresa al .jar con el .pom.

            Pero ahora me encuentro con este error:

            [DEBUG] — end configuration —
            [INFO]
            [INFO] — ace-maven-plugin:11.9.6:validate-bar-build-workspace (default-validate-bar-build-workspace) @ BG_ESB_AdministracionUsuarios_ESB —
            [DEBUG] Configuring mojo ibm.maven.plugins:ace-maven-plugin:11.9.6:validate-bar-build-workspace from plugin realm ClassRealm[extension>ibm.maven.plugins:ace-maven-plugin:11.9.6, parent: sun.misc.Launcher$AppClassLoader@4e25154f]
            [DEBUG] Configuring mojo ‘ibm.maven.plugins:ace-maven-plugin:11.9.6:validate-bar-build-workspace’ with basic configurator –>
            [DEBUG] (f) project = MavenProject: com.bgeneral.ce.bc:BG_ESB_AdministracionUsuarios_ESB:0.0.1 @ C:\GitBG\Panama\iib_services\bgp_intf_canal\BG_ESB_AdministracionUsuarios_ESB\pom.xml
            [DEBUG] (f) session = org.apache.maven.execution.MavenSession@7bb004b8
            [DEBUG] (f) unpackDependenciesDirectory = C:\GitBG\Panama\iib_services\bgp_intf_canal\BG_ESB_AdministracionUsuarios_ESB\target\ace\dependencies
            [DEBUG] (f) workspace = C:\GitBG\Panama\iib_services
            [DEBUG] — end configuration —
            [INFO] ————————————————————————
            [INFO] BUILD FAILURE
            [INFO] ————————————————————————
            [INFO] Total time: 8.713 s
            [INFO] Finished at: 2019-05-14T10:48:27-05:00
            [INFO] ————————————————————————
            [ERROR] Failed to execute goal ibm.maven.plugins:ace-maven-plugin:11.9.6:validate-bar-build-workspace (default-validate-bar-build-workspace) on project BG_ESB_AdministracionUsuarios_ESB: Error parsing .project file in: C:\GitBG\Panama\iib_services\.git: UnmarshalException: C:\GitBG\Panama\iib_services\.git\.project (El sistema no puede encontrar el archivo especificado) -> [Help 1]
            org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal ibm.maven.plugins:ace-maven-plugin:11.9.6:validate-bar-build-workspace (default-validate-bar-build-workspace) on project BG_ESB_AdministracionUsuarios_ESB: Error parsing .project file in: C:\GitBG\Panama\iib_services\.git
            at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)
            at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
            at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
            at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
            at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
            at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
            at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
            at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
            at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
            at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
            at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
            at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
            at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
            at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
            at java.lang.reflect.Method.invoke (Method.java:498)
            at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
            at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
            at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
            at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
            Caused by: org.apache.maven.plugin.MojoFailureException: Error parsing .project file in: C:\GitBG\Panama\iib_services\.git
            at ibm.maven.plugins.ace.utils.EclipseProjectUtils.getProjectDescription (EclipseProjectUtils.java:31)
            at ibm.maven.plugins.ace.utils.EclipseProjectUtils.getProjectName (EclipseProjectUtils.java:71)
            at ibm.maven.plugins.ace.mojos.ValidateBarBuildWorkspaceMojo.execute (ValidateBarBuildWorkspaceMojo.java:93)
            at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
            at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
            at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
            at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
            at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
            at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
            at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
            at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
            at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
            at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
            at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
            at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
            at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
            at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
            at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
            at java.lang.reflect.Method.invoke (Method.java:498)
            at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
            at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
            at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
            at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
            Caused by: javax.xml.bind.UnmarshalException
            at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0 (UnmarshallerImpl.java:246)
            at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal (UnmarshallerImpl.java:214)
            at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal (AbstractUnmarshallerImpl.java:157)
            at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal (AbstractUnmarshallerImpl.java:162)
            at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal (AbstractUnmarshallerImpl.java:171)
            at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal (AbstractUnmarshallerImpl.java:189)
            at ibm.maven.plugins.ace.utils.EclipseProjectUtils.unmarshallEclipseProjectFile (EclipseProjectUtils.java:162)
            at ibm.maven.plugins.ace.utils.EclipseProjectUtils.getProjectDescription (EclipseProjectUtils.java:27)
            at ibm.maven.plugins.ace.utils.EclipseProjectUtils.getProjectName (EclipseProjectUtils.java:71)
            at ibm.maven.plugins.ace.mojos.ValidateBarBuildWorkspaceMojo.execute (ValidateBarBuildWorkspaceMojo.java:93)
            at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
            at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
            at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
            at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
            at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
            at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
            at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
            at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
            at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
            at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
            at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
            at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
            at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
            at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
            at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
            at java.lang.reflect.Method.invoke (Method.java:498)
            at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
            at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
            at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
            at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
            Caused by: java.io.FileNotFoundException: C:\GitBG\Panama\iib_services\.git\.project (El sistema no puede encontrar el archivo especificado)
            at java.io.FileInputStream.open0 (Native Method)
            at java.io.FileInputStream.open (FileInputStream.java:195)
            at java.io.FileInputStream. (FileInputStream.java:138)
            at java.io.FileInputStream. (FileInputStream.java:93)
            at sun.net.www.protocol.file.FileURLConnection.connect (FileURLConnection.java:90)
            at sun.net.www.protocol.file.FileURLConnection.getInputStream (FileURLConnection.java:188)
            at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity (XMLEntityManager.java:623)
            at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion (XMLVersionDetector.java:148)
            at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse (XML11Configuration.java:806)
            at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse (XML11Configuration.java:771)
            at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse (XMLParser.java:141)
            at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse (AbstractSAXParser.java:1213)
            at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse (SAXParserImpl.java:643)
            at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0 (UnmarshallerImpl.java:243)
            at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal (UnmarshallerImpl.java:214)
            at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal (AbstractUnmarshallerImpl.java:157)
            at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal (AbstractUnmarshallerImpl.java:162)
            at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal (AbstractUnmarshallerImpl.java:171)
            at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal (AbstractUnmarshallerImpl.java:189)
            at ibm.maven.plugins.ace.utils.EclipseProjectUtils.unmarshallEclipseProjectFile (EclipseProjectUtils.java:162)
            at ibm.maven.plugins.ace.utils.EclipseProjectUtils.getProjectDescription (EclipseProjectUtils.java:27)
            at ibm.maven.plugins.ace.utils.EclipseProjectUtils.getProjectName (EclipseProjectUtils.java:71)
            at ibm.maven.plugins.ace.mojos.ValidateBarBuildWorkspaceMojo.execute (ValidateBarBuildWorkspaceMojo.java:93)
            at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
            at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
            at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
            at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
            at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
            at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
            at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
            at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
            at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
            at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
            at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
            at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
            at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
            at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
            at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
            at java.lang.reflect.Method.invoke (Method.java:498)
            at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
            at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
            at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
            at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
            [ERROR]
            [ERROR]
            [ERROR] For more information about the errors and possible solutions, please read the following articles:
            [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

          • FranRouss10 May 14, 2019

            I already managed to correct it, I downloaded the ace-maven-plugin code and in the tag ‘distributionManagement’, I added the url of my central repository as it was in ‘settings.xml’ of the local Maven. I built the ‘.jar’ file, and added the ‘.jar’ and ‘.pom’ files to the company’s nexus.

            But now I have this error:

            [INFO] ————————————————————————
            [INFO] BUILD FAILURE
            [INFO] ————————————————————————
            [INFO] Total time: 8.713 s
            [INFO] Finished at: 2019-05-14T10:48:27-05:00
            [INFO] ————————————————————————
            [ERROR] Failed to execute goal ibm.maven.plugins:ace-maven-plugin:11.9.6:validate-bar-build-workspace (default-validate-bar-build-workspace) on project BG_ESB_AdministracionUsuarios_ESB: Error parsing .project file in: C:\GitBG\Panama\iib_services\.git: UnmarshalException: C:\GitBG\Panama\iib_services\.git\.project (El sistema no puede encontrar el archivo especificado) -> [Help 1]
            org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal ibm.maven.plugins:ace-maven-plugin:11.9.6:validate-bar-build-workspace (default-validate-bar-build-workspace) on project BG_ESB_AdministracionUsuarios_ESB: Error parsing .project file in: C:\GitBG\Panama\iib_services\.git
            at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)
            at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
            at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
            at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
            at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
            at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
            at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
            at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
            at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
            at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
            at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
            at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
            at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
            at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
            at java.lang.reflect.Method.invoke (Method.java:498)
            at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
            at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
            at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
            at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)

          • FranRouss10 May 14, 2019

            Caused by: org.apache.maven.plugin.MojoFailureException: Error parsing .project file in: C:\GitBG\Panama\iib_services\.git
            at ibm.maven.plugins.ace.utils.EclipseProjectUtils.getProjectDescription (EclipseProjectUtils.java:31)
            at ibm.maven.plugins.ace.utils.EclipseProjectUtils.getProjectName (EclipseProjectUtils.java:71)
            at ibm.maven.plugins.ace.mojos.ValidateBarBuildWorkspaceMojo.execute (ValidateBarBuildWorkspaceMojo.java:93)
            at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
            at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
            at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
            at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
            at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
            at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
            at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
            at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
            at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
            at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
            at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
            at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
            at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
            at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
            at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
            at java.lang.reflect.Method.invoke (Method.java:498)
            at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
            at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
            at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
            at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
            Caused by: javax.xml.bind.UnmarshalException
            at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0 (UnmarshallerImpl.java:246)
            at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal (UnmarshallerImpl.java:214)
            at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal (AbstractUnmarshallerImpl.java:157)
            at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal (AbstractUnmarshallerImpl.java:162)
            at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal (AbstractUnmarshallerImpl.java:171)
            at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal (AbstractUnmarshallerImpl.java:189)
            at ibm.maven.plugins.ace.utils.EclipseProjectUtils.unmarshallEclipseProjectFile (EclipseProjectUtils.java:162)
            at ibm.maven.plugins.ace.utils.EclipseProjectUtils.getProjectDescription (EclipseProjectUtils.java:27)
            at ibm.maven.plugins.ace.utils.EclipseProjectUtils.getProjectName (EclipseProjectUtils.java:71)
            at ibm.maven.plugins.ace.mojos.ValidateBarBuildWorkspaceMojo.execute (ValidateBarBuildWorkspaceMojo.java:93)
            at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
            at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
            at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
            at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
            at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
            at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
            at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
            at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
            at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
            at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
            at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
            at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
            at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
            at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
            at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
            at java.lang.reflect.Method.invoke (Method.java:498)
            at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
            at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
            at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
            at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
            Caused by: java.io.FileNotFoundException: C:\GitBG\Panama\iib_services\.git\.project (El sistema no puede encontrar el archivo especificado)
            at java.io.FileInputStream.open0 (Native Method)
            at java.io.FileInputStream.open (FileInputStream.java:195)
            at java.io.FileInputStream. (FileInputStream.java:138)
            at java.io.FileInputStream. (FileInputStream.java:93)
            at sun.net.www.protocol.file.FileURLConnection.connect (FileURLConnection.java:90)
            at sun.net.www.protocol.file.FileURLConnection.getInputStream (FileURLConnection.java:188)
            at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity (XMLEntityManager.java:623)
            at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion (XMLVersionDetector.java:148)
            at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse (XML11Configuration.java:806)
            at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse (XML11Configuration.java:771)
            at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse (XMLParser.java:141)
            at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse (AbstractSAXParser.java:1213)
            at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse (SAXParserImpl.java:643)
            at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0 (UnmarshallerImpl.java:243)
            at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal (UnmarshallerImpl.java:214)
            at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal (AbstractUnmarshallerImpl.java:157)
            at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal (AbstractUnmarshallerImpl.java:162)
            at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal (AbstractUnmarshallerImpl.java:171)
            at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal (AbstractUnmarshallerImpl.java:189)
            at ibm.maven.plugins.ace.utils.EclipseProjectUtils.unmarshallEclipseProjectFile (EclipseProjectUtils.java:162)
            at ibm.maven.plugins.ace.utils.EclipseProjectUtils.getProjectDescription (EclipseProjectUtils.java:27)
            at ibm.maven.plugins.ace.utils.EclipseProjectUtils.getProjectName (EclipseProjectUtils.java:71)
            at ibm.maven.plugins.ace.mojos.ValidateBarBuildWorkspaceMojo.execute (ValidateBarBuildWorkspaceMojo.java:93)
            at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
            at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
            at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
            at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
            at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
            at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
            at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
            at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
            at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
            at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
            at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
            at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
            at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
            at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
            at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
            at java.lang.reflect.Method.invoke (Method.java:498)
            at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
            at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
            at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
            at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
            [ERROR]
            [ERROR]
            [ERROR] For more information about the errors and possible solutions, please read the following articles:
            [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

          • FranRouss10 May 14, 2019

            I have the next properties in my ‘settings.xml’ of my maven:

            inject-properties

            true

            C:\Program Files\IBM\ACE\11.0.0.4\tools
            C:\Program Files\IBM\ACE\11.0.0.4\server\bin
            C:\GitBG\Panama\iib_services\
            C:\GitBG\Panama\iib_services\perform-workspace
            http://devopscr/nexus/
            false
            C:\GitBG\Panama\iib_services

            and in the ‘.pom’ of Application Project, en el ACE Toolkit. I have en the tag ‘plugins’ the next:

            4.0.0
            com.ce.bc
            BG_ESB_AdministracionUsuarios_ESB
            0.0.1
            ace-bar
            ${project.artifactId}

            package

            .


            ibm.maven.plugins
            ace-maven-plugin
            11.9.6

            ${ace.dir}
            ${project.build.directory}\${project.artifactId}.bar
            ${eclipse.workspace}

            true
            true
            false
            ${project.artifactId}
            ${basedir}\properties
            ${project.build.directory}\properties\DEV.properties
            true
            true

            true

            org.apache.maven.plugins
            maven-javadoc-plugin
            2.10.3

            org.apache.maven.plugins
            maven-release-plugin
            2.4.2

            ${perform.workspace}

            org.apache.maven.plugins
            maven-deploy-plugin
            2.8.2

            org.apache.maven.plugins
            maven-source-plugin
            3.0.0

          • FranRouss10 May 14, 2019

            I have the next properties in my ‘settings.xml’ of my maven:

            inject-properties

            true

            C:\Program Files\IBM\ACE\11.0.0.4\tools
            C:\Program Files\IBM\ACE\11.0.0.4\server\bin
            C:\GitBG\Panama\iib_services\
            C:\GitBG\Panama\iib_services\perform-workspace
            http://devopscr/nexus/
            false
            C:\GitBG\Panama\iib_services

          • FranRouss10 May 14, 2019

            inject-properties

            true

            C:\Program Files\IBM\ACE\11.0.0.4\tools
            C:\Program Files\IBM\ACE\11.0.0.4\server\bin
            C:\GitBG\Panama\iib_services\
            C:\GitBG\Panama\iib_services\perform-workspace
            http://devopscr/nexus/
            false
            C:\GitBG\Panama\iib_services

      • AnandAwasthi May 15, 2019

        For the benefit of others I am replying to your first message. You have resolved the dependency issues as per the thread below. Now the error you are facing is ace-maven-plugin compatibility issue with Github repository. This plugin was tested to work with SVN and TFS only.
        Having said that, I have modified the plugin to work with Github as well. Please download the latest ace-maven-plugin from below url:
        https://github.com/awasthan/ace-maven-plugin.git

        Install this new plugin and update your project pom to reference to this plugin. Let me know if you face any issue.

  2. Ajitesh Shukla May 07, 2019

    Hi Anand,

    We are migrating to Openshift environment, please help us with CI build and deploy process for docker and openshift environment

    Thanks
    Ajitesh

    • AnandAwasthi May 13, 2019

      Hi Ajitesh,
      The ace-maven-plugin attached with this blog-post has been tested in Windows env only. There are some changes required to make it running on docker. I would publish blog-post around ACE-Docker-BuildAutomation soon.

      Thanks,
      Anand

  3. Ajitesh Shukla May 07, 2019

    Hi Team,

    We are migrating to openshift, please help with ACE CI build, deploy process for Docker/Openshift environment.

    Thanks
    Ajitesh

Join The Discussion

Your email address will not be published. Required fields are marked *