March 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15937) All seam runtimes are checked after adding/removing

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15937?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-15937: ---------------------------------------- JRE preferences is a good example. > All seam runtimes are checked after adding/removing > --------------------------------------------------- > > Key: JBIDE-15937 > URL: https://issues.jboss.org/browse/JBIDE-15937 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: seam2 > Affects Versions: 4.1.1.Beta1 > Reporter: Radoslav Rábara > Assignee: Daniel Azarov > Priority: Minor > Fix For: 4.2.0.Beta1 > > Attachments: seam runtimes - remaining are checked.jpg, seam runtimes - remove one.jpg > > > All seam runtimes are checked after new seam runtime is added or existing one is removed. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-472) Debugging OpenShift application: How to find out debugging port

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-472?page=com.atlassian.jira.plug... ] Marián Labuda updated TOOLSDOC-472: ----------------------------------- Summary: Debugging OpenShift application: How to find out debugging port (was: Debugging OpenShift application: How to find out debugging ports) > Debugging OpenShift application: How to find out debugging port > --------------------------------------------------------------- > > Key: TOOLSDOC-472 > URL: https://issues.jboss.org/browse/TOOLSDOC-472 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Environment: Build Name: 22443, User Guide-7.1 > Build Date: 28-02-2014 19:54:11 > Topic ID: 28342-590341 [Specified] > Reporter: Marián Labuda > Assignee: Michelle Murray > > It should be "nice to have" some information about "how to find debugging port" as Note. > I suggest something like (this is just simple example, it should be written in more comfortable way): > At first check available port in Port forwarding shell. After enabling debugging by creating and pushing OpenShift JPDA marker check ports and the new one is port for debugging. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-472) Debugging OpenShift application: How to find out debugging ports

by Marián Labuda (JIRA)

Marián Labuda created TOOLSDOC-472: -------------------------------------- Summary: Debugging OpenShift application: How to find out debugging ports Key: TOOLSDOC-472 URL: https://issues.jboss.org/browse/TOOLSDOC-472 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Enhancement Security Level: Public (Everyone can see) Environment: Build Name: 22443, User Guide-7.1 Build Date: 28-02-2014 19:54:11 Topic ID: 28342-590341 [Specified] Reporter: Marián Labuda Assignee: Michelle Murray It should be "nice to have" some information about "how to find debugging port" as Note. I suggest something like (this is just simple example, it should be written in more comfortable way): At first check available port in Port forwarding shell. After enabling debugging by creating and pushing OpenShift JPDA marker check ports and the new one is port for debugging. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16707) create teiid features overview for tools.jboss.org

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16707?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-16707: ---------------------------------------- Component/s: teiid (was: drools) > create teiid features overview for tools.jboss.org > -------------------------------------------------- > > Key: JBIDE-16707 > URL: https://issues.jboss.org/browse/JBIDE-16707 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: teiid, website > Reporter: Max Rydahl Andersen > Assignee: Barry LaFond > Fix For: 4.2.0.Beta1 > > > Create a features/teiid.adoc in jbosstools-website describing the main/cool features > We are refreshing jboss.org/tools (new name: tools.jboss.org) and one of the areas on the new website is a features overview page to let visitors know what features are actually covered in jboss tools. > You can see the current list at http://tools-stg.jboss.org/features/ following the pattern of component/project logo + component name + "tag line". > And then individual pages like http://tools-stg.jboss.org/features/openshift.html which follows the pattern of alternating paragraph + image/screenshot with title/tagline + description for each main feature. > It would be great if you could help create this page for your component. > The process is as follows: > git@github.com:jbosstools/jbosstools-website.git > cd jbosstools-website/features > create componentname.adoc (use i.e. openshift.adoc as inspiration with respect to header names) > Submit this page and related images as pullrequest > The expected launch of the site is end of march so the sooner the better :) -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16689) Crash after CTRL + rightclick + find implementation

