April 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14343) jenkins password reported in creation dialog and in environment variables dont match

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14343?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-14343: ------------------------------------------ The username and pw reported in the *environment variables* are valid (I just verified them, I could log in). The ones in the creation log are valid, too. Both seem equivalent at first sight. > jenkins password reported in creation dialog and in environment variables dont match > ------------------------------------------------------------------------------------ > > Key: JBIDE-14343 > URL: https://issues.jboss.org/browse/JBIDE-14343 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Beta1 > > Attachments: creation-log.png, creation-log.png, environment-variables.png, environment-variables.png > > > The pw as reported in the creation dialog and in the environment variables dont match (they differ from each other). > This is most likely a WATCHER issue since this is handled by the backend. I have to further investigate though (29.4.2013) -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14342) I dont get credentials reported when I create a jenkins initially (when creating an app)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14342?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14342: ------------------------------------- Priority: Critical (was: Major) > I dont get credentials reported when I create a jenkins initially (when creating an app) > ---------------------------------------------------------------------------------------- > > Key: JBIDE-14342 > URL: https://issues.jboss.org/browse/JBIDE-14342 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.1.0.Beta1 > > Attachments: correct-creation-log.png, null-creation-log.png > > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14342) I dont get credentials reported when I create a jenkins initially (when creating an app)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14342?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14342: ------------------------------------- Priority: Major (was: Critical) > I dont get credentials reported when I create a jenkins initially (when creating an app) > ---------------------------------------------------------------------------------------- > > Key: JBIDE-14342 > URL: https://issues.jboss.org/browse/JBIDE-14342 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Beta1 > > Attachments: correct-creation-log.png, null-creation-log.png > > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14342) I dont get credentials reported when I create a jenkins initially (when creating an app)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14342?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-14342: ------------------------------------------ I'm not sure that this behaviour is limited to creating jenkins beforehand (before creating the app). It actually happens to me quite often (right now) when embedding afterwards. > I dont get credentials reported when I create a jenkins initially (when creating an app) > ---------------------------------------------------------------------------------------- > > Key: JBIDE-14342 > URL: https://issues.jboss.org/browse/JBIDE-14342 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.1.0.Beta1 > > Attachments: correct-creation-log.png, null-creation-log.png > > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13762) add ui to handle error in case of typo in system properties or discovery plugin

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13762?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-13762: --------------------------------------- It was fixed in Alpha2. > add ui to handle error in case of typo in system properties or discovery plugin > ------------------------------------------------------------------------------- > > Key: JBIDE-13762 > URL: https://issues.jboss.org/browse/JBIDE-13762 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Max Rydahl Andersen > Assignee: Snjezana Peco > Fix For: 4.1.0.Beta1 > > > if system properties are broken or discovery has bugs (i.e. bad url or url/host not found) there currently are no error handling that inform the user nor us what went wrong. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13799) Source Lookup enhancements

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13799?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-13799: --------------------------------------- I am waiting for JBIDE-14003 to be applied. > Source Lookup enhancements > -------------------------- > > Key: JBIDE-13799 > URL: https://issues.jboss.org/browse/JBIDE-13799 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven > Affects Versions: 4.1.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > Fix For: 4.1.0.Beta1 > > > The PR includes the following enhancements: > - AS 7.2/EAP 6.1 are now recognized correctly > - the fix for the issue caused by changing the editor ID for ClassFileEdtor in 3.8/4.2 > - the fix for the ConcurrentModificationException exception > - included libraries can be filtered - jsf 1.2 and hibernate 3 will be excluded by default for JBoss AS Container > - JBoss Runtimes now can be included in the Java Search (this feature has been implemented in a similar way to adding PDE plugins to the Java Search) > - JBoss Java Project Source Container > See http://screencast.com/t/39LHqYx5m > Screenshot shows debugging the WeldBootstrap class in JBoss AS 7.1 and JBoss AS 7.2. > Note: > You have to have some deployment on the servers in order the WeldBootstrap class to be created. > You can add more JBoss servers to the Java Search, but it is the best to use only one at a time because of the performance reason. > The "Automatically add the JBoss Maven source container to all JBoss AS launch configurations" and "Include the following JBoss Servers in the Java Search" checkboxes aren't related. The first checkbox adds the source container that enables finding a Java source file when debugging, the second enables finding a Java source file using the Java Search (using the "Open type" command, for instance). -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13720) Add JBoss Portal Platform (JPP) 6.0.0 to downloadable runtimes

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13720?page=com.atlassian.jira.plugi... ] Peter Palaga commented on JBIDE-13720: -------------------------------------- Hi Max, should I care for adding to stacks.yml? > Add JBoss Portal Platform (JPP) 6.0.0 to downloadable runtimes > -------------------------------------------------------------- > > Key: JBIDE-13720 > URL: https://issues.jboss.org/browse/JBIDE-13720 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: runtime-detection > Reporter: Peter Palaga > Fix For: 4.1.0.Beta1 > > > Please post downloadId here when fixed. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13852) JBoss Java Project Source Container

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13852?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-13852: --------------------------------------- JBoss Java Project Source Container (Debugging Arquillian tests) When debugging an Arquillian test using a remote container, we usually do the following steps: - create a project - add the Arquillian support - create a test - configure Maven profiles - create a JBoss server - start the server in the debug mode - start the test in the debug mode We can debug the classes from the project's source by adding the Eclipse Java Project source container to the Source Lookup. However, if we want to debug some Arquillian code in a server (remote) JVM, adding the Eclipse container won't be enough. The Arquillian classes aren't included in a JBoss server and the Java Project source container searches only the project's source folders. If we can deploy the project, the JBoss Source Lookup plugin will solve all the classes from a mavenized archive so that we can debug the classes from such a project. If we can't (or don't want to) deploy the project, we can use the JBoss Java Project Source Container from the arquillian eclipse plugin. The JBoss Java Project Source Container is similar to the Java Project source container. The differ is that it searches classes from the project's classpath. The container solves source files for all the classes from a mavenized library included in the classpath. The project can, but doesn't have to be a Maven project. Test case: - create a JBoss AS Server - import the JBoss Central Java EE project (don't deploy it) - set a breakpoint in the org.jboss.arquillian.junit.Arquillian.methodInvoker(FrameworkMethod, Object) method (at line 270 in Arquillian 1.0.3) - start the server in the debug mode from JBT/JBDS - debug MemberRegistrationTest The Eclipse won't open the Arquillian source file, which happens because this method is called from within the server's JVM that doesn't know anything about the Java EE project. Adding the Eclipse Java Project source container won't help because it adds only source folders. The Remote Debug feature also won't help because we have started the server from JBT/JBDS so that we are already connected to the JVM. - install/update the Source Lookup plugin from http://snjeza.github.com/jbosstools-central - add the JBoss Java Project Source Container to the Source Lookup You will be able to debug any class from the project. It is possible to create different helper projects and add the container to different remote launch configurations. The JBoss Java Project Source Container isn't related to the arquillian-eclipse feature and/or JBoss servers and can be added to any launch configuration. See http://screencast.com/t/fHTO6ZP5dFh > JBoss Java Project Source Container > ----------------------------------- > > Key: JBIDE-13852 > URL: https://issues.jboss.org/browse/JBIDE-13852 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: maven > Affects Versions: 4.1.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > Fix For: 4.1.0.Beta1 > > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2535) JBDS70_0315, JBDS70_0413: [Commit] (Dev) (P3) Offline - Installation

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2535?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-2535. ---------------------------- Release Notes Docs Status: Not Yet Documented Assignee: Nick Boldt Release Notes Text: Installer jar can now be used as an update site archive too. Fix Version/s: 7.0.0.Beta1 Resolution: Done > JBDS70_0315, JBDS70_0413: [Commit] (Dev) (P3) Offline - Installation > -------------------------------------------------------------------- > > Key: JBDS-2535 > URL: https://issues.jboss.org/browse/JBDS-2535 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Requirements > Affects Versions: 7.0.0.GA > Reporter: Jiri Pallich > Assignee: Nick Boldt > Priority: Minor > Fix For: 7.0.0.Beta1 > > > Getting the Installer > Getting the Update site -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2556) JBDS70_0315, JBDS70_0413: [Commit] (Dev) (P2) Offline - JBDS Update Site Zip

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2556?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-2556. ---------------------------- Release Notes Docs Status: Not Yet Documented Release Notes Text: Installer jar can now be used as an update site archive too. Resolution: Done As [~dgolovin] reported in JBDS-2535, we no longer need to provide the update site zip, because the installer jar IS a viable update site archive. Verified: I can do {quote}Help > Install > Add... > Archive... > browse for a JBDS installer jar > jar:file:/home/nboldt/tmp/jbdevstudio-product-eap-universal-7.0.0.Beta1-v20130424-0301-B3478.jar!/ > install the JBDS feature(s) > restart > done! {quote} > JBDS70_0315, JBDS70_0413: [Commit] (Dev) (P2) Offline - JBDS Update Site Zip > ---------------------------------------------------------------------------- > > Key: JBDS-2556 > URL: https://issues.jboss.org/browse/JBDS-2556 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: central > Reporter: Jiri Pallich > Assignee: Nick Boldt > Fix For: 7.0.0.Beta1 > > > Offline Usage of JBoss Central (Customers without or very slow Internet access) > On-line once, then off-line - aka a user demo/instructional class - the testLocal cache is usable/complete after one on-line install. Provide a script that pre-caches everything for an instructor/demo'er in the field (online once, then offline). > Related to: JBDS-2535 -- 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, 11 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 April 2013