[JBoss JIRA] (JBIDE-13862) server adapter wizard: When creating adapter manually, the deploying project should be added automatically
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13862?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13862:
-------------------------------------
Summary: server adapter wizard: When creating adapter manually, the deploying project should be added automatically (was: Deploying project should be automatically added to OpenShift Server adapter)
> server adapter wizard: When creating adapter manually, the deploying project should be added automatically
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13862
> URL: https://issues.jboss.org/browse/JBIDE-13862
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, server
> Affects Versions: 4.1.0.Alpha1
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: server.png, server1.png, server2.png
>
>
> Deploying project is automatically added to OpenShift Server adapter after application import:
> * after application import contains the deploying project: !server.png|thumbnail!
> When created manually via OpenShift Explorer (Application - Create Server Adapter), the deploying project is not automatically added, even though I'm selecting the deploying project:
> * !server2.png|thumbnail! *->* !server1.png|thumbnail!
--
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, 5 months
[JBoss JIRA] (JBIDE-16081) Aerogear.hybrid requires org.eclipse.debug.core [3.7.0, 3.9.0) but Luna includes 3.9.0
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16081?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-16081:
-------------------------------
Description:
If org.jboss.tools.aerogear.hybrid.ios.core could be changed to depend on org.eclipse.debug.core [3.7.0,3.10.0) then it could be installed into Luna M3.
1. fire up Eclipse Standard Luna M3 package (eclipse-standard-luna-M3-linux-gtk-x86_64.tar.gz). Help > Install new > ...
* http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... (JBT 4.1.1.CR1 TP site)
* http://download.jboss.org/jbosstools/updates/nightly/core/4.1.kepler/ (JBT 4.1.1.CR1 Core update site)
uncheck "group by category" then select all features, and you'll get this:
!install-all-of-JBT-into-LunaM3-except-aerogear.hybrid.png!
!install-all-of-JBT-into-LunaM3-except-aerogear.hybrid-error-details.png!
{code}
Cannot complete the install because of a conflicting dependency.
Software being installed: JBoss Hybrid Mobile Application Development Tools (Experimental) 1.0.100.CR1-v20131116-0025-B52 (org.jboss.tools.aerogear.hybrid.feature.feature.group 1.0.100.CR1-v20131116-0025-B52)
Software currently installed: Eclipse Standard/SDK 2.1.0.20131103-0830 (epp.package.standard 2.1.0.20131103-0830)
Only one of the following can be installed at once:
Debug Core 3.9.0.v20131003-1341 (org.eclipse.debug.core 3.9.0.v20131003-1341)
Debug Core 3.9.0.v20130819-1716 (org.eclipse.debug.core 3.9.0.v20130819-1716)
Debug Core 3.9.0.v20130731-1644 (org.eclipse.debug.core 3.9.0.v20130731-1644)
Debug Core 3.8.0.v20130514-0954 (org.eclipse.debug.core 3.8.0.v20130514-0954)
Cannot satisfy dependency:
From: Eclipse Standard/SDK 2.1.0.20131103-0830 (epp.package.standard 2.1.0.20131103-0830)
To: org.eclipse.epp.package.standard.feature.feature.group [2.1.0.20131103-0830]
Cannot satisfy dependency:
From: Eclipse Standard/SDK Feature 2.1.0.20131103-0830 (org.eclipse.epp.package.standard.feature.feature.group 2.1.0.20131103-0830)
To: org.eclipse.platform.feature.group [4.4.0.v20131030-2000]
Cannot satisfy dependency:
From: Eclipse Platform 4.4.0.v20131030-2000 (org.eclipse.platform.feature.group 4.4.0.v20131030-2000)
To: org.eclipse.debug.core [3.9.0.v20131003-1341]
Cannot satisfy dependency:
From: JBoss Hybrid Mobile Application Development Tools (Experimental) 1.0.100.CR1-v20131116-0025-B52 (org.jboss.tools.aerogear.hybrid.feature.feature.group 1.0.100.CR1-v20131116-0025-B52)
To: org.jboss.tools.aerogear.hybrid.ios.core [1.0.100.CR1-v20131116-0025-B52]
Cannot satisfy dependency:
From: JBoss Hybrid Mobile App. Dev. iOS Core 1.0.100.CR1-v20131116-0025-B52 (org.jboss.tools.aerogear.hybrid.ios.core 1.0.100.CR1-v20131116-0025-B52)
To: bundle org.eclipse.debug.core [3.7.0,3.9.0)
{code}
was:
If org.jboss.tools.aerogear.hybrid.ios.core could be changed to depend on org.eclipse.debug.core [3.7.0,3.10.0) then it could be installed into Luna M3.
1. fire up Eclipse Standard Luna M3 package (eclipse-standard-luna-M3-linux-gtk-x86_64.tar.gz). Help > Install new > ...
* http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... (JBT 4.1.1.CR1 TP site)
* http://download.jboss.org/jbosstools/updates/nightly/core/4.1.kepler/ )JBT 4.1.1.CR1 Core update site)
uncheck "group by category" then select all features, and you'll get this:
!install-all-of-JBT-into-LunaM3-except-aerogear.hybrid.png!
!install-all-of-JBT-into-LunaM3-except-aerogear.hybrid-error-details.png!
{code}
Cannot complete the install because of a conflicting dependency.
Software being installed: JBoss Hybrid Mobile Application Development Tools (Experimental) 1.0.100.CR1-v20131116-0025-B52 (org.jboss.tools.aerogear.hybrid.feature.feature.group 1.0.100.CR1-v20131116-0025-B52)
Software currently installed: Eclipse Standard/SDK 2.1.0.20131103-0830 (epp.package.standard 2.1.0.20131103-0830)
Only one of the following can be installed at once:
Debug Core 3.9.0.v20131003-1341 (org.eclipse.debug.core 3.9.0.v20131003-1341)
Debug Core 3.9.0.v20130819-1716 (org.eclipse.debug.core 3.9.0.v20130819-1716)
Debug Core 3.9.0.v20130731-1644 (org.eclipse.debug.core 3.9.0.v20130731-1644)
Debug Core 3.8.0.v20130514-0954 (org.eclipse.debug.core 3.8.0.v20130514-0954)
Cannot satisfy dependency:
From: Eclipse Standard/SDK 2.1.0.20131103-0830 (epp.package.standard 2.1.0.20131103-0830)
To: org.eclipse.epp.package.standard.feature.feature.group [2.1.0.20131103-0830]
Cannot satisfy dependency:
From: Eclipse Standard/SDK Feature 2.1.0.20131103-0830 (org.eclipse.epp.package.standard.feature.feature.group 2.1.0.20131103-0830)
To: org.eclipse.platform.feature.group [4.4.0.v20131030-2000]
Cannot satisfy dependency:
From: Eclipse Platform 4.4.0.v20131030-2000 (org.eclipse.platform.feature.group 4.4.0.v20131030-2000)
To: org.eclipse.debug.core [3.9.0.v20131003-1341]
Cannot satisfy dependency:
From: JBoss Hybrid Mobile Application Development Tools (Experimental) 1.0.100.CR1-v20131116-0025-B52 (org.jboss.tools.aerogear.hybrid.feature.feature.group 1.0.100.CR1-v20131116-0025-B52)
To: org.jboss.tools.aerogear.hybrid.ios.core [1.0.100.CR1-v20131116-0025-B52]
Cannot satisfy dependency:
From: JBoss Hybrid Mobile App. Dev. iOS Core 1.0.100.CR1-v20131116-0025-B52 (org.jboss.tools.aerogear.hybrid.ios.core 1.0.100.CR1-v20131116-0025-B52)
To: bundle org.eclipse.debug.core [3.7.0,3.9.0)
{code}
> Aerogear.hybrid requires org.eclipse.debug.core [3.7.0,3.9.0) but Luna includes 3.9.0
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-16081
> URL: https://issues.jboss.org/browse/JBIDE-16081
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.CR1
> Reporter: Nick Boldt
> Labels: respin-a
> Fix For: 4.1.1.CR1, 4.2.0.Alpha1
>
> Attachments: install-all-of-JBT-into-LunaM3-except-aerogear.hybrid-error-details.png, install-all-of-JBT-into-LunaM3-except-aerogear.hybrid.png
>
>
> If org.jboss.tools.aerogear.hybrid.ios.core could be changed to depend on org.eclipse.debug.core [3.7.0,3.10.0) then it could be installed into Luna M3.
> 1. fire up Eclipse Standard Luna M3 package (eclipse-standard-luna-M3-linux-gtk-x86_64.tar.gz). Help > Install new > ...
> * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... (JBT 4.1.1.CR1 TP site)
> * http://download.jboss.org/jbosstools/updates/nightly/core/4.1.kepler/ (JBT 4.1.1.CR1 Core update site)
> uncheck "group by category" then select all features, and you'll get this:
> !install-all-of-JBT-into-LunaM3-except-aerogear.hybrid.png!
> !install-all-of-JBT-into-LunaM3-except-aerogear.hybrid-error-details.png!
> {code}
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss Hybrid Mobile Application Development Tools (Experimental) 1.0.100.CR1-v20131116-0025-B52 (org.jboss.tools.aerogear.hybrid.feature.feature.group 1.0.100.CR1-v20131116-0025-B52)
> Software currently installed: Eclipse Standard/SDK 2.1.0.20131103-0830 (epp.package.standard 2.1.0.20131103-0830)
> Only one of the following can be installed at once:
> Debug Core 3.9.0.v20131003-1341 (org.eclipse.debug.core 3.9.0.v20131003-1341)
> Debug Core 3.9.0.v20130819-1716 (org.eclipse.debug.core 3.9.0.v20130819-1716)
> Debug Core 3.9.0.v20130731-1644 (org.eclipse.debug.core 3.9.0.v20130731-1644)
> Debug Core 3.8.0.v20130514-0954 (org.eclipse.debug.core 3.8.0.v20130514-0954)
> Cannot satisfy dependency:
> From: Eclipse Standard/SDK 2.1.0.20131103-0830 (epp.package.standard 2.1.0.20131103-0830)
> To: org.eclipse.epp.package.standard.feature.feature.group [2.1.0.20131103-0830]
> Cannot satisfy dependency:
> From: Eclipse Standard/SDK Feature 2.1.0.20131103-0830 (org.eclipse.epp.package.standard.feature.feature.group 2.1.0.20131103-0830)
> To: org.eclipse.platform.feature.group [4.4.0.v20131030-2000]
> Cannot satisfy dependency:
> From: Eclipse Platform 4.4.0.v20131030-2000 (org.eclipse.platform.feature.group 4.4.0.v20131030-2000)
> To: org.eclipse.debug.core [3.9.0.v20131003-1341]
> Cannot satisfy dependency:
> From: JBoss Hybrid Mobile Application Development Tools (Experimental) 1.0.100.CR1-v20131116-0025-B52 (org.jboss.tools.aerogear.hybrid.feature.feature.group 1.0.100.CR1-v20131116-0025-B52)
> To: org.jboss.tools.aerogear.hybrid.ios.core [1.0.100.CR1-v20131116-0025-B52]
> Cannot satisfy dependency:
> From: JBoss Hybrid Mobile App. Dev. iOS Core 1.0.100.CR1-v20131116-0025-B52 (org.jboss.tools.aerogear.hybrid.ios.core 1.0.100.CR1-v20131116-0025-B52)
> To: bundle org.eclipse.debug.core [3.7.0,3.9.0)
> {code}
--
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, 5 months
[JBoss JIRA] (JBIDE-16107) Improve portlet component
by Snjezana Peco (JIRA)
Snjezana Peco created JBIDE-16107:
-------------------------------------
Summary: Improve portlet component
Key: JBIDE-16107
URL: https://issues.jboss.org/browse/JBIDE-16107
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: portal-gatein
Affects Versions: 4.1.1.CR1
Reporter: Snjezana Peco
Assignee: Snjezana Peco
Currently, the portlet component supports (or it should support) the following runtimes:
- JBoss Portal 2.7
- EPP 4.3/5.0/5.1/5.2
- GateIn 3.x
- JPP 6.x
There are three facets:
- Java Portlet
- JSF Portlet
- Seam Portlet
The required libraries are the following:
Java Portlet
- requires portlet-api that is, currently, correctly recognized for some of the above mentioned runtimes.
However, there is no rule how this library would be recognized, which means it could be broken in some new runtime.
JSF Portlet
- requires portletbridge and, optionaly, richfaces libraries
Those libraries can be added from the server runtimes or a user can use his own distribution that can be added to the JSF Portlet wizard page.
If a user creates a Seam portlet and selects his richfaces distribution, the richfaces libraries added with the seam facet will be replaced with the user's library because we can't have two richfaces versions in the application.
If a user doesn't select his richfaces distribution, the richfaces libraries from Seam will be used.
Currently, there is no rule for adding those libraries. Different server runtimes contain the libraries in different locations. Portletbridge and richfaces distributions also have different structure.
Seam Portlet
The Seam portlet uses the standard seam facet and configures web.xml
I have tried to deploy and run the seam portlet on JPP 6.1 using the Seam 2.3.2 version from WFK.
It can be deployed and run. The home page is opened, but I am not sure if all the features work correctly.
Seam 2.3.2 works properly on EAP 6.1, AS 7.1.1, AS 7.2.0.Final
Seam 2.3.1 (the latest community version) requires adding the guava module to the jboss-deployment-structure.xml
If a user selects the JBoss Maven Integration facet, the portlet component will create a maven project. It is possible to add portletbridge 2.0.0 as a maven artifact.
We would probably have to improve this feature.
We would have to define the following:
- what server runtimes we want to support in the future (AS 7+ runtimes GateIn 3.5/3.6, JPP
- what kinds of portlets we would support(Java portlet, JSF portlet, JSF Richfaces... not sure for Seam)
- how the required libraries (portletbridge, richfaces...) would be added
Is there a rule how they are placed to the server?
- will we support only a mavenized portlet (all GateIn 3.6, JPP 6.1 quickstarts are maven projects)
If we decide to support only mavenized portlets, adding libraries would be much simpler. A user would only need to choose versions, i.e., to define different Maven libraries containers.
--
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, 5 months
[JBoss JIRA] (JBIDE-16105) openshift-java-client: offer access to timeout
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16105?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16105:
-------------------------------------
Description:
express.conf now offers a setting for timeouts:
{code}
# The default timeout for network operations
#timeout=<integer>
{code}
we currently offer direct access via identical key. Since *timeout* is a very common name we should most likely offer also prefixed access (ex. openshift.timeout).
This should replace or be aliased by the system property we already use:
was:
express.conf now offers a setting for timeouts:
{code}
# The default timeout for network operations
#timeout=<integer>
{code}
we currently offer direct access via identical key. Since *timeout* is a very common name we should most likely offer also prefixed access (ex. openshift.timeout).
> openshift-java-client: offer access to timeout
> ----------------------------------------------
>
> Key: JBIDE-16105
> URL: https://issues.jboss.org/browse/JBIDE-16105
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.1.CR1
> Reporter: Andre Dietisheim
> Fix For: 4.2.x
>
>
> express.conf now offers a setting for timeouts:
> {code}
> # The default timeout for network operations
> #timeout=<integer>
> {code}
> we currently offer direct access via identical key. Since *timeout* is a very common name we should most likely offer also prefixed access (ex. openshift.timeout).
> This should replace or be aliased by the system property we already use:
--
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, 5 months
[JBoss JIRA] (JBIDE-16106) Bump maven-war-plugin version to 2.4 in openshift profile
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16106?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-16106:
--------------------------------
Description: We should update maven-war-plugin version to 2.4 for when the openshift profile is added to a pom.xml, whether the project has been added to openshift or while using the openshift profile template in the pom editor (go to <profiles> and ctrl+space) (was: We should update JBIDE-10354 When the openshift profile is added to a pom.xml, whether the project has been added to openshift or while using the openshift profile template in the pom editor (go to <profiles> and ctrl+space))
> Bump maven-war-plugin version to 2.4 in openshift profile
> ---------------------------------------------------------
>
> Key: JBIDE-16106
> URL: https://issues.jboss.org/browse/JBIDE-16106
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Reporter: Fred Bricon
> Priority: Trivial
> Fix For: 4.2.0.Alpha1
>
>
> We should update maven-war-plugin version to 2.4 for when the openshift profile is added to a pom.xml, whether the project has been added to openshift or while using the openshift profile template in the pom editor (go to <profiles> and ctrl+space)
--
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, 5 months
[JBoss JIRA] (JBIDE-16106) Bump maven-war-plugin version to 2.4 in openshift profile
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16106?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-16106:
--------------------------------
Description: We should update JBIDE-10354 When the openshift profile is added to a pom.xml, whether the project has been added to openshift or while using the openshift profile template in the pom editor (go to <profiles> and ctrl+space)
> Bump maven-war-plugin version to 2.4 in openshift profile
> ---------------------------------------------------------
>
> Key: JBIDE-16106
> URL: https://issues.jboss.org/browse/JBIDE-16106
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Reporter: Fred Bricon
> Priority: Trivial
> Fix For: 4.2.0.Alpha1
>
>
> We should update JBIDE-10354 When the openshift profile is added to a pom.xml, whether the project has been added to openshift or while using the openshift profile template in the pom editor (go to <profiles> and ctrl+space)
--
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, 5 months