June 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-12131) remote is not listened to by server adatper

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-12131: ------------------------------------------- Summary: remote is not listened to by server adatper Key: JBIDE-12131 URL: https://issues.jboss.org/browse/JBIDE-12131 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Reporter: Max Rydahl Andersen Assignee: Rob Stryker Priority: Critical Fix For: 3.3.0.CR1 create a project via openshift, set the remote to be something else than origin and with a different repo address. Most easily done by cloning a different openshift project and try add that to an existing one. Or just edit in the server adapter or edit the .settings/*openshift* file to have a different remote. Push via server adapter and notice the repository used is *not* what the remote is pointing to. The failing code is: String remoteName = behaviour.getServer().getAttribute(ExpressServerUtils.ATTRIBUTE_REMOTE_NAME, ExpressServerUtils.ATTRIBUTE_REMOTE_NAME_DEFAULT); from ExpressPublishMethod which does not get the right remote name. -- 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, 9 months

3
9
0 / 0

[JBoss JIRA] (JBIDE-12112) Not able to merge git-versioned and OpenShift application

by Stefan Bunciak (JIRA)

Stefan Bunciak created JBIDE-12112: -------------------------------------- Summary: Not able to merge git-versioned and OpenShift application Key: JBIDE-12112 URL: https://issues.jboss.org/browse/JBIDE-12112 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.x Attachments: git1.png, git2.png, git3.png While testing the capability to deploy on OpenShift an already (git) versioned project I bounced into few inconsistent situations. -- 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, 9 months

5
22
0 / 0

[JBoss JIRA] (JBIDE-12048) Maven GWT compiler seem to assume projects that uses gwt-compiler is always a WTP project

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-12048: ------------------------------------------- Summary: Maven GWT compiler seem to assume projects that uses gwt-compiler is always a WTP project Key: JBIDE-12048 URL: https://issues.jboss.org/browse/JBIDE-12048 Project: Tools (JBoss Tools) Issue Type: Bug Components: GWT, maven Reporter: Max Rydahl Andersen Assignee: Denis Golovin Priority: Critical Fix For: 3.3.0.CR1, 3.3.1 User found that if he uses gwt-compiler-plugin and the project does not have wtp on it we fail hard. Not sure what we can do besides just fail silently here or is there a way to survive without knowing the webcontent folder ? -- 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, 9 months

5
9
0 / 0

[JBoss JIRA] Created: (JBDS-1699) Product build should be able to source from upstream Updatesite build when set to RELEASE=Yes

by Nick Boldt (JIRA)

Product build should be able to source from upstream Updatesite build when set to RELEASE=Yes --------------------------------------------------------------------------------------------- Key: JBDS-1699 URL: https://issues.jboss.org/browse/JBDS-1699 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Affects Versions: 5.0.0.M2 Reporter: Nick Boldt Fix For: 5.0.0.M3 When RELEASE=Yes, zips are generated w/ a suffix such as http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_stable... When RELEASE=No, zips are generated w/ a static suffix: http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_stable... Currently, a number of files in JBDS product builder assume the filename for this file is static. For example, releng/org.jboss.ide.eclipse.releng/builders/jbds-all-package/build.properties, line 38, points at jar:file:${repoBaseLocation}/extras-Update-SNAPSHOT.zip!/ and cannot resolve variables like ${ZIPSUFFIX} or ${jbds.extra.build.archive} as defined in releng/org.jboss.ide.eclipse.releng/requirements/jbds-extra-update/build.properties. As such, this filename must currently be hard-coded and the upstream updatesite job must be set to RELEASE=No. Instead, any suffix should be supported via fetching the file's name from here: http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_stable... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
4
0 / 0

