[JBoss JIRA] (JBDS-3854) Installer: Gulp dist task doesn't report subtasks in correct order
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3854?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3854:
-----------------------------
> Installer: Gulp dist task doesn't report subtasks in correct order
> ------------------------------------------------------------------
>
> Key: JBDS-3854
> URL: https://issues.jboss.org/browse/JBDS-3854
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Pavol Pitonak
> Assignee: Pavol Pitonak
> Labels: Havoc
> Fix For: 10.0.0.Alpha1
>
>
> Gulp task _dist_ log is in wrong order, e.g. dist should finish after clean is finished (caused by mixed usage of runSequence and native Gulp dependent tasks)
> {code}
> [11:40:03] Using gulpfile ~/workspace/developer-platform-install/gulpfile.js
> [11:40:03] Starting 'check-requirements'...
> [11:40:05] Finished 'check-requirements' after 1.74 s
> [11:40:05] Starting 'dist'...
> [11:40:05] Starting 'clean'...
> [11:40:05] Finished 'dist' after 3.05 ms
> [11:40:05] Finished 'clean' after 4.52 ms
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3854) Installer: Gulp dist task doesn't report subtasks in correct order
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3854?page=com.atlassian.jira.plugin.... ]
CDW Engine reassigned JBDS-3854:
--------------------------------
> Installer: Gulp dist task doesn't report subtasks in correct order
> ------------------------------------------------------------------
>
> Key: JBDS-3854
> URL: https://issues.jboss.org/browse/JBDS-3854
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Pavol Pitonak
> Assignee: Pavol Pitonak
> Labels: Havoc
> Fix For: 10.0.0.Alpha1
>
>
> Gulp task _dist_ log is in wrong order, e.g. dist should finish after clean is finished (caused by mixed usage of runSequence and native Gulp dependent tasks)
> {code}
> [11:40:03] Using gulpfile ~/workspace/developer-platform-install/gulpfile.js
> [11:40:03] Starting 'check-requirements'...
> [11:40:05] Finished 'check-requirements' after 1.74 s
> [11:40:05] Starting 'dist'...
> [11:40:05] Starting 'clean'...
> [11:40:05] Finished 'dist' after 3.05 ms
> [11:40:05] Finished 'clean' after 4.52 ms
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3854) Installer: Gulp dist task doesn't report subtasks in correct order
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3854?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3854:
---------------------------------
Target Release: 10.0.0.GA
> Installer: Gulp dist task doesn't report subtasks in correct order
> ------------------------------------------------------------------
>
> Key: JBDS-3854
> URL: https://issues.jboss.org/browse/JBDS-3854
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Pavol Pitonak
> Assignee: Pavol Pitonak
> Labels: Havoc
> Fix For: 10.0.0.Alpha1
>
>
> Gulp task _dist_ log is in wrong order, e.g. dist should finish after clean is finished (caused by mixed usage of runSequence and native Gulp dependent tasks)
> {code}
> [11:40:03] Using gulpfile ~/workspace/developer-platform-install/gulpfile.js
> [11:40:03] Starting 'check-requirements'...
> [11:40:05] Finished 'check-requirements' after 1.74 s
> [11:40:05] Starting 'dist'...
> [11:40:05] Starting 'clean'...
> [11:40:05] Finished 'dist' after 3.05 ms
> [11:40:05] Finished 'clean' after 4.52 ms
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBTIS-674) Deprecate 'SOA 5.x Compatibility' tooling
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-674?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-674:
----------------------------------
Agreed - will deprecate 'JBoss Tools Runtime Detection'
> Deprecate 'SOA 5.x Compatibility' tooling
> -----------------------------------------
>
> Key: JBTIS-674
> URL: https://issues.jboss.org/browse/JBTIS-674
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 9.0.0.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 4.3.0.Final, 9.0.0.GA
>
> Attachments: dep1.png, dep2.png, dep3.png, dep4.png
>
>
> The SOA 5.x Development tooling shall be marked as deprecated starting with 9.0.0.GA. It shall be removed at JBDSIS 10.0.0.GA (Neon). It consists of:
> org.guvnor.tools.feature
> org.jboss.tools.esb.feature
> org.jboss.tools.jbpm3.feature
> org.jboss.tools.jbpm.common.feature
> org.jboss.tools.jbpm.convert.feature
> The runtime detector features will not be deprecated:
> org.jboss.tools.runtime.drools.detector.feature
> org.jboss.tools.runtime.esb.detector.feature
> org.jboss.tools.runtime.jbpm.detector.feature
> FYI - [~apodhrad] [~bbrodt] [~maxandersen] [~ganandan-Redhat] [[~shelly.mcgowan]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBTIS-616) TP update - Locus .Final and latest 4.3.x (Mars)
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-616?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-616.
-----------------------------------
ah... I see... (locus is something like orbit). I checked the JBTIS-TP 4.3.1.Final and all bundles which are also in Locus 1.6.0.Final are in the same version. So, I'm closing this issue.
> TP update - Locus .Final and latest 4.3.x (Mars)
> ------------------------------------------------
>
> Key: JBTIS-616
> URL: https://issues.jboss.org/browse/JBTIS-616
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.3.1.Beta1b-TP
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 4.3.1.CR1-TP
>
>
> *Reason:* Update to Locus .Final and latest 4.3.x CR1 bits
> *Project page/sources:* ...
> *Version:* 4.3.1.CR1
> *License and owner:* ...
> *Original p2 repo:*
> *JBoss mirror:*
> *Include Sources:* Yes
> *Affected JBoss Tools components:* Integration Stack
> *Include in JBDS:* Yes (JBDSIS)
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> {code}
> < org.jboss.tools.as.test.core [3.1.1.Beta2-v20160121-0132-B81]
> < org.jboss.tools.common.base.test [3.7.1.Beta2-v20160127-2129-B77]
> < org.jboss.tools.community.project.examples.feature.feature.group [3.0.1.Beta2-v20160121-2329-B74]
> < org.jboss.tools.common.test [3.7.1.Beta2-v20160127-2129-B77]
> < org.jboss.tools.project.examples.feature.feature.group [3.0.1.Beta2-v20160121-2329-B74]
> < org.jboss.tools.tests [3.6.1.Beta2-v20160127-2129-B77]
> < org.jboss.tools.community.central.feature.feature.jar [2.0.1.Beta2-v20160121-2329-B74]
> < org.jboss.tools.community.project.examples.feature.feature.jar [3.0.1.Beta2-v20160121-2329-B74]
> < org.jboss.tools.community.central [2.0.1.Beta2-v20160121-2329-B74]
> < org.jboss.tools.community.project.examples [3.0.1.Beta2-v20160121-2329-B74]
> < org.jboss.tools.community.central.feature.feature.group [2.0.1.Beta2-v20160121-2329-B74]
> < org.jboss.tools.common [3.7.1.Beta2-v20160127-2129-B77]
> < org.jboss.tools.jmx.core.test [1.7.1.Beta2-v20160121-0132-B81]
> < org.jboss.tools.project.examples.feature.feature.jar [3.0.1.Beta2-v20160121-2329-B74]
> < org.jboss.tools.project.examples.cheatsheet [3.0.1.Beta2-v20160121-2329-B74]
> < org.jboss.tools.project.examples [3.0.1.Beta2-v20160121-2329-B74]
> > org.jboss.tools.tests [3.6.1.CR1-v20160324-0436-B104]
> > org.jboss.tools.jmx.core.test [1.7.1.CR1-v20160324-2013-B109]
> > org.jboss.tools.common [3.7.1.CR1-v20160324-0436-B104]
> > org.jboss.tools.project.examples.cheatsheet [3.0.1.CR1-v20160324-1911-B99]
> > org.jboss.tools.project.examples.feature.feature.group [3.0.1.CR1-v20160324-1911-B99]
> > org.jboss.tools.project.examples.feature.feature.jar [3.0.1.CR1-v20160324-1911-B99]
> > org.jboss.tools.community.project.examples.feature.feature.group [3.0.1.CR1-v20160324-1911-B99]
> > org.jboss.tools.community.central.feature.feature.group [2.0.1.CR1-v20160324-1911-B99]
> > org.jboss.tools.project.examples [3.0.1.CR1-v20160324-1911-B99]
> > org.jboss.tools.common.base.test [3.7.1.CR1-v20160324-0436-B104]
> > org.jboss.tools.community.project.examples.feature.feature.jar [3.0.1.CR1-v20160324-1911-B99]
> > org.jboss.tools.community.project.examples [3.0.1.CR1-v20160324-1911-B99]
> > org.jboss.tools.as.test.core [3.1.1.CR1-v20160324-2013-B109]
> > org.jboss.tools.common.test [3.7.1.CR1-v20160324-0436-B104]
> > org.jboss.tools.community.central [2.0.1.CR1-v20160324-1911-B99]
> > org.jboss.tools.community.central.feature.feature.jar [2.0.1.CR1-v20160324-1911-B99]
> === Summary ===
> file:///home/pleacu/git-clone/jbosstools-integration-stack.orig/target-platform/target/target-platform.target.repo contains 16 unique IUs
> file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 16 unique IUs
> < org.eclipse.uml2.uml.validation [5.0.0.v20160118-1129]
> < org.eclipse.uml2.uml.ecore.exporter [3.0.0.v20160118-1129]
> < org.eclipse.uml2.uml.profile.standard [1.0.100.v20160118-1129]
> < org.eclipse.uml2.uml.ecore.importer [3.0.2.v20160118-1129]
> < org.jboss.tools.project.examples.feature.feature.group [3.0.1.Beta2-v20160121-2329-B74]
> < org.jboss.tools.community.central.feature.feature.group [2.0.1.Beta2-v20160121-2329-B74]
> < org.eclipse.uml2.common.edit.feature.group [2.1.0.v20160118-1129]
> < org.eclipse.emf.ecore.feature.jar [2.11.1.v20150805-0538]
> < org.eclipse.uml2.uml.edit [5.1.1.v20160118-1129]
> < org.eclipse.uml2.uml [5.1.2.v20160118-1129]
> < org.eclipse.uml2.feature.jar [5.1.2.v20160118-1129]
> < org.eclipse.uml2.common.feature.group [2.1.0.v20160118-1129]
> < org.eclipse.emf.codegen.ecore.ui [2.11.1.v20150806-0404]
> < org.eclipse.uml2.common.edit.feature.jar [2.1.0.v20160118-1129]
> < org.eclipse.uml2.uml.feature.group [5.1.2.v20160118-1129]
> < org.eclipse.uml2.feature.group [5.1.2.v20160118-1129]
> < org.jboss.tools.community.central [2.0.1.Beta2-v20160121-2329-B74]
> < org.eclipse.uml2.ant [1.0.0.v20160118-1129]
> < org.eclipse.uml2.uml.edit.feature.group [5.1.1.v20160118-1129]
> < org.eclipse.uml2 [5.0.0.v20160118-1129]
> < org.eclipse.emf.codegen.ecore.ui.feature.jar [2.11.1.v20150806-0404]
> < org.jboss.tools.community.project.examples.feature.feature.group [3.0.1.Beta2-v20160121-2329-B74]
> < org.eclipse.uml2.codegen.ecore [2.1.2.v20160118-1129]
> < org.jboss.tools.community.central.feature.feature.jar [2.0.1.Beta2-v20160121-2329-B74]
> < org.jboss.tools.community.project.examples.feature.feature.jar [3.0.1.Beta2-v20160121-2329-B74]
> < org.eclipse.uml2.uml.feature.jar [5.1.2.v20160118-1129]
> < org.eclipse.emf.codegen.ecore.ui.feature.group [2.11.1.v20150806-0404]
> < org.eclipse.emf.ecore.xmi [2.11.1.v20150805-0538]
> < org.eclipse.uml2.types [2.0.0.v20160118-1129]
> < org.eclipse.uml2.common.edit [2.1.0.v20160118-1129]
> < org.eclipse.emf.ecore.feature.group [2.11.1.v20150805-0538]
> < org.eclipse.uml2.common.feature.jar [2.1.0.v20160118-1129]
> < org.eclipse.emf.ecore [2.11.1.v20150805-0538]
> < org.eclipse.uml2.codegen.ecore.ui.feature.jar [2.1.2.v20160118-1129]
> < org.eclipse.uml2.uml.resources [5.1.0.v20160118-1129]
> < org.eclipse.uml2.uml.edit.feature.jar [5.1.1.v20160118-1129]
> < org.jboss.tools.community.project.examples [3.0.1.Beta2-v20160121-2329-B74]
> < org.eclipse.uml2.codegen.ecore.ui.feature.group [2.1.2.v20160118-1129]
> < org.eclipse.uml2.uml.editor [5.1.0.v20160118-1129]
> < org.eclipse.uml2.common [2.1.0.v20160118-1129]
> < org.eclipse.emf.ecore.change [2.11.0.v20150805-0538]
> < org.eclipse.uml2.codegen.ecore.ui [2.1.0.v20160118-1129]
> < org.jboss.tools.project.examples.feature.feature.jar [3.0.1.Beta2-v20160121-2329-B74]
> < org.jboss.tools.project.examples.cheatsheet [3.0.1.Beta2-v20160121-2329-B74]
> < org.jboss.tools.project.examples [3.0.1.Beta2-v20160121-2329-B74]
> > org.eclipse.uml2.uml.ecore.exporter [3.0.0.v20160201-0816]
> > org.eclipse.uml2.uml.validation [5.0.0.v20160201-0816]
> > org.eclipse.uml2.uml.ecore.importer [3.0.2.v20160201-0816]
> > org.eclipse.uml2.common [2.1.0.v20160201-0816]
> > org.eclipse.emf.ecore.feature.group [2.11.2.v20160208-0816]
> > org.eclipse.uml2.uml.edit.feature.jar [5.1.1.v20160201-0816]
> > org.eclipse.uml2.common.edit.feature.group [2.1.0.v20160201-0816]
> > org.eclipse.uml2.uml.edit [5.1.1.v20160201-0816]
> > org.eclipse.uml2.feature.jar [5.1.2.v20160201-0816]
> > org.eclipse.emf.ecore.xmi [2.11.1.v20160208-0816]
> > org.eclipse.uml2.uml.profile.standard [1.0.100.v20160201-0816]
> > org.eclipse.emf.ecore.feature.jar [2.11.2.v20160208-0816]
> > org.eclipse.emf.codegen.ecore.ui.feature.group [2.11.1.v20160208-0841]
> > org.eclipse.uml2.feature.group [5.1.2.v20160201-0816]
> > org.eclipse.uml2.common.edit.feature.jar [2.1.0.v20160201-0816]
> > org.eclipse.uml2.uml.feature.group [5.1.2.v20160201-0816]
> > org.jboss.tools.project.examples.feature.feature.group [3.0.1.CR1-v20160324-1911-B99]
> > org.jboss.tools.community.central.feature.feature.group [2.0.1.CR1-v20160324-1911-B99]
> > org.eclipse.emf.ecore.change [2.11.0.v20160208-0816]
> > org.jboss.tools.community.project.examples.feature.feature.jar [3.0.1.CR1-v20160324-1911-B99]
> > org.eclipse.uml2.uml.edit.feature.group [5.1.1.v20160201-0816]
> > org.eclipse.uml2.ant [1.0.0.v20160201-0816]
> > org.eclipse.uml2 [5.0.0.v20160201-0816]
> > org.jboss.tools.community.central.feature.feature.jar [2.0.1.CR1-v20160324-1911-B99]
> > org.eclipse.uml2.common.feature.group [2.1.0.v20160201-0816]
> > org.eclipse.uml2.types [2.0.0.v20160201-0816]
> > org.jboss.tools.project.examples [3.0.1.CR1-v20160324-1911-B99]
> > org.jboss.tools.community.project.examples [3.0.1.CR1-v20160324-1911-B99]
> > org.eclipse.uml2.uml.feature.jar [5.1.2.v20160201-0816]
> > org.eclipse.emf.codegen.ecore.ui.feature.jar [2.11.1.v20160208-0841]
> > org.eclipse.uml2.codegen.ecore [2.1.2.v20160201-0816]
> > org.eclipse.uml2.codegen.ecore.ui.feature.jar [2.1.2.v20160201-0816]
> > org.jboss.tools.community.central [2.0.1.CR1-v20160324-1911-B99]
> > org.eclipse.uml2.common.edit [2.1.0.v20160201-0816]
> > org.eclipse.uml2.uml.resources [5.1.0.v20160201-0816]
> > org.eclipse.uml2.uml [5.1.2.v20160201-0816]
> > org.jboss.tools.project.examples.cheatsheet [3.0.1.CR1-v20160324-1911-B99]
> > org.jboss.tools.project.examples.feature.feature.jar [3.0.1.CR1-v20160324-1911-B99]
> > org.jboss.tools.community.project.examples.feature.feature.group [3.0.1.CR1-v20160324-1911-B99]
> > org.eclipse.uml2.common.feature.jar [2.1.0.v20160201-0816]
> > org.eclipse.uml2.uml.editor [5.1.0.v20160201-0816]
> > org.eclipse.emf.codegen.ecore.ui [2.11.1.v20160208-0841]
> > org.eclipse.emf.ecore [2.11.2.v20160208-0816]
> > org.eclipse.uml2.codegen.ecore.ui.feature.group [2.1.2.v20160201-0816]
> > org.eclipse.uml2.codegen.ecore.ui [2.1.0.v20160201-0816]
> === Summary ===
> file:///home/pleacu/git-clone/jbosstools-integration-stack.orig/target-platform/target/target-platform-ea.target.repo contains 45 unique IUs
> file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform-ea.target.repo contains 45 unique IUs
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3854) Installer: Gulp dist task doesn't report subtasks in correct order
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/JBDS-3854?page=com.atlassian.jira.plugin.... ]
Pavol Pitonak updated JBDS-3854:
--------------------------------
Labels: Havoc (was: )
> Installer: Gulp dist task doesn't report subtasks in correct order
> ------------------------------------------------------------------
>
> Key: JBDS-3854
> URL: https://issues.jboss.org/browse/JBDS-3854
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Pavol Pitonak
> Assignee: Pavol Pitonak
> Labels: Havoc
> Fix For: 10.0.0.Alpha1
>
>
> Gulp task _dist_ log is in wrong order, e.g. dist should finish after clean is finished (caused by mixed usage of runSequence and native Gulp dependent tasks)
> {code}
> [11:40:03] Using gulpfile ~/workspace/developer-platform-install/gulpfile.js
> [11:40:03] Starting 'check-requirements'...
> [11:40:05] Finished 'check-requirements' after 1.74 s
> [11:40:05] Starting 'dist'...
> [11:40:05] Starting 'clean'...
> [11:40:05] Finished 'dist' after 3.05 ms
> [11:40:05] Finished 'clean' after 4.52 ms
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3854) Installer: Gulp dist task doesn't report subtasks in correct order
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/JBDS-3854?page=com.atlassian.jira.plugin.... ]
Pavol Pitonak updated JBDS-3854:
--------------------------------
Fix Version/s: 10.0.0.Alpha1
> Installer: Gulp dist task doesn't report subtasks in correct order
> ------------------------------------------------------------------
>
> Key: JBDS-3854
> URL: https://issues.jboss.org/browse/JBDS-3854
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Pavol Pitonak
> Assignee: Pavol Pitonak
> Fix For: 10.0.0.Alpha1
>
>
> Gulp task _dist_ log is in wrong order, e.g. dist should finish after clean is finished (caused by mixed usage of runSequence and native Gulp dependent tasks)
> {code}
> [11:40:03] Using gulpfile ~/workspace/developer-platform-install/gulpfile.js
> [11:40:03] Starting 'check-requirements'...
> [11:40:05] Finished 'check-requirements' after 1.74 s
> [11:40:05] Starting 'dist'...
> [11:40:05] Starting 'clean'...
> [11:40:05] Finished 'dist' after 3.05 ms
> [11:40:05] Finished 'clean' after 4.52 ms
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22228) NPE when deploying to Openshift EAP
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22228?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22228:
------------------------------------------
[~tmader] In what version did you spot this? This was in JBDS 9.1.CR1 (you indicated 10.x in the JBDS issue), wasnt it?
> NPE when deploying to Openshift EAP
> -----------------------------------
>
> Key: JBIDE-22228
> URL: https://issues.jboss.org/browse/JBIDE-22228
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Environment: Windows 10
> Reporter: Thomas Mäder
> Assignee: Max Rydahl Andersen
>
> When I try to publish to an EAP in the CDK, I get a NullPointerException:
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:309)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:298)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getDeploymentConfig(OpenShiftServerUtils.java:390)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:87)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492)
> at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:311)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months