add support for libraries to have classes

[steven-terrana]

PR Details

This Pull Request adds support for JTE libraries to contribute classes via a src directory. These classes can be imported from pipeline templates, steps from the same library, or steps from another library.

For example, a library with a src/example/Utility.groovy file of:

package example

class Utility implements Serializable{
  void doThing(steps){ steps.echo "doing a thing" }
}

could be imported and used via:

import example.Utility

Utility u = new Utility()
u.doThing(steps)

Description

The src directory contents of all loaded libraries are synced to a common src directory within the build root directory's jte directory. This happens prior to loading the steps so that the classes are available to the classloader during compilation.

How Has This Been Tested

Manual testing + relevant unit tests.

Types of Changes

• Added Unit Testing
• Docs change / refactoring / dependency upgrade
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• I have added the appropriate label for this PR
• If necessary, I have updated the documentation accordingly.
• All new and existing tests passed.

[nrayapati]

This is really cool @steven-terrana thank you for adding this feature
Hope we are adding support to load classes from the base directory as well so that we can maintain common classes among libraries

[steven-terrana]

Hey @nrayapati - The pattern I would recommend for that would to be to create a utility library that has helper steps and common classes consumed by other libraries.

Would this work for your use case?

[nrayapati]

These classes can be imported from pipeline templates, steps from the same library, or steps from another library.

It sounds like you already mentioned about it in the description that these classes can be used across other libraries as well, so I don't think of a need where we need to maintain classes in the root directory anymore. :) Thank you for quick response.

[nrayapati]

Hey @nrayapati - The pattern I would recommend for that would to be to create a utility library that has helper steps and common classes consumed by other libraries.

Would this work for your use case?

Sounds like a good idea too!

Thank you!