[JBoss JIRA] (JBDS-3276) JBDS-IS Installer
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3276?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3276:
-------------------------------------
Asigning to [~pleacu], because installer side work is done and released to master.
> JBDS-IS Installer
> -----------------
>
> Key: JBDS-3276
> URL: https://issues.jboss.org/browse/JBDS-3276
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer, integration-platform, requirements
> Affects Versions: 8.0.0.GA
> Reporter: Burr Sutter
> Assignee: Paul Leacu
> Attachments: Red Hat JBoss Developer Studio 9.0.0.Alpha2_105.png
>
>
> As a Fuse, integration-focused developer, I need a downloadable installer that will allow me to quickly and easily install JBDS with Fuse capabilities.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBDS-3276) JBDS-IS Installer
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3276?page=com.atlassian.jira.plugin.... ]
Denis Golovin reassigned JBDS-3276:
-----------------------------------
Assignee: Paul Leacu (was: Denis Golovin)
> JBDS-IS Installer
> -----------------
>
> Key: JBDS-3276
> URL: https://issues.jboss.org/browse/JBDS-3276
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer, integration-platform, requirements
> Affects Versions: 8.0.0.GA
> Reporter: Burr Sutter
> Assignee: Paul Leacu
> Attachments: Red Hat JBoss Developer Studio 9.0.0.Alpha2_105.png
>
>
> As a Fuse, integration-focused developer, I need a downloadable installer that will allow me to quickly and easily install JBDS with Fuse capabilities.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19049) Enable JBoss servers to run with java 9
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19049?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19049:
---------------------------------------------
Fuse should not override this - they should not prevent usage of a newer (or older) Java runtime for running their servers if that is what the users need to do.
If the UI is clear about this then this works just as everything else in eclipse as opposed to now it behaves differently by reducing the list for "alternate jre". It is even better since it gives you a warning.
> Enable JBoss servers to run with java 9
> ---------------------------------------
>
> Key: JBIDE-19049
> URL: https://issues.jboss.org/browse/JBIDE-19049
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.2.2.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: Java9
> Fix For: 4.3.0.Beta1
>
>
> I briefly tried to use java 9 for our tooling and to run servers.
> I downloaded it from here:
> https://jdk9.java.net/download/
> {code}
> nattura:8.0.2 rasp$ java -version
> java version "1.9.0-ea"
> Java(TM) SE Runtime Environment (build 1.9.0-ea-b45)
> Java HotSpot(TM) 64-Bit Server VM (build 1.9.0-ea-b45, mixed mode)
> {code}
> I use OS X 10.10 Yosemite.
> There are a couple of problems:
> 1. When I add a WildFly 8.2 server into JBDS 8.0.2, I cannot change the runtime to use java 9 - it seems we restrict that.
> 2. Even if I could, we need to make sure -XX:MaxPermSize is not used in the server launch command. When I tried to run WildFly 8.2 from the terminal, it wouldn't work unless I removed the max perm size argument. Apparently java 9 does not just ignore this parameter (as java 8 did), but it does not allow it at all.
> {code}
> nattura:bin rasp$ ./standalone.sh
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final
> JAVA: /Library/Java/JavaVirtualMachines/jdk1.9.0.jdk/Contents/Home/bin/java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> Unrecognized VM option 'MaxPermSize=256m'
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> {code}
> Of course it's questionable if we should allow java 9 for current servers at all as they don't support it officially. But I would say there is no need to restrict it if it works.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18772:
---------------------------------------------
I reread the links the last time, I also reread them again and I still have the same question.
About copy-or-rename stuff, we do we even have such step ? why don't we actually produce what we want/need ?
The links just shows to me how we currently are doing it which seems to be there just because thats what its been like in the past, not because its the simplest and most maintainable way.
> Include publish.sh in parent pom as versioned maven dependency
> --------------------------------------------------------------
>
> Key: JBIDE-18772
> URL: https://issues.jboss.org/browse/JBIDE-18772
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.3.0.Beta1
>
>
> instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses.
> suggestion:
> publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing.
> What this helps with is:
> a) can do changes to publish mechanism without affecting every past builds.
> b) more movable build system
> c) isolated testing possible
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19720) NPE in org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath
by Valentin Baciu (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19720?page=com.atlassian.jira.plugi... ]
Valentin Baciu updated JBIDE-19720:
-----------------------------------
Environment: Mac OS X 10.10.3, java full version "1.8.0_25-b17"
> NPE in org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath
> ----------------------------------------------------------------------------
>
> Key: JBIDE-19720
> URL: https://issues.jboss.org/browse/JBIDE-19720
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.2.3.Final
> Environment: Mac OS X 10.10.3, java full version "1.8.0_25-b17"
> Reporter: Valentin Baciu
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.3.0.Beta1
>
>
> java.lang.NullPointerException
> at org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath(EclipseResourceUtil.java:711)
> at org.jboss.tools.common.model.filesystems.impl.Libs.getNewPaths(Libs.java:141)
> at org.jboss.tools.common.model.filesystems.impl.Libs.update(Libs.java:108)
> at org.jboss.tools.common.model.util.EclipseResourceUtil.updateLibs(EclipseResourceUtil.java:535)
> at org.jboss.tools.common.model.util.EclipseResourceUtil.createObjectForResource(EclipseResourceUtil.java:417)
> at org.jboss.tools.jst.web.model.helpers.InnerModelHelper.createXModel(InnerModelHelper.java:40)
> at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.init(ClassPathMonitor.java:60)
> at org.jboss.tools.jst.web.kb.internal.KbProject.setProject(KbProject.java:202)
> at org.eclipse.core.internal.resources.NatureManager.createNature(NatureManager.java:234)
> at org.eclipse.core.internal.resources.Project.getNature(Project.java:448)
> at org.jboss.tools.jst.web.kb.KbProjectFactory.getKbProject(KbProjectFactory.java:71)
> at org.jboss.tools.jst.web.kb.KbProjectFactory.getKbProject(KbProjectFactory.java:38)
> at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.getKbProjects(ClassPathMonitor.java:193)
> at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.validateProjectDependencies(ClassPathMonitor.java:143)
> at org.jboss.tools.jst.web.kb.internal.KbProject.load(KbProject.java:347)
> at org.jboss.tools.jst.web.kb.internal.KbProject.resolveStorage(KbProject.java:315)
> at org.jboss.tools.jst.web.kb.internal.KbProject.resolve(KbProject.java:330)
> at org.jboss.tools.jst.web.kb.internal.KbProject.addKbProject(KbProject.java:216)
> at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.validateProjectDependencies(ClassPathMonitor.java:154)
> at org.jboss.tools.jst.web.kb.internal.KbProject.load(KbProject.java:347)
> at org.jboss.tools.jst.web.kb.internal.KbProject.resolveStorage(KbProject.java:315)
> at org.jboss.tools.jst.web.kb.internal.KbBuilder.build(KbBuilder.java:100)
> at org.jboss.tools.jst.web.kb.KbProjectFactory$1KbBuilderEx.build(KbProjectFactory.java:107)
> at org.jboss.tools.jst.web.kb.KbProjectFactory$1.run(KbProjectFactory.java:122)
> at org.jboss.tools.common.model.XJob.runInWorkspace(XJob.java:192)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Another code path:
> java.lang.NullPointerException
> at org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath(EclipseResourceUtil.java:711)
> at org.jboss.tools.common.model.filesystems.impl.Libs.getNewPaths(Libs.java:141)
> at org.jboss.tools.common.model.filesystems.impl.Libs.update(Libs.java:108)
> at org.jboss.tools.common.model.project.ext.AbstractClassPathMonitor.update(AbstractClassPathMonitor.java:73)
> at org.jboss.tools.jsf.jsf2.bean.build.JSF2ProjectBuilder.build(JSF2ProjectBuilder.java:116)
> at org.jboss.tools.jsf.jsf2.bean.build.JSF2ProjectBuilder.<init>(JSF2ProjectBuilder.java:71)
> at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.load(JSF2Project.java:261)
> at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.resolveStorage(JSF2Project.java:247)
> at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.resolve(JSF2Project.java:254)
> at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project$1.run(JSF2Project.java:172)
> at org.jboss.tools.common.model.XJob.runInWorkspace(XJob.java:192)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-17103) No warning/error is shown when detected runtime fails to be added
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17103?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-17103:
-------------------------------------
I've just investigated this for a bit.
The solution I have in my mind requires changes to an API interface: IRuntimeDetectorDelegate
The problem with this method is twofold:
1) It enforces a workflow where we have each detector initialize a group of definitions, so we have no feedback to know how many were created
2) The existing method initializeRuntimes(List<RuntimeDefinition> runtimeDefinitions); is a void return with no exceptions at all.
An API change would be required to commit this. I'll make a PR just in case, but no promises on it being accepted.
> No warning/error is shown when detected runtime fails to be added
> -----------------------------------------------------------------
>
> Key: JBIDE-17103
> URL: https://issues.jboss.org/browse/JBIDE-17103
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.x
>
>
> When there is a new version of a runtime, e.g. WildFly 8.1, that is not yet supported by the tooling, runtime detection usually detects it alright, but when you then click OK, the runtime+server are not added. And there is no error anywhere at all - we should fix that.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19720) NPE in org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19720?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19720:
-----------------------------------
Fix Version/s: 4.3.0.Beta1
> NPE in org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath
> ----------------------------------------------------------------------------
>
> Key: JBIDE-19720
> URL: https://issues.jboss.org/browse/JBIDE-19720
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.2.3.Final
> Reporter: Valentin Baciu
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.3.0.Beta1
>
>
> java.lang.NullPointerException
> at org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath(EclipseResourceUtil.java:711)
> at org.jboss.tools.common.model.filesystems.impl.Libs.getNewPaths(Libs.java:141)
> at org.jboss.tools.common.model.filesystems.impl.Libs.update(Libs.java:108)
> at org.jboss.tools.common.model.util.EclipseResourceUtil.updateLibs(EclipseResourceUtil.java:535)
> at org.jboss.tools.common.model.util.EclipseResourceUtil.createObjectForResource(EclipseResourceUtil.java:417)
> at org.jboss.tools.jst.web.model.helpers.InnerModelHelper.createXModel(InnerModelHelper.java:40)
> at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.init(ClassPathMonitor.java:60)
> at org.jboss.tools.jst.web.kb.internal.KbProject.setProject(KbProject.java:202)
> at org.eclipse.core.internal.resources.NatureManager.createNature(NatureManager.java:234)
> at org.eclipse.core.internal.resources.Project.getNature(Project.java:448)
> at org.jboss.tools.jst.web.kb.KbProjectFactory.getKbProject(KbProjectFactory.java:71)
> at org.jboss.tools.jst.web.kb.KbProjectFactory.getKbProject(KbProjectFactory.java:38)
> at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.getKbProjects(ClassPathMonitor.java:193)
> at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.validateProjectDependencies(ClassPathMonitor.java:143)
> at org.jboss.tools.jst.web.kb.internal.KbProject.load(KbProject.java:347)
> at org.jboss.tools.jst.web.kb.internal.KbProject.resolveStorage(KbProject.java:315)
> at org.jboss.tools.jst.web.kb.internal.KbProject.resolve(KbProject.java:330)
> at org.jboss.tools.jst.web.kb.internal.KbProject.addKbProject(KbProject.java:216)
> at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.validateProjectDependencies(ClassPathMonitor.java:154)
> at org.jboss.tools.jst.web.kb.internal.KbProject.load(KbProject.java:347)
> at org.jboss.tools.jst.web.kb.internal.KbProject.resolveStorage(KbProject.java:315)
> at org.jboss.tools.jst.web.kb.internal.KbBuilder.build(KbBuilder.java:100)
> at org.jboss.tools.jst.web.kb.KbProjectFactory$1KbBuilderEx.build(KbProjectFactory.java:107)
> at org.jboss.tools.jst.web.kb.KbProjectFactory$1.run(KbProjectFactory.java:122)
> at org.jboss.tools.common.model.XJob.runInWorkspace(XJob.java:192)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Another code path:
> java.lang.NullPointerException
> at org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath(EclipseResourceUtil.java:711)
> at org.jboss.tools.common.model.filesystems.impl.Libs.getNewPaths(Libs.java:141)
> at org.jboss.tools.common.model.filesystems.impl.Libs.update(Libs.java:108)
> at org.jboss.tools.common.model.project.ext.AbstractClassPathMonitor.update(AbstractClassPathMonitor.java:73)
> at org.jboss.tools.jsf.jsf2.bean.build.JSF2ProjectBuilder.build(JSF2ProjectBuilder.java:116)
> at org.jboss.tools.jsf.jsf2.bean.build.JSF2ProjectBuilder.<init>(JSF2ProjectBuilder.java:71)
> at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.load(JSF2Project.java:261)
> at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.resolveStorage(JSF2Project.java:247)
> at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.resolve(JSF2Project.java:254)
> at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project$1.run(JSF2Project.java:172)
> at org.jboss.tools.common.model.XJob.runInWorkspace(XJob.java:192)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19720) NPE in org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19720?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19720:
-----------------------------------
Sprint: Sprint #3 May 2015
> NPE in org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath
> ----------------------------------------------------------------------------
>
> Key: JBIDE-19720
> URL: https://issues.jboss.org/browse/JBIDE-19720
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.2.3.Final
> Reporter: Valentin Baciu
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.3.0.Beta1
>
>
> java.lang.NullPointerException
> at org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath(EclipseResourceUtil.java:711)
> at org.jboss.tools.common.model.filesystems.impl.Libs.getNewPaths(Libs.java:141)
> at org.jboss.tools.common.model.filesystems.impl.Libs.update(Libs.java:108)
> at org.jboss.tools.common.model.util.EclipseResourceUtil.updateLibs(EclipseResourceUtil.java:535)
> at org.jboss.tools.common.model.util.EclipseResourceUtil.createObjectForResource(EclipseResourceUtil.java:417)
> at org.jboss.tools.jst.web.model.helpers.InnerModelHelper.createXModel(InnerModelHelper.java:40)
> at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.init(ClassPathMonitor.java:60)
> at org.jboss.tools.jst.web.kb.internal.KbProject.setProject(KbProject.java:202)
> at org.eclipse.core.internal.resources.NatureManager.createNature(NatureManager.java:234)
> at org.eclipse.core.internal.resources.Project.getNature(Project.java:448)
> at org.jboss.tools.jst.web.kb.KbProjectFactory.getKbProject(KbProjectFactory.java:71)
> at org.jboss.tools.jst.web.kb.KbProjectFactory.getKbProject(KbProjectFactory.java:38)
> at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.getKbProjects(ClassPathMonitor.java:193)
> at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.validateProjectDependencies(ClassPathMonitor.java:143)
> at org.jboss.tools.jst.web.kb.internal.KbProject.load(KbProject.java:347)
> at org.jboss.tools.jst.web.kb.internal.KbProject.resolveStorage(KbProject.java:315)
> at org.jboss.tools.jst.web.kb.internal.KbProject.resolve(KbProject.java:330)
> at org.jboss.tools.jst.web.kb.internal.KbProject.addKbProject(KbProject.java:216)
> at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.validateProjectDependencies(ClassPathMonitor.java:154)
> at org.jboss.tools.jst.web.kb.internal.KbProject.load(KbProject.java:347)
> at org.jboss.tools.jst.web.kb.internal.KbProject.resolveStorage(KbProject.java:315)
> at org.jboss.tools.jst.web.kb.internal.KbBuilder.build(KbBuilder.java:100)
> at org.jboss.tools.jst.web.kb.KbProjectFactory$1KbBuilderEx.build(KbProjectFactory.java:107)
> at org.jboss.tools.jst.web.kb.KbProjectFactory$1.run(KbProjectFactory.java:122)
> at org.jboss.tools.common.model.XJob.runInWorkspace(XJob.java:192)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Another code path:
> java.lang.NullPointerException
> at org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath(EclipseResourceUtil.java:711)
> at org.jboss.tools.common.model.filesystems.impl.Libs.getNewPaths(Libs.java:141)
> at org.jboss.tools.common.model.filesystems.impl.Libs.update(Libs.java:108)
> at org.jboss.tools.common.model.project.ext.AbstractClassPathMonitor.update(AbstractClassPathMonitor.java:73)
> at org.jboss.tools.jsf.jsf2.bean.build.JSF2ProjectBuilder.build(JSF2ProjectBuilder.java:116)
> at org.jboss.tools.jsf.jsf2.bean.build.JSF2ProjectBuilder.<init>(JSF2ProjectBuilder.java:71)
> at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.load(JSF2Project.java:261)
> at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.resolveStorage(JSF2Project.java:247)
> at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.resolve(JSF2Project.java:254)
> at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project$1.run(JSF2Project.java:172)
> at org.jboss.tools.common.model.XJob.runInWorkspace(XJob.java:192)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months