[jira] [Updated] (GERONIMO-5778) Exclude jars from annotation scanning and/or bundle classpath

2012-04-10 Thread Ivan (Updated) (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMO-5778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan updated GERONIMO-5778:
---

Fix Version/s: 3.0-beta-2

 Exclude jars from annotation scanning and/or bundle classpath
 -

 Key: GERONIMO-5778
 URL: https://issues.apache.org/jira/browse/GERONIMO-5778
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: deployment
Affects Versions: 3.0
Reporter: Jarek Gawor
Assignee: Ivan
 Fix For: 3.0-beta-2


 In most cases large web applications with a number of embedded dependencies 
 contain jars that do not need to be scanned for annotations and/or included 
 on bundle class path. So it would be nice to have a way to specify in a 
 deployment descriptor 1) a list of jars that shouldn't be scanned for 
 annotations, and 2) a list of jars that do not need to be included in the 
 bundle class path.
 #2 is probably a bit less useful as the web application archive can always be 
 recreated but #1 might be very useful. It would help to speed up the 
 (re)deployment process.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Updated] (GERONIMO-5813) add name-value configuration entry for the deployment scope

2012-04-08 Thread Ivan (Updated) (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMO-5813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan updated GERONIMO-5813:
---

Attachment: Property-preview.patch

 add name-value configuration entry for the deployment scope
 ---

 Key: GERONIMO-5813
 URL: https://issues.apache.org/jira/browse/GERONIMO-5813
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: deployment
Affects Versions: 3.0-beta-1
Reporter: Ivan
Assignee: Ivan
 Fix For: 3.0, 3.0-beta-2

 Attachments: Property-preview.patch


 Please refer to the discussion from dev mail list
 http://apache-geronimo.328035.n3.nabble.com/Add-name-value-configuration-entry-for-the-deployment-scope-td2485710.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Updated] (GERONIMO-5813) add name-value configuration entry for the deployment scope

2012-03-01 Thread Ivan (Updated) (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMO-5813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan updated GERONIMO-5813:
---

Affects Version/s: (was: 3.0)
   3.0-beta-1
Fix Version/s: 3.0-beta-2
   3.0

 add name-value configuration entry for the deployment scope
 ---

 Key: GERONIMO-5813
 URL: https://issues.apache.org/jira/browse/GERONIMO-5813
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: deployment
Affects Versions: 3.0-beta-1
Reporter: Ivan
Assignee: Ivan
 Fix For: 3.0, 3.0-beta-2


 Please refer to the discussion from dev mail list
 http://apache-geronimo.328035.n3.nabble.com/Add-name-value-configuration-entry-for-the-deployment-scope-td2485710.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Updated] (GERONIMO-6290) Add explicit import-packages for some module builders

2012-02-27 Thread Ivan (Updated) (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMO-6290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan updated GERONIMO-6290:
---

Fix Version/s: 3.0

 Add explicit import-packages for some module builders
 -

 Key: GERONIMO-6290
 URL: https://issues.apache.org/jira/browse/GERONIMO-6290
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: deployment
Affects Versions: 3.0-beta-1
Reporter: Ivan
Assignee: Ivan
 Fix For: 3.0, 3.0-beta-2


 Sometimes, while users include some spec API classes in their applications, 
 it will cause some CCE. Considering that, it is always required to use those 
 api classes from server runtime if the application will take advantage of 
 those features from server, it is better to add those packages explicitly in 
 the defaultEnvironment. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Updated] (GERONIMO-6254) Shared library does not work in the deployment process

2012-01-08 Thread Ivan (Updated) (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMO-6254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan updated GERONIMO-6254:
---

Fix Version/s: 3.0

 Shared library does not work in the deployment process
 --

 Key: GERONIMO-6254
 URL: https://issues.apache.org/jira/browse/GERONIMO-6254
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: deployment
Affects Versions: 3.0-beta-1
Reporter: Ivan
Assignee: Ivan
 Fix For: 3.0, 3.0-beta-2


 In the deployment process, as the temp configuration is kept in the 
 DeploymentConfigurationManager, SharedLibExtender will not find its parents. 
 Will use DependencyManager to look up the dependent bundles instead. There 
 maybe issue in the trunk codes, too. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Updated] (GERONIMO-6204) Decouple OpenWebBeans dependency from web containers

2011-10-28 Thread Ivan (Updated) (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMO-6204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan updated GERONIMO-6204:
---

Attachment: 0003-GERONIMO-6204-Decouple-OpenWebBeans-from-web-contain.patch

 Decouple OpenWebBeans dependency from web containers
 

 Key: GERONIMO-6204
 URL: https://issues.apache.org/jira/browse/GERONIMO-6204
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: Tomcat
Affects Versions: 3.0-beta-1
Reporter: Ivan
Assignee: Ivan
 Attachments: 
 0003-GERONIMO-6204-Decouple-OpenWebBeans-from-web-contain.patch


 Now, even for a simple web application, Geronimo also creates a webbeans 
 context, and it really affect the performance.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Updated] (GERONIMO-6189) web access URL is not included virtual host infomation

2011-10-13 Thread Ivan (Updated) (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMO-6189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan updated GERONIMO-6189:
---

Priority: Minor  (was: Major)

 web access URL is not included virtual host infomation
 --

 Key: GERONIMO-6189
 URL: https://issues.apache.org/jira/browse/GERONIMO-6189
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.1.7, 2.2.1, 3.0
Reporter: Ivan
Priority: Minor

 On the web application administration portlet, the virtual host information 
 is not included in the web access URL

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira