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
Namespace potential collisions #646
Comments
Hmm, I must admit that I'm a bit surprised by this, too. However, the Javadoc states "The order of the @junit-team/junit-lambda Do you remember why this was implemented this way? |
Team decision: Change implementation to use |
marcphilipp
added
status: in progress
and removed
status: team discussion
status: in progress
labels
Feb 22, 2017
gaganis
added a commit
to gaganis/junit5
that referenced
this issue
Feb 27, 2017
Not taking into account the order of parts made namespace behavior non-intuitive. Closes: junit-team#646
7 tasks
gaganis
added a commit
to gaganis/junit5
that referenced
this issue
Feb 27, 2017
Not taking into account the order of parts made namespace behavior non-intuitive. Closes: junit-team#646
gaganis
added a commit
to gaganis/junit5
that referenced
this issue
Feb 27, 2017
Not taking into account the order of parts made namespace behavior non-intuitive. Closes: junit-team#646
gaganis
added a commit
to gaganis/junit5
that referenced
this issue
Feb 27, 2017
Not taking into account the order of parts made namespace behavior non-intuitive. Closes: junit-team#646
marcphilipp
pushed a commit
that referenced
this issue
Feb 28, 2017
Not taking into account the order of parts made namespace behavior non-intuitive. Fixes #646.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ExtensionContext.Namespace
is implemented via aSet
/HashSet
. This allows for two namespaces to easily collide:Intuitively namespaces should nest, meaning the above two are expected to be different. This can be easily fixed by using a List in the impl.
I'm using https://oss.sonatype.org/content/repositories/snapshots/org/junit/jupiter/junit-jupiter-api/5.0.0-SNAPSHOT/junit-jupiter-api-5.0.0-20170207.113945-373.jar
The text was updated successfully, but these errors were encountered: