[jira] [Created] (GERONIMODEVTOOLS-791) Delete module while server is stopped
Delete module while server is stopped - Key: GERONIMODEVTOOLS-791 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-791 Project: Geronimo-Devtools Issue Type: New Feature Components: eclipse-plugin Affects Versions: 3.0-beta-1 Reporter: Jarek Gawor Right now when an application is removed (i.e. undeployed) from server view in Eclipse when the server is stopped, the application is actually undeployed from the server when the server is restarted. And in the process the application is needlessly started before it is undeployed. I don't know if that's entirely possible but would be nice to actually delete the application when the server is stopped (assuming GEP is connected to a local server). -- 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
Fwd: ASF Board Report - Initial Reminder for Apr 2012
FYI Begin forwarded message: > From: ASF Board > Subject: ASF Board Report - Initial Reminder for Apr 2012 > Date: April 1, 2012 8:24:21 PM EDT > To: Kevan Miller > > > > This email was sent by an automated system on behalf of the ASF Board. > It is an initial reminder to give you plenty of time to prepare the report. > > The meeting is scheduled for Wed, 18 April 2012, 10:00:00 PST and the > deadline for > submitting your report is 1 full week prior to that (Wed, Apr 11th)! > > According to board records, you are listed as the chair of at least one > committee that is due to submit a report this month. [1] [2] > > Details on which project reports are due and how to submit a report > are enclosed below. > > Please submit your report with sufficient time to allow the board members > to review and digest. Again, the very latest you should submit your report > is 1 full week (7days) prior to the board meeting (Wed, Apr 11th). > > If you feel that an error has been made, please consult [1] and if there > is still an issue then contact the board directly. > > As always, PMC chairs are welcome to attend the board meeting. > > Thanks, > The ASF Board > > [1] - https://svn.apache.org/repos/private/committers/board/committee-info.txt > [2] - https://svn.apache.org/repos/private/committers/board/calendar.txt > [3] - https://svn.apache.org/repos/private/committers/board/templates > > > Submitting your Report > -- > > Full details about the process and schedule are in [1]. > > The report should be committed to the meeting agenda in the board directory > in the foundation repository, trying to keep a similar format to the others. > This can be found at: > > https://svn.apache.org/repos/private/foundation/board > > Your report should also be sent in plain-text format to bo...@apache.org > with a Subject line that follows the below format: > >Subject: [REPORT] Project Name > > Cutting and pasting directly from a Wiki is not acceptable due to formatting > issues. Line lengths should be limited to 77 characters. > > > Resolutions > --- > > There are several templates for use for various Board resolutions. > They can be found in [3] and you are encouraged to use them. It is > strongly recommended that if you have a resolution before the board, > you are encouraged to attend that board meeting. > > > ASF Board Reports > - > > Reports are due from you for the following committees: > >- Geronimo
[jira] [Resolved] (GERONIMO-6277) Server cannot start if the installation path includes parenthesis character "(" or ")"
[
https://issues.apache.org/jira/browse/GERONIMO-6277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Forrest Xia resolved GERONIMO-6277.
---
Resolution: Fixed
Fix Version/s: 3.0
Picked up fileinstall 3.2.0 release to fix this issue, committed at
3.0-beta@1308026, trunk@1308027.
> Server cannot start if the installation path includes parenthesis character
> "(" or ")"
> --
>
> Key: GERONIMO-6277
> URL: https://issues.apache.org/jira/browse/GERONIMO-6277
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: startup/shutdown
>Affects Versions: 3.0, 3.0-beta-1, 3.0-beta-2
>Reporter: Forrest Xia
>Assignee: Saphen Qiu
>Priority: Minor
> Fix For: 3.0
>
>
> If you install the server in a folder with parenthesis characters "(" or ")",
> the server won't start. An exception like this:
> D:\tmp\3.0-beta-2 (snapshot)\bin>geronimo run -l
> Using GERONIMO_HOME: D:\tmp\3.0-beta-2 (snapshot)
> Using GERONIMO_TMPDIR: D:\tmp\3.0-beta-2 (snapshot)\var\temp
> Using JRE_HOME:d:\t\jdk\sunjdk6\jre
> __ _
> / /___ _ (_) ___
>/ / __ / _ \/ ___/ __ \/ __ \/ // __ `__ \/ __ \
> / /_/ // __/ / / /_/ / / / / // / / / / / /_/ /
> \/ \___/_/ \/_/ /_/_//_/ /_/ /_/\/
> Apache Geronimo (3.0-beta-2-SNAPSHOT)
> Hit '' for a list of available commands
> and '[cmd] --help' for help on a specific command.
> Hit '' or 'osgi:shutdown' to shutdown Geronimo.
> geronimo> 2012-02-17 16:02:39,572 WARN [FeaturesServiceImpl] Unable to add
> feat
> ures repository
> mvn:org.apache.geronimo.framework/karaf-framework/3.0-beta-2-SNA
> PSHOT/xml/features at startup
> java.lang.RuntimeException: URL
> [mvn:org.apache.geronimo.framework/karaf-framewo
> rk/3.0-beta-2-SNAPSHOT/xml/features] could not be resolved.
> at
> org.ops4j.pax.url.mvn.internal.Connection.getInputStream(Connection.j
> ava:195)
> at
> org.apache.karaf.features.internal.FeatureValidationUtil.validate(Fea
> tureValidationUtil.java:49)
> at
> org.apache.karaf.features.internal.FeaturesServiceImpl.validateReposi
> tory(FeaturesServiceImpl.java:199)
> at
> org.apache.karaf.features.internal.FeaturesServiceImpl.internalAddRep
> ository(FeaturesServiceImpl.java:210)
> at
> org.apache.karaf.features.internal.FeaturesServiceImpl.start(Features
> ServiceImpl.java:918)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.aries.blueprint.utils.ReflectionUtils.invoke(ReflectionUti
> ls.java:226)
> at
> org.apache.aries.blueprint.container.BeanRecipe.invoke(BeanRecipe.jav
> a:824)
> at
> org.apache.aries.blueprint.container.BeanRecipe.runBeanProcInit(BeanR
> ecipe.java:636)
> at
> org.apache.aries.blueprint.container.BeanRecipe.internalCreate(BeanRe
> cipe.java:724)
> at
> org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.ja
> va:64)
> at
> org.apache.aries.blueprint.container.BlueprintRepository.createInstan
> ces(BlueprintRepository.java:219)
> at
> org.apache.aries.blueprint.container.BlueprintRepository.createAll(Bl
> ueprintRepository.java:147)
> at
> org.apache.aries.blueprint.container.BlueprintContainerImpl.instantia
> teEagerComponents(BlueprintContainerImpl.java:640)
> at
> org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(Blu
> eprintContainerImpl.java:331)
> at
> org.apache.aries.blueprint.container.BlueprintContainerImpl.run(Bluep
> rintContainerImpl.java:227)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:44
> 1)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
> access$301(ScheduledThreadPoolExecutor.java:98)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
> run(ScheduledThreadPoolExecutor.java:206)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
> utor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
> .java:908)
> at java.lang.Thread.run(Thread.java:662)
> 2012-02-17 16:02:40,038 WARN [JexlEngine]
> org.apache.aries.blueprint.ext.JexlEx
> pres
Re: Reduce the file copying in the application deployment
On Sat, Mar 31, 2012 at 9:29 PM, Ivan wrote: > Hi, while deploying one common application in the Geronimo server, now we > copy the files for three times, > a. Copy the deployed application file to a temp directory, there are some > comments in the Deployer.java file : > > // todo jar url handling with Sun's VM on Windows leaves a lock on the > module file preventing rebuilds > // to address this we use a gross hack and copy the file to a > temporary directory > // the lock on the file will prevent that being deleted > properly until the URLJarFile has > // been GC'ed. > > b. Extract the application file to a temp directory > c. Copy the extracted application files to the corresponding repository > directory. > > I am thinking that we may only do one time copying action, which is to > extract the application file to the repository directory directly. > For #a, after checking the svn log, it is added long long ago, I am not > sure whether we still have this issue, in my environment, it looks to me > that the file is not locked, may be this only occurs in some special > scenarios. > For #a, I think we may get some clue by referring to https://issues.apache.org/jira/browse/GERONIMO-4037. > For #b, since we also keep the application extracted in the repository > directory, think that it is possible to skip that. > > My idea is to introduce a 'fast.deploy' system property, and it is enabled > by default, with this property configured, the deployer will skip the step > #a and #b. Thoughts ? > Reducing file copy times when deployment is a nice improvement idea, let's move forwards for now :-) > -- > Ivan > -- Thanks! Regards, Forrest
[jira] [Commented] (GERONIMO-6312) Expose OSGi 4.3 core API
[ https://issues.apache.org/jira/browse/GERONIMO-6312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13243674#comment-13243674 ] Forrest Xia commented on GERONIMO-6312: --- 1307717 fixed the compilation failures when using maven 2.2.1, however, I've updated tck env to use maven 3.0.3 now. > Expose OSGi 4.3 core API > > > Key: GERONIMO-6312 > URL: https://issues.apache.org/jira/browse/GERONIMO-6312 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: osgi >Affects Versions: 3.0-beta-1 >Reporter: Jarek Gawor >Assignee: Jarek Gawor > > Geronimo is already using Equinox 3.7 which implements OSGi 4.3 API. However, > the system bundle currently exposes OSGi 4.2 API. > Let's update Geronimo to expose OSGi 4.3 core API. -- 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
