October 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18397) Application wizard: openshift maven profile for WildFly cartridge generates <outputDirectory>null</outputDirectory>

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18397?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18397: ----------------------------------- Labels: application_wizard new_and_noteworthy (was: application_wizard new_and_noteworhty) > Application wizard: openshift maven profile for WildFly cartridge generates <outputDirectory>null</outputDirectory> > ------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18397 > URL: https://issues.jboss.org/browse/JBIDE-18397 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Critical > Labels: application_wizard, new_and_noteworthy > Fix For: 4.2.0.CR2 > > > - Create a new maven war project testapp > - Add custom index.html > - Create new openshift application with WildFly 8.1 quickstart > - deploy testapp on openshift > - ASSERT your changes are published online > -> FAIL the default Wildfly 8 cartridge app is shown > This is caused by openshift tooling generating an invalid outputDirectory value (null) instead of the expected one (deployments) > {noformat}<profile> >  >  >  >  > <id>openshift</id> > <build> > <finalName>testapp</finalName> > <plugins> > <plugin> > <artifactId>maven-war-plugin</artifactId> > <version>2.4</version> > <configuration> > <outputDirectory>null</outputDirectory> > <warName>ROOT</warName> > </configuration> > </plugin> > </plugins> > </build> > </profile> > {noformat} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18397) Application wizard: openshift maven profile for WildFly cartridge generates <outputDirectory>null</outputDirectory>

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18397?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-18397. ---------------------------------- Resolution: Done > Application wizard: openshift maven profile for WildFly cartridge generates <outputDirectory>null</outputDirectory> > ------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18397 > URL: https://issues.jboss.org/browse/JBIDE-18397 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Critical > Labels: application_wizard, new_and_noteworthy > Fix For: 4.2.0.CR2 > > > - Create a new maven war project testapp > - Add custom index.html > - Create new openshift application with WildFly 8.1 quickstart > - deploy testapp on openshift > - ASSERT your changes are published online > -> FAIL the default Wildfly 8 cartridge app is shown > This is caused by openshift tooling generating an invalid outputDirectory value (null) instead of the expected one (deployments) > {noformat}<profile> >  >  >  >  > <id>openshift</id> > <build> > <finalName>testapp</finalName> > <plugins> > <plugin> > <artifactId>maven-war-plugin</artifactId> > <version>2.4</version> > <configuration> > <outputDirectory>null</outputDirectory> > <warName>ROOT</warName> > </configuration> > </plugin> > </plugins> > </build> > </profile> > {noformat} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18454) Cant connect to OpenShift running on RHEL 6.6 (javax.net.ssl.SSLException: Could not generate DH keypair)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18454?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-18454. ---------------------------------- Resolution: Done > Cant connect to OpenShift running on RHEL 6.6 (javax.net.ssl.SSLException: Could not generate DH keypair) > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18454 > URL: https://issues.jboss.org/browse/JBIDE-18454 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 4.2.0.CR2 > > Attachments: ssl-error-on-connect.png > > > In https://bugzilla.redhat.com/show_bug.cgi?id=1145848 openshift-java-client cant connect to OpenShift running on RHEL 6.6 when using jdks (openjdk and sun) < 1.8 on linux. We have to verify that this affects the Eclipse based tooling (that's also using openshift-java-client) > {code} > java.io.IOException: com.openshift.client.OpenShiftEndpointException: Could not request https://broker.ose21z-auto.com.cn/broker/rest/api: javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate DH keypair > at hudson.plugins.openshift.OpenShiftCloud.getOpenShiftConnection(OpenShiftCloud.java:186) > at hudson.plugins.openshift.OpenShiftCloud.getSlaves(OpenShiftCloud.java:877) > at hudson.plugins.openshift.OpenShiftCloud.provisionSlave(OpenShiftCloud.java:451) > at hudson.plugins.openshift.OpenShiftCloud.provision(OpenShiftCloud.java:413) > at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:281) > at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:51) > at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:368) > at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > Caused by: com.openshift.client.OpenShiftEndpointException: Could not request https://broker.ose21z-auto.com.cn/broker/rest/api: javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate DH keypair > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18454) Cant connect to OpenShift running on RHEL 6.6 (javax.net.ssl.SSLException: Could not generate DH keypair)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18454?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18454: ----------------------------------- Labels: new_and_noteworthy (was: new_and_noteworhty) > Cant connect to OpenShift running on RHEL 6.6 (javax.net.ssl.SSLException: Could not generate DH keypair) > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18454 > URL: https://issues.jboss.org/browse/JBIDE-18454 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 4.2.0.CR2 > > Attachments: ssl-error-on-connect.png > > > In https://bugzilla.redhat.com/show_bug.cgi?id=1145848 openshift-java-client cant connect to OpenShift running on RHEL 6.6 when using jdks (openjdk and sun) < 1.8 on linux. We have to verify that this affects the Eclipse based tooling (that's also using openshift-java-client) > {code} > java.io.IOException: com.openshift.client.OpenShiftEndpointException: Could not request https://broker.ose21z-auto.com.cn/broker/rest/api: javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate DH keypair > at hudson.plugins.openshift.OpenShiftCloud.getOpenShiftConnection(OpenShiftCloud.java:186) > at hudson.plugins.openshift.OpenShiftCloud.getSlaves(OpenShiftCloud.java:877) > at hudson.plugins.openshift.OpenShiftCloud.provisionSlave(OpenShiftCloud.java:451) > at hudson.plugins.openshift.OpenShiftCloud.provision(OpenShiftCloud.java:413) > at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:281) > at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:51) > at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:368) > at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > Caused by: com.openshift.client.OpenShiftEndpointException: Could not request https://broker.ose21z-auto.com.cn/broker/rest/api: javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate DH keypair > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18323) JBoss Maven Repository not recognized

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18323?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-18323. --------------------------------- Resolution: Done Closing after adding new_noteworthy label > JBoss Maven Repository not recognized > ------------------------------------- > > Key: JBIDE-18323 > URL: https://issues.jboss.org/browse/JBIDE-18323 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Reporter: Andrea Vibelli > Assignee: Fred Bricon > Priority: Minor > Labels: new_and_noteworthy > Fix For: 4.2.0.CR2 > > > I am using JBoss Developer Studio Version: 8.0.0.Beta3, and trying to import my Maven Repository, but it doesn't get recognized. Does the Maven repository have to contain specific metadata / pom f/ GAVs in order to be recognized? > JBoss Maven Integration has version: 1.6.0.Beta3-v20140718-1719-B77 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18323) JBoss Maven Repository not recognized

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18323?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-18323: -------------------------------- Labels: new_and_noteworthy (was: ) > JBoss Maven Repository not recognized > ------------------------------------- > > Key: JBIDE-18323 > URL: https://issues.jboss.org/browse/JBIDE-18323 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Reporter: Andrea Vibelli > Assignee: Fred Bricon > Priority: Minor > Labels: new_and_noteworthy > Fix For: 4.2.0.CR2 > > > I am using JBoss Developer Studio Version: 8.0.0.Beta3, and trying to import my Maven Repository, but it doesn't get recognized. Does the Maven repository have to contain specific metadata / pom f/ GAVs in order to be recognized? > JBoss Maven Integration has version: 1.6.0.Beta3-v20140718-1719-B77 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18669) HTML5 Palette: Custom palette group

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18669?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18669: ----------------------------------- Labels: new_and_noteworthy (was: ) > HTML5 Palette: Custom palette group > ----------------------------------- > > Key: JBIDE-18669 > URL: https://issues.jboss.org/browse/JBIDE-18669 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Labels: new_and_noteworthy > Fix For: 4.3.x > > > It would be nice to have custom HTML5 Palette group. > It should be possible for users to select which items to show in that group: > 1. Last used items > 2. The most popular items > 3. Custom set of items (defined by user) > It should be possible to limit number of items and edit set of items (for 1 and 2) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18669) HTML5 Palette: Custom palette group

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18669?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18669: ----------------------------------- Fix Version/s: 4.3.x > HTML5 Palette: Custom palette group > ----------------------------------- > > Key: JBIDE-18669 > URL: https://issues.jboss.org/browse/JBIDE-18669 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Fix For: 4.3.x > > > It would be nice to have custom HTML5 Palette group. > It should be possible for users to select which items to show in that group: > 1. Last used items > 2. The most popular items > 3. Custom set of items (defined by user) > It should be possible to limit number of items and edit set of items (for 1 and 2) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3192) HTML5 Palette: Custom palette group

