November 2011 - jbosstools-issues

[JBoss JIRA] (JBIDE-9878) Materialize library should warn/verify before doing its thing

by Max Rydahl Andersen (Created) (JIRA)

Materialize library should warn/verify before doing its thing ------------------------------------------------------------- Key: JBIDE-9878 URL: https://issues.jboss.org/browse/JBIDE-9878 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: maven Reporter: Max Rydahl Andersen Assignee: Fred Bricon Priority: Critical Fix For: 3.3.0.Beta1 Materialize library is great but dangerous so we should treat it as such ;) In the wizard tell what will happen, currently it does: "Copy selected jars from 'classpath container name' to the destination folder." which is fine, but in case of Maven it actually also removes the Maven nature. Thus I would add to the description if the container is the Maven Nature "This will also remove the Maven configuration from this project". or something similar. When pressing Finish the user should be repeated that info + a "This operation cannot be undone, are you sure ?" -- 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

14 years, 4 months

5
6
0 / 0

[JBoss JIRA] (JBIDE-10078) NPE when attempt to log event in HibernateJptPlugin

by Dmitry Geraskov (Created) (JIRA)

NPE when attempt to log event in HibernateJptPlugin --------------------------------------------------- Key: JBIDE-10078 URL: https://issues.jboss.org/browse/JBIDE-10078 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.Beta1 LogFilter.isLoggable threw a non-fatal unchecked exception as follows: java.lang.NullPointerException at org.eclipse.core.internal.runtime.Log.isLoggable(Log.java:101) at org.eclipse.equinox.log.internal.ExtendedLogReaderServiceFactory.safeIsLoggable(ExtendedLogReaderServiceFactory.java:57) at org.eclipse.equinox.log.internal.ExtendedLogReaderServiceFactory.logPrivileged(ExtendedLogReaderServiceFactory.java:158) at org.eclipse.equinox.log.internal.ExtendedLogReaderServiceFactory.log(ExtendedLogReaderServiceFactory.java:146) at org.eclipse.equinox.log.internal.ExtendedLogServiceFactory.log(ExtendedLogServiceFactory.java:65) at org.eclipse.equinox.log.internal.ExtendedLogServiceImpl.log(ExtendedLogServiceImpl.java:87) at org.eclipse.equinox.log.internal.LoggerImpl.log(LoggerImpl.java:54) at org.eclipse.core.internal.runtime.Log.log(Log.java:60) at org.jboss.tools.hibernate.jpt.core.internal.HibernateJptPlugin.log(HibernateJptPlugin.java:56) -- 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

14 years, 4 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6177) More convenient ant based examples import

by Jiri Peterka (JIRA)

More convenient ant based examples import ----------------------------------------- Key: JBIDE-6177 URL: https://jira.jboss.org/jira/browse/JBIDE-6177 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Archives Affects Versions: 3.1.0.GA Reporter: Jiri Peterka Fix For: 3.2.next Importing EAP and SOA ant based examples (not JBT examples) is quite uncomfortable (importing through file system). More advanced way should be provided for these imports. It should be at lease able to create project and perform basic project setting. -- 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

14 years, 4 months

6
17
0 / 0

[JBoss JIRA] (JBIDE-10060) CLONE - SSH key setup needs to be aligned with openshift as otherwise its very easy to end up with hard to handle auth key errors

by Andre Dietisheim (Created) (JIRA)

CLONE - SSH key setup needs to be aligned with openshift as otherwise its very easy to end up with hard to handle auth key errors --------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-10060 URL: https://issues.jboss.org/browse/JBIDE-10060 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Reporter: Andre Dietisheim Assignee: Andre Dietisheim Priority: Blocker Fix For: 3.3.0.M4 Attachments: create-libra-key-2.patch, create-libra-key.patch It turns out that openshift command line forces a specific key name in their ssh usage and even hardcodes it into ~/.ssh/config for all communication with *.rhcloud.com. this config git/jscsh listens too and thus no matter what the user does in eclipse he will get auth errors unless he actually used the exact same key. And to make matters worse jcsh only reads this configuration on startup of eclipse so to align keys you have to restart eclipse after doing changes config. The problem with all this is that if you are a new user using the tools you will bump into problems as soon as you need to use tail-files or add cartridges because we create the key with a different name that the command line tools expect. To remedy this problem three changes are to be made: 1) on create domain we will check if <sshhome>/libra_id_rsa.pub exist - if it does we prefill the key name with that. 2) New will only create a key named <sshome>/libra_id_rsa(.pub) - if such file already exist it will say it won't create one -- 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

14 years, 4 months

5
4
0 / 0

