[JBoss JIRA] (JBIDE-18272) Update Thym release on TP
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18272?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-18272:
--------------------------------------
build tag 201409051537 is good
> Update Thym release on TP
> -------------------------
>
> Key: JBIDE-18272
> URL: https://issues.jboss.org/browse/JBIDE-18272
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform, upstream
> Affects Versions: 4.2.0.Beta3
> Reporter: Gorkem Ercan
> Assignee: Mickael Istria
> Priority: Blocker
> Fix For: 4.2.0.CR1
>
>
> *Reason:* Update Eclipse Thym to pickup fixes to JBDS issues
> *License and owner:* Eclipse
> *Original p2 repo:* http://download.eclipse.org/thym/snapshots
> *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/thym/0.1.0-SNAP...
> *Sources:* https://github.com/eclipse/thym
> *Affected projects:* jbosstools-aerogear
> *Include in JBDS:* YES
> *Type of dependency:* build
> *List of bundles added/removed:*
> {code}
> mistria@mistria--rh:~/git/jbosstools-target-platforms/jbosstools/multiple$ ~/git/p2diff/org.eclipse.equinox.p2.example.p2diff.packaging/target/products/org.eclipse.equinox.p2.example.p2diff.product/linux/gtk/x86_64/p2diff http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... file:$(pwd)/target/jbosstools-multiple.target.repo/
> < org.eclipse.thym.feature.feature.group [0.1.0.201408251101]
> < org.eclipse.thym.core [0.1.0.201408251101]
> < org.eclipse.thym.ios.ui [0.1.0.201408251101]
> < org.eclipse.thym.android.core [0.1.0.201408251101]
> < org.eclipse.thym.android.ui [0.1.0.201408251101]
> < org.eclipse.thym.ios.core [0.1.0.201408251101]
> < org.eclipse.thym.ui [0.1.0.201408251101]
> < org.eclipse.thym.feature.feature.jar [0.1.0.201408251101]
> > org.eclipse.thym.ios.ui [0.1.0.201408271516]
> > org.eclipse.thym.android.ui [0.1.0.201408271516]
> > org.eclipse.thym.core [0.1.0.201408271516]
> > org.eclipse.thym.feature.feature.group [0.1.0.201408271516]
> > org.eclipse.thym.android.core [0.1.0.201408271516]
> > org.eclipse.thym.ui [0.1.0.201408271516]
> > org.eclipse.thym.feature.feature.jar [0.1.0.201408271516]
> > org.eclipse.thym.ios.core [0.1.0.201408271516]
> === Summary ===
> http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... contains 8 unique IUs
> file:/home/mistria/git/jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo/ contains 8 unique IUs
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18272) Update Thym release on TP
by Gorkem Ercan (JIRA)
Gorkem Ercan created JBIDE-18272:
------------------------------------
Summary: Update Thym release on TP
Key: JBIDE-18272
URL: https://issues.jboss.org/browse/JBIDE-18272
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: target-platform, upstream
Affects Versions: 4.2.0.Beta3
Reporter: Gorkem Ercan
Assignee: Mickael Istria
Priority: Blocker
Fix For: 4.2.0.CR1
*Reason:* Update Eclipse Thym to pickup fixes to JBDS issues
*License and owner:* Eclipse
*Original p2 repo:* http://download.eclipse.org/thym/snapshots
*JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/thym/0.1.0-SNAP...
*Sources:* https://github.com/eclipse/thym
*Affected projects:* jbosstools-aerogear
*Include in JBDS:* YES
*Type of dependency:* build
*List of bundles added/removed:*
{code}
mistria@mistria--rh:~/git/jbosstools-target-platforms/jbosstools/multiple$ ~/git/p2diff/org.eclipse.equinox.p2.example.p2diff.packaging/target/products/org.eclipse.equinox.p2.example.p2diff.product/linux/gtk/x86_64/p2diff http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... file:$(pwd)/target/jbosstools-multiple.target.repo/
< org.eclipse.thym.feature.feature.group [0.1.0.201408251101]
< org.eclipse.thym.core [0.1.0.201408251101]
< org.eclipse.thym.ios.ui [0.1.0.201408251101]
< org.eclipse.thym.android.core [0.1.0.201408251101]
< org.eclipse.thym.android.ui [0.1.0.201408251101]
< org.eclipse.thym.ios.core [0.1.0.201408251101]
< org.eclipse.thym.ui [0.1.0.201408251101]
< org.eclipse.thym.feature.feature.jar [0.1.0.201408251101]
> org.eclipse.thym.ios.ui [0.1.0.201408271516]
> org.eclipse.thym.android.ui [0.1.0.201408271516]
> org.eclipse.thym.core [0.1.0.201408271516]
> org.eclipse.thym.feature.feature.group [0.1.0.201408271516]
> org.eclipse.thym.android.core [0.1.0.201408271516]
> org.eclipse.thym.ui [0.1.0.201408271516]
> org.eclipse.thym.feature.feature.jar [0.1.0.201408271516]
> org.eclipse.thym.ios.core [0.1.0.201408271516]
=== Summary ===
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... contains 8 unique IUs
file:/home/mistria/git/jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo/ contains 8 unique IUs
{code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBTIS-289) JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration - 4.1.x
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-289?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-289:
----------------------------------
Hey Brian - please verify - if okay you can close this jira
http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st...
> JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration - 4.1.x
> ----------------------------------------------------------------
>
> Key: JBTIS-289
> URL: https://issues.jboss.org/browse/JBTIS-289
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: ESB
> Affects Versions: 4.0.0
> Reporter: Brian Fitzpatrick
> Assignee: Brian Fitzpatrick
> Fix For: 4.0.0
>
>
> JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration
> Steps as defined by Nick (thanks Nick!):
> a) the contents of the examples are in a former employee's SVN workspace
> and haven't been updated since a couple of years. They don't really work
> as well as they could.
> b) the examples are all mostly duplicated in the quickstarts folder that
> ships with SOA-P 5.3.1. See
> https://bugzilla.redhat.com/show_bug.cgi?id=951677 and
> https://issues.jboss.org/browse/JBTIS-62
> Basically, we need to:
> * fix the quickstarts in SOA-P 6 so they ACTUALLY WORK as importable
> eclipse projects (merge in contents from duplicate examples in Denny's
> workspace). Could decide to backport to 5.3 if there's a 5.3.2 planned;
> if not, no great need.
> * copy the older examples that are not already in SOA-P 5.3 - the ones
> that are *exclusively* in Denny's workspace - into SOA-P 6 so they'll be
> available there.
> * update the BPEL Examples guide as needed
> * document the fact that these examples are no longer available as
> importable zipped example projects contributed by a plugin, but rather
> as already-unpacked projects nested within the SOA-P runtime zip
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-15517) Explorer: There's currently no way to see that an application is scaled
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15517?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-15517 at 9/5/14 11:23 AM:
-------------------------------------------------------------------
Yes you're right, this is about an application being able to scale (vs. the fact that it's actually scaled across different gears)
This ability is available in the application in the following way:
{code:title=IApplication}
public ApplicationScale getApplicationScale();
{code}
was (Author: adietish):
Yes you're right, this is about an application being able to scale (vs. the fact that it's actually scaled across different gears)
> Explorer: There's currently no way to see that an application is scaled
> -----------------------------------------------------------------------
>
> Key: JBIDE-15517
> URL: https://issues.jboss.org/browse/JBIDE-15517
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Jeff Cantrill
> Labels: explorer
> Fix For: 4.3.x
>
>
> There's currently no way for the user to see that an application is scaled.
> We should show this to the user via decorations in the OpenShift Explorer and also in the application details.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-15517) Explorer: There's currently no way to see that an application is scaled
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15517?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-15517:
------------------------------------------
we discussed that we should add the information in 3 places:
* decroation in the OpenShift Explorer
* Application details (dialog)
* Application properties (view)
> Explorer: There's currently no way to see that an application is scaled
> -----------------------------------------------------------------------
>
> Key: JBIDE-15517
> URL: https://issues.jboss.org/browse/JBIDE-15517
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Jeff Cantrill
> Labels: explorer
> Fix For: 4.3.x
>
>
> There's currently no way for the user to see that an application is scaled.
> We should show this to the user via decorations in the OpenShift Explorer and also in the application details.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-15517) Explorer: There's currently no way to see that an application is scaled
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15517?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-15517 at 9/5/14 11:16 AM:
-------------------------------------------------------------------
Yes you're right, this is about an application being able to scale (vs. the fact that it's actually scaled across different gears)
was (Author: adietish):
These are 2 different things and both may possibly make sense:
* decoreate scalable applications: I'm not aware of non-scalable applications, are there any?
* decorate scaled applications: this is meaningfull imho: ex. you cannot embed phpmyadmin to a scalable application. You only get to know about this impossibility when you try to embed phpmyadmin and get warned about it (we added some warning in the UI)
> Explorer: There's currently no way to see that an application is scaled
> -----------------------------------------------------------------------
>
> Key: JBIDE-15517
> URL: https://issues.jboss.org/browse/JBIDE-15517
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Jeff Cantrill
> Labels: explorer
> Fix For: 4.3.x
>
>
> There's currently no way for the user to see that an application is scaled.
> We should show this to the user via decorations in the OpenShift Explorer and also in the application details.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBTIS-289) JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration - 4.1.x
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-289?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-289:
----------------------------------
The staging area still had the July 25th version. I've renamed that directory in staging and restarted the build. Strange...
> JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration - 4.1.x
> ----------------------------------------------------------------
>
> Key: JBTIS-289
> URL: https://issues.jboss.org/browse/JBTIS-289
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: ESB
> Affects Versions: 4.0.0
> Reporter: Brian Fitzpatrick
> Assignee: Brian Fitzpatrick
> Fix For: 4.0.0
>
>
> JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration
> Steps as defined by Nick (thanks Nick!):
> a) the contents of the examples are in a former employee's SVN workspace
> and haven't been updated since a couple of years. They don't really work
> as well as they could.
> b) the examples are all mostly duplicated in the quickstarts folder that
> ships with SOA-P 5.3.1. See
> https://bugzilla.redhat.com/show_bug.cgi?id=951677 and
> https://issues.jboss.org/browse/JBTIS-62
> Basically, we need to:
> * fix the quickstarts in SOA-P 6 so they ACTUALLY WORK as importable
> eclipse projects (merge in contents from duplicate examples in Denny's
> workspace). Could decide to backport to 5.3 if there's a 5.3.2 planned;
> if not, no great need.
> * copy the older examples that are not already in SOA-P 5.3 - the ones
> that are *exclusively* in Denny's workspace - into SOA-P 6 so they'll be
> available there.
> * update the BPEL Examples guide as needed
> * document the fact that these examples are no longer available as
> importable zipped example projects contributed by a plugin, but rather
> as already-unpacked projects nested within the SOA-P runtime zip
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18268) Error while validating credentials in download EAP 6.3 dialog
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18268?page=com.atlassian.jira.plugi... ]
Rob Stryker reassigned JBIDE-18268:
-----------------------------------
Assignee: Rob Stryker
> Error while validating credentials in download EAP 6.3 dialog
> -------------------------------------------------------------
>
> Key: JBIDE-18268
> URL: https://issues.jboss.org/browse/JBIDE-18268
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.2.0.CR1
> Reporter: Radoslav Rábara
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-a
> Fix For: 4.2.0.CR1
>
> Attachments: download eap 6-3.jpg
>
>
> After validation of valid credentials, the following error message appears
> {code}
> " An error occurred while validating your credentials. org.eclipse.core.runtime.CoreException - Unknown response code: 404"
> {code}
> I don't get an error when I try to download another runtime (I reproduced it only when I tried to download EAP 6.3)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18258) "Cannot find navigator content extension" when starting a local server after setting up a remote server
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18258?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-18258:
-------------------------------------
These appear to relate to the autodetected jvm's in jmx.local. Will investigate.
> "Cannot find navigator content extension" when starting a local server after setting up a remote server
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18258
> URL: https://issues.jboss.org/browse/JBIDE-18258
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx, server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Critical
> Labels: respin-a
> Fix For: 4.2.0.CR1
>
>
> When I set up a local server, then a remote server and then I start the local server, I get errors:
> {code}
> !ENTRY org.eclipse.ui.navigator 4 0 2014-09-04 11:46:26.700
> !MESSAGE Cannot find navigator content extension (using triggerPoints) for object "org.jboss.modules.Main [22362]" parent path: "R/". Check that you have an expression for this object in a navigatorContent triggerPoints or enablement.
> !ENTRY org.eclipse.ui.navigator 4 0 2014-09-04 11:46:26.703
> !MESSAGE Cannot find navigator content extension (using triggerPoints) for object "org.jboss.modules.Main [22362]" parent path: "R/". Check that you have an expression for this object in a navigatorContent triggerPoints or enablement.
> !ENTRY org.eclipse.ui.navigator 4 0 2014-09-04 11:46:26.895
> !MESSAGE Cannot find navigator content extension (using triggerPoints) for object "org.jboss.modules.Main [22362]" parent path: "R/". Check that you have an expression for this object in a navigatorContent triggerPoints or enablement.
> {code}
> I'm not exactly sure how this works, but strangely, the errors are thrown even after I remove the remote server. But they did not occur before I created the remote server. So perhaps it has something to do with the existence of the remote system and not really the remote server itself? I don't know.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17935) AS7/WildFly8 fails to start when bound to your hostname even with web poller
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17935?page=com.atlassian.jira.plugi... ]
Pavol Srna edited comment on JBIDE-17935 at 9/5/14 10:34 AM:
-------------------------------------------------------------
Yes, Martin is correct in describing what I see. And then after 1-2 minutes the tooling says that it looks like there is some other server running on that ip. But it isn't. !server.png!
was (Author: psrna):
Yes, Martin is correct in describing what I see. And then after 1-2 minutes the tooling says that it looks like there is some other server running on that ip. But it isn't.
> AS7/WildFly8 fails to start when bound to your hostname even with web poller
> ----------------------------------------------------------------------------
>
> Key: JBIDE-17935
> URL: https://issues.jboss.org/browse/JBIDE-17935
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta3
> Environment: JBDS 8.0.0.Beta3b B193
> Reporter: Martin Malina
> Assignee: Andre Dietisheim
> Fix For: 4.2.0.CR1
>
> Attachments: server.png
>
>
> This is a follow up of JBIDE-17173.
> Rob changed the default poller for the local profile to Web poller, which should be correct. So when you change your hostname in the server editor from localhost to your actual hostname, it should correctly recognize your server has started. But it does not.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months