[JBoss JIRA] (JBIDE-18820) define how to handle ide.properties and avoid parent pom to always change
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18820?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-18820.
------------------------------
> define how to handle ide.properties and avoid parent pom to always change
> -------------------------------------------------------------------------
>
> Key: JBIDE-18820
> URL: https://issues.jboss.org/browse/JBIDE-18820
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build, devdoc
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Labels: devdoc
> Fix For: 4.4.2.Final
>
>
> As illustrated in JBIDE-18806 our current setup of how ide.properties and project versioning are not working or at least we seem to not get it updated right.
> Current workaround applied is that parent pom now again defines the global version even though this is not reliable at all since not all plugins will be rebuilt. (see JBIDE-13452 for earlier attempts on this)
> Opening this jira to make sure we walkthrough and write down which values should be in ide.properties and what level (4.2.0.CR1, 4.2.0 or 4.2. etc), when they get updated (hopefully rarely) and how to avoid parent pom from always having to respin because of a maintanence release.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-18820) define how to handle ide.properties and avoid parent pom to always change
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18820?page=com.atlassian.jira.plugi... ]
Nick Boldt resolved JBIDE-18820.
--------------------------------
Fix Version/s: 4.4.2.Final
(was: 4.3.x)
Assignee: Nick Boldt (was: Jeff MAURY)
Resolution: Done
This has been punted around for 2 years so ... closing it.
> define how to handle ide.properties and avoid parent pom to always change
> -------------------------------------------------------------------------
>
> Key: JBIDE-18820
> URL: https://issues.jboss.org/browse/JBIDE-18820
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build, devdoc
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Labels: devdoc
> Fix For: 4.4.2.Final
>
>
> As illustrated in JBIDE-18806 our current setup of how ide.properties and project versioning are not working or at least we seem to not get it updated right.
> Current workaround applied is that parent pom now again defines the global version even though this is not reliable at all since not all plugins will be rebuilt. (see JBIDE-13452 for earlier attempts on this)
> Opening this jira to make sure we walkthrough and write down which values should be in ide.properties and what level (4.2.0.CR1, 4.2.0 or 4.2. etc), when they get updated (hopefully rarely) and how to avoid parent pom from always having to respin because of a maintanence release.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBDS-3439) Unable to add a new Forge Runtime
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3439?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov reassigned JBDS-3439:
------------------------------------
Assignee: Jeff MAURY (was: Alexey Kazakov)
> Unable to add a new Forge Runtime
> ---------------------------------
>
> Key: JBDS-3439
> URL: https://issues.jboss.org/browse/JBDS-3439
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Quality Risk
> Components: forge
> Affects Versions: 8.0.0.GA, 8.1.0.GA
> Environment: Fedora 20, jdk1.7.0_67, JBoss Developer Studio 8+
> Reporter: Miguel Angel Morales Pedraza
> Assignee: Jeff MAURY
> Priority: Optional
> Labels: forge, runtime
> Fix For: 8.x
>
>
> Unable to add a new Forge runtime on JBDS 8.0.0 and 8.1.0. The button "Add" it doesn't shown anymore.
> On the JBDS v7.1.1 this button appears.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-20676) NPE in org.jboss.tools.jst.web.ui.palette.PaletteAdapter.refreshDynamicDrawer()
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20676?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-20676:
--------------------------------------
Assignee: Jeff MAURY (was: Alexey Kazakov)
> NPE in org.jboss.tools.jst.web.ui.palette.PaletteAdapter.refreshDynamicDrawer()
> -------------------------------------------------------------------------------
>
> Key: JBIDE-20676
> URL: https://issues.jboss.org/browse/JBIDE-20676
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common
> Affects Versions: 4.3.0.CR1
> Environment: Linux x86_64 SWT_GTK3=1
> Reporter: Denis Golovin
> Assignee: Jeff MAURY
> Priority: Minor
> Fix For: 4.3.x
>
>
> Exception below occurs in case of switching between jsp and html editord oprened for the same html5 file. kitchensink-angularjs example from central is good test project for this issue. {code}java.lang.NullPointerException
> at org.jboss.tools.jst.web.ui.palette.PaletteAdapter.refreshDynamicDrawer(PaletteAdapter.java:130)
> at org.jboss.tools.jst.web.ui.palette.PaletteAdapter.activated(PaletteAdapter.java:101)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.PalettePageImpl$1.partActivated(PalettePageImpl.java:71)
> at org.eclipse.ui.internal.WorkbenchPage$14.run(WorkbenchPage.java:4885)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.WorkbenchPage.firePartActivated(WorkbenchPage.java:4882)
> at org.eclipse.ui.internal.WorkbenchPage.access$19(WorkbenchPage.java:4870)
> at org.eclipse.ui.internal.WorkbenchPage$E4PartListener.partActivated(WorkbenchPage.java:202)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl$3.run(PartServiceImpl.java:245)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.firePartActivated(PartServiceImpl.java:242)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:711)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:639)
> at org.eclipse.e4.ui.internal.workbench.swt.AbstractPartRenderer.activate(AbstractPartRenderer.java:106)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer$1.handleEvent(ContributedPartRenderer.java:63)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1353)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1338)
> at org.eclipse.swt.widgets.Shell.setActiveControl(Shell.java:1756)
> at org.eclipse.swt.widgets.Control.gtk_button_press_event(Control.java:3073)
> at org.eclipse.swt.widgets.Control.gtk_button_press_event(Control.java:3009)
> at org.eclipse.swt.widgets.Composite.gtk_button_press_event(Composite.java:731)
> at org.eclipse.swt.widgets.Tree.gtk_button_press_event(Tree.java:1839)
> at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1959)
> at org.eclipse.swt.widgets.Control.windowProc(Control.java:5590)
> at org.eclipse.swt.widgets.Tree.windowProc(Tree.java:3612)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:4717)
> at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9279)
> at org.eclipse.swt.widgets.Display.eventProc(Display.java:1225)
> at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
> at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2425)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3428)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> 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:139)
> 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:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488){code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-15246) JQuery Checkboxes have broken CSS layout on desktop browsers
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15246?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-15246:
--------------------------------------
Assignee: Jeff MAURY (was: Alexey Kazakov)
> JQuery Checkboxes have broken CSS layout on desktop browsers
> ------------------------------------------------------------
>
> Key: JBIDE-15246
> URL: https://issues.jboss.org/browse/JBIDE-15246
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples, upstream
> Affects Versions: 4.1.0.CR1
> Reporter: Karel Piwko
> Assignee: Jeff MAURY
> Fix For: 4.5.0.AM1
>
> Attachments: browserSim.png, chrome.png, firefox.png, int.png, jquery-mobile-checkboxes-desktop.png
>
>
> JQuery Mobile palette does render properly on desktop browser (internal browser, chrome).
> How to reproduce:
> 1/ Create mobile example from JBoss Central
> 2/ Add "Checkboxes" from JQuery Mobile palette
> 3/ Deploy and open on desktop
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-14732) Hide preview should hide preview only
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14732?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-14732:
--------------------------------------
Assignee: Jeff MAURY (was: Alexey Kazakov)
> Hide preview should hide preview only
> -------------------------------------
>
> Key: JBIDE-14732
> URL: https://issues.jboss.org/browse/JBIDE-14732
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html-source-editing
> Affects Versions: 4.1.0.Beta1
> Environment: Any
> Reporter: Denis Golovin
> Assignee: Jeff MAURY
> Labels: usability
> Fix For: LATER
>
> Attachments: dialog-new.gif, dialog.gif
>
>
> Now Hide Preview button forces to close whole right part of wizard. It looks ok, but jumps to much and hides html source too. Looks like this:
> !dialog.gif!
> Would it be better to have it implemented like this:
> !dialog-new.gif!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-6314) NPE on every start of eclipse
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-6314?page=com.atlassian.jira.plugin... ]
Alexey Kazakov reassigned JBIDE-6314:
-------------------------------------
Assignee: Jeff MAURY (was: Alexey Kazakov)
> NPE on every start of eclipse
> -----------------------------
>
> Key: JBIDE-6314
> URL: https://issues.jboss.org/browse/JBIDE-6314
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 3.2.x
> Environment: nightly build 201005181730
> java.version=1.6.0_16
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=bg_BG
> Framework arguments: -product org.eclipse.epp.package.jee.product
> Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product -clean
> Reporter: Krasimir Goutcev
> Assignee: Jeff MAURY
> Fix For: LATER
>
> Attachments: hibernate3.jar
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> An internal error occurred during: "JBoss Tools Model Update".
> log:
> java.lang.NullPointerException
> at java.util.zip.ZipFile.getInputStream(ZipFile.java:180)
> at org.jboss.tools.common.model.filesystems.impl.JarAccess.getContent(JarAccess.java:200)
> at org.jboss.tools.common.model.filesystems.impl.JarAccess.isTextEntry(JarAccess.java:235)
> at org.jboss.tools.common.model.filesystems.impl.JarFolderImpl.createFileObject(JarFolderImpl.java:90)
> at org.jboss.tools.common.model.filesystems.impl.JarFolderImpl.loadChildren(JarFolderImpl.java:74)
> at org.jboss.tools.common.model.filesystems.impl.JarSystemImpl.loadChildren(JarSystemImpl.java:46)
> at org.jboss.tools.common.model.impl.RegularObjectImpl.getChildByPathPart(RegularObjectImpl.java:140)
> at org.jboss.tools.common.model.filesystems.impl.JarFolderImpl.getChildByPathPart(JarFolderImpl.java:131)
> at org.jboss.tools.common.model.impl.XModelObjectImpl.getChildByPath(XModelObjectImpl.java:335)
> at org.jboss.tools.jst.web.tld.TaglibMapping.findTldsInJar(TaglibMapping.java:224)
> at org.jboss.tools.jst.web.tld.TaglibMapping.findTldsInJars(TaglibMapping.java:208)
> at org.jboss.tools.jst.web.tld.TaglibMapping.revalidate(TaglibMapping.java:84)
> at org.jboss.tools.jsf.web.JSFWatcherContributor.updateProject(JSFWatcherContributor.java:49)
> at org.jboss.tools.common.model.project.Watcher.updateAll(Watcher.java:106)
> at org.jboss.tools.common.model.project.Watcher.access$0(Watcher.java:89)
> at org.jboss.tools.common.model.project.Watcher$WatcherRunnable.run(Watcher.java:47)
> at org.jboss.tools.common.model.XJob.runInWorkspace(XJob.java:158)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-18963) when whatsnew index generation is run on files that refer components that does not exist an error message containing what component is at fault should be printed
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18963?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-18963:
--------------------------------------
Assignee: Jeff MAURY (was: Alexey Kazakov)
> when whatsnew index generation is run on files that refer components that does not exist an error message containing what component is at fault should be printed
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18963
> URL: https://issues.jboss.org/browse/JBIDE-18963
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: website
> Affects Versions: 4.2.3.Beta1
> Reporter: Max Rydahl Andersen
> Assignee: Jeff MAURY
> Fix For: LATER
>
>
> today when having invalid components you get something like:
> {code}
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:65:in `block (4 levels) in singletonclass'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:64:in `each'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:64:in `block (3 levels) in singletonclass'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:29:in `each'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:29:in `block (2 levels) in singletonclass'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:27:in `each'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:27:in `block in singletonclass'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:65533:in `instance_eval'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:65533:in `singletonclass'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:65531:in `__tilt_70190394039780'
> {code}
> as found in https://github.com/jbosstools/jbosstools-website/pull/311/files
> the logic is all embedded in haml leaving no room for proper error handling.
> should do some basic asserts in the pipeline for that ids actually exists in components.yml or at least just use component id as fall back name.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months