- 27 7月, 2013 1 次提交
-
-
由 Vincent Latombe 提交于
Following kohsuke' s review, keeping the item name at the beginning, displaying parent's full display name after between brackets
-
- 20 7月, 2013 15 次提交
-
-
由 Olivier Lamy 提交于
Fix javadoc tag which was not closed, remove ignored @author tag
-
由 Olivier Lamy 提交于
Remove empty @return javadoc tags - add no value
-
由 Olivier Lamy 提交于
Fix javadoc warnings in method parameters
-
由 Olivier Lamy 提交于
Fix malformed @see javadoc reference
-
由 Mark Waite 提交于
Can use source code history to locate original author.
-
由 Mark Waite 提交于
-
由 Seiji Sogabe 提交于
Javadoc fixes for Jenkins core
-
由 Mark Waite 提交于
-
由 Mark Waite 提交于
-
由 Mark Waite 提交于
-
由 Mark Waite 提交于
-
由 Mark Waite 提交于
-
由 Mark Waite 提交于
-
由 Mark Waite 提交于
-
由 Mark Waite 提交于
@sine -> @since @lnk -> @link @author: -> @author Make embedded @ sign literal in one case where it is literal
-
- 19 7月, 2013 5 次提交
-
-
由 Jesse Glick 提交于
-
由 Ulli Hafner 提交于
Fix small typo
-
由 ssogabe 提交于
-
由 Wynn Netherland 提交于
-
由 Jesse Glick 提交于
Also ensuring that Jenkins configuration is saved after new XML is POSTed.
-
- 18 7月, 2013 19 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
... as the newer Groovy compiler produces the proper enclosing class infromation.
-
由 Kohsuke Kawaguchi 提交于
It turns out that Groovy compiler we use to compile src/test/groovy was not properly generating the 'enclosing class' information inside *.class, which was causing the load failure of the descriptors marked by @TestExtension in test code. To fix this and forestall other possible GMaven related issues, I decided to bump up the GMaven version. As it turns out, Codehaus GMaven had ceased the development of the 1.x branch, so I initially tried 2.x release line. The 2.x release line got rid of the stub generation functionality, which we badly need for annotation processing. It instead recommend using Eclipse compiler to jointly compile Java and Groovy source code together, but when I tried to compile our tests, it failed to properly handle nested classes. The compiler quality appears quite premature. I was then going back to GMaven 1.5, the last 1.x release. I took this opportunity to rebase my local patches in org.kohsuke.gmaven to the latest release, which in my mind gets justified now that the upstream has ceased the development. My local patch to GMaven is captured in GMAVEN-3 and GMAVEN-4 (see http://jira.codehaus.org/browse/GMAVEN-3 and http://jira.codehaus.org/browse/GMAVEN-4). GMAVEN-4 is claimed to be fixed, but when I tried to compile our source tree I discovered that its handling of nested types breaks the generated stub code. In the end, I managed to patch gmaven and posted 1.5-jenkins-1. The bottom line is, we can now use @TestExtension correctly with Groovy tests. Also on the upside, we can get rid of org.kohsuke.gmaven and avoid the current confusion situation of using two GMaven plugins. I'll make a follow-up change to remove org.kohsuke.gmaven from elsewhere in our POM.
-
由 Kohsuke Kawaguchi 提交于
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
If so, retry with (6+) slave JVM, setting maven-{compiler,surefire}-plugin properties to point to original.
-
由 Oliver Gondža 提交于
-
由 Jesse Glick 提交于
Otherwise the idiom t.printStackTrace(listener.error("…")) does not work.
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
-
由 Harald Albers 提交于
"Manage Credentials" is defined in credentials-plugin. I will create a pull request for that as well.
-
由 Harald Albers 提交于
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
Merge branch 'prevent-too-recent-bytecode-in-deps' of github.com:Batmat/jenkins into Batmat-prevent-too-recent-bytecode-in-deps
-
由 Jesse Glick 提交于
-