[JBoss JIRA] (JBIDE-18914) Spring cleaning for /targetplatforms/ folder
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18914?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-18914:
----------------------------------------
Fix Version/s: 4.2.3.Final
(was: 4.2.2.Final)
> Spring cleaning for /targetplatforms/ folder
> --------------------------------------------
>
> Key: JBIDE-18914
> URL: https://issues.jboss.org/browse/JBIDE-18914
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform, updatesite
> Affects Versions: 4.2.1.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.2.3.Final, 4.3.0.Alpha1
>
>
> Related to JBDS-3208, I'd like to purge all the unneeded old target platforms in [0].
> [0] http://download.jboss.org/jbosstools/targetplatforms/
> Specifically, this would involve moving and re-linking these into the equivalent folder under /static/ [1]:
> {code}
> [DIR] 3.62.0.Final-SNAPSHOT/
> [DIR] 3.72.0.Final-SNAPSHOT/
> [DIR] 4.20.5.Final-SNAPSHOT/
> [DIR] 4.20.6.Final-SNAPSHOT/
> [DIR] 4.21.3.Final-SNAPSHOT/
> [DIR] 4.21.4.Final-SNAPSHOT/
> [DIR] 4.22.0.Final-SNAPSHOT/
> [DIR] 4.22.1.Final-SNAPSHOT/
> [DIR] 4.22.2.Final-SNAPSHOT/
> {code}
> Then we can purge all the 4.\{3?,4?}.\*.\*-SNAPSHOT folders for all the pre-Final builds; the rest should already be in /static/, but we can verify that and move any that are not already there. Really, we only need the handful of *.Final folders, and they should all be in /static/ [1].
> [1] http://download.jboss.org/jbosstools/static/targetplatforms/
> I believe we can also purge things like 4.40.0.Beta* from here [2]:
> [2] http://download.jboss.org/jbosstools/static/targetplatforms/jbosstoolstar...
> But for that one we need to verify that [~pleacu] doesn't still need them (ie., they're not used for an older JBTIS/JBDSIS Beta release build on Eclipse 4.4.0 / JBoss Tools 4.2.0.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-18769) ResourceException when generating hbm.xml
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18769?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-18769:
----------------------------------------
Fix Version/s: 4.2.3.Final
(was: 4.2.2.Final)
> ResourceException when generating hbm.xml
> -----------------------------------------
>
> Key: JBIDE-18769
> URL: https://issues.jboss.org/browse/JBIDE-18769
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.2.0.Final
> Reporter: Rastislav Wagner
> Assignee: Koen Aers
> Priority: Blocker
> Fix For: 4.2.3.Final, 4.3.0.Alpha1
>
>
> {code}
> org.eclipse.core.internal.resources.ResourceException: Resource '/jboss-javaee6-webapp/org/jboss/tools/examples/model' does not exist.
> at org.eclipse.core.internal.resources.Resource.checkExists(Resource.java:341)
> at org.eclipse.core.internal.resources.Resource.checkAccessible(Resource.java:215)
> at org.eclipse.core.internal.resources.File.create(File.java:115)
> at org.eclipse.core.internal.resources.File.create(File.java:188)
> at org.eclipse.jdt.internal.corext.refactoring.nls.changes.CreateFileChange.perform(CreateFileChange.java:165)
> at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278)
> at org.hibernate.eclipse.jdt.ui.wizards.NewHibernateMappingPreviewPage.performFinish(NewHibernateMappingPreviewPage.java:299)
> at org.hibernate.eclipse.jdt.ui.wizards.NewHibernateMappingFileWizard.performFinish(NewHibernateMappingFileWizard.java:408)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:853)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:438)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3799)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3409)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:832)
> at org.eclipse.jface.window.Window.open(Window.java:808)
> at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:269)
> at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:294)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> 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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:247)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:229)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:149)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:159)
> 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$5.handleEvent(ActionContributionItem.java:420)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3799)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3409)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> 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.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-18711) Cordova plugin addition and removal fails when config.xml is in a linked folder
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18711?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-18711:
----------------------------------------
Fix Version/s: 4.2.3.Final
(was: 4.2.2.Final)
> Cordova plugin addition and removal fails when config.xml is in a linked folder
> -------------------------------------------------------------------------------
>
> Key: JBIDE-18711
> URL: https://issues.jboss.org/browse/JBIDE-18711
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.Final
> Environment: Oracle JDK 1.8.0_05, Mac OS X Mavericks
> Reporter: Vineet Reynolds
> Assignee: Gorkem Ercan
> Fix For: 4.2.3.Final, 4.3.0.Alpha1
>
>
> When config.xml is present in an Eclipse Linked folder (not in a symbolic link), then attempting to add or remove plugins (and possibly other operations on config.xml) fails with a spurious NullPointerException (without a stacktrace).
> This pretty much means that the Hybrid Mobile application project with a linked folder for 'www' is in a read-only state for plugin addition/removal. If any plugin should be added or removed, the linked folder must be dropped, converted to an ordinary folder (or symbolic link), and then re-created after modifications.
> To verify
> 1. create a new project
> 2. copy www folder to an alternate location
> 3. remove www folder
> 4.add www folder from alternate location as a linked folder (New Folder > Advanced> Link to alternate location)
> 5. add cordova plugins to the project. [Check they are added]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-18274) AS7/WildFly8/EAP6 with oracle java 7 fails to start when bound to your hostname
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18274?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-18274:
----------------------------------------
Fix Version/s: 4.2.3.Final
(was: 4.2.2.Final)
> AS7/WildFly8/EAP6 with oracle java 7 fails to start when bound to your hostname
> -------------------------------------------------------------------------------
>
> Key: JBIDE-18274
> URL: https://issues.jboss.org/browse/JBIDE-18274
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.2.3.Final, 4.3.0.Alpha1
>
> Attachments: server-adapter.png, server-editor.png, server-logs.png, server-runtime.png
>
>
> This is a follow up of JBIDE-17935 .
> Previously, Rob fixed this:
> {quote}
> I've surprisingly been able to replicate this and it's a race-condition. I'll need to synchronize some variables in this class here.
> {quote}
> But in this rare case it still fails for me.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-18724) HTML Validation: Ability to ignore custom htm tags (e.g. <ion-*>)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18724?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-18724:
----------------------------------------
Fix Version/s: 4.2.3.Final
(was: 4.2.2.Final)
moving of to 4.2.3
> HTML Validation: Ability to ignore custom htm tags (e.g. <ion-*>)
> -----------------------------------------------------------------
>
> Key: JBIDE-18724
> URL: https://issues.jboss.org/browse/JBIDE-18724
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing, upstream
> Reporter: Victor Rubezhny
> Assignee: Victor Rubezhny
> Labels: new_and_noteworthy
> Fix For: 4.2.3.Final
>
>
> WTP HTML validator marks any custom html tags as unknown. It's possible to disable this validation at all: Window->Preferences->Web->HTML Files->Validation ==> Set Elements -> Unknown tag name severity to "Ignore":
> !00001262.png!
> But it would be useful to have ability to make HTML validator ignore some particular tags only.
> I suggest to contribute a patch to WTP to fix it.
> We have already did it for attributes, so lets do it for tags too:
> - New preferences with a list of ignored tags (a mask can be used)
> - A new preference page to set these preferences
> - QuickFix for validation problem which will add the tag name/mask to this list/preferences
> - Extension in our angular/ionic plugin which will disable validation for <ion-*> tags.
> I've filed it to bugzilla - https://bugs.eclipse.org/bugs/show_bug.cgi?id=444545 but we have to provide a patch for it if we want to have it done ;)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months