Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / play2war/play2-war-plugin issues and pull requests
#181 - Glassfish can't read some files when play2.1.2 project's war is deployed
Issue -
State: open - Opened by ricardoMogg about 11 years ago
- 6 comments
Labels: bug, core
#181 - Glassfish can't read some files when play2.1.2 project's war is deployed
Issue -
State: open - Opened by ricardoMogg about 11 years ago
- 6 comments
Labels: bug, core
#181 - Glassfish can't read some files when play2.1.2 project's war is deployed
Issue -
State: open - Opened by ricardoMogg about 11 years ago
- 6 comments
Labels: bug, core
#181 - Glassfish can't read some files when play2.1.2 project's war is deployed
Issue -
State: open - Opened by ricardoMogg about 11 years ago
- 6 comments
Labels: bug, core
#167 - Websphere 8.5.5 - models.Customer is NOT an Entity Bean registered with this server
Issue -
State: open - Opened by KevinSheedy over 11 years ago
- 16 comments
#167 - Websphere 8.5.5 - models.Customer is NOT an Entity Bean registered with this server
Issue -
State: open - Opened by KevinSheedy over 11 years ago
- 16 comments
#167 - Websphere 8.5.5 - models.Customer is NOT an Entity Bean registered with this server
Issue -
State: open - Opened by KevinSheedy over 11 years ago
- 16 comments
#167 - Websphere 8.5.5 - models.Customer is NOT an Entity Bean registered with this server
Issue -
State: open - Opened by KevinSheedy over 11 years ago
- 16 comments
#167 - Websphere 8.5.5 - models.Customer is NOT an Entity Bean registered with this server
Issue -
State: open - Opened by KevinSheedy over 11 years ago
- 16 comments
#167 - Websphere 8.5.5 - models.Customer is NOT an Entity Bean registered with this server
Issue -
State: open - Opened by KevinSheedy over 11 years ago
- 16 comments
#167 - Websphere 8.5.5 - models.Customer is NOT an Entity Bean registered with this server
Issue -
State: open - Opened by KevinSheedy over 11 years ago
- 16 comments
#166 - Should request().username() be set by play2war 0.9 if I've set up Tomcat 7 security?
Issue -
State: open - Opened by ckarle over 11 years ago
- 7 comments
Labels: enhancement, core
#166 - Should request().username() be set by play2war 0.9 if I've set up Tomcat 7 security?
Issue -
State: open - Opened by ckarle over 11 years ago
- 7 comments
Labels: enhancement, core
#166 - Should request().username() be set by play2war 0.9 if I've set up Tomcat 7 security?
Issue -
State: open - Opened by ckarle over 11 years ago
- 7 comments
Labels: enhancement, core
#166 - Should request().username() be set by play2war 0.9 if I've set up Tomcat 7 security?
Issue -
State: open - Opened by ckarle over 11 years ago
- 7 comments
Labels: enhancement, core
#157 - Support Caucho Resin
Issue -
State: closed - Opened by dlecan over 11 years ago
- 4 comments
Labels: enhancement
#157 - Support Caucho Resin
Issue -
State: closed - Opened by dlecan over 11 years ago
- 4 comments
Labels: enhancement
#157 - Support Caucho Resin
Issue -
State: closed - Opened by dlecan over 11 years ago
- 4 comments
Labels: enhancement
#149 - TomEE : Servlets named [Play] deployed twice which is not permitted
Issue -
State: closed - Opened by programmist over 11 years ago
- 21 comments
#149 - TomEE : Servlets named [Play] deployed twice which is not permitted
Issue -
State: closed - Opened by programmist over 11 years ago
- 21 comments
#149 - TomEE : Servlets named [Play] deployed twice which is not permitted
Issue -
State: closed - Opened by programmist over 11 years ago
- 21 comments
#149 - TomEE : Servlets named [Play] deployed twice which is not permitted
Issue -
State: closed - Opened by programmist over 11 years ago
- 21 comments
#149 - TomEE : Servlets named [Play] deployed twice which is not permitted
Issue -
State: closed - Opened by programmist over 11 years ago
- 21 comments
#149 - TomEE : Servlets named [Play] deployed twice which is not permitted
Issue -
State: closed - Opened by programmist over 11 years ago
- 21 comments
#124 - Memory leak with Tomcat, Guice and Play 2.1-RC2
Issue -
State: closed - Opened by antoineleclair almost 12 years ago
- 10 comments
Labels: invalid
#124 - Memory leak with Tomcat, Guice and Play 2.1-RC2
Issue -
State: closed - Opened by antoineleclair almost 12 years ago
- 10 comments
Labels: invalid
#124 - Memory leak with Tomcat, Guice and Play 2.1-RC2
Issue -
State: closed - Opened by antoineleclair almost 12 years ago
- 10 comments
Labels: invalid
#124 - Memory leak with Tomcat, Guice and Play 2.1-RC2
Issue -
State: closed - Opened by antoineleclair almost 12 years ago
- 10 comments
Labels: invalid
#124 - Memory leak with Tomcat, Guice and Play 2.1-RC2
Issue -
State: closed - Opened by antoineleclair almost 12 years ago
- 10 comments
Labels: invalid
#124 - Memory leak with Tomcat, Guice and Play 2.1-RC2
Issue -
State: closed - Opened by antoineleclair almost 12 years ago
- 10 comments
Labels: invalid
#110 - closed
Pull Request -
State: closed - Opened by sqs almost 12 years ago
#110 - closed
Pull Request -
State: closed - Opened by sqs almost 12 years ago
#110 - closed
Pull Request -
State: closed - Opened by sqs almost 12 years ago
#110 - closed
Pull Request -
State: closed - Opened by sqs almost 12 years ago
#110 - closed
Pull Request -
State: closed - Opened by sqs almost 12 years ago
#110 - closed
Pull Request -
State: closed - Opened by sqs almost 12 years ago
#108 - [Tomcat7]Leak error and Tomcat is never shutdown
Issue -
State: closed - Opened by takezoe almost 12 years ago
- 6 comments
Labels: invalid
#108 - [Tomcat7]Leak error and Tomcat is never shutdown
Issue -
State: closed - Opened by takezoe almost 12 years ago
- 6 comments
Labels: invalid
#108 - [Tomcat7]Leak error and Tomcat is never shutdown
Issue -
State: closed - Opened by takezoe almost 12 years ago
- 6 comments
Labels: invalid
#108 - [Tomcat7]Leak error and Tomcat is never shutdown
Issue -
State: closed - Opened by takezoe almost 12 years ago
- 6 comments
Labels: invalid
#108 - [Tomcat7]Leak error and Tomcat is never shutdown
Issue -
State: closed - Opened by takezoe almost 12 years ago
- 6 comments
Labels: invalid
#108 - [Tomcat7]Leak error and Tomcat is never shutdown
Issue -
State: closed - Opened by takezoe almost 12 years ago
- 6 comments
Labels: invalid
#108 - [Tomcat7]Leak error and Tomcat is never shutdown
Issue -
State: closed - Opened by takezoe almost 12 years ago
- 6 comments
Labels: invalid
#96 - How to deploy on JBoss 5.1 ?
Issue -
State: closed - Opened by roopajavali about 12 years ago
- 9 comments
Labels: question
#96 - How to deploy on JBoss 5.1 ?
Issue -
State: closed - Opened by roopajavali about 12 years ago
- 9 comments
Labels: question
#96 - How to deploy on JBoss 5.1 ?
Issue -
State: closed - Opened by roopajavali about 12 years ago
- 9 comments
Labels: question
#96 - How to deploy on JBoss 5.1 ?
Issue -
State: closed - Opened by roopajavali about 12 years ago
- 9 comments
Labels: question
#96 - How to deploy on JBoss 5.1 ?
Issue -
State: closed - Opened by roopajavali about 12 years ago
- 9 comments
Labels: question
#79 - WebSocket should be handled
Issue -
State: closed - Opened by dlecan about 12 years ago
- 2 comments
Labels: requirements, core
#79 - WebSocket should be handled
Issue -
State: closed - Opened by dlecan about 12 years ago
- 2 comments
Labels: requirements, core
#79 - WebSocket should be handled
Issue -
State: closed - Opened by dlecan about 12 years ago
- 2 comments
Labels: requirements, core
#79 - WebSocket should be handled
Issue -
State: closed - Opened by dlecan about 12 years ago
- 2 comments
Labels: requirements, core
#79 - WebSocket should be handled
Issue -
State: closed - Opened by dlecan about 12 years ago
- 2 comments
Labels: requirements, core
#79 - WebSocket should be handled
Issue -
State: closed - Opened by dlecan about 12 years ago
- 2 comments
Labels: requirements, core
#79 - WebSocket should be handled
Issue -
State: closed - Opened by dlecan about 12 years ago
- 2 comments
Labels: requirements, core
#79 - WebSocket should be handled
Issue -
State: closed - Opened by dlecan about 12 years ago
- 2 comments
Labels: requirements, core
#54 - Play logger is in conflict with JBoss one
Issue -
State: closed - Opened by dlecan over 12 years ago
- 37 comments
Labels: bug, core
#54 - Play logger is in conflict with JBoss one
Issue -
State: closed - Opened by dlecan over 12 years ago
- 37 comments
Labels: bug, core
#54 - Play logger is in conflict with JBoss one
Issue -
State: closed - Opened by dlecan over 12 years ago
- 37 comments
Labels: bug, core
#54 - Play logger is in conflict with JBoss one
Issue -
State: closed - Opened by dlecan over 12 years ago
- 37 comments
Labels: bug, core
#54 - Play logger is in conflict with JBoss one
Issue -
State: closed - Opened by dlecan over 12 years ago
- 37 comments
Labels: bug, core
#54 - Play logger is in conflict with JBoss one
Issue -
State: closed - Opened by dlecan over 12 years ago
- 37 comments
Labels: bug, core
#54 - Play logger is in conflict with JBoss one
Issue -
State: closed - Opened by dlecan over 12 years ago
- 37 comments
Labels: bug, core
#45 - Upgrade Sbt version to 0.11.3
Pull Request -
State: closed - Opened by roddet over 12 years ago
- 3 comments
#45 - Upgrade Sbt version to 0.11.3
Pull Request -
State: closed - Opened by roddet over 12 years ago
- 3 comments
#45 - Upgrade Sbt version to 0.11.3
Pull Request -
State: closed - Opened by roddet over 12 years ago
- 3 comments
#45 - Upgrade Sbt version to 0.11.3
Pull Request -
State: closed - Opened by roddet over 12 years ago
- 3 comments
#45 - Upgrade Sbt version to 0.11.3
Pull Request -
State: closed - Opened by roddet over 12 years ago
- 3 comments
#45 - Upgrade Sbt version to 0.11.3
Pull Request -
State: closed - Opened by roddet over 12 years ago
- 3 comments
#45 - Upgrade Sbt version to 0.11.3
Pull Request -
State: closed - Opened by roddet over 12 years ago
- 3 comments
#27 - Integration tests should be run on Glassfish 4
Issue -
State: closed - Opened by dlecan over 12 years ago
- 1 comment
Labels: enhancement, core
#27 - Integration tests should be run on Glassfish 4
Issue -
State: closed - Opened by dlecan over 12 years ago
- 1 comment
Labels: enhancement, core
#27 - Integration tests should be run on Glassfish 4
Issue -
State: closed - Opened by dlecan over 12 years ago
- 1 comment
Labels: enhancement, core
#27 - Integration tests should be run on Glassfish 4
Issue -
State: closed - Opened by dlecan over 12 years ago
- 1 comment
Labels: enhancement, core
#27 - Integration tests should be run on Glassfish 4
Issue -
State: closed - Opened by dlecan over 12 years ago
- 1 comment
Labels: enhancement, core
#27 - Integration tests should be run on Glassfish 4
Issue -
State: closed - Opened by dlecan over 12 years ago
- 1 comment
Labels: enhancement, core
#27 - Integration tests should be run on Glassfish 4
Issue -
State: closed - Opened by dlecan over 12 years ago
- 1 comment
Labels: enhancement, core
#16 - Removed an extra resolvers += that was breaking sbt
Pull Request -
State: closed - Opened by imeredith over 12 years ago
- 2 comments
#16 - Removed an extra resolvers += that was breaking sbt
Pull Request -
State: closed - Opened by imeredith over 12 years ago
- 2 comments
#16 - Removed an extra resolvers += that was breaking sbt
Pull Request -
State: closed - Opened by imeredith over 12 years ago
- 2 comments
#16 - Removed an extra resolvers += that was breaking sbt
Pull Request -
State: closed - Opened by imeredith over 12 years ago
- 2 comments
#16 - Removed an extra resolvers += that was breaking sbt
Pull Request -
State: closed - Opened by imeredith over 12 years ago
- 2 comments
#16 - Removed an extra resolvers += that was breaking sbt
Pull Request -
State: closed - Opened by imeredith over 12 years ago
- 2 comments
#16 - Removed an extra resolvers += that was breaking sbt
Pull Request -
State: closed - Opened by imeredith over 12 years ago
- 2 comments