[JBoss JIRA] (JBIDE-12121) Application wizard: the openshift profile is added to newly created maven projects, regardless of their packaging type
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12121?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-12121:
------------------------------------------
setting fixVersion to LATER since the main focus now is to create tooling for OpenShift v3.
> Application wizard: the openshift profile is added to newly created maven projects, regardless of their packaging type
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-12121
> URL: https://issues.jboss.org/browse/JBIDE-12121
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.0.CR1
> Reporter: Fred Bricon
> Labels: application_wizard
> Fix For: LATER
>
> Attachments: new-openarchetype-project-2.png, new-openarchetype-project.png
>
>
> I created a project using the org.openarchetypes:multi-javaee6-archetype:0.0.1-SNAPSHOT from http://open-archetypes.github.com/maven-repo/snapshots/archetype-catalog.xml (Maven > Archetypes > Add Remote Catalog)
> This creates a multi module project, containing a parent pom, an ear, war, ejb and utility projects. This openshift profile was added to the pom project :
> {code:xml}
> <profiles>
> <profile>
> <!-- When built in OpenShift the openshift profile will be used when invoking mvn. -->
> <!-- Use this profile for any OpenShift specific customization your app will need. -->
> <!-- By default that is to put the resulting archive into the deployments folder. -->
> <!-- http://maven.apache.org/guides/mini/guide-building-for-different-environm... -->
> <id>openshift</id>
> <build>
> <finalName>hello</finalName>
> <plugins>
> <plugin>
> <artifactId>maven-war-plugin</artifactId>
> <version>2.1.1</version>
> <configuration>
> <outputDirectory>deployments</outputDirectory>
> <warName>ROOT</warName>
> </configuration>
> </plugin>
> </plugins>
> </build>
> </profile>
> {code}
> Actually, it should :
> - check the packaging type of *all* the generated projects
> - if some EARs are found, then add the following to the parent pom (pay attention to the <pluginManagement> section) :
> {code:xml}
> <profile>
> <id>openshift</id>
> <build>
> <pluginManagement>
> <plugins>
> <plugin>
> <artifactId>maven-ear-plugin</artifactId>
> <version>2.7</version>
> <configuration>
> <outputDirectory>deployments</outputDirectory>
> </configuration>
> </plugin>
> </plugins>
> </pluginManagement>
> </build>
> </profile>
> {code}
> - if there are no EARs but some WARs are found (count them), then add the following to the parent pom (pay attention to the <pluginManagement> section) :
> {code:xml}
> <profiles>
> <profile>
> <id>openshift</id>
> <build>
> <pluginManagement>
> <plugins>
> <plugin>
> <artifactId>maven-war-plugin</artifactId>
> <version>2.2</version>
> <configuration>
> <outputDirectory>deployments</outputDirectory>
> <!-- Add warName ROOT ONLY if there's ONE War, otherwise, skip it -->
> <warName>ROOT</warName>
> </configuration>
> </plugin>
> </plugins>
> </pluginManagement>
> </build>
> </profile>
> {code}
> The finalName is irrelevant to openshift, only the warName counts.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-16921) Application wizard: <NEW CONNECTION> is preselected after removing first connection (out of 2)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16921?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16921:
-------------------------------------
Fix Version/s: LATER
(was: 4.2.x)
> Application wizard: <NEW CONNECTION> is preselected after removing first connection (out of 2)
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-16921
> URL: https://issues.jboss.org/browse/JBIDE-16921
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Beta1
> Reporter: Andre Dietisheim
> Priority: Minor
> Labels: application_wizard
> Fix For: LATER
>
>
> ASSERT: Have a connection (e.g. seconduser(a)somewhere.xx) in OpenShift Explorer.
> EXEC: Add another connection starting with a letter that's first in the alphabetical order (there is alphabetical order e.g. firstuser(a)somewhere.xx). It'll be listed first in the Explorer .
> EXEC: Open OpenShift application wizard via File->New->OpenShift->New Application.
> ASSERT: Wizard is opened. First connection is preselected.
> EXEC: close wizard
> EXEC: Remove first connection from OpenShift explorer.
> EXEC: Open OpenShift application wizard via File->New->OpenShift->New Application
> RESULT: Connection dialog is show with <NEW CONNECTION> preselected
> EXPECTED RESULT: Connection dialog is shown with remaining connection preselected
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-16921) Application wizard: <NEW CONNECTION> is preselected after removing first connection (out of 2)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16921?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-16921:
------------------------------------------
setting fixVersion to LATER since the main focus now is to create tooling for OpenShift v3.
> Application wizard: <NEW CONNECTION> is preselected after removing first connection (out of 2)
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-16921
> URL: https://issues.jboss.org/browse/JBIDE-16921
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Beta1
> Reporter: Andre Dietisheim
> Priority: Minor
> Labels: application_wizard
> Fix For: LATER
>
>
> ASSERT: Have a connection (e.g. seconduser(a)somewhere.xx) in OpenShift Explorer.
> EXEC: Add another connection starting with a letter that's first in the alphabetical order (there is alphabetical order e.g. firstuser(a)somewhere.xx). It'll be listed first in the Explorer .
> EXEC: Open OpenShift application wizard via File->New->OpenShift->New Application.
> ASSERT: Wizard is opened. First connection is preselected.
> EXEC: close wizard
> EXEC: Remove first connection from OpenShift explorer.
> EXEC: Open OpenShift application wizard via File->New->OpenShift->New Application
> RESULT: Connection dialog is show with <NEW CONNECTION> preselected
> EXPECTED RESULT: Connection dialog is shown with remaining connection preselected
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-16888) Tail Files: Cannot see log of cron cartridge
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16888?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16888:
-------------------------------------
Fix Version/s: LATER
(was: 4.2.x)
> Tail Files: Cannot see log of cron cartridge
> --------------------------------------------
>
> Key: JBIDE-16888
> URL: https://issues.jboss.org/browse/JBIDE-16888
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta1
> Reporter: Marián Labuda
> Priority: Minor
> Labels: tail_files
> Fix For: LATER
>
> Attachments: cron-log.png, tail-log-pattern.png
>
>
> After adding embeddable cartridge Cron into the application it is not possible to tail the cron-logs out-of-the-box. It is required to modify tail files pattern to include Cron job's log store in /cron/log.
> !tail-log-pattern.png!
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-14632) Explorer: "could not store password" logged whenever right clicking user/navigating tree
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14632?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-14632:
-------------------------------------
Fix Version/s: 4.3.x
> Explorer: "could not store password" logged whenever right clicking user/navigating tree
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-14632
> URL: https://issues.jboss.org/browse/JBIDE-14632
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Beta1
> Reporter: Max Rydahl Andersen
> Priority: Minor
> Labels: explorer
> Fix For: 4.2.x, 4.3.x
>
>
> created connection.
> get bunch of these stacktraces - especially when right clicking on the node.
> {code}
> org.jboss.tools.openshift.express.internal.ui.utils.SecurePasswordStoreException: Could not store password
> at org.jboss.tools.openshift.express.internal.ui.utils.SecurePasswordStore.storeInPreferences(SecurePasswordStore.java:102)
> at org.jboss.tools.openshift.express.internal.ui.utils.SecurePasswordStore.update(SecurePasswordStore.java:56)
> at org.jboss.tools.openshift.express.internal.ui.utils.SecurePasswordStore.setPassword(SecurePasswordStore.java:50)
> at org.jboss.tools.openshift.express.internal.core.connection.Connection.saveOrClearPassword(Connection.java:441)
> at org.jboss.tools.openshift.express.internal.core.connection.Connection.save(Connection.java:430)
> at org.jboss.tools.openshift.express.internal.core.connection.Connection.connect(Connection.java:196)
> at org.jboss.tools.openshift.express.internal.core.connection.Connection.getDefaultDomain(Connection.java:332)
> at org.jboss.tools.openshift.express.internal.ui.action.DeleteDomainAction.validate(DeleteDomainAction.java:47)
> at org.jboss.tools.openshift.express.internal.ui.explorer.actionProvider.AbstractOpenShiftExplorerViewerActionProvider.fillContextMenu(AbstractOpenShiftExplorerViewerActionProvider.java:50)
> at org.eclipse.ui.navigator.NavigatorActionService$2.run(NavigatorActionService.java:221)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.navigator.NavigatorActionService.addCommonActionProviderMenu(NavigatorActionService.java:216)
> at org.eclipse.ui.navigator.NavigatorActionService.fillContextMenu(NavigatorActionService.java:173)
> at org.eclipse.ui.navigator.CommonNavigatorManager.fillContextMenu(CommonNavigatorManager.java:260)
> at org.eclipse.ui.navigator.CommonNavigatorManager$4.menuAboutToShow(CommonNavigatorManager.java:275)
> at org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:343)
> at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:475)
> at org.eclipse.jface.action.MenuManager.access$1(MenuManager.java:470)
> at org.eclipse.jface.action.MenuManager$2.menuShown(MenuManager.java:500)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:255)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4164)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1470)
> at org.eclipse.swt.widgets.Menu.menuWillOpen(Menu.java:806)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5606)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
> at org.eclipse.swt.internal.cocoa.NSMenu.popUpContextMenu(NSMenu.java:77)
> at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:278)
> at org.eclipse.swt.widgets.Display.runPopups(Display.java:4087)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3642)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1109)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> 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:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> 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:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> Caused by: org.eclipse.equinox.security.storage.StorageException: No password provided.
> at org.eclipse.equinox.internal.security.storage.SecurePreferencesRoot.getModulePassword(SecurePreferencesRoot.java:304)
> at org.eclipse.equinox.internal.security.storage.SecurePreferencesRoot.getPassword(SecurePreferencesRoot.java:224)
> at org.eclipse.equinox.internal.security.storage.SecurePreferences.put(SecurePreferences.java:224)
> at org.eclipse.equinox.internal.security.storage.SecurePreferencesWrapper.put(SecurePreferencesWrapper.java:110)
> at org.jboss.tools.openshift.express.internal.ui.utils.SecurePasswordStore.storeInPreferences(SecurePasswordStore.java:99)
> ... 52 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-18872) Promote JBoss Tools CAT in JBT/JBDS About box
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18872?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18872:
---------------------------------------------
this is a JBDS about box issue - should be moved to JBDS but since this is a subtask that aren't doable :/ (did I say how much I hate subtasks in jira ? :)
> Promote JBoss Tools CAT in JBT/JBDS About box
> ---------------------------------------------
>
> Key: JBIDE-18872
> URL: https://issues.jboss.org/browse/JBIDE-18872
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Affects Versions: 4.2.0.Final
> Reporter: Vlado Pakan
> Fix For: 4.2.3.Final
>
>
> Would be nice to put link to JBT CAT or JBT CAT logo with link to it to JBDS/JBT About box to make JBT CAT more visible.
> New link/image should be visible without resizing About box
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months