[JBoss JIRA] (JBIDE-11710) java.util.ConcurrentModificationException while compiling default Java EE Project (from JBoss Central)

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-11710: ------------------------------------ Summary: java.util.ConcurrentModificationException while compiling default Java EE Project (from JBoss Central) Key: JBIDE-11710 URL: https://issues.jboss.org/browse/JBIDE-11710 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 3.3.0.Beta3 Environment: JBT 3.3.0.Beta3-trunk, L64 Reporter: Jiri Peterka Assignee: Alexey Kazakov Fix For: 3.3.0.CR1 java.util.ConcurrentModificationException while compiling default Java EE Project (from JBoss Central). Unable to replicate again java.util.ConcurrentModificationException at java.util.Hashtable$Enumerator.next(Hashtable.java:1081) at org.eclipse.wst.html.core.internal.modelquery.CMNamedNodeMapForBuddySystem.makeBuddySystem(CMNamedNodeMapForBuddySystem.java:100) at org.eclipse.wst.html.core.internal.modelquery.CMDocumentForBuddySystem$Elements.<init>(CMDocumentForBuddySystem.java:36) at org.eclipse.wst.html.core.internal.modelquery.CMDocumentForBuddySystem.getElements(CMDocumentForBuddySystem.java:90) at org.eclipse.wst.xml.core.internal.contentmodel.modelqueryimpl.SimpleAssociationProvider.getCMElementDeclaration(SimpleAssociationProvider.java:45) at org.eclipse.wst.xml.core.internal.contentmodel.modelqueryimpl.ModelQueryImpl.getCMElementDeclaration(ModelQueryImpl.java:116) at org.eclipse.wst.html.core.internal.modelquery.HTMLModelQueryImpl.getCMElementDeclaration(HTMLModelQueryImpl.java:152) at org.eclipse.wst.xml.core.internal.document.ElementImpl.getDeclaration(ElementImpl.java:369) at org.eclipse.wst.xml.core.internal.document.CMNodeUtil.getElementDeclaration(CMNodeUtil.java:40) at org.eclipse.wst.html.core.internal.document.HTMLModelParserAdapter.canContain(HTMLModelParserAdapter.java:86) at org.eclipse.wst.xml.core.internal.document.XMLModelParser.insertNode(XMLModelParser.java:1327) at org.eclipse.wst.xml.core.internal.document.XMLModelParser.insertStartTag(XMLModelParser.java:1402) at org.eclipse.wst.xml.core.internal.document.XMLModelParser.insertStartTag(XMLModelParser.java:1499) at org.eclipse.wst.xml.core.internal.document.XMLModelParser.insertStructuredDocumentRegion(XMLModelParser.java:1510) at org.eclipse.wst.xml.core.internal.document.XMLModelParser.replaceStructuredDocumentRegions(XMLModelParser.java:2354) at org.eclipse.wst.xml.core.internal.document.DOMModelImpl.internalSetNewDocument(DOMModelImpl.java:661) at org.eclipse.wst.xml.core.internal.document.DOMModelImpl.setStructuredDocument(DOMModelImpl.java:936) at org.eclipse.wst.sse.core.internal.model.AbstractModelLoader.createModel(AbstractModelLoader.java:127) at org.eclipse.wst.sse.core.internal.FileBufferModelManager.getModel(FileBufferModelManager.java:725) at org.eclipse.wst.sse.core.internal.FileBufferModelManager.getModel(FileBufferModelManager.java:685) at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl._doCommonGetModel(ModelManagerImpl.java:544) at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl._commonGetModel(ModelManagerImpl.java:508) at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl._commonGetModel(ModelManagerImpl.java:481) at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl.getModelForRead(ModelManagerImpl.java:1419) at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:379) at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:222) at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:211) at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:200) at org.jboss.tools.jsf.web.validation.composite.CompositeComponentValidator.validateResource(CompositeComponentValidator.java:188) at org.jboss.tools.jsf.web.validation.composite.CompositeComponentValidator.validateAll(CompositeComponentValidator.java:167) at org.jboss.tools.common.validation.ValidatorManager.validateAll(ValidatorManager.java:132) at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:84) at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- 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, 9 months

2
4
0 / 0

[JBoss JIRA] (JBIDE-10080) Embedded property should be highligted on Open Mapping action.

by Dmitry Geraskov (Created) (JIRA)

