Log message: From: To:
Path:
Author:
Issue:
File name:
File type:
Activity by path
Activity by time
2008-04
Activity by year and month
Activity by author
authors by first/last commit
Core group
Developer turnover
Changes    Collaboration    Timeline    Rss    Widget         
1 - 20 of 62105  Next ›
62105 26.05.2013 03:12:36, by java_re
[maven-release-plugin] prepare for next development iteration
62104 26.05.2013 03:12:34, by java_re
[maven-release-plugin] copy for tag org.glassfish.fighterfish.test.util-1.1.7
62103 26.05.2013 03:12:31, by java_re
[maven-release-plugin] prepare release org.glassfish.fighterfish.test.util-1.1.7
62102 25.05.2013 05:39:01, by danniel1205
Get message by using ResourceBundle before MessageFormat
62101 24.05.2013 18:49:35, by paul_parkinson
GLASSFISH-20532 wrong @Priority and GLASSFISH-20533 rollbackOn dontRollbackOn inheritance fixes and tests
62100 24.05.2013 17:21:10, by phil.zampino
GLASSFISH-20025 - Only explicitly load bean classes (rather than all module classes). Passed QL, CDI devtests, EJB devtests
62099 24.05.2013 17:20:55, by oleksiys
+ remove "exclude" property for findbugs
62098 24.05.2013 08:13:13, by java_re
Set svn property svn:eol-style to files
62097 24.05.2013 01:51:09, by oleksiys
+ should fix the build
62096 24.05.2013 00:03:35, by oleksiys
+ fix copyright headers
62095 23.05.2013 23:49:16, by oleksiys
+ create glassfish-spdy module, which inherits grizzly-spdy + implements glassfish CLI commands to enable spdy
62094 23.05.2013 23:28:50, by tjquinn
GlassFish-13083 - j2ee 1.4 web svc jndi lookup broken gfv301, gfv31b16

The test apps attached to the issue illustrate that in some cases the generated client JAR for a stand-alone app client needs to be augmented with other artifacts, not just those from the app client deployment itself. Originally, the deployment code (which is now responsible for creating the generated client JAR file) was overwriting the generated app client JAR from the stand-alone app client deployment with its own copy. Among other things, the new file contained a minimal manifest which caused the app client launch to fail.

These changes cause the client JAR creation code to merge any content that is already generated into the client JAR (as happens with stand-alone app client deployments) with any artifacts contributed by other modules.

Tests: QL, ejb devtests, deployment devtests, webservices devtests, the test described in the issue
62093 23.05.2013 23:15:46, by oleksiys
+ change grizzly-config dependencies
62092 23.05.2013 20:28:55, by swchan2
enable resourceURLFromLocalJar
62091 23.05.2013 20:28:34, by swchan2
add a new test for ServletContext#getResource, #getResourceAsStream
62090 23.05.2013 20:28:02, by swchan2
allow return code 301 and 302
62089 23.05.2013 20:27:01, by swchan2
add context.xml with antiJARLocking property
62088 23.05.2013 20:26:28, by swchan2
add antiJARLocking property
62087 23.05.2013 20:23:54, by swchan2
fix issue https://java.net/jira/browse/GLASSFISH-20386
("Deployment is slow because of WebappClassLoader.extractResource")
62086 23.05.2013 17:51:08, by andriy.zhdanov
FPP-1782: quick fix to prevent updating domain.xml when not needed (revised)
1 2 3 4 5 6 7 8 9 10 Next