by Daniel Azarov (JIRA)

Daniel Azarov created JBDS-3192: ----------------------------------- Summary: HTML5 Palette: Custom palette group Key: JBDS-3192 URL: https://issues.jboss.org/browse/JBDS-3192 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: jsp/jsf/xml/html source editing Reporter: Daniel Azarov Assignee: Daniel Azarov It would be nice to have custom HTML5 Palette group. It should be possible for users to select which items to show in that group: 1. Last used items 2. The most popular items 3. Custom set of items (defined by user) It should be possible to limit number of items and edit set of items (for 1 and 2) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18668) CSS content assist: Multiple error messages in case of invalid URI

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-18668: -------------------------------------- Summary: CSS content assist: Multiple error messages in case of invalid URI Key: JBIDE-18668 URL: https://issues.jboss.org/browse/JBIDE-18668 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml/html source editing Affects Versions: 4.2.0.CR2 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 4.2.1.Final, 4.3.0.Alpha1 I have an html page with the following CSS link: <link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Open+Sans:300,300italic,400,400it..."> Ctrl+Click for any <* class="|"> causes multiple error messages: {code} java.lang.IllegalArgumentException: Invalid uri 'https://fonts.googleapis.com/css?family=Open+Sans:300,300italic,400,400it...': Invalid query at org.apache.commons.httpclient.HttpMethodBase.<init>(HttpMethodBase.java:222) at org.apache.commons.httpclient.methods.GetMethod.<init>(GetMethod.java:89) at org.jboss.tools.common.util.HttpUtil.executeGetMethod(HttpUtil.java:141) at org.jboss.tools.common.util.HttpUtil.executeGetMethod(HttpUtil.java:126) at org.jboss.tools.common.util.HttpUtil.getInputStreamFromUrlByGetMethod(HttpUtil.java:55) at org.jboss.tools.jst.web.kb.internal.RemoteFileManager$DownloaderImpl.getInputStream(RemoteFileManager.java:394) at org.jboss.tools.jst.web.kb.internal.RemoteFileManager$DownloadingJob.run(RemoteFileManager.java:327) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2014