Embedded property should be highligted on Open Mapping action. -------------------------------------------------------------- Key: JBIDE-10080 URL: https://issues.jboss.org/browse/JBIDE-10080 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 3.3.0.M4 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Fix For: 3.3.0.Final This work for core hbm.xml mapping(composite-id), but because of a different syntax doesn't work for orm.xml mapping (embedded-id and embedded). See test result for MappingTestsJpa JUnit and jpa.springframework.samples.petclinic package: Highlighted region for property id is empty. (package jpa.springframework.samples.petclinic) The property is a property of class TestId. Would be good to improve the message also. -- 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, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6178) releng update site, feature naming conventions

by Darryl Miles (JIRA)

releng update site, feature naming conventions ---------------------------------------------- Key: JBIDE-6178 URL: https://jira.jboss.org/jira/browse/JBIDE-6178 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: updatesite Affects Versions: 3.1.0.GA Reporter: Darryl Miles Priority: Minor Please consider the impact of users using the "All Update Site" view when installing JBoss plugins. Some rules to consider: 1) If JBoss creates a new top-level group (which consists entirely of JBoss features) then that top-level name should begin with the word "JBoss". 2) If JBoss reuses a top-level group which belongs to another vendor (for which JBT is built on top of, for example BIRT/Maven/DTP) then you can reuse the top-level group name of the outside vendor, but ensure your features underneath are prefixed with the word "JBoss"." In enclose a screen grab from 3.1.0.GA which indicates the discrepancy; BIRT is following the above rules, but "Maven Support" is not (and also "Data Services" top level group is not). The "All in one JBoss" top-level group doesn't really need to follow this convention, since the top level group clearly indicates it is from JBoss and entirely contains JBoss features and those features are a duplicated entrypoint for installation (i.e. each feature also exist somewhere else in the "features to install" tree view). The ambigiouty is over such names as "Maven Support" and "Data Services" in the context of the "all update site view" from the drop-down filter at the top of the page. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

10
26
0 / 0

[JBoss JIRA] (JBIDE-9851) Get JBossTools added to wtp 3.3's list of server adapters :: Indigo

by Nick Boldt (Created) (JIRA)

Get JBossTools added to wtp 3.3's list of server adapters :: Indigo ------------------------------------------------------------------- Key: JBIDE-9851 URL: https://issues.jboss.org/browse/JBIDE-9851 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: UpStream Affects Versions: 3.2.0.Final Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.2.2.Final, 3.3.0.M4 It seems what happens is you must make use of the org.eclipse.wst.server.discovery plugin. This plugin has a file (discovery.xml) which has "sites", and those sites (such as http://public.dhe.ibm.com/software/websphere/wasce/updates/) seem to be an eclipse update site. The entry point for this wizard is in the New Runtime wizard. At the top is a hyperlink that reads "Download other adapters" (or something similar). It then queries these sites, and allows you to select one of those available. It seems the objects are then downloaded as IInstallableUnit's, which is in the org.eclipse.equinox.p2.metadata package. I kinda lose track of it here, but, I suspect that after this it is downloaded as an actual eclipse bundle and added into the eclipse installation. But I guess I could trace through further Changes to our site would require adding the category and adding it to certain features in our site.xml. -- 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, 9 months

6
6
0 / 0

[JBoss JIRA] (JBDS-1979) Add error handling for p2Director errors in universal installer

by Denis Golovin (Created) (JIRA)

Add error handling for p2Director errors in universal installer --------------------------------------------------------------- Key: JBDS-1979 URL: https://issues.jboss.org/browse/JBDS-1979 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: installer Affects Versions: 5.0.0.M5 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 5.0.0.Beta1 -- 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, 9 months

4
7
0 / 0

[JBoss JIRA] (JBIDE-10221) Resorce leak problems in JBossTools

by Vitali Yemialyanchyk (Created) (JIRA)

Resorce leak problems in JBossTools ----------------------------------- Key: JBIDE-10221 URL: https://issues.jboss.org/browse/JBIDE-10221 Project: Tools (JBoss Tools) Issue Type: Bug Components: Cleanup Affects Versions: 3.3.0.M4 Reporter: Vitali Yemialyanchyk Assignee: Max Rydahl Andersen I've find several places in several components, which I've check - I'll create separate issues for this. There is a chance what there are leak in other components, which I did not inspect. -- 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, 9 months

8
11
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 June 2012