Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Coveralls github actions fails because sample packages conflict on package names #556

Open
hazendaz opened this issue May 9, 2021 · 3 comments
Assignees

Comments

@hazendaz
Copy link
Member

hazendaz commented May 9, 2021

All the samples use the same package space. This is generally not a good idea. In order to fix coveralls so it works during github actions, all the samples need to be put into their own name spaces.

This can be seen by simply running this dummy run locally to emulate the issue. Then go into any sample and the issue goes away.

mvn test jacoco:report coveralls:report -q -D"license.skip=true" -DrepoToken=x -DserviceName=github

Note the above run is not intended to work, just to show the issue then show that isolated samples do not have the problem. If you look at the file in error, it happens in all samples and the lines different in each. Most tools would already complain of this approach type.

Solution would be to add in the type of the package. So sample.mybatis for example should become sample.freemarker.mybatis if in the freemarker package.

@hazendaz hazendaz self-assigned this May 9, 2021
snagapuriosc pushed a commit to snagapuriosc/spring-boot-starter that referenced this issue Oct 6, 2021
package names mybatis#556

changed sample package names as per language and usage.
@snagapuriosc
Copy link

@hazendaz I am trying to work on this as good first issue , Can you please validate if changes all sample packages from sample.mybatis to sample.freemarker or sample.groovy etc ... will fix the package issue ? Also I changed test package accordingly sample.annotation.test.mybatis.

@hazendaz
Copy link
Member Author

hazendaz commented Oct 6, 2021

Hi @snagapuriosc, I had completely lost track of this. That would do it though. Basic issue is the overlaping naming that it has issues with. By splitting those out the names won't overlap any longer. I forget all the exact details of this issue now but nothing was ever done and I think the instructions I left were enough to address. I probably intended that I did that at some point and was a place holder to not forget but have at it as I see you started playing around with that already.

@snagapuriosc
Copy link

@harryharanb @rdx-delhi
Hi Hari, Vatsala.

As discussed to get started on open source contribution I worked on open issue,Can you guys please review and advise on below commit id before I create a PR.
snagapuriosc@4ab48cc

Thanks
Sunil

@kazuki43zoo kazuki43zoo added this to the General Backlog milestone May 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants