[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
13 years, 4 months
[JBoss JIRA] (JBDS-2277) Unable to install Spring via JBoss Central
by Len DiMaggio (JIRA)
Len DiMaggio created JBDS-2277:
----------------------------------
Summary: Unable to install Spring via JBoss Central
Key: JBDS-2277
URL: https://issues.jboss.org/browse/JBDS-2277
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: central
Affects Versions: 6.0.0.Alpha1
Environment: Version: 6.0.0.H25
Build id: Alpha1-v20120911-2223-H25
Build date: 20120911-2223
Reporter: Len DiMaggio
Assignee: Snjezana Peco
Priority: Blocker
Fix For: 6.0.0.Alpha2
Attachments: error.log
The error log (attached) shows this error:
!ENTRY org.eclipse.mylyn.discovery.ui 4 0 2012-09-17 13:51:26.563
!MESSAGE Problems occurred while performing installation: Operation details
!STACK 1
org.eclipse.core.runtime.CoreException: Operation details
at org.eclipse.mylyn.internal.discovery.ui.PrepareInstallProfileJob_e_3_6.resolveInstall(PrepareInstallProfileJob_e_3_6.java:198)
at org.eclipse.mylyn.internal.discovery.ui.PrepareInstallProfileJob_e_3_6.run(PrepareInstallProfileJob_e_3_6.java:99)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 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
13 years, 4 months
[JBoss JIRA] (JBIDE-12562) org.sourceforge.pmd.eclipse has invalid OSGi MANIFEST.MF
by Jiri Peterka (JIRA)
Jiri Peterka created JBIDE-12562:
------------------------------------
Summary: org.sourceforge.pmd.eclipse has invalid OSGi MANIFEST.MF
Key: JBIDE-12562
URL: https://issues.jboss.org/browse/JBIDE-12562
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 4.0.0.Alpha1
Environment: JBT 4.0.0.Alfa1
Reporter: Jiri Peterka
Assignee: Nick Boldt
Fix For: 4.0.0.Alpha2
org.sourceforge.pmd.eclipse is not valid OSGI bundle and cannot be loaded as target runtime in eclipse
It contains only:
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.7.0
Created-By: 10.0-b19 (Sun Microsystems Inc.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-12633) Support for JAX-RS Application subclassing with configuration in web.xml
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-12633:
-------------------------------------
Summary: Support for JAX-RS Application subclassing with configuration in web.xml
Key: JBIDE-12633
URL: https://issues.jboss.org/browse/JBIDE-12633
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Webservices
Affects Versions: 4.0.0.Alpha1
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 4.0.0.Alpha2
As described in https://docs.jboss.org/author/display/AS7/JAX-RS+Reference+Guide, the plugin should support the following use case:
{quote}
Subclassing javax.ws.rs.core.Application and using web.xml
If you do not wish to use @ApplicationPath but still need to subclass Application you can set up the JAX-RS mapping in web.xml:
{quote}
{code}
public class MyApplication extends Application {
}
{code}
{code}
<servlet-mapping>
<servlet-name>com.acme.MyApplication</servlet-name>
<url-pattern>/hello/*</url-pattern>
</servlet-mapping>
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBDS-2290) Add m2e-apt 1.0.1 to JBDS 6.0.0.Alpha2
by Fred Bricon (JIRA)
Fred Bricon created JBDS-2290:
---------------------------------
Summary: Add m2e-apt 1.0.1 to JBDS 6.0.0.Alpha2
Key: JBDS-2290
URL: https://issues.jboss.org/browse/JBDS-2290
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: installer
Affects Versions: 6.0.0.Alpha2
Reporter: Fred Bricon
Fix For: 6.0.0.Alpha2
I thought m2e-apt 1.0.1 was added to the JBDS installer, as requested in JBIDE-12649 but 1.0.0 is still shipped with current JBDS 6.0.0.Alpha2.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-12761) Target-platfom should contain depdencies in the "minimal compatible" version
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-12761:
--------------------------------------
Summary: Target-platfom should contain depdencies in the "minimal compatible" version
Key: JBIDE-12761
URL: https://issues.jboss.org/browse/JBIDE-12761
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 4.0.0.Beta1
Currently, TP contains the latest version of all dependencies. However, JBT can run on lower versions of Eclipse. It happens that developer introduce a depdendency on a very recent version when it's not necessary because they rely on our target-platform.
Instead, TP should contain the minimal versions of all dependencies that are compatible with JBoss Tools. Then developers can rely on very old version, and when necessary, request usage of new one and break dependencies.
Installation tests are already there to verify installation on latest versions of Eclipse.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months