[JBoss JIRA] (JBDS-2427) GA Installer still says CR1
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2427?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2427:
-----------------------------
Labels: respin-e (was: )
> GA Installer still says CR1
> ---------------------------
>
> Key: JBDS-2427
> URL: https://issues.jboss.org/browse/JBDS-2427
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build, installer
> Affects Versions: 6.0.0.GA
> Reporter: Pavol Srna
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: respin-e
> Fix For: 6.0.0.GA
>
> Attachments: desktoplauncherwrongversion.png, wrongMenuItemsversion.png
>
>
> "This installer will guide you through the installation of JBoss Developer Studio 6.0.0.CR1."
> Once installed, the splash screen shows correct version (GA). So does the About screen.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-11121) Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone
by Dan Florian (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi... ]
Dan Florian updated JBIDE-11121:
--------------------------------
Attachment: ModeShapeToolsBuildLog.txt
Attaching the ModeShape Tools maven build log. Build was successful.
> Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-11121
> URL: https://issues.jboss.org/browse/JBIDE-11121
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: SOA Tooling
> Affects Versions: 3.3.0.Beta1-SOA
> Reporter: Nick Boldt
> Assignee: Douglas Palmer
> Priority: Blocker
> Labels: f2f2012
> Fix For: 4.0.x
>
> Attachments: ModeShapeToolsBuildLog.txt
>
>
> Generate target platforms for JBT/JBDS SOA Tooling which include:
> 1. JBT Core TP + last stable JBT Core milestone.
> 2. JBDS Core TP + last stable JBDS Core milestone.
> Then, all SOA Component jobs should be rekeyed to use these new TPs when building instead of the JBT/JBDS Core ones.
> This includes Drools, which currently builds against Helios instead of Indigo, and Savara, which has requirements which are not as yet in the JBT/JBDS Core TPs (eg., GMF and Graphiti).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBDS-2427) GA Installer still says CR1
by Pavol Srna (JIRA)
Pavol Srna created JBDS-2427:
--------------------------------
Summary: GA Installer still says CR1
Key: JBDS-2427
URL: https://issues.jboss.org/browse/JBDS-2427
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Build, installer
Affects Versions: 6.0.0.GA
Reporter: Pavol Srna
Assignee: Nick Boldt
Priority: Blocker
Fix For: 6.0.0.GA
"This installer will guide you through the installation of JBoss Developer Studio 6.0.0.CR1."
Once installed, the splash screen shows correct version (GA). So does the About screen.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-13253) Maven Project Examples have empty group id by default and name complains about being empty
by Martin Malina (JIRA)
Martin Malina created JBIDE-13253:
-------------------------------------
Summary: Maven Project Examples have empty group id by default and name complains about being empty
Key: JBIDE-13253
URL: https://issues.jboss.org/browse/JBIDE-13253
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: maven, project-examples
Affects Versions: 3.3.1, 4.0.0.CR1
Reporter: Martin Malina
Assignee: Fred Bricon
Priority: Minor
Fix For: 3.3.2, 4.0.x
When you try to create one of the maven archetype examples using File -> New -> Example -> Project Examples -> JBoss Maven Project Examples there are these minor issues:
Group Id of the project is empty by default (from central there's a non-empty default). And also the project name is pre-set but complains it's empty.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-13254) In Seam 2.3 seam-gen generated project imported in JBDS, EL completion for Seam Messages doesn't work
by Ron Šmeral (JIRA)
Ron Šmeral created JBIDE-13254:
----------------------------------
Summary: In Seam 2.3 seam-gen generated project imported in JBDS, EL completion for Seam Messages doesn't work
Key: JBIDE-13254
URL: https://issues.jboss.org/browse/JBIDE-13254
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam 2
Affects Versions: 4.0.0.Beta2, 3.3.1
Environment: WFK 2.1.0.CR2 Seam.2.3.0.Final-redhat-1, JBDS 5.0.1.GA, JBDS 6.0.0.Beta2a
Reporter: Ron Šmeral
Assignee: Alexey Kazakov
After importing a Seam 2.3 seam-gen generated project in JBDS, the EL completion for Seam Messages doesn't work.
This works OK for a Seam project created in JBDS and for a Maven project imported to JBDS.
Actual results:
Even though the "messages" component is suggested, no actual messages from the properties files are suggested. A warning is shown for e.g #{messages['org.jboss.seam.NotLoggedIn']}.
Expected results:
Messages from messages_xx.properties should be suggested without warnings.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-13245) Cannot create examples from JBoss Maven Archetypes category via Project Examples wizard
by Rastislav Wagner (JIRA)
Rastislav Wagner created JBIDE-13245:
----------------------------------------
Summary: Cannot create examples from JBoss Maven Archetypes category via Project Examples wizard
Key: JBIDE-13245
URL: https://issues.jboss.org/browse/JBIDE-13245
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven, project-examples
Affects Versions: 4.0.0.CR1
Reporter: Rastislav Wagner
Assignee: Fred Bricon
Priority: Critical
Fix For: 4.0.0.CR1
Error downloading archetype null:null:null
{code}java.lang.reflect.InvocationTargetException
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:477)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1028)
at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.getRequiredProperties(ArchetypeExamplesWizardPage.java:184)
at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.initializeArchetype(ArchetypeExamplesWizardPage.java:135)
at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.setProjectExample(ArchetypeExamplesWizardPage.java:472)
at org.jboss.tools.project.examples.wizard.NewProjectExamplesMainPage$1.selectionChanged(NewProjectExamplesMainPage.java:216)
at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:164)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:162)
at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2188)
at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1211)
at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1241)
at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:239)
at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:233)
at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:403)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1276)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.jboss.tools.central.actions.NewProjectExamplesWizardHandler.execute(NewProjectExamplesWizardHandler.java:62)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:76)
at sun.reflect.GeneratedMethodAccessor242.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:229)
at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:210)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:131)
at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:171)
at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:500)
at org.eclipse.ui.menus.CommandContributionItem.handleWidgetSelection(CommandContributionItem.java:824)
at org.eclipse.ui.menus.CommandContributionItem.access$19(CommandContributionItem.java:810)
at org.eclipse.ui.menus.CommandContributionItem$5.handleEvent(CommandContributionItem.java:800)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1276)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1029)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:923)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
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:601)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
at org.eclipse.equinox.launcher.Main.main(Main.java:1414)
Caused by: org.apache.maven.artifact.InvalidArtifactRTException: For artifact {null:null:null:pom}: The groupId cannot be empty.
at org.apache.maven.artifact.DefaultArtifact.validateIdentity(DefaultArtifact.java:130)
at org.apache.maven.artifact.DefaultArtifact.<init>(DefaultArtifact.java:123)
at org.apache.maven.artifact.factory.DefaultArtifactFactory.createArtifact(DefaultArtifactFactory.java:157)
at org.apache.maven.artifact.factory.DefaultArtifactFactory.createArtifact(DefaultArtifactFactory.java:117)
at org.apache.maven.artifact.factory.DefaultArtifactFactory.createArtifact(DefaultArtifactFactory.java:111)
at org.apache.maven.artifact.factory.DefaultArtifactFactory.createArtifactWithClassifier(DefaultArtifactFactory.java:45)
at org.apache.maven.repository.legacy.LegacyRepositorySystem.createArtifactWithClassifier(LegacyRepositorySystem.java:129)
at org.eclipse.m2e.core.internal.embedder.MavenImpl.resolve(MavenImpl.java:639)
at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.downloadArchetype(ArchetypeExamplesWizardPage.java:255)
at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.access$4(ArchetypeExamplesWizardPage.java:245)
at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$3.run(ArchetypeExamplesWizardPage.java:199)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
... 64 more
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months