-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Fix release artifacts so cucumber-clojure can be released. #270
Comments
I don't know how to fix the javadoc issue, but would like to comment on the examples: An updated clojure example is available at https://github.com/nilswloka/cucumber-jvm/tree/new-clojure-example. I will send an pull request for that one once I've released a stable version of the lein-cucumber plugin used in the new example (probably not before lein 2 and cucumber-jvm are stable). |
Awesome! Bring it on. I'll handle the javadoc issue. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Ran into this one again for #1336. Fixed it using: https://vzurczak.wordpress.com/2014/08/01/generate-an-empty-javadoc-jar-file/ <plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<executions>
<execution>
<id>empty-javadoc-jar</id>
<phase>package</phase>
<goals>
<goal>jar</goal>
</goals>
<configuration>
<classifier>javadoc</classifier>
<classesDirectory>${basedir}/javadoc</classesDirectory>
</configuration>
</execution>
</executions>
</plugin> |
/cc @nilswloka @rplevy-draker @hiredman
Release 1.0.0.RC23 does not include cucumber-clojure because sonatype-nexus (where jars are deployed) refuse to release artifacts that don't have javadoc (idiotic, but that's the way it is - see #231).
The workaround is to include a dummy java class (or perhaps a package.html) in cucumber-clojure now that the entire backend is implemented in clojure.
At the same time, we should also exclude the various examples from the release.
The text was updated successfully, but these errors were encountered: