bitbucket pipeline src/main/java file fetch issue

Aditya Dhatingan

I have a maven project (JAVA)

---

ChatGPT-BitbucketIntegration:

      - step:

          script:

            - echo "System Information:"

            - uname -a

            - echo "OS Information:"

            - cat /etc/os-release

            - echo "Commit ID is $BITBUCKET_COMMIT"

            - mvn exec:java -DcommitId="$BITBUCKET_COMMIT"

This is script of pipeline.

---

The pom.xml file contains 

<plugin>

                <groupId>org.codehaus.mojo</groupId>

                <artifactId>exec-maven-plugin</artifactId>

                <version>3.0.0</version>

                <executions>

                    <execution>

                        <goals>

                            <goal>java</goal>

                        </goals>

                    </execution>

                </executions>

                <configuration>

                    <mainClass>bitbucket.CommitCommenter</mainClass>

                    <arguments>

                        <argument>${commitId}</argument>

                    </arguments>

                    <includeProjectDependencies>true</includeProjectDependencies>

                </configuration>

            </plugin>

---

I am calling the main class in the pipeline script

using command mvn exec:java -DcommitId= "<commitId>"

When I am running the same file locally there is no issue. But on pipeline I am facing the issue 

<span>[WARNING] </span>

14657

<span>java.lang.ClassNotFoundException: bitbucket.CommitCommenter</span>

14658

<span>at java.net.URLClassLoader.findClass (URLClassLoader.java:433)</span>

14659

<span>at java.lang.ClassLoader.loadClass (ClassLoader.java:586)</span>

14660

<span>at java.lang.ClassLoader.loadClass (ClassLoader.java:519)</span>

14661

<span>at org.codehaus.mojo.exec.ExecJavaMojo$1.run (ExecJavaMojo.java:246)</span>

14662

<span>at java.lang.Thread.run (Thread.java:831)</span>

Note: I have two java packages in repository

src.main.java

and 

src.test.java

Patrik S

Hey @Aditya Dhatingan and thank you for reaching out to Community!

Maven framework falls a little outside of my expertise, but since pipeline builds run inside docker containers,  I would suggest in your case to try debugging your pipeline locally with docker to troubleshoot the issue and check if you can identify the fix. With this, you are able to reproduce a local environment very close to pipelines.

If you are able to find the solution to fix the error locally by testing with docker, then you can push the changes to your bitbucket repository and the pipeline should complete successfully as well.

Thank you, @Aditya Dhatingan !

Patrik S