[JBoss JIRA] (JBIDE-16612) NPE after importing ui project from WFK 2.3
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16612?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-16612:
----------------------------------------
Fix Version/s: 4.2.1.Final
> NPE after importing ui project from WFK 2.3
> -------------------------------------------
>
> Key: JBIDE-16612
> URL: https://issues.jboss.org/browse/JBIDE-16612
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate, upstream
> Affects Versions: 4.2.0.Alpha2
> Environment: JBDS 8.0.Alpha2b, Linus 64, Fedora 19, OpenJDK 1.7
> Reporter: Jiri Peterka
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Fix For: 4.2.1.Final, 4.3.x
>
> Attachments: npe-ui-prj-hibernate.png
>
>
> After import there are multiple errors in error log
> {code}
> java.lang.NullPointerException
> at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaPersistentAttribute.getMappingKey(AbstractJavaPersistentAttribute.java:212)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.AbstractPersistentAttributeValidator.validate(AbstractPersistentAttributeValidator.java:33)
> at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaPersistentAttribute.validateAttribute(AbstractJavaPersistentAttribute.java:646)
> at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaPersistentAttribute.validate(AbstractJavaPersistentAttribute.java:641)
> at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaPersistentType.validateAttribute(AbstractJavaPersistentType.java:858)
> at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaPersistentType.validateAttributes(AbstractJavaPersistentType.java:852)
> at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaPersistentType.validate(AbstractJavaPersistentType.java:838)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericClassRef.validateJavaManagedType(GenericClassRef.java:444)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericClassRef.validate(GenericClassRef.java:438)
> at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.validateClassRefs(AbstractPersistenceUnit.java:2403)
> at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.validate(AbstractPersistenceUnit.java:2285)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistence.validatePersistenceUnit(GenericPersistence.java:347)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistence.validate(GenericPersistence.java:303)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistenceXml.validate(GenericPersistenceXml.java:243)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.GenericContextRoot.validate(GenericContextRoot.java:248)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.validate(AbstractJpaProject.java:1459)
> at org.jboss.tools.hibernate.jpt.core.internal.HibernateJpaProject.validate(HibernateJpaProject.java:289)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.getValidationMessages(AbstractJpaProject.java:1447)
> at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.buildValidationMessages_(InternalJpaProjectManager.java:584)
> at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager$BuildValidationMessagesCommand.execute(InternalJpaProjectManager.java:572)
> at org.eclipse.jpt.common.core.internal.utility.command.CommandJobCommandAdapter.execute(CommandJobCommandAdapter.java:50)
> at org.eclipse.jpt.common.core.internal.utility.command.JobCommandJob.run(JobCommandJob.java:42)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {code}
> {code}
> java.lang.NullPointerException
> at org.eclipse.jpt.jpa.ui.internal.structure.MappingStructureItemLabelProviderFactory$AttributeMappingImageDescriptorTransformer.getJpaPlatformUi(MappingStructureItemLabelProviderFactory.java:192)
> at org.eclipse.jpt.jpa.ui.internal.structure.MappingStructureItemLabelProviderFactory$AttributeMappingImageDescriptorTransformer.getAttributeMappingUiDefinition(MappingStructureItemLabelProviderFactory.java:187)
> at org.eclipse.jpt.jpa.ui.internal.structure.MappingStructureItemLabelProviderFactory$AttributeMappingImageDescriptorTransformer.transform(MappingStructureItemLabelProviderFactory.java:182)
> at org.eclipse.jpt.jpa.ui.internal.structure.MappingStructureItemLabelProviderFactory$AttributeMappingImageDescriptorTransformer.transform(MappingStructureItemLabelProviderFactory.java:1)
> at org.eclipse.jpt.common.utility.internal.model.value.TransformationPropertyValueModel.transform(TransformationPropertyValueModel.java:113)
> at org.eclipse.jpt.common.utility.internal.model.value.TransformationPropertyValueModel.engageModel(TransformationPropertyValueModel.java:137)
> at org.eclipse.jpt.common.utility.internal.model.value.AbstractPropertyValueModel.addPropertyChangeListener(AbstractPropertyValueModel.java:83)
> at org.eclipse.jpt.common.ui.internal.jface.AbstractModelItemLabelProvider.<init>(AbstractModelItemLabelProvider.java:65)
> at org.eclipse.jpt.common.ui.internal.jface.ModelItemExtendedLabelProvider.<init>(ModelItemExtendedLabelProvider.java:48)
> at org.eclipse.jpt.jpa.ui.internal.structure.MappingStructureItemLabelProviderFactory.buildPersistentAttributeProvider(MappingStructureItemLabelProviderFactory.java:143)
> at org.eclipse.jpt.jpa.ui.internal.platform.generic.GenericNavigatorItemLabelProviderFactory.buildPersistentAttributeProvider(GenericNavigatorItemLabelProviderFactory.java:150)
> at org.eclipse.jpt.jpa.ui.internal.platform.generic.GenericNavigatorItemLabelProviderFactory.buildProvider(GenericNavigatorItemLabelProviderFactory.java:78)
> at org.eclipse.jpt.jpa.ui.internal.navigator.JpaNavigatorItemLabelProviderFactory.buildProvider(JpaNavigatorItemLabelProviderFactory.java:37)
> at org.eclipse.jpt.common.ui.internal.jface.AbstractItemStructuredStateProviderManager.addLabelProvider(AbstractItemStructuredStateProviderManager.java:245)
> at org.eclipse.jpt.common.ui.internal.jface.AbstractItemStructuredStateProviderManager.add(AbstractItemStructuredStateProviderManager.java:241)
> at org.eclipse.jpt.common.ui.internal.jface.ItemTreeStateProviderManager.add(ItemTreeStateProviderManager.java:118)
> at org.eclipse.jpt.common.ui.internal.jface.AbstractItemStructuredStateProviderManager.addAll(AbstractItemStructuredStateProviderManager.java:220)
> at org.eclipse.jpt.common.ui.internal.jface.ItemTreeStateProviderManager.add(ItemTreeStateProviderManager.java:121)
> at org.eclipse.jpt.common.ui.internal.jface.AbstractItemStructuredStateProviderManager.addAll(AbstractItemStructuredStateProviderManager.java:220)
> at org.eclipse.jpt.common.ui.internal.jface.ItemTreeStateProviderManager.add(ItemTreeStateProviderManager.java:121)
> at org.eclipse.jpt.common.ui.internal.jface.AbstractItemStructuredStateProviderManager.addAll(AbstractItemStructuredStateProviderManager.java:220)
> at org.eclipse.jpt.common.ui.internal.jface.ItemTreeStateProviderManager.add(ItemTreeStateProviderManager.java:121)
> at org.eclipse.jpt.common.ui.internal.jface.AbstractItemStructuredStateProviderManager.addAll(AbstractItemStructuredStateProviderManager.java:220)
> at org.eclipse.jpt.common.ui.internal.jface.ItemTreeStateProviderManager.add(ItemTreeStateProviderManager.java:121)
> at org.eclipse.jpt.common.ui.internal.jface.AbstractItemStructuredStateProviderManager.addAll(AbstractItemStructuredStateProviderManager.java:231)
> at org.eclipse.jpt.common.ui.internal.jface.ItemTreeStateProviderManager.childrenChanged_(ItemTreeStateProviderManager.java:110)
> at org.eclipse.jpt.common.ui.internal.jface.ItemTreeStateProviderManager.childrenChanged(ItemTreeStateProviderManager.java:105)
> at org.eclipse.jpt.common.ui.internal.jface.ModelItemTreeContentProvider.notifyManager(ModelItemTreeContentProvider.java:63)
> at org.eclipse.jpt.common.ui.internal.jface.ModelItemContentProvider.childrenAdded_(ModelItemContentProvider.java:119)
> at org.eclipse.jpt.common.ui.internal.jface.ModelItemContentProvider.childrenAdded(ModelItemContentProvider.java:113)
> at org.eclipse.jpt.common.ui.internal.jface.ModelItemContentProvider$ChildrenListener.itemsAdded(ModelItemContentProvider.java:92)
> at org.eclipse.jpt.common.ui.internal.swt.listeners.SWTCollectionChangeListenerWrapper.forward(SWTCollectionChangeListenerWrapper.java:51)
> at org.eclipse.jpt.common.ui.internal.swt.listeners.SWTCollectionChangeListenerWrapper.forward(SWTCollectionChangeListenerWrapper.java:1)
> at org.eclipse.jpt.common.ui.internal.swt.listeners.SWTListenerWrapperDelegate.forwardEvents(SWTListenerWrapperDelegate.java:92)
> at org.eclipse.jpt.common.ui.internal.swt.listeners.SWTListenerWrapperDelegate$ForwardEventsRunnable.run(SWTListenerWrapperDelegate.java:81)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3746)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3394)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1122)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1006)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:146)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:615)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:566)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:125)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:109)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:80)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:372)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:226)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18447) Both of jbosstools-discovery publish same version of Central TPs
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18447?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-18447:
----------------------------------------
[~nickboldt] I don't have a good idea on how to set up a branching/versioning convention for those discovery targets. I have the impression that since we branch it together with JBT/JBDS, it would better be versioned according to the version of JBT/JBDS they target, but this would imply that we have a 1-N mapping (ie a discovery site is only good for one version of JBT/JBDS).
> Both of jbosstools-discovery publish same version of Central TPs
> ----------------------------------------------------------------
>
> Key: JBIDE-18447
> URL: https://issues.jboss.org/browse/JBIDE-18447
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: discovery, target-platform
> Affects Versions: 4.2.0.CR1
> Reporter: Mickael Istria
> Fix For: 4.3.0.Alpha1
>
>
> jbosstools-discovery plugin is branched according to JBoss Tools train. However, it contains TPs that are versioned according to Eclipse release train.
> Because of that, we currently have the same version of the Discovery target definitions on both master and jbosstools-4.2.x branch. That leads to some uncertainity about which branch/job is going to publish the Central site.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18447) Both of jbosstools-discovery publish same version of Central TPs
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-18447:
--------------------------------------
Summary: Both of jbosstools-discovery publish same version of Central TPs
Key: JBIDE-18447
URL: https://issues.jboss.org/browse/JBIDE-18447
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: discovery, target-platform
Affects Versions: 4.2.0.CR1
Reporter: Mickael Istria
jbosstools-discovery plugin is branched according to JBoss Tools train. However, it contains TPs that are versioned according to Eclipse release train.
Because of that, we currently have the same version of the Discovery target definitions on both master and jbosstools-4.2.x branch. That leads to some uncertainity about which branch/job is going to publish the Central site.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18436) Central archetype versions should depend on selected runtime version
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18436?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18436:
---------------------------------------------
I honestly thought we already did this since it was necessary very early on - and yes, remote servers we won't be able to handle unless we add support for asking a running server what version it is.
> Central archetype versions should depend on selected runtime version
> --------------------------------------------------------------------
>
> Key: JBIDE-18436
> URL: https://issues.jboss.org/browse/JBIDE-18436
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.CR1
> Environment: JBDS 8 CR1, Fedora 20
> Reporter: Vineet Reynolds
> Assignee: Fred Bricon
> Priority: Critical
> Fix For: 4.2.0.CR2
>
>
> A newly created project using the "Java EE Web Project" in JBoss Central, uses the {{org.jboss.bom:jboss-javaee-6.0-with-tools:1.0.4.Final-redhat-4}} and {{org.jboss.bom:jboss-javaee-6.0-with-hibernate:1.0.4.Final-redhat-4}} BOMs in the {{dependencyManagement}} section.
> These are the older versions. It should instead be using the BOMs from the {{org.jboss.bom.wfk}} and {{org.jboss.bom.eap}} groupIds instead.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18438) OpenShift: can complete New App Wizard without selecting gear profile
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18438?page=com.atlassian.jira.plugi... ]
Michelle Murray commented on JBIDE-18438:
-----------------------------------------
OK - could we make the field start with option "<default>" then? then the user at least knows that "default" gear profile will be selected rather than guessing.
> OpenShift: can complete New App Wizard without selecting gear profile
> ---------------------------------------------------------------------
>
> Key: JBIDE-18438
> URL: https://issues.jboss.org/browse/JBIDE-18438
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.CR1
> Reporter: Michelle Murray
> Priority: Minor
>
> In New OpenShift Application wizard, on page where select 'Gear Profile' - this field is initially blank and user can leave it blank and still successfully complete the wizard. So it works.
> But I don't think it is a good user experience. User should not be able to move to next page until there is a value in this field. Perhaps this field should have a value to start with instead of being blank based on the users account?
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18239) Create new update site zip(s) (rather than target platform zip) for JBT content needed for Central/EA site
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18239?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18239:
---------------------------------------------
You still seem to think i've been suggesting moving away from TP to define what is in the updatesites - i'm not.
A) I don't know why we would hide the content from central on the main updatesite - got an example of something that would not make sense there ? (at least I don't think that could be a general blanket rule leaving out things here just because they are list in central and not installed by default installer)
B) What I don't grok here is why this sounds like JBT and JBDS main updatesite is to be treated different from each other ?
C) And no, I don't see me saying or suggesting us moving away from TP's to define what is in early access and move to a category.xml format instead which does not have the validation benefits and strictness that TP's has (thats at least what I see in the PR's) - I simply suggested remove the duplicated JBT content in central. Nothing else.
But could we park this for f2f now ? Is there anything here that is critical for GA ?
> Create new update site zip(s) (rather than target platform zip) for JBT content needed for Central/EA site
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18239
> URL: https://issues.jboss.org/browse/JBIDE-18239
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, central, discovery, updatesite
> Affects Versions: 4.2.0.CR1
> Reporter: Nick Boldt
> Labels: f2f2014
> Fix For: 4.3.0.Alpha1
>
> Attachments: JBIDE18239-proposed.png
>
>
> In order to simplify the process for getting JBT features into Central (for JBDS) and EA (for both JBT/JBDS), it's been suggested (by [~maxandersen], who doesn't like opening JIRAs :D) that instead of a target platform which needs to be updated every time we spin or respin a build, we could instead just produce an update site containing the handful of IUs (cordovasim, arquillian, etc.).
> We could further extend this idea to include all the things that currently are in BOTH JBT or JBDS and in Central, such as TestNG.
> These would be produced as new zips using the JBT aggregate builder:
> https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregate/
> Need to decide what to call this... "Extras" "JBT-not-in-JBDS" "Shared" ...?
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months