[JBoss JIRA] (JBIDE-18186) XMLMemento cannot parse a file where first node is a comment
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18186?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen closed JBIDE-18186.
---------------------------------------
this is just for internal code fix - already covered by junit IMO.
the issue to test for qe is the linked one.
> XMLMemento cannot parse a file where first node is a comment
> ------------------------------------------------------------
>
> Key: JBIDE-18186
> URL: https://issues.jboss.org/browse/JBIDE-18186
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core
> Affects Versions: 4.2.0.CR1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.2.0.CR1
>
>
> The class XMLMemento, originally taken from upstream eclipse, is unable to parse a xml input stream if the first node is not an Element. This restriction should be worked around. This is a patch needed by astools for solving /JBIDE-18130
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-16103) Port Forwarding: "Start All" is enabled even though all ports are started
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16103?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16103:
-------------------------------------
Steps to Reproduce:
# ASSERT: make sure that you have an application running on OpenShift
# EXEC: in OpenShift Explorer: select your application and pick *Port Forwarding*
# ASSERT: *Stop All* button is disabled, *Start All* button is enabled
!port-forwarding-stop-disabled.png!
# EXEC: hit *Start All*
# ASSERT: Port forwarding is successfull, all ports are started
Result:
!port-forwarding-start-enabled.png!
*Start All* button is enabled, should be disabled
!port-forwarding-start-enabled.png.png!
was:
# ASSERT: make sure that you have an application running on OpenShift
# EXEC: in OpenShift Explorer: select your application and pick *Port Forwarding*
# ASSERT: *Stop All* button is disabled, *Start All* button is enabled
!port-forwarding-stop-disabled.png!
# EXEC: hit *Start All*
# ASSERT: Port forwarding is successfull, all ports are started
Result:
!port-forwarding-start-enabled.png!
*Start All* button is enabled, should be disabled
> Port Forwarding: "Start All" is enabled even though all ports are started
> -------------------------------------------------------------------------
>
> Key: JBIDE-16103
> URL: https://issues.jboss.org/browse/JBIDE-16103
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.CR1
> Reporter: Andre Dietisheim
> Labels: port_forwarding_wizard
> Fix For: 4.2.x
>
> Attachments: port-forwarding-start-enabled.png.png, port-forwarding-stop-disabled.png
>
>
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-16517) SSL Certificate dialog: need to show to what server we're connecting
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16517?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16517:
-------------------------------------
Fix Version/s: 4.3.x
(was: 4.2.x)
> SSL Certificate dialog: need to show to what server we're connecting
> --------------------------------------------------------------------
>
> Key: JBIDE-16517
> URL: https://issues.jboss.org/browse/JBIDE-16517
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Andre Dietisheim
> Labels: connection_wizard
> Fix For: 4.3.x
>
> Attachments: certificate-dialog.png
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> The current dialog does not show explicitly to what server we're talking:
> !certificate-dialog.png!
> We should add some text like
> ...untrusted SSL certificate *presented by server <server-url>*
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18250) ESB 4.2.x build issue
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18250?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick updated JBIDE-18250:
--------------------------------------
Fix Version/s: 4.2.1.Final
(was: 4.2.0.Final)
> ESB 4.2.x build issue
> ---------------------
>
> Key: JBIDE-18250
> URL: https://issues.jboss.org/browse/JBIDE-18250
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: esb
> Affects Versions: 4.2.0.Beta3
> Reporter: Brian Fitzpatrick
> Assignee: Brian Fitzpatrick
> Fix For: 4.2.1.Final
>
>
> Looking into 4.2.x ESB build issue:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-esb-4.2.x/32/
> {code}
> [ERROR] Internal error: java.lang.RuntimeException: Failed to resolve target definition <http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-esb-4.2.x/ws/.r...>: Could not find "org.jboss.tools.locus.jcip.annotations/1.0.0.Final-v20131024-0922-B64" in the repositories of the current location -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Failed to resolve target definition <http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-esb-4.2.x/ws/.r...>
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:164)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: java.lang.RuntimeException: Failed to resolve target definition <http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-esb-4.2.x/ws/.r...>
> at org.eclipse.tycho.p2.target.TargetDefinitionResolver.resolveContent(TargetDefinitionResolver.java:84)
> at org.eclipse.tycho.p2.target.TargetDefinitionResolverService.resolveFromArguments(TargetDefinitionResolverService.java:65)
> at org.eclipse.tycho.p2.target.TargetDefinitionResolverService.getTargetDefinitionContent(TargetDefinitionResolverService.java:55)
> at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.resolveTargetDefinitions(TargetPlatformFactoryImpl.java:212)
> at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.createTargetPlatform(TargetPlatformFactoryImpl.java:146)
> at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.createTargetPlatform(TargetPlatformFactoryImpl.java:119)
> at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.createTargetPlatform(TargetPlatformFactoryImpl.java:1)
> at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.computeTargetPlatform(P2TargetPlatformResolver.java:215)
> at org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:100)
> at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:75)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:271)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
> ... 11 more
> Caused by: org.eclipse.tycho.p2.target.facade.TargetDefinitionResolutionException: Could not find "org.jboss.tools.locus.jcip.annotations/1.0.0.Final-v20131024-0922-B64" in the repositories of the current location
> at org.eclipse.tycho.p2.target.TargetDefinitionResolver.getUnitInstance(TargetDefinitionResolver.java:213)
> at org.eclipse.tycho.p2.target.TargetDefinitionResolver.resolveContentWithExceptions(TargetDefinitionResolver.java:127)
> at org.eclipse.tycho.p2.target.TargetDefinitionResolver.resolveContent(TargetDefinitionResolver.java:79)
> ... 22 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18250) ESB 4.2.x build issue
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18250?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick commented on JBIDE-18250:
-------------------------------------------
>From Paul - "There was an issue a while back with locus dependencies. It's been corrected - find the 4.2.0.Alpha1 JBTIS TP reference in your pom and replace it with 4.2.0.Alpha8."
Done.
> ESB 4.2.x build issue
> ---------------------
>
> Key: JBIDE-18250
> URL: https://issues.jboss.org/browse/JBIDE-18250
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: esb
> Affects Versions: 4.2.0.Beta3
> Reporter: Brian Fitzpatrick
>
> Looking into 4.2.x ESB build issue:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-esb-4.2.x/32/
> {code}
> [ERROR] Internal error: java.lang.RuntimeException: Failed to resolve target definition <http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-esb-4.2.x/ws/.r...>: Could not find "org.jboss.tools.locus.jcip.annotations/1.0.0.Final-v20131024-0922-B64" in the repositories of the current location -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Failed to resolve target definition <http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-esb-4.2.x/ws/.r...>
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:164)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: java.lang.RuntimeException: Failed to resolve target definition <http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-esb-4.2.x/ws/.r...>
> at org.eclipse.tycho.p2.target.TargetDefinitionResolver.resolveContent(TargetDefinitionResolver.java:84)
> at org.eclipse.tycho.p2.target.TargetDefinitionResolverService.resolveFromArguments(TargetDefinitionResolverService.java:65)
> at org.eclipse.tycho.p2.target.TargetDefinitionResolverService.getTargetDefinitionContent(TargetDefinitionResolverService.java:55)
> at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.resolveTargetDefinitions(TargetPlatformFactoryImpl.java:212)
> at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.createTargetPlatform(TargetPlatformFactoryImpl.java:146)
> at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.createTargetPlatform(TargetPlatformFactoryImpl.java:119)
> at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.createTargetPlatform(TargetPlatformFactoryImpl.java:1)
> at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.computeTargetPlatform(P2TargetPlatformResolver.java:215)
> at org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:100)
> at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:75)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:271)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
> ... 11 more
> Caused by: org.eclipse.tycho.p2.target.facade.TargetDefinitionResolutionException: Could not find "org.jboss.tools.locus.jcip.annotations/1.0.0.Final-v20131024-0922-B64" in the repositories of the current location
> at org.eclipse.tycho.p2.target.TargetDefinitionResolver.getUnitInstance(TargetDefinitionResolver.java:213)
> at org.eclipse.tycho.p2.target.TargetDefinitionResolver.resolveContentWithExceptions(TargetDefinitionResolver.java:127)
> at org.eclipse.tycho.p2.target.TargetDefinitionResolver.resolveContent(TargetDefinitionResolver.java:79)
> ... 22 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-12803) Server Adapter: Cannot publish after I renamed the maven artifact
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12803?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12803:
-------------------------------------
Description:
Using JBDS, I used
* Refactor - Rename Maven Artifact
* Refactor - Rename
to change my project name - this project had previously been deployed to Openshift and now the Full Publish fails.
was:
Using JBDS, I used
Refactor - Rename Maven Artifact
and
Refactor - Rename
to change my project name - this project had previously been deployed to Openshift and now the Full Publish fails.
The workaround is to double-click on the Openshift server adapter (Servers Tab) and reset which project it is tied to.
Workaround Description: double-click on the Openshift server adapter (Servers Tab) and reset which project it is tied to.
Workaround: Workaround Exists
> Server Adapter: Cannot publish after I renamed the maven artifact
> -----------------------------------------------------------------
>
> Key: JBIDE-12803
> URL: https://issues.jboss.org/browse/JBIDE-12803
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Burr Sutter
> Priority: Minor
> Labels: server_adapter
> Fix For: 4.2.x
>
> Attachments: 2012-10-04_1859.png
>
>
> Using JBDS, I used
> * Refactor - Rename Maven Artifact
> * Refactor - Rename
> to change my project name - this project had previously been deployed to Openshift and now the Full Publish fails.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18250) ESB 4.2.x build issue
by Brian Fitzpatrick (JIRA)
Brian Fitzpatrick created JBIDE-18250:
-----------------------------------------
Summary: ESB 4.2.x build issue
Key: JBIDE-18250
URL: https://issues.jboss.org/browse/JBIDE-18250
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 4.2.0.Beta3
Reporter: Brian Fitzpatrick
Looking into 4.2.x ESB build issue:
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-esb-4.2.x/32/
{code}
[ERROR] Internal error: java.lang.RuntimeException: Failed to resolve target definition <http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-esb-4.2.x/ws/.r...>: Could not find "org.jboss.tools.locus.jcip.annotations/1.0.0.Final-v20131024-0922-B64" in the repositories of the current location -> [Help 1]
org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Failed to resolve target definition <http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-esb-4.2.x/ws/.r...>
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:164)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: java.lang.RuntimeException: Failed to resolve target definition <http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-esb-4.2.x/ws/.r...>
at org.eclipse.tycho.p2.target.TargetDefinitionResolver.resolveContent(TargetDefinitionResolver.java:84)
at org.eclipse.tycho.p2.target.TargetDefinitionResolverService.resolveFromArguments(TargetDefinitionResolverService.java:65)
at org.eclipse.tycho.p2.target.TargetDefinitionResolverService.getTargetDefinitionContent(TargetDefinitionResolverService.java:55)
at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.resolveTargetDefinitions(TargetPlatformFactoryImpl.java:212)
at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.createTargetPlatform(TargetPlatformFactoryImpl.java:146)
at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.createTargetPlatform(TargetPlatformFactoryImpl.java:119)
at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.createTargetPlatform(TargetPlatformFactoryImpl.java:1)
at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.computeTargetPlatform(P2TargetPlatformResolver.java:215)
at org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:100)
at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:75)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:271)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
... 11 more
Caused by: org.eclipse.tycho.p2.target.facade.TargetDefinitionResolutionException: Could not find "org.jboss.tools.locus.jcip.annotations/1.0.0.Final-v20131024-0922-B64" in the repositories of the current location
at org.eclipse.tycho.p2.target.TargetDefinitionResolver.getUnitInstance(TargetDefinitionResolver.java:213)
at org.eclipse.tycho.p2.target.TargetDefinitionResolver.resolveContentWithExceptions(TargetDefinitionResolver.java:127)
at org.eclipse.tycho.p2.target.TargetDefinitionResolver.resolveContent(TargetDefinitionResolver.java:79)
... 22 more
{code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-12571) Connection wizard: Eclipse preferences: allow users to define a default server
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12571?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12571:
-------------------------------------
Parent: (was: JBIDE-12168)
Issue Type: Feature Request (was: Sub-task)
> Connection wizard: Eclipse preferences: allow users to define a default server
> ------------------------------------------------------------------------------
>
> Key: JBIDE-12571
> URL: https://issues.jboss.org/browse/JBIDE-12571
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.Final
> Reporter: Andre Dietisheim
> Labels: connection_wizard, new_and_noteworthy
> Fix For: 4.3.x
>
> Attachments: 2012-09-10 13.10.bmml, 2012-09-10 13.10.bmml, 2012-09-10 13.10.png
>
>
> Add UI to the preferences that allows users to provide a default OpenShift server to connect to. In terms of widget we need a text-field for the server url and a checkbox that allows people to refer to the default server that is defined in the openshift configfurations (~/.openshift/express.conf and /etc/openshift/express.conf). If the checkbox is checked, the text-field is disabled, prefilled with the server that is present in the (rhc cli-tooling) openshift configuration. Once unchecked the user can enter a default server and override the openshift server that is configured in the configuration.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months