October 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-12459) git repository for imported project is not detected correctly if it is in the parent folder

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-12459: ---------------------------------------- Summary: git repository for imported project is not detected correctly if it is in the parent folder Key: JBIDE-12459 URL: https://issues.jboss.org/browse/JBIDE-12459 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.Final Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.2, 3.4.0.M1 When the application creation wizard tries to merge into an existing project, it does not detect the git repository correctly if the given project is within a folder of a git repo. -- 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, 3 months

1
6
0 / 0

[JBoss JIRA] (JBIDE-12252) Multi-module project throws ClassNotFoundException when deployed on OpenShift's EAP

by Stefan Bunciak (JIRA)

13 years, 3 months

3
18
0 / 0

[JBoss JIRA] (JBIDE-12121) The openshift profile is added to newly created maven projects, regardless of their packaging type

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-12121: ----------------------------------- Summary: The openshift profile is added to newly created maven projects, regardless of their packaging type Key: JBIDE-12121 URL: https://issues.jboss.org/browse/JBIDE-12121 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.CR1 Reporter: Fred Bricon Assignee: Andre Dietisheim Fix For: 3.3.1 I created a project using the org.openarchetypes:multi-javaee6-archetype:0.0.1-SNAPSHOT from http://open-archetypes.github.com/maven-repo/snapshots/archetype-catalog.xml (Maven > Archetypes > Add Remote Catalog) This creates a multi module project, containing a parent pom, an ear, war, ejb and utility projects. This openshift profile was added to the pom project : {code:xml} <profiles> <profile>     <id>openshift</id> <build> <finalName>hello</finalName> <plugins> <plugin> <artifactId>maven-war-plugin</artifactId> <version>2.1.1</version> <configuration> <outputDirectory>deployments</outputDirectory> <warName>ROOT</warName> </configuration> </plugin> </plugins> </build> </profile> {code} Actually, it should : - check the packaging type of *all* the generated projects - if some EARs are found, then add the following to the parent pom (pay attention to the <pluginManagement> section) : {code:xml} <profile> <id>openshift</id> <build> <pluginManagement> <plugins> <plugin> <artifactId>maven-ear-plugin</artifactId> <version>2.7</version> <configuration> <outputDirectory>deployments</outputDirectory> </configuration> </plugin> </plugins> </pluginManagement> </build> </profile> {code} - if there are no EARs but some WARs are found (count them), then add the following to the parent pom (pay attention to the <pluginManagement> section) : {code:xml} <profiles> <profile> <id>openshift</id> <build> <pluginManagement> <plugins> <plugin> <artifactId>maven-war-plugin</artifactId> <version>2.2</version> <configuration> <outputDirectory>deployments</outputDirectory>  <warName>ROOT</warName> </configuration> </plugin> </plugins> </pluginManagement> </build> </profile> {code} The finalName is irrelevant to openshift, only the warName counts. -- 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, 3 months

3
10
0 / 0

[JBoss JIRA] (JBIDE-12098) OpenShift Explorer: Timeout exception when forcing domain deletion

by Stefan Bunciak (JIRA)

Stefan Bunciak created JBIDE-12098: -------------------------------------- Summary: OpenShift Explorer: Timeout exception when forcing domain deletion Key: JBIDE-12098 URL: https://issues.jboss.org/browse/JBIDE-12098 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.CR1 Reporter: Stefan Bunciak Assignee: Andre Dietisheim Priority: Critical Fix For: 3.3.0.CR1, 3.3.x Attachments: deletedomain.png Tried to force domain deletion while having (medium geared) application on OpenShift. Screenshot: !deletedomain.png|thumbnail! Stack trace: {code} com.openshift.client.OpenShiftTimeoutException: Could not request url https://openshift.redhat.com/broker/rest/domains/rhdomain, connection timed out at com.openshift.internal.client.RestService.request(RestService.java:109) at com.openshift.internal.client.RestService.request(RestService.java:89) at com.openshift.internal.client.RestService.request(RestService.java:74) at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:137) at com.openshift.internal.client.DomainResource$DeleteDomainRequest.execute(DomainResource.java:329) at com.openshift.internal.client.DomainResource.destroy(DomainResource.java:166) at org.jboss.tools.openshift.express.internal.ui.action.DeleteDomainAction$1.run(DeleteDomainAction.java:94) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code} -- 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, 3 months

2
15
0 / 0