[JBoss JIRA] (JBIDE-10006) CLONE - Error when publishing project without git repo associated

by Max Rydahl Andersen (Created) (JIRA)

CLONE - Error when publishing project without git repo associated ----------------------------------------------------------------- Key: JBIDE-10006 URL: https://issues.jboss.org/browse/JBIDE-10006 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Reporter: Max Rydahl Andersen Assignee: Rob Stryker Priority: Blocker Fix For: 3.3.0.M4 try publishing project or deployable individual file without a git repo to an openshift server. publishng server doesn't check if project has a repository! java.lang.NullPointerException at org.eclipse.egit.core.IteratorService.createInitialIterator(IteratorService.java:39) at org.jboss.ide.eclipse.as.egit.core.EGitUtils.countCommitableChanges(EGitUtils.java:459) at org.jboss.tools.openshift.express.internal.core.behaviour.ExpressPublishMethod.publishModule(ExpressPublishMethod.java:50) at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:92) at org.jboss.ide.eclipse.as.core.server.internal.v7.DelegatingJBoss7ServerBehavior.publishModule(DelegatingJBoss7ServerBehavior.java:84) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1046) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1138) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:955) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774) at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3027) at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:341) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) this one is a blocker since if you drag a project to a server or use run as then it will keep giving NPE's and removal is broken too. -- 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

14 years, 4 months

6
6
0 / 0

[JBoss JIRA] (JBIDE-10073) Erros in tests Unable to instantiate default tuplizer

by Dmitry Geraskov (Created) (JIRA)

Erros in tests Unable to instantiate default tuplizer ----------------------------------------------------- Key: JBIDE-10073 URL: https://issues.jboss.org/browse/JBIDE-10073 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 3.3.0.M3 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Fix For: 3.3.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

14 years, 4 months

4
3
0 / 0

[JBoss JIRA] (JBIDE-10084) Pressing "< Back" on the first wizard page doesn't work if password field is empty

by Pavol Srna (Created) (JIRA)

Pressing "< Back" on the first wizard page doesn't work if password field is empty ---------------------------------------------------------------------------------- Key: JBIDE-10084 URL: https://issues.jboss.org/browse/JBIDE-10084 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.M4 Reporter: Pavol Srna Assignee: Andre Dietisheim Fix For: 3.3.0.Beta1 User credentials are validated when pressing "< Back" button on the first wizard page. This sometimes cause that an exception is thrown and the wizard doesn't navigate step back. steps to reproduce: 1) File -> New -> OpenShift -> OpenShift Express Application 2) Leave the password field empty 3) press "< Back" button You'll get an exception as shown on the attached screenshot. -- 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

14 years, 4 months

5
4
0 / 0

[JBoss JIRA] (JBIDE-10040) Delete app, cannot create new app with same name

by Max Rydahl Andersen (Created) (JIRA)

Delete app, cannot create new app with same name ------------------------------------------------ Key: JBIDE-10040 URL: https://issues.jboss.org/browse/JBIDE-10040 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.M4 Reporter: Max Rydahl Andersen Assignee: Andre Dietisheim Fix For: 3.3.0.Beta1 >From Grant Shipley: "If you delete an app, it appears to be cached and it will not allow you to create an app with the same name until you exit the wizard and restart it." -- 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

14 years, 4 months

3
2
0 / 0

[JBoss JIRA] (JBIDE-10092) CLONE - Rename "All JBoss Tools" category to "Abridged JBoss Tools"

by Pavol Srna (Created) (JIRA)

CLONE - Rename "All JBoss Tools" category to "Abridged JBoss Tools" ------------------------------------------------------------------- Key: JBIDE-10092 URL: https://issues.jboss.org/browse/JBIDE-10092 Project: Tools (JBoss Tools) Issue Type: Bug Components: updatesite Reporter: Pavol Srna Assignee: Nick Boldt Priority: Critical Fix For: 3.3.0.M4, 3.3.0.Beta1 Many users keeps falling into our trap of thinking that the "All JBoss Tools" contains everything when it does not. The word Abridged would keep it still at the top and actually mean what it means: "not full, but reduced set of stuff" And the category description should be changed too to not show as the only line (default visible): "Contains ALL the plugins that are available from" to something like: "An abridged selection of JBoss Tools plugins" Nick, placed on M4 in case its a trivial site.xml editing job - otherwise move it off to just be done in trunk/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

14 years, 4 months

4
3
0 / 0

[JBoss JIRA] (JBIDE-10076) JPA: HibernateOrmXmlContextNodeFactory cannot be cast to OrmXml2_0ContextNodeFactory

by Dmitry Geraskov (Created) (JIRA)

