[JBoss JIRA] (JBIDE-14354) I dont get credentials reported when I create a jenkins initially (when creating an app) (WATCHER ISSUE)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14354?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-14354:
-------------------------------------
Issue Type: Bug (was: Task)
> I dont get credentials reported when I create a jenkins initially (when creating an app) (WATCHER ISSUE)
> --------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-14354
> URL: https://issues.jboss.org/browse/JBIDE-14354
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.1.x
>
> Attachments: correct-creation-log.png, no-information-from-openshift.png, null-creation-log.png
>
>
> # EXEC: launch the OpenShift application wizard
> # EXEC: in the embedded cartridges, check jenkins-client
> # ASSERT: you get a dialog that tells you that you have to create a jenkins application
> # EXEC: hit "Apply"
> # ASSERT: you get prompted to provide a name for the jenkins application
> # EXEC: provide some name
> # ASSERT: wait until you get the creation log presented in a dialog
> Result:
> The dialogs shows *null*
> !null-creation-log.png!
> Expected:
> The creation log dialog prints the IP, username and password for your jenkins instance
> !correct-creation-log.png!
> Workaround:
> * embed jenkins-client afterwards by picking *Edit Embeddable Cartridges* in the context menu of your application in the OpenShift Explorer
> =OR=
> * look the credentials up in the environment variables by picking *Environament Variables* in the context menu of your application in OpenShift Explorer
--
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
11 years, 1 month
[JBoss JIRA] (JBTIS-70) JBTIS Kepler component content
by Paul Leacu (JIRA)
Paul Leacu created JBTIS-70:
-------------------------------
Summary: JBTIS Kepler component content
Key: JBTIS-70
URL: https://issues.jboss.org/browse/JBTIS-70
Project: JBoss Tools Integration Stack
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: BPEL, BPMN2, drools/ jBPM5, ESB, Fuse IDE, modeshape, savara, switchyard, teiid
Affects Versions: 4.1.0
Reporter: Paul Leacu
Assignee: Paul Leacu
Fix For: 4.1.0
--
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
11 years, 1 month
[JBoss JIRA] (JBIDE-14122) Add VJET to Central
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14122?page=com.atlassian.jira.plugi... ]
Victor Rubezhny edited comment on JBIDE-14122 at 4/30/13 4:25 PM:
------------------------------------------------------------------
The patches that remove the references to JUnit4 are provided for [Bug 406254 - Start using org.junit.* packages instead of the deprecated org.junit4.* ones|https://bugs.eclipse.org/bugs/show_bug.cgi?id=406254]
was (Author: vrubezhny):
The patched that removes the references to JUnit4 are provided for [Bug 406254 - Start using org.junit.* packages instead of the deprecated org.junit4.* ones|https://bugs.eclipse.org/bugs/show_bug.cgi?id=406254]
> Add VJET to Central
> -------------------
>
> Key: JBIDE-14122
> URL: https://issues.jboss.org/browse/JBIDE-14122
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central, target-platform
> Affects Versions: 4.1.0.Beta1
> Reporter: Victor Rubezhny
> Assignee: Victor Rubezhny
> Fix For: 4.1.0.Beta1
>
> Attachments: installing-vjet-from-jbt-mirrors.png, installing-vjet-from-jbt-mirrors2.png, installing-vjet-from-jbt-mirrors3-problem-with-junit4.png, installing-vjet-from-jbt-mirrors4-success.png, installing-vjet-from-jbt-mirrors5-problem-with-junit4-SOLVED.png, JBIDE14122-central-with-vjet.png
>
>
> We should provide an ability to install VJET v.0.10 through Central
> The latest stable VJET Update Site: [http://download.eclipse.org/vjet/updates-0.10] - v.0.10.0, Released
> The following dependencies (in addition to what we already have in TP) are to be satisfied in order to run VJet:
> {code:title=Orbit bundles for VJET}
> <unit id="org.apache.xml.serializer" version="2.7.1.v201005080400"/>
> <unit id="org.apache.xml.resolver" version="1.2.0.v201005080400"/>
> <unit id="org.apache.batik.css" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.css.source" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.dom" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.dom.source" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.util" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.util.source" version="1.7.0.v201011041433"/>
> <unit id="org.apache.xerces" version="2.9.0.v201101211617"/>
> <unit id="org.ccil.cowan.tagsoup" version="1.2.0.v201202211000"/>
> <unit id="org.w3c.css.sac" version="1.3.1.v200903091627"/>
> <unit id="org.w3c.css.sac.source" version="1.3.1.v200903091627"/>
> <unit id="org.w3c.dom.svg" version="1.1.0.v201011041433"/>
> <unit id="org.w3c.dom.svg.source" version="1.1.0.v201011041433"/>
> <unit id="javax.xml" version="1.3.4.v201005080400"/>
> <unit id="org.apache.commons.collections" version="3.2.0.v2013030210310"/>
> <unit id="org.apache.commons.io" version="2.0.1.v201105210651"/>
> {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
11 years, 1 month
[JBoss JIRA] (JBIDE-14122) Add VJET to Central
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14122?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-14122:
-----------------------------------------
The patched that removes the references to JUnit4 are provided for [Bug 406254 - Start using org.junit.* packages instead of the deprecated org.junit4.* ones|https://bugs.eclipse.org/bugs/show_bug.cgi?id=406254]
> Add VJET to Central
> -------------------
>
> Key: JBIDE-14122
> URL: https://issues.jboss.org/browse/JBIDE-14122
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central, target-platform
> Affects Versions: 4.1.0.Beta1
> Reporter: Victor Rubezhny
> Assignee: Victor Rubezhny
> Fix For: 4.1.0.Beta1
>
> Attachments: installing-vjet-from-jbt-mirrors.png, installing-vjet-from-jbt-mirrors2.png, installing-vjet-from-jbt-mirrors3-problem-with-junit4.png, installing-vjet-from-jbt-mirrors4-success.png, installing-vjet-from-jbt-mirrors5-problem-with-junit4-SOLVED.png, JBIDE14122-central-with-vjet.png
>
>
> We should provide an ability to install VJET v.0.10 through Central
> The latest stable VJET Update Site: [http://download.eclipse.org/vjet/updates-0.10] - v.0.10.0, Released
> The following dependencies (in addition to what we already have in TP) are to be satisfied in order to run VJet:
> {code:title=Orbit bundles for VJET}
> <unit id="org.apache.xml.serializer" version="2.7.1.v201005080400"/>
> <unit id="org.apache.xml.resolver" version="1.2.0.v201005080400"/>
> <unit id="org.apache.batik.css" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.css.source" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.dom" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.dom.source" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.util" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.util.source" version="1.7.0.v201011041433"/>
> <unit id="org.apache.xerces" version="2.9.0.v201101211617"/>
> <unit id="org.ccil.cowan.tagsoup" version="1.2.0.v201202211000"/>
> <unit id="org.w3c.css.sac" version="1.3.1.v200903091627"/>
> <unit id="org.w3c.css.sac.source" version="1.3.1.v200903091627"/>
> <unit id="org.w3c.dom.svg" version="1.1.0.v201011041433"/>
> <unit id="org.w3c.dom.svg.source" version="1.1.0.v201011041433"/>
> <unit id="javax.xml" version="1.3.4.v201005080400"/>
> <unit id="org.apache.commons.collections" version="3.2.0.v2013030210310"/>
> <unit id="org.apache.commons.io" version="2.0.1.v201105210651"/>
> {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
11 years, 1 month
[JBoss JIRA] (JBIDE-14122) Add VJET to Central
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14122?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-14122:
-----------------------------------------
Yes, it looks like a warning... I suppose that the reason of this message could be the fact that we already have Apache Batik CSS v.1.6 installed. But VJET requires Apache Batik CSS v.1.7.
Probably some JBT (or JBDS) plug-in has a restriction to use Apache Batik CSS of version not later than v.1.6, so, the installation is decided to leave it (not to remove).
At least when I've being tested the VJET installation from Central, the installed VJET was working (its perspective appeared, JS-editor could be started).
> Add VJET to Central
> -------------------
>
> Key: JBIDE-14122
> URL: https://issues.jboss.org/browse/JBIDE-14122
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central, target-platform
> Affects Versions: 4.1.0.Beta1
> Reporter: Victor Rubezhny
> Assignee: Victor Rubezhny
> Fix For: 4.1.0.Beta1
>
> Attachments: installing-vjet-from-jbt-mirrors.png, installing-vjet-from-jbt-mirrors2.png, installing-vjet-from-jbt-mirrors3-problem-with-junit4.png, installing-vjet-from-jbt-mirrors4-success.png, installing-vjet-from-jbt-mirrors5-problem-with-junit4-SOLVED.png, JBIDE14122-central-with-vjet.png
>
>
> We should provide an ability to install VJET v.0.10 through Central
> The latest stable VJET Update Site: [http://download.eclipse.org/vjet/updates-0.10] - v.0.10.0, Released
> The following dependencies (in addition to what we already have in TP) are to be satisfied in order to run VJet:
> {code:title=Orbit bundles for VJET}
> <unit id="org.apache.xml.serializer" version="2.7.1.v201005080400"/>
> <unit id="org.apache.xml.resolver" version="1.2.0.v201005080400"/>
> <unit id="org.apache.batik.css" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.css.source" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.dom" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.dom.source" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.util" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.util.source" version="1.7.0.v201011041433"/>
> <unit id="org.apache.xerces" version="2.9.0.v201101211617"/>
> <unit id="org.ccil.cowan.tagsoup" version="1.2.0.v201202211000"/>
> <unit id="org.w3c.css.sac" version="1.3.1.v200903091627"/>
> <unit id="org.w3c.css.sac.source" version="1.3.1.v200903091627"/>
> <unit id="org.w3c.dom.svg" version="1.1.0.v201011041433"/>
> <unit id="org.w3c.dom.svg.source" version="1.1.0.v201011041433"/>
> <unit id="javax.xml" version="1.3.4.v201005080400"/>
> <unit id="org.apache.commons.collections" version="3.2.0.v2013030210310"/>
> <unit id="org.apache.commons.io" version="2.0.1.v201105210651"/>
> {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
11 years, 1 month
[JBoss JIRA] (JBIDE-12321) handle IApplication#getEmbeddedCartridges correctly with changes to protocol 1.2
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12321?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12321:
-------------------------------------
Summary: handle IApplication#getEmbeddedCartridges correctly with changes to protocol 1.2 (was: handle IApplication#getEmbeddedCartridges correctly with changes to protocol 1.1)
> handle IApplication#getEmbeddedCartridges correctly with changes to protocol 1.2
> --------------------------------------------------------------------------------
>
> Key: JBIDE-12321
> URL: https://issues.jboss.org/browse/JBIDE-12321
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Affects Versions: 4.0.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Beta1
>
> Attachments: app-type-listed-as-embedded.png
>
>
> In 1.1 the cartridges that you get reported when listing them on a application changed (IApplication#getEmbeddedCartridges):
> * 1.0:
> would report the embedded cartridges only
> * 1.1:
> would report the embedded cartridges and the application type (cartridge)
> !app-type-listed-as-embedded.png!
> see here: https://github.com/openshift/crankcase/pull/224
> The error that this caused was discussed here:
> https://bugzilla.redhat.com/show_bug.cgi?id=838611
> OpenShift pushed the discussed change (application-type reported as embedded cartridge) to protocol v1.1 and fixed the issue on the server-side. Our client, that currently requests protocol v1.0 has no issue since the fix. We have to make sure we support protocol 1.1 and are able to handle this correctly.
--
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
11 years, 1 month
[JBoss JIRA] (JBIDE-12320) support protocol version 1.2 in openshift-java-client
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12320?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12320:
-------------------------------------
Fix Version/s: 4.1.0.Beta1
(was: 4.1.x)
> support protocol version 1.2 in openshift-java-client
> -----------------------------------------------------
>
> Key: JBIDE-12320
> URL: https://issues.jboss.org/browse/JBIDE-12320
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.0.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: new_and_noteworthy
> Fix For: 4.1.0.Beta1
>
>
> The protocol for the OpenShift REST service has evolved over time and currently has v1.3. The rest service currently delivers 1.0, 1.1, 1.2 and 1.3.
> OpenShift Enterprise talks 1.2 and we therefore want to drop everything below it
> 2012-03-14 in #libra
> {quote}
> 07:08:20 PM) clayton: then adietish that's your answer - you're good to drop 1.1 and 1.0 support because we have no supported products in the field that use those api versions
> {quote}
--
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
11 years, 1 month