[JBoss JIRA] (JBDS-2847) Java EE 7 Tech Preview
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBDS-2847?page=com.atlassian.jira.plugin.... ]
Xavier Coulon commented on JBDS-2847:
-------------------------------------
[~ldimaggio], [~mmalina], [~jpeterka],
I had the same problems at the beginning, but IIRC, after editing the pom.xml, deleting the projects from the workspace, removing all .project, .classpath and .settings/* files, it worked all good.
If you're still blocked on this problem, I suggest that you comment out the Groovy compiler in the parent pom.xml. It may cause issues for mvn build from the command line since some modules require Groovy to run tests with Spock, but it should not prevent from editing some files and deploying on WildFly.
> Java EE 7 Tech Preview
> ----------------------
>
> Key: JBDS-2847
> URL: https://issues.jboss.org/browse/JBDS-2847
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements
> Reporter: Burr Sutter
> Assignee: Xavier Coulon
> Labels: JBDS80_Approved_Scope
> Fix For: 8.0.0.CR1
>
>
> Successfully/cleanly import the Java EE 7 Samples that have been migrated/ported to Wildfly
> https://github.com/javaee-samples/javaee7-samples
> They should import nicely (without errors) into JBT/JBDS and deploy to a JBT/JBDS managed Wildfly.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (JBIDE-17808) Identify which installed IUs are from Early Access vs. supported/tested versions
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17808?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-17808:
-----------------------------------
Attachment: JBIDE17808.jpeg
> Identify which installed IUs are from Early Access vs. supported/tested versions
> --------------------------------------------------------------------------------
>
> Key: JBIDE-17808
> URL: https://issues.jboss.org/browse/JBIDE-17808
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Labels: documentation
> Fix For: 4.2.0.CR1
>
> Attachments: JBIDE17808.jpeg
>
>
> [~maxandersen] brought up a good point on a call today:
> we have no way from within JBDS of identifying which installed IUs were installed from Early Access vs. those what were installed from Central or another "supported" location.
> Thus we need some sort of UI to list installed IUs that are "Early Access".
> This could be... (brainstorming now):
> * a text file with the list of things installed from Early Access (features and plugins)
> * a set of asterisks added to the Help > About dialogs when browsing for installed features / plugins
> * a way to filter the plugin view (Help > About) to show only EA content (or exclude it)
> * ... ?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (JBIDE-17808) Identify which installed IUs are from Early Access vs. supported/tested versions
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17808?page=com.atlassian.jira.plugi... ]
Mickael Istria edited comment on JBIDE-17808 at 8/7/14 2:25 AM:
----------------------------------------------------------------
Current layout is
!JBIDE17808.jpeg!
was (Author: mickael_istria):
Current layout is
!JBIDE-17808.jpeg!
> Identify which installed IUs are from Early Access vs. supported/tested versions
> --------------------------------------------------------------------------------
>
> Key: JBIDE-17808
> URL: https://issues.jboss.org/browse/JBIDE-17808
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Labels: documentation
> Fix For: 4.2.0.CR1
>
> Attachments: JBIDE17808.jpeg
>
>
> [~maxandersen] brought up a good point on a call today:
> we have no way from within JBDS of identifying which installed IUs were installed from Early Access vs. those what were installed from Central or another "supported" location.
> Thus we need some sort of UI to list installed IUs that are "Early Access".
> This could be... (brainstorming now):
> * a text file with the list of things installed from Early Access (features and plugins)
> * a set of asterisks added to the Help > About dialogs when browsing for installed features / plugins
> * a way to filter the plugin view (Help > About) to show only EA content (or exclude it)
> * ... ?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (JBIDE-17808) Identify which installed IUs are from Early Access vs. supported/tested versions
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17808?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-17808:
-----------------------------------
Labels: documentation (was: )
> Identify which installed IUs are from Early Access vs. supported/tested versions
> --------------------------------------------------------------------------------
>
> Key: JBIDE-17808
> URL: https://issues.jboss.org/browse/JBIDE-17808
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Labels: documentation
> Fix For: 4.2.0.CR1
>
> Attachments: JBIDE17808.jpeg
>
>
> [~maxandersen] brought up a good point on a call today:
> we have no way from within JBDS of identifying which installed IUs were installed from Early Access vs. those what were installed from Central or another "supported" location.
> Thus we need some sort of UI to list installed IUs that are "Early Access".
> This could be... (brainstorming now):
> * a text file with the list of things installed from Early Access (features and plugins)
> * a set of asterisks added to the Help > About dialogs when browsing for installed features / plugins
> * a way to filter the plugin view (Help > About) to show only EA content (or exclude it)
> * ... ?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (JBIDE-17808) Identify which installed IUs are from Early Access vs. supported/tested versions
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17808?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-17808:
-----------------------------------
Attachment: JBIDE-17808.jpeg
Current layout is
!JBIDE-17808.jpeg!
> Identify which installed IUs are from Early Access vs. supported/tested versions
> --------------------------------------------------------------------------------
>
> Key: JBIDE-17808
> URL: https://issues.jboss.org/browse/JBIDE-17808
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 4.2.0.CR1
>
>
> [~maxandersen] brought up a good point on a call today:
> we have no way from within JBDS of identifying which installed IUs were installed from Early Access vs. those what were installed from Central or another "supported" location.
> Thus we need some sort of UI to list installed IUs that are "Early Access".
> This could be... (brainstorming now):
> * a text file with the list of things installed from Early Access (features and plugins)
> * a set of asterisks added to the Help > About dialogs when browsing for installed features / plugins
> * a way to filter the plugin view (Help > About) to show only EA content (or exclude it)
> * ... ?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (JBIDE-17808) Identify which installed IUs are from Early Access vs. supported/tested versions
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17808?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-17808:
-----------------------------------
Attachment: (was: JBIDE-17808.jpeg)
> Identify which installed IUs are from Early Access vs. supported/tested versions
> --------------------------------------------------------------------------------
>
> Key: JBIDE-17808
> URL: https://issues.jboss.org/browse/JBIDE-17808
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 4.2.0.CR1
>
>
> [~maxandersen] brought up a good point on a call today:
> we have no way from within JBDS of identifying which installed IUs were installed from Early Access vs. those what were installed from Central or another "supported" location.
> Thus we need some sort of UI to list installed IUs that are "Early Access".
> This could be... (brainstorming now):
> * a text file with the list of things installed from Early Access (features and plugins)
> * a set of asterisks added to the Help > About dialogs when browsing for installed features / plugins
> * a way to filter the plugin view (Help > About) to show only EA content (or exclude it)
> * ... ?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (JBIDE-17973) Obscure database password
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17973?page=com.atlassian.jira.plugi... ]
Marián Labuda edited comment on JBIDE-17973 at 8/7/14 2:13 AM:
---------------------------------------------------------------
I agree with Catherine in her last post. We could check if Embedded Cartridge shell, which is showed up after embedding a cartridge or using DIY/Jenkins basic cartridges, contains keyword "password" and if there is this keyword, we could provide collapsed text area with button to show content and warning right before it, that there are sensitive information. WDYT?
was (Author: mlabuda):
I agree with Catherine. We could check if Embedded Cartridge shell, which is showed up after embedding a cartridge or using DIY/Jenkins basic cartridges, contains keyword "password" and if there is this keyword, we could provide collapsed text area with button to show content and warning right before it, that there are sensitive information. WDYT?
> Obscure database password
> -------------------------
>
> Key: JBIDE-17973
> URL: https://issues.jboss.org/browse/JBIDE-17973
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.2.0.Beta2
> Reporter: Catherine Robson
> Assignee: Max Rydahl Andersen
> Priority: Minor
> Labels: uxtest
> Fix For: 4.3.x
>
>
> When creating an OpenShift application with a database cartridge, the database password is shown in clear text. This password should be obscured.
> It was noted that OpenShift does show clear text passwords in some locations, the difference here is that the user did not prompt for this information meaning we are displaying a password in clear text at a potential point where the user is not aware they need to be in a 'secure' environment.
> Reproduce steps:
> 1. Open new OpenShift Application wizard
> 2. Sign in & proceed to next screen
> 3. Choose application cartridge (JBoss EAP 6 for instance) & proceed to next screen
> 4. Add embedded cartridge for database (mySQL 5.5 for instance) & proceed to next screen
> 5. Click next on set up project screen
> 6. Click finish on next screen
> 7 -> ISSUE HERE. Once app is created, pop-up is shown with mySQL database password shown in clear text. Screenshot: https://www.evernote.com/shard/s230/sh/cd8123fb-a400-4699-ad08-bcbc06f7b5...
> Expected: Password on this pop-up should be obscured.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (JBIDE-17973) Obscure database password
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17973?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-17973:
---------------------------------------
I agree with Catherine. We could check if Embedded Cartridge shell, which is showed up after embedding a cartridge or using DIY/Jenkins basic cartridges, contains keyword "password" and if there is this keyword, we could provide collapsed text area with button to show content and warning right before it, that there are sensitive information. WDYT?
> Obscure database password
> -------------------------
>
> Key: JBIDE-17973
> URL: https://issues.jboss.org/browse/JBIDE-17973
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.2.0.Beta2
> Reporter: Catherine Robson
> Assignee: Max Rydahl Andersen
> Priority: Minor
> Labels: uxtest
> Fix For: 4.3.x
>
>
> When creating an OpenShift application with a database cartridge, the database password is shown in clear text. This password should be obscured.
> It was noted that OpenShift does show clear text passwords in some locations, the difference here is that the user did not prompt for this information meaning we are displaying a password in clear text at a potential point where the user is not aware they need to be in a 'secure' environment.
> Reproduce steps:
> 1. Open new OpenShift Application wizard
> 2. Sign in & proceed to next screen
> 3. Choose application cartridge (JBoss EAP 6 for instance) & proceed to next screen
> 4. Add embedded cartridge for database (mySQL 5.5 for instance) & proceed to next screen
> 5. Click next on set up project screen
> 6. Click finish on next screen
> 7 -> ISSUE HERE. Once app is created, pop-up is shown with mySQL database password shown in clear text. Screenshot: https://www.evernote.com/shard/s230/sh/cd8123fb-a400-4699-ad08-bcbc06f7b5...
> Expected: Password on this pop-up should be obscured.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (JBIDE-18055) NullPionterException in VPE Preview Editor initialization
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18055?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-18055:
----------------------------------
Fix Version/s: 4.2.0.CR1
> NullPionterException in VPE Preview Editor initialization
> ---------------------------------------------------------
>
> Key: JBIDE-18055
> URL: https://issues.jboss.org/browse/JBIDE-18055
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.Beta3
> Reporter: Denis Golovin
> Priority: Minor
> Fix For: 4.2.0.CR1
>
>
> Exception below can happen sometimes in case re-sizing visual preview part while preview server serving the editor is not started yet.
> {code}java.lang.NullPointerException
> at org.jboss.tools.vpe.preview.core.server.VpvServer.getPort(VpvServer.java:66)
> at org.jboss.tools.vpe.preview.editor.VpvEditor.formRequestToServer(VpvEditor.java:503)
> at org.jboss.tools.vpe.preview.editor.VpvEditor.reload(VpvEditor.java:494)
> at org.jboss.tools.vpe.preview.editor.VpvEditorPart.updateVisualEditorVisibility(VpvEditorPart.java:769)
> at org.jboss.tools.vpe.preview.editor.VpvEditorPart$5.controlResized(VpvEditorPart.java:386)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:235)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1393)
> at org.eclipse.swt.widgets.Control.setBounds(Control.java:1042)
> at org.eclipse.swt.widgets.Composite.setBounds(Composite.java:1435)
> at org.eclipse.swt.widgets.Control.setBounds(Control.java:851)
> at org.eclipse.swt.custom.SashForm.onDragSash(SashForm.java:288)
> at org.eclipse.swt.custom.SashForm$1.handleEvent(SashForm.java:90)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412)
> at org.eclipse.swt.widgets.Widget.sendSelectionEvent(Widget.java:1526)
> at org.eclipse.swt.widgets.Sash.gtk_motion_notify_event(Sash.java:396)
> at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2104)
> at org.eclipse.swt.widgets.Control.windowProc(Control.java:5510)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:4700)
> 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:9074)
> at org.eclipse.swt.widgets.Display.eventProc(Display.java:1253)
> 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:2473)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3439)
> 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:382)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
> 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: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.2.6#6264)
11 years, 10 months