by Edoardo Barolo (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16689?page=com.atlassian.jira.plugi... ] Edoardo Barolo commented on JBIDE-16689: ---------------------------------------- I'm going to reproduce the problem as soon as I'm again on dev duty.. Now they put me on manual and tech analysis writing task :( Maybe the next week :) > Crash after CTRL + rightclick + find implementation > --------------------------------------------------- > > Key: JBIDE-16689 > URL: https://issues.jboss.org/browse/JBIDE-16689 > Project: Tools (JBoss Tools) > Issue Type: Bug > Reporter: Edoardo Barolo > -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16689) Crash after CTRL + rightclick + find implementation

by Edoardo Barolo (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16689?page=com.atlassian.jira.plugi... ] Edoardo Barolo commented on JBIDE-16689: ---------------------------------------- Thank you for he suggestion Nick but I cannot use Jboss tools 7 because you removed struts support. In one of the projects I'm working struts is required and struts tooling is very useful for me. I think you should consider also that there are not only new super new tech projects on the world but also the very old one to maintain :)... In fact I cannot understand the struts tooling scrap... This is not intended as a flame but my simple personal thoughts :) > Crash after CTRL + rightclick + find implementation > --------------------------------------------------- > > Key: JBIDE-16689 > URL: https://issues.jboss.org/browse/JBIDE-16689 > Project: Tools (JBoss Tools) > Issue Type: Bug > Reporter: Edoardo Barolo > -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16689) Crash after CTRL + rightclick + find implementation

