June 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15021) forge2 runtime cannot be built locally

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15021?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-15021: --------------------------------------- works for me after I build/install forge/core 2.0 branch to the same local maven repository I use to build forge module > forge2 runtime cannot be built locally > -------------------------------------- > > Key: JBIDE-15021 > URL: https://issues.jboss.org/browse/JBIDE-15021 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.CR1 > Reporter: Max Rydahl Andersen > Priority: Critical > Fix For: 4.1.0.CR1 > > > both @dgolovin and I cannot build forge2 runtime: > "[ERROR] Failed to execute goal org.jboss.forge:forge-maven-plugin:1.0.0.Alpha5:addon-install (deploy-addons) on project org.jboss.tools.forge2.runtime: Execution deploy-addons of goal org.jboss.forge:forge-maven-plugin:1.0.0.Alpha5:addon-install failed: A required class was missing while executing org.jboss.forge:forge-maven-plugin:1.0.0.Alpha5:addon-install: org/apache/maven/repository/internal/MavenServiceLocator > [ERROR] -----------------------------------------------------" > it works on jenkins but not locally. > Tried using both java6 and java7 - same problem -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14922) There is no problem icon on the file with problems in Package/Project explorer

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14922?page=com.atlassian.jira.plugi... ] Victor Rubezhny edited comment on JBIDE-14922 at 6/28/13 3:55 PM: ------------------------------------------------------------------ Issue is not reproducible for me neither while using JBDS 7.0.0Beta2, nor while Eclipse 4.3 (Release) + WTP 3.5 (Release). BUt it's easily reproducible in JBT 4.1.0.Beta2 installed on Eclipse 4.3 (Release). So, probably the real reason somewhere in difference between JBT and JBDS. was (Author: vrubezhny): I suppose that this is UpStream issue, a result of [Bug 224571|https://bugs.eclipse.org/bugs/show_bug.cgi?id=224571] - [Decorators] Missing problem markers on IFile in Package Explorer. Issue is not reproducible for me neither while using JBDS 7.0.0Beta2, nor while Eclipse 4.3 (Release) + WTP 3.5 (Release). > There is no problem icon on the file with problems in Package/Project explorer > ------------------------------------------------------------------------------ > > Key: JBIDE-14922 > URL: https://issues.jboss.org/browse/JBIDE-14922 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.1.0.Beta2 > Reporter: Alexey Kazakov > Assignee: Victor Rubezhny > Priority: Minor > Fix For: 4.1.1.Final > > Attachments: scr.png > > > If there is a validation problem in some xml or xhtml file I can see a problem marker in Problems view. Also I see a problem icon on the parent folder of the file but there is no problem icon on the file. > We need to investigate it and report in bugzilla if it's a pure upstream issue or fix the issue if it's a JBT bug. > !scr.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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15021) forge2 runtime cannot be built locally

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15021?page=com.atlassian.jira.plugi... ] Denis Golovin edited comment on JBIDE-15021 at 6/28/13 3:42 PM: ---------------------------------------------------------------- after adding making copy of settings.xml from jenkins build still cannot resolve two addons: {code}<addonId>org.jboss.forge.addon:addons,${version.forge}</addonId> <addonId>org.jboss.forge.addon:addon-manager,${version.forge}</addonId>{code} I can build forge2.runtime only after those two addons removed from list. was (Author: dgolovin): after adding making copy of settings.xml from jenkins build still cannot resolve two addons: <addonId>org.jboss.forge.addon:addons,${version.forge}</addonId> <addonId>org.jboss.forge.addon:addon-manager,${version.forge}</addonId> I can build forge2.runtime only after those two addons removed from list. > forge2 runtime cannot be built locally > -------------------------------------- > > Key: JBIDE-15021 > URL: https://issues.jboss.org/browse/JBIDE-15021 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.CR1 > Reporter: Max Rydahl Andersen > Priority: Critical > Fix For: 4.1.0.CR1 > > > both @dgolovin and I cannot build forge2 runtime: > "[ERROR] Failed to execute goal org.jboss.forge:forge-maven-plugin:1.0.0.Alpha5:addon-install (deploy-addons) on project org.jboss.tools.forge2.runtime: Execution deploy-addons of goal org.jboss.forge:forge-maven-plugin:1.0.0.Alpha5:addon-install failed: A required class was missing while executing org.jboss.forge:forge-maven-plugin:1.0.0.Alpha5:addon-install: org/apache/maven/repository/internal/MavenServiceLocator > [ERROR] -----------------------------------------------------" > it works on jenkins but not locally. > Tried using both java6 and java7 - same problem -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-69) Refactor TP POM for nexus deployment consistency

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-69?page=com.atlassian.jira.plugin.s... ] Paul Leacu commented on JBTIS-69: --------------------------------- Staging deployment/ release promotion complete for JBTIS-4.0.1 TP. Ref: https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... https://github.com/jbosstools/jbosstools-integration-stack/commit/25db000... > Refactor TP POM for nexus deployment consistency > ------------------------------------------------ > > Key: JBTIS-69 > URL: https://issues.jboss.org/browse/JBTIS-69 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: target-platform > Affects Versions: 4.0.0, 4.1.0.Beta1 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.1.0.Beta1 > > > Depends on the GAV of the thing you deployed. > I might consider refactoring your pom so that it ends up in this folder, > for consistency: > https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... > As you can see, we have 2 TPs for each (unified, multiple) of > jbdevstudio and jbosstools. You could have jbds-is and jbt-is, or > perhaps jbdevstudio-integration and jbosstools-integration. > The way the path is produced comes from the pom: > https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... > <groupId>org.jboss.tools.targetplatforms</groupId> (from parent) > <artifactId>jbdevstudio-multiple</artifactId> > <version>4.30.5.Alpha3</version> (from parent) -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-3628) Plugins should be .jar's not directories for efficiency sake

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-3628?page=com.atlassian.jira.plugin... ] Denis Golovin edited comment on JBIDE-3628 at 6/28/13 3:21 PM: --------------------------------------------------------------- {quote} eclipse knows how to handle jars inside jared plugins, it put all such jars into cache and then use them without unzipping constantly.{quote} The jars should be just referenced right way in Runtime section of manifest.https://issues.jboss.org/browse/JBIDE was (Author: dgolovin): {quote} eclipse knows how to handle jars inside jared plugins, it put all such jars into cache and then use them without unzipping constantly.{quote} The jars should be just referenced right way in Runtime section of manifest. > Plugins should be .jar's not directories for efficiency sake > ------------------------------------------------------------ > > Key: JBIDE-3628 > URL: https://issues.jboss.org/browse/JBIDE-3628 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Build/Releng > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 4.2.0.Alpha1 > > Attachments: exception.log > > > 65 of our plugins are bundled exploded instead of a .jar > Some are probably just mistakes and can easily be packed others are because of legacy code assuming it can access the files directly and even store data in the plugins - that should be fixed. > What should be fixed: > 1. The way how plug-ins use images in plugin.xml, in java code and in .meta xmodel files > 2. Plug-ins that loads resources should be aware that they are in jar now (VPE should be able to load templates from plugin jar files) > 3. Some plug-ins contain resources registered in XML catalog > 4. common.projecttemplates contains resources that is used as template for new projects > 5. TBD -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11348) Not generate clientsample codes in user-created folder on JBoss web services, only in src folder.

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11348?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-11348: ---------------------------------- Fix Version/s: 3.3.2.Final > Not generate clientsample codes in user-created folder on JBoss web services, only in src folder. > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-11348 > URL: https://issues.jboss.org/browse/JBIDE-11348 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Affects Versions: 3.3.0.M5 > Environment: Eclipse Indigo 3.7.2, JBossTools 3.3 > Reporter: Joseph Hwang > Assignee: Brian Fitzpatrick > Priority: Minor > Fix For: 3.3.2.Final > > Attachments: 1_buildpath.jpg, 2_no_folder_choice.jpg, 3_generate_user_defined_folder.jpg, 4_choose_user_defined_folder.jpg, 5_generate_ws_client_code.jpg, 6_no_client_sample.jpg, 7_choose_src_folder.jpg, client_2.jpg, client_3.jpg, client_4.jpg, generating_client.doc, HelloWorld.zip, readme_pls.docx > > > Web Services deployment is ok! But generating clientsample codes is failed in user-created folder. > clientsample codes is generated only in default 'src' folder. > Pls, check this thread https://community.jboss.org/thread/196669?start=0&tstart=0 . -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11348) Not generate clientsample codes in user-created folder on JBoss web services, only in src folder.

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11348?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-11348: ---------------------------------- Fix Version/s: (was: 4.0.x) > Not generate clientsample codes in user-created folder on JBoss web services, only in src folder. > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-11348 > URL: https://issues.jboss.org/browse/JBIDE-11348 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Affects Versions: 3.3.0.M5 > Environment: Eclipse Indigo 3.7.2, JBossTools 3.3 > Reporter: Joseph Hwang > Assignee: Brian Fitzpatrick > Priority: Minor > Attachments: 1_buildpath.jpg, 2_no_folder_choice.jpg, 3_generate_user_defined_folder.jpg, 4_choose_user_defined_folder.jpg, 5_generate_ws_client_code.jpg, 6_no_client_sample.jpg, 7_choose_src_folder.jpg, client_2.jpg, client_3.jpg, client_4.jpg, generating_client.doc, HelloWorld.zip, readme_pls.docx > > > Web Services deployment is ok! But generating clientsample codes is failed in user-created folder. > clientsample codes is generated only in default 'src' folder. > Pls, check this thread https://community.jboss.org/thread/196669?start=0&tstart=0 . -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12306) OpenShift wizard remebers filled app info even though I'm using a different user

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12306?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-12306: ---------------------------------- Fix Version/s: 4.0.0.Alpha1 (was: 4.0.x) > OpenShift wizard remebers filled app info even though I'm using a different user > -------------------------------------------------------------------------------- > > Key: JBIDE-12306 > URL: https://issues.jboss.org/browse/JBIDE-12306 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.0.0.Alpha1 > > Attachments: JBIDE-11310.patch, JBIDE12306.patch, prefilled.png > > > The wizard model probably doesn't refresh/reset... -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12306) OpenShift wizard remebers filled app info even though I'm using a different user

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12306?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-12306: --------------------------------------- 3.4.0.M1 was changed to 4.0.0.Alpha1 > OpenShift wizard remebers filled app info even though I'm using a different user > -------------------------------------------------------------------------------- > > Key: JBIDE-12306 > URL: https://issues.jboss.org/browse/JBIDE-12306 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.0.x > > Attachments: JBIDE-11310.patch, JBIDE12306.patch, prefilled.png > > > The wizard model probably doesn't refresh/reset... -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14987) Forge 2 Notification Popup is not working in Windows 8

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14987?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-14987: ---------------------------------- Fix Version/s: 4.1.0.CR1 > Forge 2 Notification Popup is not working in Windows 8 > ------------------------------------------------------ > > Key: JBIDE-14987 > URL: https://issues.jboss.org/browse/JBIDE-14987 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.Beta1 > Environment: JBoss Developer Studio 7.0.0.Beta1 > Reporter: George Gastaldi > Fix For: 4.1.0.CR1 > > > The following exception is thrown: > {code} > Caused by: java.lang.NullPointerException > at org.jboss.tools.forge.ui.notifications.NotificationDialog.calculateInitialLocation(NotificationDialog.java:80) > at org.jboss.tools.forge.ui.notifications.NotificationDialog.createShell(NotificationDialog.java:68) > at org.jboss.tools.forge.ui.notifications.NotificationDialog.<init>(NotificationDialog.java:55) > at org.jboss.tools.forge.ui.notifications.NotificationDialog.notify(NotificationDialog.java:29) > at org.jboss.tools.forge.ui.ext.wizards.ForgeWizard$1.run(ForgeWizard.java:123) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135){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

10 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2013