[JBoss JIRA] (JBIDE-26038) [Red Hat Central] Update to latest Subclipse
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26038?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-26038:
------------------------------------
[~dstephan] Is it safe to assume this issue is not urgent for 11.x and thus can be fixed for 12.0.0, rather than requiring a backport for the 11.x users?
> [Red Hat Central] Update to latest Subclipse
> --------------------------------------------
>
> Key: JBIDE-26038
> URL: https://issues.jboss.org/browse/JBIDE-26038
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central-update
> Affects Versions: 4.5.3.Final
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Fix For: 4.6.0.AM3
>
>
> An error has been reported on the sme-jbds mail ling list:
> {noformat}
> Hi,
> I have a customer who is having issues with Subversion in JBDS 11.3.
> They have installed Subclipse + SVNKit from RedHat Central and then create a new project, then add the project to SVN. They then update a dummy text file in the project.
> They then try to synchronize the project and after this all of the team options are greyed out.
> The only exception in the log is:
> !ENTRY org.tigris.subversion.subclipse.core 4 -6 2018-05-10 15:41:57.217
> !MESSAGE The SVN synchronization information for 'jClaretyBatchClientProject' has become corrupt or does not exist.
> !ENTRY org.tigris.subversion.subclipse.ui 4 -6 2018-05-10 15:41:57.217
> !MESSAGE Property Exception
> !STACK 0
> java.lang.NullPointerException
> at org.tigris.subversion.subclipse.ui.properties.SVNPropertyPage.getStatus(SVNPropertyPage.java:290)
> at org.tigris.subversion.subclipse.ui.properties.SVNPropertyPage.createContents(SVNPropertyPage.java:81)
> at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:241)
> at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1426)
> at org.eclipse.jface.preference.PreferenceDialog$8.run(PreferenceDialog.java:1193)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil.lambda$0(JFaceUtil.java:44)
> ...
> If they download the latest Subclipse version plus JavaHL and use this instead of SVNKit it works.
> They wanted to have JavaHL as an option in RedHat Central but I advised this wasn't going to happen as per [1].
> They raised the issue with Subclipse with this response:
> "There are no options in the product that are predicated on using one adapter or the other. There can be bugs or slight differences in behavior in one API implementation or the other, but both provide all of the API's we use. JavaHL is already the default implementation provided that it has been installed and is available.
> So obviously you had some kind of problem here, but your diagnosis of the causes was not correct. I do generally recommend you use JavaHL if possible, since that is the API implementation that comes from Subversion itself so is going to be most compatible with the SVN command line and other clients you might be using. That said, SVNKit generally offers very good compatibility as well.
> I am closing this just because I do not see that there is anything here that can be acted upon."
> Any ideas on why SVNKit might not be working here?
> Cheers
> Dave
> [1] https://issues.jboss.org/browse/JBIDE-14795
> SF case ref: https://gss--c.na7.visual.force.com/apex/Case_View?id=500A000000aqrrSIAQ
> Portal Case Ref: https://access.redhat.com/support/cases/#/case/02094880
> {noformat}
> I tried and was able to reproduce.
> I then tried but installed from https://dl.bintray.com/subclipse/releases/subclipse/4.2.x instead of Red Hat Central and the error is gone
> So I compared both update sites (https://devstudio.redhat.com/11/stable/updates/ and https://dl.bintray.com/subclipse/releases/subclipse/4.2.x) and noticed that org.tmatesoft.svnkit is 1.8.15 in DevStudio and 1.8.12 in Subclipse
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-26038) [Red Hat Central] Update to latest Subclipse
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26038?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-26038:
-------------------------------
Workaround Description: Install latest Subclipse from https://dl.bintray.com/subclipse/releases/subclipse/4.2.x
Workaround: Workaround Exists
> [Red Hat Central] Update to latest Subclipse
> --------------------------------------------
>
> Key: JBIDE-26038
> URL: https://issues.jboss.org/browse/JBIDE-26038
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central-update
> Affects Versions: 4.5.3.Final
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Fix For: 4.6.0.AM3
>
>
> An error has been reported on the sme-jbds mail ling list:
> {noformat}
> Hi,
> I have a customer who is having issues with Subversion in JBDS 11.3.
> They have installed Subclipse + SVNKit from RedHat Central and then create a new project, then add the project to SVN. They then update a dummy text file in the project.
> They then try to synchronize the project and after this all of the team options are greyed out.
> The only exception in the log is:
> !ENTRY org.tigris.subversion.subclipse.core 4 -6 2018-05-10 15:41:57.217
> !MESSAGE The SVN synchronization information for 'jClaretyBatchClientProject' has become corrupt or does not exist.
> !ENTRY org.tigris.subversion.subclipse.ui 4 -6 2018-05-10 15:41:57.217
> !MESSAGE Property Exception
> !STACK 0
> java.lang.NullPointerException
> at org.tigris.subversion.subclipse.ui.properties.SVNPropertyPage.getStatus(SVNPropertyPage.java:290)
> at org.tigris.subversion.subclipse.ui.properties.SVNPropertyPage.createContents(SVNPropertyPage.java:81)
> at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:241)
> at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1426)
> at org.eclipse.jface.preference.PreferenceDialog$8.run(PreferenceDialog.java:1193)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil.lambda$0(JFaceUtil.java:44)
> ...
> If they download the latest Subclipse version plus JavaHL and use this instead of SVNKit it works.
> They wanted to have JavaHL as an option in RedHat Central but I advised this wasn't going to happen as per [1].
> They raised the issue with Subclipse with this response:
> "There are no options in the product that are predicated on using one adapter or the other. There can be bugs or slight differences in behavior in one API implementation or the other, but both provide all of the API's we use. JavaHL is already the default implementation provided that it has been installed and is available.
> So obviously you had some kind of problem here, but your diagnosis of the causes was not correct. I do generally recommend you use JavaHL if possible, since that is the API implementation that comes from Subversion itself so is going to be most compatible with the SVN command line and other clients you might be using. That said, SVNKit generally offers very good compatibility as well.
> I am closing this just because I do not see that there is anything here that can be acted upon."
> Any ideas on why SVNKit might not be working here?
> Cheers
> Dave
> [1] https://issues.jboss.org/browse/JBIDE-14795
> SF case ref: https://gss--c.na7.visual.force.com/apex/Case_View?id=500A000000aqrrSIAQ
> Portal Case Ref: https://access.redhat.com/support/cases/#/case/02094880
> {noformat}
> I tried and was able to reproduce.
> I then tried but installed from https://dl.bintray.com/subclipse/releases/subclipse/4.2.x instead of Red Hat Central and the error is gone
> So I compared both update sites (https://devstudio.redhat.com/11/stable/updates/ and https://dl.bintray.com/subclipse/releases/subclipse/4.2.x) and noticed that org.tmatesoft.svnkit is 1.8.15 in DevStudio and 1.8.12 in Subclipse
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-26038) [Red Hat Central] Update to latest Subclipse
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26038?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-26038:
-------------------------------
Summary: [Red Hat Central] Update to latest Subclipse (was: Subclipse broken in Red Hat Central)
> [Red Hat Central] Update to latest Subclipse
> --------------------------------------------
>
> Key: JBIDE-26038
> URL: https://issues.jboss.org/browse/JBIDE-26038
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central-update
> Affects Versions: 4.5.3.Final
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Fix For: 4.6.0.AM3
>
>
> An error has been reported on the sme-jbds mail ling list:
> {noformat}
> Hi,
> I have a customer who is having issues with Subversion in JBDS 11.3.
> They have installed Subclipse + SVNKit from RedHat Central and then create a new project, then add the project to SVN. They then update a dummy text file in the project.
> They then try to synchronize the project and after this all of the team options are greyed out.
> The only exception in the log is:
> !ENTRY org.tigris.subversion.subclipse.core 4 -6 2018-05-10 15:41:57.217
> !MESSAGE The SVN synchronization information for 'jClaretyBatchClientProject' has become corrupt or does not exist.
> !ENTRY org.tigris.subversion.subclipse.ui 4 -6 2018-05-10 15:41:57.217
> !MESSAGE Property Exception
> !STACK 0
> java.lang.NullPointerException
> at org.tigris.subversion.subclipse.ui.properties.SVNPropertyPage.getStatus(SVNPropertyPage.java:290)
> at org.tigris.subversion.subclipse.ui.properties.SVNPropertyPage.createContents(SVNPropertyPage.java:81)
> at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:241)
> at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1426)
> at org.eclipse.jface.preference.PreferenceDialog$8.run(PreferenceDialog.java:1193)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil.lambda$0(JFaceUtil.java:44)
> ...
> If they download the latest Subclipse version plus JavaHL and use this instead of SVNKit it works.
> They wanted to have JavaHL as an option in RedHat Central but I advised this wasn't going to happen as per [1].
> They raised the issue with Subclipse with this response:
> "There are no options in the product that are predicated on using one adapter or the other. There can be bugs or slight differences in behavior in one API implementation or the other, but both provide all of the API's we use. JavaHL is already the default implementation provided that it has been installed and is available.
> So obviously you had some kind of problem here, but your diagnosis of the causes was not correct. I do generally recommend you use JavaHL if possible, since that is the API implementation that comes from Subversion itself so is going to be most compatible with the SVN command line and other clients you might be using. That said, SVNKit generally offers very good compatibility as well.
> I am closing this just because I do not see that there is anything here that can be acted upon."
> Any ideas on why SVNKit might not be working here?
> Cheers
> Dave
> [1] https://issues.jboss.org/browse/JBIDE-14795
> SF case ref: https://gss--c.na7.visual.force.com/apex/Case_View?id=500A000000aqrrSIAQ
> Portal Case Ref: https://access.redhat.com/support/cases/#/case/02094880
> {noformat}
> I tried and was able to reproduce.
> I then tried but installed from https://dl.bintray.com/subclipse/releases/subclipse/4.2.x instead of Red Hat Central and the error is gone
> So I compared both update sites (https://devstudio.redhat.com/11/stable/updates/ and https://dl.bintray.com/subclipse/releases/subclipse/4.2.x) and noticed that org.tmatesoft.svnkit is 1.8.15 in DevStudio and 1.8.12 in Subclipse
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-26040) Error for JAX-RS 2.1 @Context types
by Rich DiCroce (JIRA)
Rich DiCroce created JBIDE-26040:
------------------------------------
Summary: Error for JAX-RS 2.1 @Context types
Key: JBIDE-26040
URL: https://issues.jboss.org/browse/JBIDE-26040
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: webservices
Affects Versions: 4.5.3.Final
Reporter: Rich DiCroce
JAX-RS 2.1 adds some new types that can be injected into methods using the Context annotation, e.g. Sse and SseEventSink. Currently, JBoss Tools flags these with an error:
{quote}
@Context annotation is only allowed on method parameters of type '[javax.ws.rs.core.HttpHeaders, javax.ws.rs.core.UriInfo, javax.ws.rs.core.Request, javax.servlet.http.HttpServletRequest, javax.servlet.http.HttpServletResponse, javax.servlet.ServletConfig, javax.servlet.ServletContext, javax.ws.rs.core.SecurityContext]'.
{quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-26039) Generate one master .ts file
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-26039:
-----------------------------------
Summary: Generate one master .ts file
Key: JBIDE-26039
URL: https://issues.jboss.org/browse/JBIDE-26039
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: stack-server-protocol
Affects Versions: 4.6.0.AM1
Reporter: Rob Stryker
A single ts file would be easier for vs-code plugin to consume.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-26035) Convert SSP to function in an osgi environment
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26035?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-26035.
---------------------------------
Resolution: Done
This has been merged into master.
Instructions to deploy it and run it are basically in the description of this jira.
> Convert SSP to function in an osgi environment
> ----------------------------------------------
>
> Key: JBIDE-26035
> URL: https://issues.jboss.org/browse/JBIDE-26035
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: stack-server-protocol
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.6.0.AM2
>
>
> {code}
> mkdir felix
> cd felix
> wget http://download.nextag.com/apache/felix/org.apache.felix.main.distributio...
> unzip org.apache.felix.main.distribution-5.6.10.zip
> cd ../
> git clone git@github.com:robstryker/org.jboss.tools.ssp.git
> cd org.jboss.tools.ssp
> git checkout osgi_branch1
> mvn clean install
> #cp api/target/org.jboss.tools.ssp.api-0.8-SNAPSHOT.jar ../felix/felix-framework-5.6.10/bundle/
> #cp launching/target/org.jboss.tools.ssp.launching-0.8-SNAPSHOT.jar ../felix/felix-framework-5.6.10/bundle
> #cp server-spi/target/org.jboss.tools.ssp.server.spi-0.8-SNAPSHOT.jar ../felix/felix-framework-5.6.10/bundle/
> #cp server/target/org.jboss.tools.ssp.server-0.8-SNAPSHOT.jar ../felix/felix-framework-5.6.10/bundle/
> du -ah | grep "jar$" | grep "target/" | grep -v "test-classes" | grep -v "classes/" | grep -v "schema" | grep -v "client" | cut -c 1,2,3,4 --complement | awk '{ print "cp " $0 " ../felix/felix-framework-5.6.10/bundle/";}' | sh
> cd ../felix/felix-framework-5.6.10/
> java -jar bin/felix.jar
> {code}
> Note error:
> API Bundle Started
> Launching Bundle Started
> Server bundle started
> ERROR: Bundle org.jboss.tools.ssp.server.wildfly [11] Error starting file:/home/rob/tmp/ssp_osgi/felix/felix-framework-5.6.10/bundle/org.jboss.tools.ssp.server.wildfly-0.8-SNAPSHOT.jar (org.osgi.framework.BundleException: Activator start error in bundle org.jboss.tools.ssp.server.wildfly [11].)
> java.lang.NoClassDefFoundError: org/osgi/framework/BundleActivator
> at java.base/java.lang.ClassLoader.defineClass1(Native Method)
> at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1007)
> This is very strange. All the other bundles start fine. This bundle can't even find its osgi classes.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25974) CDK 3.4 runtime detection failing
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25974?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-25974:
---------------------------------------
Worked for me, thanks!
> CDK 3.4 runtime detection failing
> ---------------------------------
>
> Key: JBIDE-25974
> URL: https://issues.jboss.org/browse/JBIDE-25974
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.6.0.AM1
>
> Attachments: image-2018-05-07-17-59-59-316.png
>
>
> Runtime detection doesn't work for 3.4.0 with the whitelist. A regex would be better
> steps:
> # EXE: Preferences > JBoss Runtime Detection > Download
> # ASSERT: List of available runtimes shows up, containing CDK 3.4.0
> # EXEC: Choose "CDK 3.4.0" & hit "Next"
> # EXEC: next page: provide credentials & hit "Next"
> # EXEC: next page: accept the terms & hit "Next"
> # EXEC: next page: use the suggested defaults, make sure that "Install folder" is a separate folder (ex. freshly created ~/cdk/) & hit "Finish"
> # ASSERT: wait for the download to finish
> Result:
> The download wont detect the new CDK 3.4.0 that you just downloaded
> !image-2018-05-07-17-59-59-316.png!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months