JPA: HibernateOrmXmlContextNodeFactory cannot be cast to OrmXml2_0ContextNodeFactory ------------------------------------------------------------------------------------ Key: JBIDE-10076 URL: https://issues.jboss.org/browse/JBIDE-10076 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 3.3.0.M3 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Fix For: 3.3.0.Beta1 Apepared when tried to build project with orm.xml mapping. java.lang.ClassCastException: org.jboss.tools.hibernate.jpt.core.internal.context.orm.HibernateOrmXmlContextNodeFactory cannot be cast to org.eclipse.jpt.jpa.core.jpa2.context.orm.OrmXml2_0ContextNodeFactory at org.eclipse.jpt.jpa.core.internal.context.orm.AbstractOrmXmlContextNode.getContextNodeFactory2_0(AbstractOrmXmlContextNode.java:73) at org.jboss.tools.hibernate.jpt.core.internal.context.orm.HibernateOrmEntityImpl.buildCacheable(HibernateOrmEntityImpl.java:90) at org.jboss.tools.hibernate.jpt.core.internal.context.orm.HibernateOrmEntityImpl.<init>(HibernateOrmEntityImpl.java:59) at org.jboss.tools.hibernate.jpt.core.internal.context.orm.HibernateOrmXmlContextNodeFactory.buildOrmEntity(HibernateOrmXmlContextNodeFactory.java:62) at org.eclipse.jpt.jpa.core.internal.context.orm.OrmEntityDefinition.buildContextMapping(OrmEntityDefinition.java:65) at org.eclipse.jpt.jpa.core.internal.context.orm.OrmEntityDefinition.buildContextMapping(OrmEntityDefinition.java:1) at org.eclipse.jpt.jpa.core.internal.jpa1.context.orm.GenericOrmPersistentType.buildMapping(GenericOrmPersistentType.java:170) at org.eclipse.jpt.jpa.core.internal.jpa1.context.orm.GenericOrmPersistentType.<init>(GenericOrmPersistentType.java:109) at org.jboss.tools.hibernate.jpt.core.internal.context.orm.HibernateOrmPersistentType.<init>(HibernateOrmPersistentType.java:26) at org.jboss.tools.hibernate.jpt.core.internal.context.orm.HibernateOrmXmlContextNodeFactory.buildOrmPersistentType(HibernateOrmXmlContextNodeFactory.java:113) at org.eclipse.jpt.jpa.core.internal.context.orm.AbstractEntityMappings.buildPersistentType(AbstractEntityMappings.java:553) at org.eclipse.jpt.jpa.core.internal.context.orm.AbstractEntityMappings.initializePersistentTypes(AbstractEntityMappings.java:595) at org.eclipse.jpt.jpa.core.internal.context.orm.AbstractEntityMappings.<init>(AbstractEntityMappings.java:111) at org.eclipse.jpt.jpa.core.internal.jpa1.context.orm.GenericEntityMappings.<init>(GenericEntityMappings.java:25) at org.eclipse.jpt.jpa.core.internal.context.orm.AbstractOrmXmlContextNodeFactory.buildEntityMappings(AbstractOrmXmlContextNodeFactory.java:168) at org.eclipse.jpt.jpa.core.internal.jpa1.context.orm.GenericOrmXml.buildRoot(GenericOrmXml.java:164) at org.eclipse.jpt.jpa.core.internal.jpa1.context.orm.GenericOrmXml.<init>(GenericOrmXml.java:78) at org.eclipse.jpt.jpa.core.internal.AbstractJpaFactory.buildMappingFile(AbstractJpaFactory.java:201) at org.eclipse.jpt.jpa.core.internal.AbstractJpaFactory.buildMappingFile(AbstractJpaFactory.java:1) at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractMappingFileRef.buildMappingFile(AbstractMappingFileRef.java:189) at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractMappingFileRef.buildMappingFile(AbstractMappingFileRef.java:111) at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractMappingFileRef.<init>(AbstractMappingFileRef.java:63) at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericMappingFileRef.<init>(GenericMappingFileRef.java:38) at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceXmlContextNodeFactory.buildMappingFileRef(AbstractPersistenceXmlContextNodeFactory.java:49) at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.buildSpecifiedMappingFileRef(AbstractPersistenceUnit.java:527) at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.initializeSpecifiedMappingFileRefs(AbstractPersistenceUnit.java:548) at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.<init>(AbstractPersistenceUnit.java:196) at org.jboss.tools.hibernate.jpt.core.internal.context.HibernatePersistenceUnit.<init>(HibernatePersistenceUnit.java:79) -- 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

14 years, 4 months

3
2
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 November 2011