We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The Maven convention is to bump the version and not to change the artifact id. i.e. you have gone from
<dependency> <groupId>net.anthavio</groupId> <artifactId>phanbedder-1.9.8</artifactId> <version>1.0.0</version> <scope>test</scope> </dependency>
to
<dependency> <groupId>net.anthavio</groupId> <artifactId>phanbedder-2.1.1</artifactId> <version>1.0.0</version> <scope>test</scope> </dependency>
Instead of
<dependency> <groupId>net.anthavio</groupId> <artifactId>phanbedder</artifactId> <version>1.9.8</version> <scope>test</scope> </dependency>
<dependency> <groupId>net.anthavio</groupId> <artifactId>phanbedder</artifactId> <version>2.1.1</version> <scope>test</scope> </dependency>
If you keep the artifactId the same then maven repositories/search engines will list all the versions together making it easier to see. e.g. http://mvnrepository.com/artifact/org.springframework/spring-context
The text was updated successfully, but these errors were encountered:
Yeah, that was bit unfortunate decision I made at the start. No reason to change it now as PhantomJS development is pretty much halted https://groups.google.com/forum/m/#!topic/phantomjs/9aI5d-LDuNE Means no more need to release phanbedder
Sorry, something went wrong.
No branches or pull requests
The Maven convention is to bump the version and not to change the artifact id.
i.e. you have gone from
to
Instead of
to
If you keep the artifactId the same then maven repositories/search engines will list all the versions together making it easier to see.
e.g. http://mvnrepository.com/artifact/org.springframework/spring-context
The text was updated successfully, but these errors were encountered: