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

ClassInitializer definitions inside package_to_scan only should be considered #170

Open
sswaroopgupta opened this issue Jul 2, 2018 · 2 comments

Comments

@sswaroopgupta
Copy link
Contributor

Actual behavior
All ClassInitializers definitions are considered irrespective of package_to_scan configured.

Steps to replicate

The definition in package initializer RegisterIOC is considered. Only definitions in package_to_scan should be considered.

Version

Gauge version: 1.0.1.nightly-2018-06-27
Commit Hash: 0e3c1fc

Plugins
-------
java (0.6.9.nightly-2018-06-29)

Blocks #161

@0vid1u
Copy link

0vid1u commented Jan 14, 2019

Hi,
Have you any progress with this issue?
Could you suggest an workaround?

Thanks in advance!

Gauge version: 1.0.4.nightly-2018-12-25
Commit Hash: fe5e7da

Plugins

dotnet (0.1.0)
html-report (4.0.6)
java (0.7.0.nightly-2019-01-14)
json-report (0.2.2)
screenshot (0.0.1)
spectacle (0.1.3)

@ajoecker
Copy link
Contributor

Please be cautious with this introduction, as this has impact on existing projects (similar to the multi-line step), which would break afterwards.

@nehashri nehashri added triage and removed tiage labels Feb 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

4 participants