[JBoss JIRA] (JBIDE-26065) Add RH Central connector for nodeclipse
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26065?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-26065:
------------------------------------
Discovery site rebuilding:
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... >= 4317
Results will be here (accessible to AM3 users automatically):
http://download.jboss.org/jbosstools/photon/snapshots/updates/discovery.c... (should see 4317 in plugins/ folder)
> Add RH Central connector for nodeclipse
> ---------------------------------------
>
> Key: JBIDE-26065
> URL: https://issues.jboss.org/browse/JBIDE-26065
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build, central-update, updatesite, upstream
> Affects Versions: 4.6.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.6.0.AM3
>
> Attachments: eclipse-marketplace-nodeclipse.png, license-node-asl2.txt, license-node-chromium.txt, license-node-jshint-eclipse-license-unknown.txt, license-node-markdown-editor-EPL-version-unknown.txt, license-nodepluginslist-paul-verest.txt, node-license-agreements.png
>
>
> Steps to perform:
> a) mirror a copy of the latest Nodeclipse update site onto dl.jb.org for reproduceability
> b) add that to the 3rd party target platform used for building RH Central
> c) create a connector in Central for installing Nodeclipse into BOTH *devstudio* and *jbosstools*
> The list of features to include will be those recommended in the screenshots here [1], under the *B) UPDATE SITE (BIGGER CHOICE)* section, or can be collected based on the existing Eclipse Marketplace connector provided by nodeclipse [2].
>
> [1] http://www.nodeclipse.org/updates/
> [2] https://marketplace.eclipse.org/content/nodeclipse
> !eclipse-marketplace-nodeclipse.png|thumbnail!
> Installed size is about 111M for these 14 features:
> {code}
> org.nodeclipse_1.0.2.201509250223
> org.nodeclipse.enide.editors.jade.feature_1.0.2.201509250223
> org.nodeclipse.pluginslist.feature_1.0.2.201509250223
> com.eclipsesource.jshint.feature_0.10.1.20160216-0911
> de.bastiankrol.startexplorer.feature_1.7.0
> gitaddon.feature_1.0.0.20140303-0606
> markdown.editor.feature_1.2.0.201501260515
> net.mihai-nita.ansicon_1.3.1.201508091828
> pm.eclipse.editbox.feature_0.70.0.201508180438
> org.chromium.debug_0.3.9.201509250223
> org.chromium.sdk_0.3.9.201509250223
> tern-feature_1.1.0.201511082254
> tern-jsdt-feature_1.1.0.201511082254
> tern-server-nodejs-feature_1.1.0.201511082254
> {code}
> If any of these assumptions / feature brief details are incorrect, please correct them in this description or add comments to this JIRA.
> PR to do mirror, if licenses are allowed:
> https://github.com/jbosstools/jbosstools-download.jboss.org/pull/638
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26038) [Red Hat Central] Update to latest Subclipse & older SVNKit
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26038?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-26038:
------------------------------------
Discovery site rebuilding:
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... >= 4317
Results will be here (accessible to AM3 users automatically):
http://download.jboss.org/jbosstools/photon/snapshots/updates/discovery.c... (should see 4317 in plugins/ folder)
> [Red Hat Central] Update to latest Subclipse & older SVNKit
> -----------------------------------------------------------
>
> 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:
> http://post-office.corp.redhat.com/archives/sme-jbds/2018-May/msg00004.html
> {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, 9 months
[JBoss JIRA] (JBIDE-26065) Add RH Central connector for nodeclipse
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26065?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-26065:
------------------------------------
For now, I've added an external connector to Central so users can choose to accept the licenses themselves, as we do for JRebel and Android tools.
https://github.com/jbosstools/jbosstools-discovery/pull/380
> Add RH Central connector for nodeclipse
> ---------------------------------------
>
> Key: JBIDE-26065
> URL: https://issues.jboss.org/browse/JBIDE-26065
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build, central-update, updatesite, upstream
> Affects Versions: 4.6.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.6.0.AM3
>
> Attachments: eclipse-marketplace-nodeclipse.png, license-node-asl2.txt, license-node-chromium.txt, license-node-jshint-eclipse-license-unknown.txt, license-node-markdown-editor-EPL-version-unknown.txt, license-nodepluginslist-paul-verest.txt, node-license-agreements.png
>
>
> Steps to perform:
> a) mirror a copy of the latest Nodeclipse update site onto dl.jb.org for reproduceability
> b) add that to the 3rd party target platform used for building RH Central
> c) create a connector in Central for installing Nodeclipse into BOTH *devstudio* and *jbosstools*
> The list of features to include will be those recommended in the screenshots here [1], under the *B) UPDATE SITE (BIGGER CHOICE)* section, or can be collected based on the existing Eclipse Marketplace connector provided by nodeclipse [2].
>
> [1] http://www.nodeclipse.org/updates/
> [2] https://marketplace.eclipse.org/content/nodeclipse
> !eclipse-marketplace-nodeclipse.png|thumbnail!
> Installed size is about 111M for these 14 features:
> {code}
> org.nodeclipse_1.0.2.201509250223
> org.nodeclipse.enide.editors.jade.feature_1.0.2.201509250223
> org.nodeclipse.pluginslist.feature_1.0.2.201509250223
> com.eclipsesource.jshint.feature_0.10.1.20160216-0911
> de.bastiankrol.startexplorer.feature_1.7.0
> gitaddon.feature_1.0.0.20140303-0606
> markdown.editor.feature_1.2.0.201501260515
> net.mihai-nita.ansicon_1.3.1.201508091828
> pm.eclipse.editbox.feature_0.70.0.201508180438
> org.chromium.debug_0.3.9.201509250223
> org.chromium.sdk_0.3.9.201509250223
> tern-feature_1.1.0.201511082254
> tern-jsdt-feature_1.1.0.201511082254
> tern-server-nodejs-feature_1.1.0.201511082254
> {code}
> If any of these assumptions / feature brief details are incorrect, please correct them in this description or add comments to this JIRA.
> PR to do mirror, if licenses are allowed:
> https://github.com/jbosstools/jbosstools-download.jboss.org/pull/638
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26069) Spring Boot Project configurator: Creating child module for main project fails
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26069?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-26069:
------------------------------------------
[~rawb] any idea?
> Spring Boot Project configurator: Creating child module for main project fails
> -------------------------------------------------------------------------------
>
> Key: JBIDE-26069
> URL: https://issues.jboss.org/browse/JBIDE-26069
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.6.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: project_configurator, springboot
> Fix For: 4.6.0.Final
>
> Attachments: image-2018-05-30-22-31-37-635.png
>
>
> steps:
> # ASSERT: We dont know for now, really. We can only reproduce this on [~jeffmaury]'s machine (happens to him in Windows and Linux - doesn't for others in Linux nor Mac).
> # EXEC: import the 2 maven projects that are attached to JBIDE-25504 (camel-ose-springboot-xml and penguins
> # EXEC: in project properties for project *camel-ose-springboot-xml*: pick "Deployment Assembly"
> # ASSERT: verify that *penguins* is defined as child module
> Result:
> !image-2018-05-30-22-31-37-635.png!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26069) Spring Boot Project configurator: Creating child module for main project fails
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26069?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-26069:
------------------------------------------
postponing due to missing further info/insights.
> Spring Boot Project configurator: Creating child module for main project fails
> -------------------------------------------------------------------------------
>
> Key: JBIDE-26069
> URL: https://issues.jboss.org/browse/JBIDE-26069
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.6.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: project_configurator, springboot
> Fix For: 4.6.0.Final
>
> Attachments: image-2018-05-30-22-31-37-635.png
>
>
> steps:
> # ASSERT: We dont know for now, really. We can only reproduce this on [~jeffmaury]'s machine (happens to him in Windows and Linux - doesn't for others in Linux nor Mac).
> # EXEC: import the 2 maven projects that are attached to JBIDE-25504 (camel-ose-springboot-xml and penguins
> # EXEC: in project properties for project *camel-ose-springboot-xml*: pick "Deployment Assembly"
> # ASSERT: verify that *penguins* is defined as child module
> Result:
> !image-2018-05-30-22-31-37-635.png!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26069) Spring Boot Project configurator: Creating child module for main project fails
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26069?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26069:
-------------------------------------
Fix Version/s: 4.6.0.Final
(was: 4.6.0.AM3)
> Spring Boot Project configurator: Creating child module for main project fails
> -------------------------------------------------------------------------------
>
> Key: JBIDE-26069
> URL: https://issues.jboss.org/browse/JBIDE-26069
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.6.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: project_configurator, springboot
> Fix For: 4.6.0.Final
>
> Attachments: image-2018-05-30-22-31-37-635.png
>
>
> steps:
> # ASSERT: We dont know for now, really. We can only reproduce this on [~jeffmaury]'s machine (happens to him in Windows and Linux - doesn't for others in Linux nor Mac).
> # EXEC: import the 2 maven projects that are attached to JBIDE-25504 (camel-ose-springboot-xml and penguins
> # EXEC: in project properties for project *camel-ose-springboot-xml*: pick "Deployment Assembly"
> # ASSERT: verify that *penguins* is defined as child module
> Result:
> !image-2018-05-30-22-31-37-635.png!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26065) Add RH Central connector for nodeclipse
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26065?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-26065:
-------------------------------
Description:
Steps to perform:
a) mirror a copy of the latest Nodeclipse update site onto dl.jb.org for reproduceability
b) add that to the 3rd party target platform used for building RH Central
c) create a connector in Central for installing Nodeclipse into BOTH *devstudio* and *jbosstools*
The list of features to include will be those recommended in the screenshots here [1], under the *B) UPDATE SITE (BIGGER CHOICE)* section, or can be collected based on the existing Eclipse Marketplace connector provided by nodeclipse [2].
[1] http://www.nodeclipse.org/updates/
[2] https://marketplace.eclipse.org/content/nodeclipse
!eclipse-marketplace-nodeclipse.png|thumbnail!
Installed size is about 111M for these 14 features:
{code}
org.nodeclipse_1.0.2.201509250223
org.nodeclipse.enide.editors.jade.feature_1.0.2.201509250223
org.nodeclipse.pluginslist.feature_1.0.2.201509250223
com.eclipsesource.jshint.feature_0.10.1.20160216-0911
de.bastiankrol.startexplorer.feature_1.7.0
gitaddon.feature_1.0.0.20140303-0606
markdown.editor.feature_1.2.0.201501260515
net.mihai-nita.ansicon_1.3.1.201508091828
pm.eclipse.editbox.feature_0.70.0.201508180438
org.chromium.debug_0.3.9.201509250223
org.chromium.sdk_0.3.9.201509250223
tern-feature_1.1.0.201511082254
tern-jsdt-feature_1.1.0.201511082254
tern-server-nodejs-feature_1.1.0.201511082254
{code}
If any of these assumptions / feature brief details are incorrect, please correct them in this description or add comments to this JIRA.
PR to do mirror, if licenses are allowed:
https://github.com/jbosstools/jbosstools-download.jboss.org/pull/638
was:
Steps to perform:
a) mirror a copy of the latest Nodeclipse update site onto dl.jb.org for reproduceability
b) add that to the 3rd party target platform used for building RH Central
c) create a connector in Central for installing Nodeclipse into BOTH *devstudio* and *jbosstools*
The list of features to include will be those recommended in the screenshots here [1], under the *B) UPDATE SITE (BIGGER CHOICE)* section, or can be collected based on the existing Eclipse Marketplace connector provided by nodeclipse [2].
[1] http://www.nodeclipse.org/updates/
[2] https://marketplace.eclipse.org/content/nodeclipse
!eclipse-marketplace-nodeclipse.png|thumbnail!
Installed size is about 111M for these features:
{code}
org.nodeclipse_1.0.2.201509250223
org.nodeclipse.enide.editors.jade.feature_1.0.2.201509250223
org.nodeclipse.pluginslist.feature_1.0.2.201509250223
com.eclipsesource.jshint.feature_0.10.1.20160216-0911
de.bastiankrol.startexplorer.feature_1.7.0
gitaddon.feature_1.0.0.20140303-0606
markdown.editor.feature_1.2.0.201501260515
net.mihai-nita.ansicon_1.3.1.201508091828
pm.eclipse.editbox.feature_0.70.0.201508180438
org.chromium.debug_0.3.9.201509250223
org.chromium.sdk_0.3.9.201509250223
tern-feature_1.1.0.201511082254
tern-jsdt-feature_1.1.0.201511082254
tern-server-nodejs-feature_1.1.0.201511082254
{code}
If any of these assumptions / feature brief details are incorrect, please correct them in this description or add comments to this JIRA.
PR to do mirror, if licenses are allowed:
https://github.com/jbosstools/jbosstools-download.jboss.org/pull/638
> Add RH Central connector for nodeclipse
> ---------------------------------------
>
> Key: JBIDE-26065
> URL: https://issues.jboss.org/browse/JBIDE-26065
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build, central-update, updatesite, upstream
> Affects Versions: 4.6.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.6.0.AM3
>
> Attachments: eclipse-marketplace-nodeclipse.png, license-node-asl2.txt, license-node-chromium.txt, license-node-jshint-eclipse-license-unknown.txt, license-node-markdown-editor-EPL-version-unknown.txt, license-nodepluginslist-paul-verest.txt, node-license-agreements.png
>
>
> Steps to perform:
> a) mirror a copy of the latest Nodeclipse update site onto dl.jb.org for reproduceability
> b) add that to the 3rd party target platform used for building RH Central
> c) create a connector in Central for installing Nodeclipse into BOTH *devstudio* and *jbosstools*
> The list of features to include will be those recommended in the screenshots here [1], under the *B) UPDATE SITE (BIGGER CHOICE)* section, or can be collected based on the existing Eclipse Marketplace connector provided by nodeclipse [2].
>
> [1] http://www.nodeclipse.org/updates/
> [2] https://marketplace.eclipse.org/content/nodeclipse
> !eclipse-marketplace-nodeclipse.png|thumbnail!
> Installed size is about 111M for these 14 features:
> {code}
> org.nodeclipse_1.0.2.201509250223
> org.nodeclipse.enide.editors.jade.feature_1.0.2.201509250223
> org.nodeclipse.pluginslist.feature_1.0.2.201509250223
> com.eclipsesource.jshint.feature_0.10.1.20160216-0911
> de.bastiankrol.startexplorer.feature_1.7.0
> gitaddon.feature_1.0.0.20140303-0606
> markdown.editor.feature_1.2.0.201501260515
> net.mihai-nita.ansicon_1.3.1.201508091828
> pm.eclipse.editbox.feature_0.70.0.201508180438
> org.chromium.debug_0.3.9.201509250223
> org.chromium.sdk_0.3.9.201509250223
> tern-feature_1.1.0.201511082254
> tern-jsdt-feature_1.1.0.201511082254
> tern-server-nodejs-feature_1.1.0.201511082254
> {code}
> If any of these assumptions / feature brief details are incorrect, please correct them in this description or add comments to this JIRA.
> PR to do mirror, if licenses are allowed:
> https://github.com/jbosstools/jbosstools-download.jboss.org/pull/638
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months