[JBoss JIRA] (JBIDE-23302) https no longer working on tools.jboss.org
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23302?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23302:
-------------------------------
Description:
Is it expected that tools.jboss.org no longer provides https?
https keeps redirecting to http for me, so I'm getting errors in Eclipse as thrown by AERI, eg:
{code}Server 'org.jboss.tools' failed with exception: Connect to tools.jboss.org:443 [tools.jboss.org/10.4.129.28] failed: connect timed out. ; version: 2.0.1.201608030901
{code}
To see this in action, go here:
https://tools.jboss.org --> redirects to http://tools.jboss.org
or, go here:
https://tools.jboss.org:443/ --> redirects to http://tools.jboss.org
I bet this is a problem for eng-ops@ or the new PnT portal.
was:
Is it expected that tools.jboss.org no longer provides https?
https keeps redirecting to http for me, so I'm getting errors in Eclipse as thrown by AERI, eg:
{code}Server 'org.jboss.tools' failed with exception: Connect to tools.jboss.org:443 [tools.jboss.org/10.4.129.28] failed: connect timed out. ; version: 2.0.1.201608030901
{code}
> https no longer working on tools.jboss.org
> ------------------------------------------
>
> Key: JBIDE-23302
> URL: https://issues.jboss.org/browse/JBIDE-23302
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aeri, website
> Reporter: Nick Boldt
>
> Is it expected that tools.jboss.org no longer provides https?
> https keeps redirecting to http for me, so I'm getting errors in Eclipse as thrown by AERI, eg:
> {code}Server 'org.jboss.tools' failed with exception: Connect to tools.jboss.org:443 [tools.jboss.org/10.4.129.28] failed: connect timed out. ; version: 2.0.1.201608030901
> {code}
> To see this in action, go here:
> https://tools.jboss.org --> redirects to http://tools.jboss.org
> or, go here:
> https://tools.jboss.org:443/ --> redirects to http://tools.jboss.org
> I bet this is a problem for eng-ops@ or the new PnT portal.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-17827) "Missing beans.xml" in a Seam project
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17827?page=com.atlassian.jira.plugi... ]
Aurélien Pupier commented on JBIDE-17827:
-----------------------------------------
Hi,
we have the same kind of issue with camel-sprintboot quickstart sample, see [OSFUSE-351]
If I understand well, the best proposed workaround is to modify the pom.xml by adding <m2e.cdi.activation>false</m2e.cdi.activation>
As it was 2 years, maybe we have newer idea/possibilities?
> "Missing beans.xml" in a Seam project
> -------------------------------------
>
> Key: JBIDE-17827
> URL: https://issues.jboss.org/browse/JBIDE-17827
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi, seam2
> Environment: JBDS 8.0.0.Beta2d
> Reporter: Ron Šmeral
> Assignee: Alexey Kazakov
> Fix For: 4.2.0.CR1
>
>
> In an imported Seam 2.3 project, there's a warning:
> _Missing beans.xml file in the project contactlist-ejb. This file is required for bean archives \[JSR-299 §12.1\] contactlist-ejb_
> Seam projects don't need a beans.xml file.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBTIS-704) Marketplace entries use the old license
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-704?page=com.atlassian.jira.plugin.... ]
Paul Leacu resolved JBTIS-704.
------------------------------
Resolution: Done
Corrected in JBDSIS 9.0.2.GA
> Marketplace entries use the old license
> ---------------------------------------
>
> Key: JBTIS-704
> URL: https://issues.jboss.org/browse/JBTIS-704
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 9.0.0.GA
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Fix For: 9.0.2.GA
>
> Attachments: jbdsis901ga_marketplace.png
>
>
> The following features still use the old license
> - com.jboss.devstudio.integration-stack.bpr.feature
> - com.jboss.devstudio.integration-stack.ds.feature (on EA)
> - com.jboss.devstudio.integration-stack.fuse.feature (on EA)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4097) Support maven plugins used by Fuse Quickstarts
by Aurélien Pupier (JIRA)
Aurélien Pupier created JBDS-4097:
-------------------------------------
Summary: Support maven plugins used by Fuse Quickstarts
Key: JBDS-4097
URL: https://issues.jboss.org/browse/JBDS-4097
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Feature Request
Reporter: Aurélien Pupier
known plugins:
- cxf-java2wadl-plugin
- cxf-java2ws-plugins
- fabric-cxf-plugins
The best is to implement m2e connector.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23030) Scaling a service changes the wrong deployment
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23030?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-23030:
---------------------------------------
[~jeffmaury] [~adietish] Do you think this PR is sufficient? Can it be rebased and merged?
> Scaling a service changes the wrong deployment
> ----------------------------------------------
>
> Key: JBIDE-23030
> URL: https://issues.jboss.org/browse/JBIDE-23030
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
> Priority: Critical
>
> In openshift explorer, when scaling a service that has 2 deployments, it deploys pod from the oldest deployment instead of the latest. Eventually, these pods are killed by openshift.
> The workaround is to open the properties view and issue a scale command on a deployment directly.
> However, because scaling is such a front-and-center feature from the explorer, I believe it's critical we fix it ASAP
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months