[JBoss JIRA] (JBIDE-12302) Can't sign in to OpenShift from Eclipse behind a proxy
by Beth Boose (JIRA)
Beth Boose created JBIDE-12302:
----------------------------------
Summary: Can't sign in to OpenShift from Eclipse behind a proxy
Key: JBIDE-12302
URL: https://issues.jboss.org/browse/JBIDE-12302
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Environment: Windows 7 Eclipse 3.7.1
Reporter: Beth Boose
Assignee: Andre Dietisheim
When I try to create an OpenShift Application from the JBoss Central page in Eclipse the wizard displays the following message after I enter username and password:
Could not check user credentials: Could not request /api: java.net.UnknownHostException: openshift.redhat.com
Verified that manual proxy setting are configured correctly in Eclipse under Window -> Preferences-> General -> Network Connections (proxy settings work with other plugins).
When I'm not behind a proxy OpenShift login works as expected.
I don't see the OpenShift UI or JBoss tools version listed in the Affects Version list, I have 2.3.1 for OpenShift tools.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (JBIDE-12294) Remove m2e-apt from parent pom, JBT Composite Juno Reqs Mirror, JBT & JBDS Central, and JBDS Product (Installer)
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-12294:
----------------------------------
Summary: Remove m2e-apt from parent pom, JBT Composite Juno Reqs Mirror, JBT & JBDS Central, and JBDS Product (Installer)
Key: JBIDE-12294
URL: https://issues.jboss.org/browse/JBIDE-12294
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: Build/Releng, maven, updatesite, UpStream
Affects Versions: 3.3.0.Beta3
Reporter: Fred Bricon
Assignee: Fred Bricon
Fix For: 3.3.0.Beta3
m2e-apt needs to be a first class citizen of JBT / JBDS
For JBT : needs to be available from the software install tab in JBoss Central
For JBDS : needs to be included in the installer
{quote}
rather it goes into Indigo core reqs site, product build, and installer
http://download.jboss.org/jbosstools/updates/indigo/SR2/
and http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk....
{quote}
Waiting for the jenkins build #7 (triggered in release mode) to finish : https://hudson.qa.jboss.com/hudson/view/DevStudio/view/m2eclipse-wtp/job/...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] Created: (JBIDE-8993) Unable to run DroolTest.java because of missing org.eclipse.jdt.core*.jar in project classpath
by Vlado Pakan (JIRA)
Unable to run DroolTest.java because of missing org.eclipse.jdt.core*.jar in project classpath
----------------------------------------------------------------------------------------------
Key: JBIDE-8993
URL: https://issues.jboss.org/browse/JBIDE-8993
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.3.0.M1
Environment: Linux 32bit, Sun JDK 1.6_25, jbosstools-3.3.0.M1a.aggregate-Update-2011-05-11_15-56-28-H2359
Reporter: Vlado Pakan
Priority: Critical
Fix For: 3.3.0.M1
When creating new Drools Runtime from Drools plugin bundled to JBT org.eclipse.jdt.core*.jar file is not included in this runtime and therefore when running DroolTest.java this error is displayed in console:
org.drools.RuntimeDroolsException: Unable to load dialect 'org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java:org.drools.rule.builder.dialect.java.JavaDialectConfiguration'
at org.drools.compiler.PackageBuilderConfiguration.addDialect(PackageBuilderConfiguration.java:277)
at org.drools.compiler.PackageBuilderConfiguration.buildDialectConfigurationMap(PackageBuilderConfiguration.java:262)
at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:175)
at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:153)
at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:218)
at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:146)
at org.drools.builder.impl.KnowledgeBuilderFactoryServiceImpl.newKnowledgeBuilder(KnowledgeBuilderFactoryServiceImpl.java:34)
at org.drools.builder.KnowledgeBuilderFactory.newKnowledgeBuilder(KnowledgeBuilderFactory.java:46)
at com.sample.DroolsTest.readKnowledgeBase(DroolsTest.java:39)
at com.sample.DroolsTest.main(DroolsTest.java:23)
Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath
at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.setCompiler(JavaDialectConfiguration.java:93)
at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.init(JavaDialectConfiguration.java:54)
at org.drools.compiler.PackageBuilderConfiguration.addDialect(PackageBuilderConfiguration.java:273)
... 9 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months