[JBoss JIRA] (JBIDE-19110) Add Mockito to Target platform 4.50.0
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19110?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19110:
------------------------------------------
JBIDE-18053 (powermock) would be a nice add-on but I grok the imcompatibilities make this impossible for now.
IMHO that Mockito as-is from Locus is what we should be thriving for right now. I dont see any need for specific customizations right now and I guess that we should restrain from doing such. We could restart the discussions if it turns out we cannot get along without those.
> Add Mockito to Target platform 4.50.0
> -------------------------------------
>
> Key: JBIDE-19110
> URL: https://issues.jboss.org/browse/JBIDE-19110
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform
> Reporter: Matej Gagyi
> Priority: Optional
> Fix For: 4.3.0.Final
>
>
> *Reason:* Needed to simplify testing of jbosstools-openshift
> *Project page/sources:* https://github.com/mockito/mockito
> *Version:* 1.9.5
> *License and owner:* MIT
> *Original p2 repo:* http://download.eclipse.org/tools/orbit/downloads/drops/R20140525021250/r...
> *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/orbit/S20141129...
> *Include Sources:* Yes
> *Affected projects:*
> *Include in JBDS:* No
> *Type of dependency:* testing
> *List of bundles added/removed:*
> {code}
> diff --git a/jbosstools/multiple/jbosstools-multiple.target b/jbosstools/multiple/jbosstools-multiple.ta
> index c17fb92..51f6076 100644
> --- a/jbosstools/multiple/jbosstools-multiple.target
> +++ b/jbosstools/multiple/jbosstools-multiple.target
> @@ -10,8 +10,6 @@
> <!-- JBIDE-12815 JBoss Tools Locus bundles: not quite ready to be included -->
> <!-- <location includeAllPlatforms="false" includeMode="slicer" type="InstallableUnit" includeSourc
> <repository location="http://download.jboss.org/jbosstools/updates/integration/kepler/core/locus/
> - <!-- JBIDE-12971 Mockito
> - <unit id="org.jboss.tools.locus.mockito" version="1.9.5.Final_patched_TEIIDDES-1681-v20130507-202
> <!-- JBIDE-12972 Fest Assert
> <unit id="org.jboss.tools.locus.easytesting.fest-assert" version="1.4.0.Final-v20130507-2028-B7"/
> <!-- </location> -->
> @@ -86,6 +84,10 @@
> <unit id="org.apache.jasper.glassfish" version="2.2.2.v201205150955"/>
> <!-- <unit id="ch.qos.logback.slf4j" version="1.0.7.v20121108-1250"/> -->
> <unit id="org.slf4j.api" version="1.7.2.v20121108-1250"/>
> +
> + <!-- Testing -->
> + <unit id="org.mockito" version="1.9.5.v201311280930"/>
> + <unit id="org.objenesis" version="1.0.0.v201105211943"/>
> </location>
>
> <!-- TODO: make sure these versions match up across JBT/JBDS/Central target platforms (JBIDE-17429)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19096) Connection wizard: Allow v2 and v3 Connections
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19096?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19096:
---------------------------------------------
"but I wouldn't allow that to hold up completion of this feature." - i'm not sure what "this feature" is if its not to handle different types of logins ?
if OSv3 still just support username/password then I agree we are fine and can move forward on that just fine, but dont see what is missing ?
> Connection wizard: Allow v2 and v3 Connections
> ----------------------------------------------
>
> Key: JBIDE-19096
> URL: https://issues.jboss.org/browse/JBIDE-19096
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Alpha1
> Reporter: Andre Dietisheim
> Labels: connection_wizard
> Fix For: 4.3.0.Alpha1
>
> Attachments: fullauthoptions.bmml, fullauthoptions.png, screenshot-openshift-signin.png
>
>
> !screenshot-openshift-signin.png!
> In order to allow us to present v2 and v3 connections we have to change the connection wizard:
> When creating a new connection, we only know whether a server is a v2 or v3 OpenShift host once, we have the url for it. The required settings that the user then has to provide then are different:
> * v2 connections currently use username/password (and will most likely also allow x509, kerberos)
> * v3 connections will most likely require OAuth settings.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19045) Update Tern.java (TP) and AngularJS (Central) IDE v.0.7
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19045?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen edited comment on JBIDE-19045 at 2/2/15 4:57 AM:
---------------------------------------------------------------------
Remind me again why the TP needs to have both version included ? When is there a build or user that needs to have both the 0.6 and 0.7 version ?
If this is to be able to run tests against old TP then I would think this is indicating that Tern would be better moved to updatesite inclusion similar to what is done for master.
Then the new tern comes from updatesite and tern is not included in updated TP. And then 0.6 is actually only included when testing against old install which is fine actually what is expected imo.
Since there actually here is an api "breakage" so might as well make it explicit.
was (Author: maxandersen):
Remind me again why the TP needs to have both version included ? When is there a build that needs the 0.6 version ?
> Update Tern.java (TP) and AngularJS (Central) IDE v.0.7
> -------------------------------------------------------
>
> Key: JBIDE-19045
> URL: https://issues.jboss.org/browse/JBIDE-19045
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: central, jsp/jsf/xml/html source editing, target-platform
> Reporter: Alexey Kazakov
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 4.2.3.Beta1
>
>
> We are going to update Tern to v0.7.0 for 4.2.x.
> Master will be updated to the latest 0.8.0 (see the corresponding issue JBIDE-19002)
> p2diff output:
> {code}
> ./jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4...
> < tern.eclipse.ide.tools.core [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.ui [0.7.0.201412012159]
> < tern.eclipse.ide.tools.ui [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.win32.win32.x86_64 [0.7.0.201412012159]
> < tern-jsdt-feature.feature.jar [0.7.0.201412012159]
> < tern.server.nodejs [0.7.0.201412012159]
> < tern-server-nodejs-feature.feature.jar [0.7.0.201412012159]
> < tern.core [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86 [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.win32.win32.x86 [0.7.0.201412012159]
> < tern.eclipse.ide.core [0.7.0.201412012159]
> < tern-server-nodejs-feature.feature.group [0.7.0.201412012159]
> < tern-feature.feature.group [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.core [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.feature.jar [0.7.0.201412012159]
> < tern.eclipse.ide.ui [0.7.0.201412012159]
> < tern.eclipse.ide.tools.feature.feature.jar [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.macosx.cocoa.x86_64 [0.7.0.201412012159]
> < tern-jsdt-feature.feature.group [0.7.0.201412012159]
> < tern-feature.feature.jar [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64 [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.feature.group [0.7.0.201412012159]
> < tern.eclipse.ide.jsdt [0.7.0.201412012159]
> < tern.eclipse.ide.tools.feature.feature.group [0.7.0.201412012159]
> < tern.eclipse [0.7.0.201412012159]
> > tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64 [0.6.0.201409231610]
> > tern.eclipse.ide.core [0.6.0.201409231610]
> > tern-feature.feature.jar [0.6.0.201409231610]
> > tern.eclipse.ide.tools.feature.feature.group [0.6.0.201409231610]
> > tern.server.nodejs [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.win32.win32.x86 [0.6.0.201409231610]
> > tern-jsdt-feature.feature.jar [0.6.0.201409231610]
> > tern-feature.feature.group [0.6.0.201409231610]
> > tern.eclipse.ide.tools.ui [0.6.0.201409231610]
> > tern-jsdt-feature.feature.group [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.ui [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.win32.win32.x86_64 [0.6.0.201409231610]
> > tern-server-nodejs-feature.feature.jar [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.feature.group [0.6.0.201409231610]
> > tern.eclipse [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.core [0.6.0.201409231610]
> > tern.eclipse.ide.ui [0.6.0.201409231610]
> > tern.core [0.6.0.201409231610]
> > tern-server-nodejs-feature.feature.group [0.6.0.201409231610]
> > tern.eclipse.ide.tools.core [0.6.0.201409231610]
> > tern.eclipse.ide.jsdt [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86 [0.6.0.201409231610]
> > tern.eclipse.ide.tools.feature.feature.jar [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.macosx.cocoa.x86_64 [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.feature.jar [0.6.0.201409231610]
> === Summary ===
> ./jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo contains 25 unique IUs
> http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... contains 25 unique IUs
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19045) Update Tern.java (TP) and AngularJS (Central) IDE v.0.7
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19045?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19045:
---------------------------------------------
Remind me again why the TP needs to have both version included ? When is there a build that needs the 0.6 version ?
> Update Tern.java (TP) and AngularJS (Central) IDE v.0.7
> -------------------------------------------------------
>
> Key: JBIDE-19045
> URL: https://issues.jboss.org/browse/JBIDE-19045
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: central, jsp/jsf/xml/html source editing, target-platform
> Reporter: Alexey Kazakov
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 4.2.3.Beta1
>
>
> We are going to update Tern to v0.7.0 for 4.2.x.
> Master will be updated to the latest 0.8.0 (see the corresponding issue JBIDE-19002)
> p2diff output:
> {code}
> ./jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4...
> < tern.eclipse.ide.tools.core [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.ui [0.7.0.201412012159]
> < tern.eclipse.ide.tools.ui [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.win32.win32.x86_64 [0.7.0.201412012159]
> < tern-jsdt-feature.feature.jar [0.7.0.201412012159]
> < tern.server.nodejs [0.7.0.201412012159]
> < tern-server-nodejs-feature.feature.jar [0.7.0.201412012159]
> < tern.core [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86 [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.win32.win32.x86 [0.7.0.201412012159]
> < tern.eclipse.ide.core [0.7.0.201412012159]
> < tern-server-nodejs-feature.feature.group [0.7.0.201412012159]
> < tern-feature.feature.group [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.core [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.feature.jar [0.7.0.201412012159]
> < tern.eclipse.ide.ui [0.7.0.201412012159]
> < tern.eclipse.ide.tools.feature.feature.jar [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.macosx.cocoa.x86_64 [0.7.0.201412012159]
> < tern-jsdt-feature.feature.group [0.7.0.201412012159]
> < tern-feature.feature.jar [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64 [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.feature.group [0.7.0.201412012159]
> < tern.eclipse.ide.jsdt [0.7.0.201412012159]
> < tern.eclipse.ide.tools.feature.feature.group [0.7.0.201412012159]
> < tern.eclipse [0.7.0.201412012159]
> > tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64 [0.6.0.201409231610]
> > tern.eclipse.ide.core [0.6.0.201409231610]
> > tern-feature.feature.jar [0.6.0.201409231610]
> > tern.eclipse.ide.tools.feature.feature.group [0.6.0.201409231610]
> > tern.server.nodejs [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.win32.win32.x86 [0.6.0.201409231610]
> > tern-jsdt-feature.feature.jar [0.6.0.201409231610]
> > tern-feature.feature.group [0.6.0.201409231610]
> > tern.eclipse.ide.tools.ui [0.6.0.201409231610]
> > tern-jsdt-feature.feature.group [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.ui [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.win32.win32.x86_64 [0.6.0.201409231610]
> > tern-server-nodejs-feature.feature.jar [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.feature.group [0.6.0.201409231610]
> > tern.eclipse [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.core [0.6.0.201409231610]
> > tern.eclipse.ide.ui [0.6.0.201409231610]
> > tern.core [0.6.0.201409231610]
> > tern-server-nodejs-feature.feature.group [0.6.0.201409231610]
> > tern.eclipse.ide.tools.core [0.6.0.201409231610]
> > tern.eclipse.ide.jsdt [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86 [0.6.0.201409231610]
> > tern.eclipse.ide.tools.feature.feature.jar [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.macosx.cocoa.x86_64 [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.feature.jar [0.6.0.201409231610]
> === Summary ===
> ./jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo contains 25 unique IUs
> http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... contains 25 unique IUs
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-12282) Local AS7/EAP6 fails to stop when bound to IPv6 address or anything but localhost really
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12282?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-12282.
---------------------------------
Assignee: Rob Stryker
Resolution: Done
pushed to maintenance and master. Please re-open for ANY issues regarding 'stop'. For 'start' issues using mgmt, also re-open this issue. For start issues using web port poller, please open a new issue.
> Local AS7/EAP6 fails to stop when bound to IPv6 address or anything but localhost really
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-12282
> URL: https://issues.jboss.org/browse/JBIDE-12282
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 3.3.0.Final
> Environment: JBDS 5.0.0.GA
> Fedora 17 / OS X 10.7 Lion
> JBoss EAP 6.0.0.GA
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha1
>
>
> When you set up your server to be bound to IPv6 (but you don't bind the management port to anything), the server fails to stop. Second attempt will force the server to stop.
> This is the error in the log:
> {code}
> !ENTRY org.eclipse.wst.server.core 4 0 2012-07-02 16:49:05.284
> !MESSAGE Server jboss-eap-6.0.0.GA failed to stop.
> {code}
> This happens most probably because in such scenario, the management port is bound to IPv4 localhost (127.0.0.1).
> Indeed I just verified that this is not related to IPv6 specifically but any host name other than localhost - if you don't check "Expose your management port" (and don't set -Dmanagement manually) and the hostname is something else than localhost, then this issue will arise. Note that with remote servers you don't need to bind the management port to anything for server stop to work. So we either need to set -Dmanagement always or make sure it is not needed.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-12282) Local AS7/EAP6 fails to stop when bound to IPv6 address or anything but localhost really
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12282?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-12282:
--------------------------------
Fix Version/s: 4.2.3.Beta1
4.3.0.Alpha1
(was: LATER)
> Local AS7/EAP6 fails to stop when bound to IPv6 address or anything but localhost really
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-12282
> URL: https://issues.jboss.org/browse/JBIDE-12282
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 3.3.0.Final
> Environment: JBDS 5.0.0.GA
> Fedora 17 / OS X 10.7 Lion
> JBoss EAP 6.0.0.GA
> Reporter: Martin Malina
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha1
>
>
> When you set up your server to be bound to IPv6 (but you don't bind the management port to anything), the server fails to stop. Second attempt will force the server to stop.
> This is the error in the log:
> {code}
> !ENTRY org.eclipse.wst.server.core 4 0 2012-07-02 16:49:05.284
> !MESSAGE Server jboss-eap-6.0.0.GA failed to stop.
> {code}
> This happens most probably because in such scenario, the management port is bound to IPv4 localhost (127.0.0.1).
> Indeed I just verified that this is not related to IPv6 specifically but any host name other than localhost - if you don't check "Expose your management port" (and don't set -Dmanagement manually) and the hostname is something else than localhost, then this issue will arise. Note that with remote servers you don't need to bind the management port to anything for server stop to work. So we either need to set -Dmanagement always or make sure it is not needed.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months