by Edoardo Barolo (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16689?page=com.atlassian.jira.plugi... ] Edoardo Barolo edited comment on JBIDE-16689 at 3/6/14 3:21 AM: ---------------------------------------------------------------- Thank you for he suggestion Nick but I cannot use Jboss tools 7 because you removed struts support. In one of the projects I'm working struts is required and struts tooling is very useful for me. I think you should consider also that there are not only super new tech projects on the world but also the very old one to maintain :)... In fact I cannot understand the struts tooling scrap... This is not intended as a flame but my simple personal thoughts :) was (Author: velteyn): Thank you for he suggestion Nick but I cannot use Jboss tools 7 because you removed struts support. In one of the projects I'm working struts is required and struts tooling is very useful for me. I think you should consider also that there are not only new super new tech projects on the world but also the very old one to maintain :)... In fact I cannot understand the struts tooling scrap... This is not intended as a flame but my simple personal thoughts :) > Crash after CTRL + rightclick + find implementation > --------------------------------------------------- > > Key: JBIDE-16689 > URL: https://issues.jboss.org/browse/JBIDE-16689 > Project: Tools (JBoss Tools) > Issue Type: Bug > Reporter: Edoardo Barolo > -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16606) New Server Wizard updated for 'profiles'

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16606?page=com.atlassian.jira.plugi... ] Martin Malina reassigned JBIDE-16606: ------------------------------------- Assignee: Rob Stryker (was: Martin Malina) Hey Rob, I commented on the other JIRA - JBIDE-15162. To add to that: On the page when you select local or rse, since we already have some wording above the combo box, perhaps we could add a line to describe the two options? I'm worried that while a lot of people know what "rse" means, still a lot others wouldn't know. I would even prefer for it to be called "remote", but maybe you think that it should be called rse, since that's what it is under the hood? > New Server Wizard updated for 'profiles' > ---------------------------------------- > > Key: JBIDE-16606 > URL: https://issues.jboss.org/browse/JBIDE-16606 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.2.0.Beta1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Beta1 > > Attachments: new-new-server.png, new_server.jpg, new_server_remote.jpg > > > With the additions of server profiles, servers in the rse profile (or others) do not necessarily require a local runtime. This means in a new server wizard, we don't need to force the user to create a runtime until they're in a profile that requires one. > This will make changes to the new server wizard workflow which may affect some swt bot tests and documentation -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16696) IllegalStateException when Arquillian deployment uses Maven resolver

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16696?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16696: --------------------------------------------- >They aren't related. After fixing the described issue, I have faced the two new issues mentioned in my previous comment. if the issues are not related please open another jira to resolve this other new issue. Thanks. > IllegalStateException when Arquillian deployment uses Maven resolver > -------------------------------------------------------------------- > > Key: JBIDE-16696 > URL: https://issues.jboss.org/browse/JBIDE-16696 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools > Affects Versions: 4.1.1.Final > Reporter: Rich DiCroce > Assignee: Snjezana Peco > > In an Arquillian test class, if the @Deployment method uses the ShrinkWrap Maven Resolver API, the method will be marked with the following warning and the Arquillian Cruiser view does not show the deployment: > {noformat} > java.lang.IllegalStateException: There is more then a one service for serviceClass org.jboss.shrinkwrap.resolver.api.maven.MavenResolverSystem(project=arquillian-bug-test) > {noformat} > There is no stack trace to indicate how the problem might be happening. At first, I thought this might be a ShrinkWrap bug, but this exception doesn't occur when I actually run the test. Eclipse shows only one implementation of MavenResolverSystem on the classpath. > Example test class to reproduce the problem: > {code} > package test; > import org.jboss.arquillian.container.test.api.Deployment; > import org.jboss.arquillian.junit.Arquillian; > import org.jboss.shrinkwrap.api.Archive; > import org.jboss.shrinkwrap.api.ShrinkWrap; > import org.jboss.shrinkwrap.api.spec.WebArchive; > import org.jboss.shrinkwrap.resolver.api.maven.Maven; > import org.junit.Test; > import org.junit.runner.RunWith; > @RunWith(Arquillian.class) > public class ARQJBTBugTest { > @Test > public void test() { > > } > > @Deployment > public static Archive<?> createDeployment() { > return ShrinkWrap.create(WebArchive.class) > .addAsLibraries(Maven.resolver() > .loadPomFromFile("pom.xml") > .importRuntimeDependencies() > .resolve() > .withTransitivity() > .asFile()); > } > > } > {code} > And the POM to go with it: > {code:xml} > <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> > <modelVersion>4.0.0</modelVersion> > <groupId>com.lapis.throwaway</groupId> > <artifactId>arquillian-bug-test</artifactId> > <version>0.0.1-SNAPSHOT</version> > <packaging>war</packaging> > <properties> > <project.build.sourceEncoding> > UTF-8 > </project.build.sourceEncoding> > <version.arquillian_core>1.1.3.Final</version.arquillian_core> > </properties> > <dependencies> > <dependency> > <groupId>junit</groupId> > <artifactId>junit</artifactId> > <version>4.10</version> > <scope>test</scope> > </dependency> > <dependency> > <groupId>org.jboss.arquillian.junit</groupId> > <artifactId>arquillian-junit-container</artifactId> > <scope>test</scope> > </dependency> > <dependency> > <groupId>org.jboss.shrinkwrap.resolver</groupId> > <artifactId>shrinkwrap-resolver-impl-maven-archive</artifactId> > <scope>test</scope> > </dependency> > </dependencies> > <dependencyManagement> > <dependencies> > <dependency> > <groupId>org.jboss.arquillian</groupId> > <artifactId>arquillian-bom</artifactId> > <version>${version.arquillian_core}</version> > <type>pom</type> > <scope>import</scope> > </dependency> > </dependencies> > </dependencyManagement> > <build> > <plugins> > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-compiler-plugin</artifactId> > <version>2.5.1</version> > <configuration> > <source>1.7</source> > <target>1.7</target> > </configuration> > </plugin> > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-surefire-plugin</artifactId> > <version>2.12</version> > </plugin> > </plugins> > </build> > </project> > {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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15937) All seam runtimes are checked after adding/removing

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15937?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-15937: --------------------------------------- OK, now I get why it happens (probably) - the seam runtimes are all effectively default (unless you have two or more of the same version). I agree, it would be better to ensure they stay checked, but I'm not sure how to handle this - maybe take the approach of Installed JREs? When you uncheck the default JRE, you get an error message that at least one has to be selected (in this case we would need to add "of this version"). > All seam runtimes are checked after adding/removing > --------------------------------------------------- > > Key: JBIDE-15937 > URL: https://issues.jboss.org/browse/JBIDE-15937 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: seam2 > Affects Versions: 4.1.1.Beta1 > Reporter: Radoslav Rábara > Assignee: Daniel Azarov > Priority: Minor > Fix For: 4.2.0.Beta1 > > Attachments: seam runtimes - remaining are checked.jpg, seam runtimes - remove one.jpg > > > All seam runtimes are checked after new seam runtime is added or existing one is removed. -- 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

12 years, 3 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 March 2014