[JBoss JIRA] (JBIDE-19427) Redundant warning for JPA entity
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19427?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-19427:
------------------------------
Fix Version/s: 4.3.0.Beta2
(was: 4.3.0.Beta1)
> Redundant warning for JPA entity
> --------------------------------
>
> Key: JBIDE-19427
> URL: https://issues.jboss.org/browse/JBIDE-19427
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.3.0.Alpha2
> Reporter: Arun Gupta
> Assignee: Koen Aers
> Fix For: 4.3.0.Beta2
>
> Attachments: Screen Shot 2015-03-10 at 2.39.46 PM.png
>
>
> Student entity is defined as:
> {code}
> @Entity
> @XmlRootElement
> @NamedQuery(name="findAllStudents", query="select s from Student s")
> public class Student implements Serializable {
> {code}
> Persistence.xml is defined as:
> {code}
> <?xml version="1.0" encoding="UTF-8"?>
> <persistence version="2.1"
> xmlns="http://xmlns.jcp.org/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/persistence http://xmlns.jcp.org/xml/ns/persistence/persistence_2_1.xsd">
> <persistence-unit name="HelloJavaEE7">
> <properties>
> <property name="javax.persistence.schema-generation.database.action"
> value="drop-and-create" />
> <property name="javax.persistence.schema-generation.create-source"
> value="metadata" />
> <property name="javax.persistence.schema-generation.drop-source"
> value="metadata" />
> <property name="hibernate.show_sql" value="true" />
> <property name="hibernate.format_sql" value="true" />
> </properties>
> </persistence-unit>
> </persistence>
> {code}
> Editor shows a red cross on Student class declaration with the error message "Class "org.sample.Student" is managed, but is not listed in the persistence.xml file".
> By default, all entities are included and this error should not occur.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19323) java.lang.NullPointerException and no results after HQL query execution
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19323?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-19323:
------------------------------
Fix Version/s: 4.3.0.Beta2
(was: 4.3.0.Beta1)
> java.lang.NullPointerException and no results after HQL query execution
> -----------------------------------------------------------------------
>
> Key: JBIDE-19323
> URL: https://issues.jboss.org/browse/JBIDE-19323
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.3.0.Alpha1
> Reporter: Jiri Peterka
> Assignee: Jiri Peterka
> Priority: Minor
> Fix For: 4.3.0.Beta2
>
>
> New for 4.3.x, works with 4.2.x.
> {code}
> !ENTRY org.eclipse.ui 4 0 2015-02-19 10:39:33.217
> !MESSAGE Unhandled event loop exception
> !STACK 0
> java.lang.NullPointerException
> at org.hibernate.cfg.Configuration.buildTypeRegistrations(Configuration.java:1886)
> at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1843)
> at org.jboss.tools.hibernate.proxy.ConfigurationProxy.buildSessionFactory(ConfigurationProxy.java:117)
> at org.hibernate.console.ConsoleConfiguration$5.execute(ConsoleConfiguration.java:285)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108)
> at org.hibernate.console.ConsoleConfiguration.buildSessionFactory(ConsoleConfiguration.java:280)
> at org.hibernate.eclipse.console.actions.ExecuteQueryAction.execute(ExecuteQueryAction.java:81)
> at org.hibernate.eclipse.console.actions.ExecuteQueryAction.run(ExecuteQueryAction.java:55)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
> at org.hibernate.eclipse.console.actions.ExecuteQueryAction.runWithEvent(ExecuteQueryAction.java:59)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:462)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4480)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1413)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3818)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3428)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:648)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:592)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.jboss.reddeer.eclipse.core.UITestApplication.start(UITestApplication.java:47)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBDS-3377) Random "not responding" message when installing from central
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3377?page=com.atlassian.jira.plugin.... ]
Mickael Istria closed JBDS-3377.
--------------------------------
Resolution: Cannot Reproduce Bug
Closing as cannot reproduce (With Fedora 21). If you find out some steps to reproduce with some newer Fedora versions, feel free to reopen.
> Random "not responding" message when installing from central
> ------------------------------------------------------------
>
> Key: JBDS-3377
> URL: https://issues.jboss.org/browse/JBDS-3377
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central, ui/branding
> Affects Versions: 8.1.0.CR1
> Environment: Fedora 20 64-bit, OpenJDK 1.7.0_75
> Reporter: Jan Richter
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 9.0.0.Beta1
>
>
> Trying to install all from central sometimes causes the "not responding" dialog to pop up while the "Calculating Dependencies" dialog is active. The app is still responding when the dialog opens though.
> I cannot find a particular pattern to this, it looks completely random.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19715) Get rid of "fullSite", stick with "repository"
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19715?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-19715:
-----------------------------------
Fix Version/s: 4.3.0.Beta2
(was: 4.3.0.Beta1)
> Get rid of "fullSite", stick with "repository"
> ----------------------------------------------
>
> Key: JBIDE-19715
> URL: https://issues.jboss.org/browse/JBIDE-19715
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.3.0.Alpha1
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.0.Beta2
>
>
> Currently, some builds such as aggregate create a "site/target/fullSite" folder, which is aimed at being deployed. However, it would be simpler to populate the site/target/repository folder, so it would be only one directory to move, and the same one for all builds.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-18772) Include publish steps in pom files
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-18772:
-----------------------------------
Fix Version/s: 4.3.0.Beta2
(was: 4.3.0.Beta1)
> Include publish steps in pom files
> ----------------------------------
>
> Key: JBIDE-18772
> URL: https://issues.jboss.org/browse/JBIDE-18772
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.3.0.Beta2
>
> Attachments: jbds-publish-to-snapshots.png
>
>
> instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses.
> suggestion:
> publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing.
> What this helps with is:
> a) can do changes to publish mechanism without affecting every past builds.
> b) more movable build system
> c) isolated testing possible
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19768) Add possibility to select which nested projects to import
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19768?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-19768:
-----------------------------------
Fix Version/s: 4.3.0.Beta2
(was: 4.3.0.Beta1)
> Add possibility to select which nested projects to import
> ---------------------------------------------------------
>
> Key: JBIDE-19768
> URL: https://issues.jboss.org/browse/JBIDE-19768
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: easymport
> Affects Versions: 4.3.0.Alpha2
> Reporter: Lucia Jelinkova
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.3.0.Beta2
>
>
> At the moment, all nested projects are imported - it would be useful to have the possibility to select which projects one wants to import.
> Also, sometimes projects contain test data that are detected as projects - this feature would help also in this case.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19607) Offline quickstarts not working - Could not calculate build plan
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19607?page=com.atlassian.jira.plugi... ]
Rastislav Wagner commented on JBIDE-19607:
------------------------------------------
Tested with maven 3.0.5 and I saw no issues when I tried offline mode with Eclipse's maven 3.3.3.
> Offline quickstarts not working - Could not calculate build plan
> ----------------------------------------------------------------
>
> Key: JBIDE-19607
> URL: https://issues.jboss.org/browse/JBIDE-19607
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, project-examples
> Affects Versions: 4.3.0.Alpha2
> Environment: JBDS 9.0.0 nightly build Alpha2-v20150414-2227-B2953
> Reporter: Radim Hopp
> Assignee: Fred Bricon
> Fix For: 4.3.0.Beta1
>
>
> After running offline script and configuring JBDS to use that (without internet connectivity) I'm unable to import any of quickstarts. Some (as HTML5 project archetype for example) throw error into error log right after wizard startup:
> {noformat:title=Could not resolve artifact org.wildfly.archetype:wildfly-html5-mobile-archetype:pom:8.2.0.Final}
> org.eclipse.core.runtime.CoreException: Could not resolve artifact org.wildfly.archetype:wildfly-html5-mobile-archetype:pom:8.2.0.Final
> at org.eclipse.m2e.core.internal.embedder.MavenImpl$5.call(MavenImpl.java:776)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl$5.call(MavenImpl.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.resolve(MavenImpl.java:743)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.resolve(MavenImpl.java:720)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.downloadArchetype(ArchetypeExamplesWizardPage.java:262)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.access$4(ArchetypeExamplesWizardPage.java:252)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$3.run(ArchetypeExamplesWizardPage.java:206)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:463)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:371)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1002)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.getRequiredProperties(ArchetypeExamplesWizardPage.java:191)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.initializeArchetype(ArchetypeExamplesWizardPage.java:140)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.createControl(ArchetypeExamplesWizardPage.java:113)
> at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:175)
> at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:705)
> at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:597)
> at org.eclipse.jface.window.Window.create(Window.java:430)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096)
> at org.eclipse.jface.window.Window.open(Window.java:792)
> at org.jboss.tools.central.editors.GettingStartedPage.openWizard(GettingStartedPage.java:700)
> at org.jboss.tools.central.editors.GettingStartedPage.access$14(GettingStartedPage.java:685)
> at org.jboss.tools.central.editors.GettingStartedPage$7.linkActivated(GettingStartedPage.java:639)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233)
> at org.eclipse.ui.forms.widgets.ImageHyperlink.handleActivate(ImageHyperlink.java:201)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4477)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3815)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> Contains: Failure to transfer org.wildfly.archetype:wildfly-html5-mobile-archetype:pom:8.2.0.Final from https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.wildfly.archetype:wildfly-html5-mobile-archetype:pom:8.2.0.Final from/to central (https://repo.maven.apache.org/maven2): repo.maven.apache.org: unknown error
> org.eclipse.aether.transfer.ArtifactTransferException: Failure to transfer org.wildfly.archetype:wildfly-html5-mobile-archetype:pom:8.2.0.Final from https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.wildfly.archetype:wildfly-html5-mobile-archetype:pom:8.2.0.Final from/to central (https://repo.maven.apache.org/maven2): repo.maven.apache.org: unknown error
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:238)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:206)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads(DefaultArtifactResolver.java:585)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:503)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:421)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223)
> at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:294)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl$5.call(MavenImpl.java:753)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl$5.call(MavenImpl.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.resolve(MavenImpl.java:743)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.resolve(MavenImpl.java:720)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.downloadArchetype(ArchetypeExamplesWizardPage.java:262)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.access$4(ArchetypeExamplesWizardPage.java:252)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$3.run(ArchetypeExamplesWizardPage.java:206)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:463)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:371)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1002)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.getRequiredProperties(ArchetypeExamplesWizardPage.java:191)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.initializeArchetype(ArchetypeExamplesWizardPage.java:140)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.createControl(ArchetypeExamplesWizardPage.java:113)
> at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:175)
> at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:705)
> at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:597)
> at org.eclipse.jface.window.Window.create(Window.java:430)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096)
> at org.eclipse.jface.window.Window.open(Window.java:792)
> at org.jboss.tools.central.editors.GettingStartedPage.openWizard(GettingStartedPage.java:700)
> at org.jboss.tools.central.editors.GettingStartedPage.access$14(GettingStartedPage.java:685)
> at org.jboss.tools.central.editors.GettingStartedPage$7.linkActivated(GettingStartedPage.java:639)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233)
> at org.eclipse.ui.forms.widgets.ImageHyperlink.handleActivate(ImageHyperlink.java:201)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4477)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3815)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {noformat}
> After hitting Finish on wizard, the imported project (if it was imported) cannot be build, because it cannot resolve maven-resources-plugin. Error log:
> {noformat:title=Errors occurred during the build.}
> org.eclipse.core.internal.resources.ResourceException: Errors occurred during the build.
> at org.eclipse.core.internal.resources.Workspace.buildInternal(Workspace.java:498)
> at org.eclipse.core.internal.resources.Workspace.build(Workspace.java:398)
> at org.jboss.tools.project.examples.internal.ProjectExamplesActivator$1.run(ProjectExamplesActivator.java:207)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Contains: Errors running builder 'Maven Project Builder' on project 'jboss-greeter'.
> org.eclipse.core.runtime.CoreException: Could not calculate build plan: Plugin org.apache.maven.plugins:maven-resources-plugin:2.6 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-resources-plugin:jar:2.6
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:410)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl$2.call(MavenImpl.java:420)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl$2.call(MavenImpl.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:418)
> at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.setupMojoExecution(ProjectRegistryManager.java:950)
> at org.eclipse.m2e.core.internal.project.registry.MavenProjectFacade.getMojoExecution(MavenProjectFacade.java:408)
> at org.eclipse.m2e.core.project.configurator.AbstractCustomizableLifecycleMapping.getBuildParticipants(AbstractCustomizableLifecycleMapping.java:66)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1$1.call(MavenBuilder.java:113)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:105)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:86)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:200)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382)
> at org.eclipse.core.internal.resources.Workspace.buildInternal(Workspace.java:486)
> at org.eclipse.core.internal.resources.Workspace.build(Workspace.java:398)
> at org.jboss.tools.project.examples.internal.ProjectExamplesActivator$1.run(ProjectExamplesActivator.java:207)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.plugins:maven-resources-plugin:2.6 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-resources-plugin:jar:2.6
> at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:117)
> at org.eclipse.m2e.core.internal.project.registry.EclipsePluginDependenciesResolver.resolve(EclipsePluginDependenciesResolver.java:47)
> at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.java:179)
> at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:298)
> at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:241)
> at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.setupMojoExecution(DefaultLifecycleExecutionPlanCalculator.java:169)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:408)
> ... 30 more
> Caused by: org.eclipse.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for org.apache.maven.plugins:maven-resources-plugin:jar:2.6
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:302)
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:218)
> at org.eclipse.aether.internal.impl.DefaultRepositorySystem.readArtifactDescriptor(DefaultRepositorySystem.java:287)
> at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:103)
> ... 36 more
> Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Failure to transfer org.apache.maven.plugins:maven-resources-plugin:pom:2.6 from https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.plugins:maven-resources-plugin:pom:2.6 from/to central (https://repo.maven.apache.org/maven2): repo.maven.apache.org
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223)
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:287)
> ... 39 more
> Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Failure to transfer org.apache.maven.plugins:maven-resources-plugin:pom:2.6 from https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.plugins:maven-resources-plugin:pom:2.6 from/to central (https://repo.maven.apache.org/maven2): repo.maven.apache.org
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:238)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:206)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads(DefaultArtifactResolver.java:585)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:503)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:421)
> ... 42 more
> Contains: Could not calculate build plan: Plugin org.apache.maven.plugins:maven-resources-plugin:2.6 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-resources-plugin:jar:2.6
> org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.plugins:maven-resources-plugin:2.6 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-resources-plugin:jar:2.6
> at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:117)
> at org.eclipse.m2e.core.internal.project.registry.EclipsePluginDependenciesResolver.resolve(EclipsePluginDependenciesResolver.java:47)
> at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.java:179)
> at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:298)
> at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:241)
> at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.setupMojoExecution(DefaultLifecycleExecutionPlanCalculator.java:169)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:408)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl$2.call(MavenImpl.java:420)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl$2.call(MavenImpl.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:418)
> at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.setupMojoExecution(ProjectRegistryManager.java:950)
> at org.eclipse.m2e.core.internal.project.registry.MavenProjectFacade.getMojoExecution(MavenProjectFacade.java:408)
> at org.eclipse.m2e.core.project.configurator.AbstractCustomizableLifecycleMapping.getBuildParticipants(AbstractCustomizableLifecycleMapping.java:66)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1$1.call(MavenBuilder.java:113)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:105)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:86)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:200)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382)
> at org.eclipse.core.internal.resources.Workspace.buildInternal(Workspace.java:486)
> at org.eclipse.core.internal.resources.Workspace.build(Workspace.java:398)
> at org.jboss.tools.project.examples.internal.ProjectExamplesActivator$1.run(ProjectExamplesActivator.java:207)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: org.eclipse.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for org.apache.maven.plugins:maven-resources-plugin:jar:2.6
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:302)
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:218)
> at org.eclipse.aether.internal.impl.DefaultRepositorySystem.readArtifactDescriptor(DefaultRepositorySystem.java:287)
> at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:103)
> ... 36 more
> Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Failure to transfer org.apache.maven.plugins:maven-resources-plugin:pom:2.6 from https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.plugins:maven-resources-plugin:pom:2.6 from/to central (https://repo.maven.apache.org/maven2): repo.maven.apache.org
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223)
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:287)
> ... 39 more
> Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Failure to transfer org.apache.maven.plugins:maven-resources-plugin:pom:2.6 from https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.plugins:maven-resources-plugin:pom:2.6 from/to central (https://repo.maven.apache.org/maven2): repo.maven.apache.org
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:238)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:206)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads(DefaultArtifactResolver.java:585)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:503)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:421)
> ... 42 more
> {noformat}
> Note, that all artifacts that eclipse cannot resolve (maven-resources-plugin, HTML5 archetype, ...) I have in my local repository (were downloaded by offline script correctly). I checked few sha1 checksums and they are correct.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19835) 'JPA Tools -> Generate Tables from Entities' does not work for Hibernate 4.0
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19835?page=com.atlassian.jira.plugi... ]
Koen Aers resolved JBIDE-19835.
-------------------------------
Resolution: Done
> 'JPA Tools -> Generate Tables from Entities' does not work for Hibernate 4.0
> ----------------------------------------------------------------------------
>
> Key: JBIDE-19835
> URL: https://issues.jboss.org/browse/JBIDE-19835
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Reporter: Koen Aers
> Assignee: Koen Aers
> Fix For: 4.3.0.Beta1
>
>
> This issue is a result of further investigation of JBIDE-19431 and JBIDE-19535. This investigation showed me that the generation of DDL works fine (wether a defined console configuration is used or not) unless version 4.0 of Hibernate is used.
> So for JPA 2.0 (which uses Hibernate 4.0 under the covers) the DDL generation does not work if the console configuration is used, nor when the use of a console configuration is disabled and Hibernate 4.0 is selected in the DDL generation dialog. It works however for Hibernate 3.5, 3.6 and 4.3.
> For a JPA 1.0 project, DDL generation works with the console configuration and when console configuration is disabled and Hibernate 3.5, 3.6 or 4.3 are selected in the DDL generation dialog.
> For JPA 2.1, only Hibernate 4.3 is a compatible Hibernate version and DDL generation works in this case both with and without using the console configuration.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months