Pet-projects | Pet projects - Projects based on tutorials | Frontend Framework library

I have a Cucumber-Selenium based test written using Spring Boot. The problem is that if I have just one step definition file GoolgeCalcStepDefinition.java then the program works and test passes without any issue but as soon as I added BingSearchStepDefinition.java along with feature file then I get following error.

I googled around on how to configure Spring Boot with Cucumber but most of the examples/articles available online shows only one step definition file.

mvn verify

I have an Spring Boot based java application which is producing a JAR artifact when I run mvn clean install with the name my-nexus-demo-0.0.1-SNAPSHOT.jar.

But when I do mvn clean deploy I see my-nexus-demo-0.0.1-20190806.161150-1.jar deployed in my local filesystem (will be using Nexus in the future). Not sure why it is appending datetime and increment # as suffix when I am using mvn clean deploy command.

I have already mentioned ${project.artifactId} in my pom and also specified false as well.

I have couple of questions here:

1. How can I have the consistent artifact name across .m2 and both SNAPSHOT and RELEASE repos?
2. What's the best practice that a developer should following while building and deploying artifacts? Shouldn't the artifacts names be consistent throughout?

pom.xml

I am getting following error while running my Cucumber Selenium tests using Spring Boot

I have already added Background in the feature file. Not sure how to generalize the parameters that are getting passed in it.

Please guide.

Error:

Let's say I have some pet-projects on Laravel (or any other PHP project with Composer).

They have some similar functionality and I want to extract in into a composer package hosted on GitHub.

What are my actions?

I see this approach:

1. Create a new project (e.g. in PhpStorm). Write an extension with tests (migrate from one of the projects).

2. Create a GitHub repository, push the code there.

3. Add it to packagist.

4. Composer require the package on all projects and install it properly.

This is ok. But what if I need to add some new feature or fix a bug? How do I do it properly?

It's convenient to try it directly on some of the projects, which has the extension installed, but it's strange to edit "vendor" directory, and even if the files are edited, how to push them back to the repository?

It's also awkward to edit the code in the separate PHPStorm project for the repository "blindly" and push it each time, the composer update from the project to see how it works.

Any other convenient flow? Thanks.