[JBoss JIRA] (JBIDE-11903) OpenShift Explorer: add Application start/stop/restart
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11903?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-11903:
-------------------------------------
Fix Version/s: 4.1.0.Beta2
(was: 4.1.0.Beta1)
> OpenShift Explorer: add Application start/stop/restart
> -------------------------------------------------------
>
> Key: JBIDE-11903
> URL: https://issues.jboss.org/browse/JBIDE-11903
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.Beta2
> Environment: Eclipse plugin
> Reporter: Nam Duong
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Beta2
>
>
> The OpenShift Console view should contain controls for application start|stop|restart to match the functionality of the CLI. Currently, if you select Window->Show View->Others->OpenShift Express Console, then login in and select an application. The right-click menu doesn't have start|stop|restart so users have to either install the rhc client tools or ssh onto the OpenShift host gear.
--
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
12 years, 11 months
[JBoss JIRA] (JBDS-2484) 3rd party certification for JBDS 7.x (JBDS70_1211)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2484?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-2484 at 5/13/13 10:49 AM:
------------------------------------------------------------
Found some new updates this weekend:
* PMD 3.2.6 -> 4.0.0
* Subclipse 1.8.18_1.7.8.1 -> 1.8.20_1.7.9.1
* SpringIDE (same version 3.2.0.201303060654-RELEASE but now on a Kepler-based update site instead of Juno-based one, so installation / dependencies might have changed?)
* TestNG 6.8.1.20130330_0839
* SWTBot 2.1 -> 2.1.1.201305101559
* Atlassian 3.2.0.v20130212 -> 3.2.1
* GWT 3.2.1 -> 3.2.3.v201304260926-rel-r42
Also, should probably consider these 3rd party now since they come from Eclipse.org (even if it's Bob who's developing them):
* Eclipse BPEL 1.0.3
* BPMN2 Modeler 0.2.5.201305101845
was (Author: nickboldt):
Found some new updates this weekend:
* PMD 3.2.6 -> 4.0.0
* Subclipse 1.8.18_1.7.8.1 -> 1.8.20_1.7.9.1
* SpringIDE (same version 3.2.0.201303060654-RELEASE but now on a Kepler-based update site instead of Juno-based one, so installation / dependencies might have changed?)
* TestNG 6.8.1.20130330_0839
* swtbot 2.1 -> 2.1.1.201305101559
* atlassian 3.2.0.v20130212 -> 3.2.1
* gwt 3.2.1 -> 3.2.3.v201304260926-rel-r42
Also, should probably consider these 3rd party now since they come from Eclipse.org (even if it's Bob who's developing them):
* Eclipse BPEL 1.0.3
* bpmn2-modeler 0.2.5.201305101845
> 3rd party certification for JBDS 7.x (JBDS70_1211)
> --------------------------------------------------
>
> Key: JBDS-2484
> URL: https://issues.jboss.org/browse/JBDS-2484
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rdPartyCertification, 3rdPartyDependencies, Requirements
> Affects Versions: 7.0.0.Alpha1
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Priority: Blocker
> Fix For: 7.0.0.Beta1
>
>
> For JBDS 7, we need to ensure this list is as current and up to date as possible.
> The current list of Extras/Central connectors that we mirror are:
> * atlassian/3.0.6.v20120628 --> 3.2.0.v20130212 - JBIDE-13670, JBIDE-13682
> * gwt/3.1.0.v201208080121-rel-r42 --> 3.2.1 - JBDS-2486
> * springide/2.7.2.201109122348 --> 3.2.0 - JBDS-2395
> * subclipse/1.8.16_1.7.5.v1 --> 1.8.18_1.7.8.1 - JBDS-2485
> * testng/6.7.0.20120825_1316 --> 6.8.0.20121120_1820 - JBDS-2415
> * VJET 0.10 - JBIDE-14122
> These are currently unchanged since December when we released JBDS 6.0.0:
> * eclipsecs/5.6.0.201209221626 - nothing new as of 2013.03.22
> * findbugs/2.0.2.20121210 - nothing new as of 2013.03.22
> * pmd/3.2.6 - nothing new as of 2013.03.22
> Additionally:
> * egit/2.3.1.201302201838-r - JBIDE-13629 (not included in Kepler M5, but in M6; not part of Central as this is included in TP / Core)
> * swtbot 2.1 / junit4 - JBIDE-13843 (included in JBT TP; needed for running UI tests)
> See comments below for latest site URLs.
--
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
12 years, 11 months
[JBoss JIRA] (JBDS-2484) 3rd party certification for JBDS 7.x (JBDS70_1211)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2484?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-2484 at 5/13/13 10:49 AM:
------------------------------------------------------------
Found some new updates this weekend:
* PMD 3.2.6 -> 4.0.0
* Subclipse 1.8.18_1.7.8.1 -> 1.8.20_1.7.9.1
* SpringIDE (same version 3.2.0.201303060654-RELEASE but now on a Kepler-based update site instead of Juno-based one, so installation / dependencies might have changed?)
* TestNG 6.8.0.20121120_1820 -> 6.8.1.20130330_0839
* SWTBot 2.1 -> 2.1.1.201305101559
* Atlassian 3.2.0.v20130212 -> 3.2.1
* GWT 3.2.1 -> 3.2.3.v201304260926-rel-r42
Also, should probably consider these 3rd party now since they come from Eclipse.org (even if it's Bob who's developing them):
* Eclipse BPEL 1.0.3
* BPMN2 Modeler 0.2.5.201305101845
was (Author: nickboldt):
Found some new updates this weekend:
* PMD 3.2.6 -> 4.0.0
* Subclipse 1.8.18_1.7.8.1 -> 1.8.20_1.7.9.1
* SpringIDE (same version 3.2.0.201303060654-RELEASE but now on a Kepler-based update site instead of Juno-based one, so installation / dependencies might have changed?)
* TestNG 6.8.1.20130330_0839
* SWTBot 2.1 -> 2.1.1.201305101559
* Atlassian 3.2.0.v20130212 -> 3.2.1
* GWT 3.2.1 -> 3.2.3.v201304260926-rel-r42
Also, should probably consider these 3rd party now since they come from Eclipse.org (even if it's Bob who's developing them):
* Eclipse BPEL 1.0.3
* BPMN2 Modeler 0.2.5.201305101845
> 3rd party certification for JBDS 7.x (JBDS70_1211)
> --------------------------------------------------
>
> Key: JBDS-2484
> URL: https://issues.jboss.org/browse/JBDS-2484
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rdPartyCertification, 3rdPartyDependencies, Requirements
> Affects Versions: 7.0.0.Alpha1
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Priority: Blocker
> Fix For: 7.0.0.Beta1
>
>
> For JBDS 7, we need to ensure this list is as current and up to date as possible.
> The current list of Extras/Central connectors that we mirror are:
> * atlassian/3.0.6.v20120628 --> 3.2.0.v20130212 - JBIDE-13670, JBIDE-13682
> * gwt/3.1.0.v201208080121-rel-r42 --> 3.2.1 - JBDS-2486
> * springide/2.7.2.201109122348 --> 3.2.0 - JBDS-2395
> * subclipse/1.8.16_1.7.5.v1 --> 1.8.18_1.7.8.1 - JBDS-2485
> * testng/6.7.0.20120825_1316 --> 6.8.0.20121120_1820 - JBDS-2415
> * VJET 0.10 - JBIDE-14122
> These are currently unchanged since December when we released JBDS 6.0.0:
> * eclipsecs/5.6.0.201209221626 - nothing new as of 2013.03.22
> * findbugs/2.0.2.20121210 - nothing new as of 2013.03.22
> * pmd/3.2.6 - nothing new as of 2013.03.22
> Additionally:
> * egit/2.3.1.201302201838-r - JBIDE-13629 (not included in Kepler M5, but in M6; not part of Central as this is included in TP / Core)
> * swtbot 2.1 / junit4 - JBIDE-13843 (included in JBT TP; needed for running UI tests)
> See comments below for latest site URLs.
--
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
12 years, 11 months
[JBoss JIRA] (JBDS-2484) 3rd party certification for JBDS 7.x (JBDS70_1211)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2484?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2484:
----------------------------------
Found some new updates this weekend:
* PMD 3.2.6 -> 4.0.0
* Subclipse 1.8.18_1.7.8.1 -> 1.8.20_1.7.9.1
* SpringIDE (same version 3.2.0.201303060654-RELEASE but now on a Kepler-based update site instead of Juno-based one, so installation / dependencies might have changed?)
* TestNG 6.8.1.20130330_0839
* swtbot 2.1 -> 2.1.1.201305101559
* atlassian 3.2.0.v20130212 -> 3.2.1
* gwt 3.2.1 -> 3.2.3.v201304260926-rel-r42
Also, should probably consider these 3rd party now since they come from Eclipse.org (even if it's Bob who's developing them):
* Eclipse BPEL 1.0.3
* bpmn2-modeler 0.2.5.201305101845
> 3rd party certification for JBDS 7.x (JBDS70_1211)
> --------------------------------------------------
>
> Key: JBDS-2484
> URL: https://issues.jboss.org/browse/JBDS-2484
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rdPartyCertification, 3rdPartyDependencies, Requirements
> Affects Versions: 7.0.0.Alpha1
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Priority: Blocker
> Fix For: 7.0.0.Beta1
>
>
> For JBDS 7, we need to ensure this list is as current and up to date as possible.
> The current list of Extras/Central connectors that we mirror are:
> * atlassian/3.0.6.v20120628 --> 3.2.0.v20130212 - JBIDE-13670, JBIDE-13682
> * gwt/3.1.0.v201208080121-rel-r42 --> 3.2.1 - JBDS-2486
> * springide/2.7.2.201109122348 --> 3.2.0 - JBDS-2395
> * subclipse/1.8.16_1.7.5.v1 --> 1.8.18_1.7.8.1 - JBDS-2485
> * testng/6.7.0.20120825_1316 --> 6.8.0.20121120_1820 - JBDS-2415
> * VJET 0.10 - JBIDE-14122
> These are currently unchanged since December when we released JBDS 6.0.0:
> * eclipsecs/5.6.0.201209221626 - nothing new as of 2013.03.22
> * findbugs/2.0.2.20121210 - nothing new as of 2013.03.22
> * pmd/3.2.6 - nothing new as of 2013.03.22
> Additionally:
> * egit/2.3.1.201302201838-r - JBIDE-13629 (not included in Kepler M5, but in M6; not part of Central as this is included in TP / Core)
> * swtbot 2.1 / junit4 - JBIDE-13843 (included in JBT TP; needed for running UI tests)
> See comments below for latest site URLs.
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-14350) Search field disappears when Central editor is too small
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14350?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-14350:
-------------------------------------
[~snjeza]: what kind of icon do you have in mind?
I'd rather keep the checkbox and just hide the label (make sure a tooltip is available), whence the width is too small. Display the label when resizing > threshold width.
> Search field disappears when Central editor is too small
> --------------------------------------------------------
>
> Key: JBIDE-14350
> URL: https://issues.jboss.org/browse/JBIDE-14350
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.1.0.Alpha2
> Reporter: Radim Hopp
> Assignee: Fred Bricon
> Priority: Minor
> Fix For: 4.1.0.Beta1
>
> Attachments: searchField.png, searchField1.png
>
>
> Search field disappears, when Central editor is shrinked to certain width.
> Would it be possible either move the search field under buttons and "show on startup" checkbox or define some minimal width.
> Thanks
> !searchField.png!
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-12121) The openshift profile is added to newly created maven projects, regardless of their packaging type
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12121?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-12121:
-----------------------------------
Assignee: Andre Dietisheim (was: Fred Bricon)
After creating a project, one possibility is to use m2e's LocalScanner to collect projects under a root parent.
See https://github.com/jbosstools/jbosstools-central/blob/master/maven/plugin... as an example.
> 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
> Assignee: Andre Dietisheim
> Fix For: 4.1.x
>
> 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 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
12 years, 11 months