[JBoss JIRA] (JBDS-2335) JBDS 6.0..alpha2 - Mylun plugin displays unclear error message with bad login to JBoss JIRA

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-2335: ---------------------------------- Summary: JBDS 6.0..alpha2 - Mylun plugin displays unclear error message with bad login to JBoss JIRA Key: JBDS-2335 URL: https://issues.jboss.org/browse/JBDS-2335 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: 3rdPartyCertification Affects Versions: 6.0.0.Alpha2 Environment: Version: 6.0.0.Alpha2 Build id: Alpha2-v20120924-2110-B28 Build date: 20120924-2110 Reporter: Len DiMaggio Fix For: 6.0.0.Beta1 If a user attempts to connect to JBoss JIRA with an invalid password, this error is returned to the user: JIRA RPC services are not enabled. Please contact your JIRA administrator. A better error message would explicitly refer to an invalid username/password. -- 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, 3 months

3
9
0 / 0

[JBoss JIRA] (JBIDE-12384) Error trying install JBoss SOA tools 3.? for Eclipse 4.2 (Juno) has error

by Robb Greathouse (JIRA)

Robb Greathouse created JBIDE-12384: --------------------------------------- Summary: Error trying install JBoss SOA tools 3.? for Eclipse 4.2 (Juno) has error Key: JBIDE-12384 URL: https://issues.jboss.org/browse/JBIDE-12384 Project: Tools (JBoss Tools) Issue Type: Bug Components: SOA Tooling Affects Versions: 3.3.1 Environment: MacOS Mountain Lion with Eclipse 4.2 (Juno). Reporter: Robb Greathouse Assignee: Douglas Palmer -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] (JBIDE-12371) Update Eclipse Target Platform to use Graphiti 0.9

by Rob Cernich (JIRA)

Rob Cernich created JBIDE-12371: ----------------------------------- Summary: Update Eclipse Target Platform to use Graphiti 0.9 Key: JBIDE-12371 URL: https://issues.jboss.org/browse/JBIDE-12371 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: SOA Tooling, SwitchYard, target-platform Affects Versions: 3.3.x Reporter: Rob Cernich Assignee: Douglas Palmer Priority: Critical SwitchYard loosely integrates with the Eclipse BPMN2 editor, which has recently upgraded to Graphiti 0.9. Because of this, SwitchYard could not be installed alongside the BPMN2, so SwitchYard needed to upgrade to Graphiti 0.9. This has caused the soa-tools 3.3.x aggregate build to fail because it cannot locate the Graphiti 0.9 plugins. If SwitchYard is the only project relying on Graphiti, we can simply upgrade the target platforms for Indigo and Juno to include Graphiti 0.9. -- 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, 3 months

3
6
0 / 0

[JBoss JIRA] (JBIDE-12409) Smooks Editor is not properly connecting source and target data, drawing lines on random directions

by Isaac Rooskov (JIRA)

Isaac Rooskov created JBIDE-12409: ------------------------------------- Summary: Smooks Editor is not properly connecting source and target data, drawing lines on random directions Key: JBIDE-12409 URL: https://issues.jboss.org/browse/JBIDE-12409 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.2.2.Final Reporter: Vinicius Martinez Assignee: Brian Fitzpatrick Priority: Critical *From Bugzilla* Description of problem: Users are facing an accord issue with Smooks Editor which is not connecting input and outputs sources, thus, it's drawing lines on "random" directions Steps to Reproduce: 1- Create a new ESB project 2 - File > New > Other > Smooks Configuration File 3 - Select Input Task 4 -Set Input Type to XSD/WSDL 5 - Add an XSD file in the Input Data section 6 - Click (+) next to Input Task > Apply Template > Message Type XML > Load an XSD file Actual results: Line does not connect two elements, and is drawn in a random direction Expected results: The "connection" between Input and Destiny should be perfectly aligned Isaac's Note: Setting Vinicius as the reporter since he was in Bugzilla. -- 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, 3 months

2
4
0 / 0

[JBoss JIRA] (JBIDE-10929) Support for password not being kept in secure storage

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-10929: ------------------------------------- Summary: Support for password not being kept in secure storage Key: JBIDE-10929 URL: https://issues.jboss.org/browse/JBIDE-10929 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.Beta1 Reporter: Xavier Coulon Assignee: Rob Stryker Fix For: 3.3.x Currently, OpenShift accounts' passwords are kept in the secure storage, even if the user did not set the 'Save password' checkbox to true. -- 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, 3 months

5
21
0 / 0

[JBoss JIRA] (JBIDE-12862) OpenShift Connection dialog overwrites user accounts in OpenShift Explorer

by Stefan Bunciak (JIRA)

Stefan Bunciak created JBIDE-12862: -------------------------------------- Summary: OpenShift Connection dialog overwrites user accounts in OpenShift Explorer Key: JBIDE-12862 URL: https://issues.jboss.org/browse/JBIDE-12862 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.0.0.Beta1 Reporter: Stefan Bunciak Assignee: Andre Dietisheim Priority: Critical Fix For: 4.0.0.Beta1 User gets stucked even with just 2 OpenShift accounts. -- 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, 3 months

3
13
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 2012