[JBoss JIRA] (JBTIS-1015) Latest JBDSIS Target Platform cannot be used locally
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1015?page=com.atlassian.jira.plugin... ]
Paul Leacu updated JBTIS-1015:
------------------------------
Attachment: b2.png
b1.png
> Latest JBDSIS Target Platform cannot be used locally
> ----------------------------------------------------
>
> Key: JBTIS-1015
> URL: https://issues.jboss.org/browse/JBTIS-1015
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.4.1.CR2-TP
> Reporter: Aurélien Pupier
> Assignee: Paul Leacu
> Attachments: a1.png, a2.png, a3.png, a4.png, a5.png, b1.png, b2.png
>
>
> Current state of understanding:
> There are 2 different bugs:
> * when using local "Directory": the jars which should be exploded in folder stay in jars
> ** wondering if org.jboss.tools.tycho-plugins:target-platform-utils should be responsible to explode them or if it should be the task for P2 itself?
> ** the implication is that we can't start a CDK server with such a TP
> * when using local "Software site": the JVM packages are not recognized (javax.crypto for instance)
> ** looks like a p2 bugs
> ** the implication is that the TP doesn't resolve at all
> If one of these two bugs can be fixed, we will have a way to consume a local Target Platform.
> see [JBTIS-1008] for original discussions
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBTIS-1015) Latest JBDSIS Target Platform cannot be used locally
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1015?page=com.atlassian.jira.plugin... ]
Aurélien Pupier commented on JBTIS-1015:
----------------------------------------
I don't understand.
In your screenshot you are using a remote repo "http://download.jboss.org/jbosstools/development/updates"
Which "unzipped local repo" are you using? if I use the one that i pointed, I have the javax.crypto error when loading the content of the target Platform. it is the use case described that leads to the screenshot available in the previous jira issue: https://issues.jboss.org/secure/attachment/12414277/screenshot-1.png
> Latest JBDSIS Target Platform cannot be used locally
> ----------------------------------------------------
>
> Key: JBTIS-1015
> URL: https://issues.jboss.org/browse/JBTIS-1015
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.4.1.CR2-TP
> Reporter: Aurélien Pupier
> Assignee: Paul Leacu
> Attachments: a1.png, a2.png, a3.png, a4.png, a5.png
>
>
> Current state of understanding:
> There are 2 different bugs:
> * when using local "Directory": the jars which should be exploded in folder stay in jars
> ** wondering if org.jboss.tools.tycho-plugins:target-platform-utils should be responsible to explode them or if it should be the task for P2 itself?
> ** the implication is that we can't start a CDK server with such a TP
> * when using local "Software site": the JVM packages are not recognized (javax.crypto for instance)
> ** looks like a p2 bugs
> ** the implication is that the TP doesn't resolve at all
> If one of these two bugs can be fixed, we will have a way to consume a local Target Platform.
> see [JBTIS-1008] for original discussions
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBTIS-1015) Latest JBDSIS Target Platform cannot be used locally
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1015?page=com.atlassian.jira.plugin... ]
Paul Leacu commented on JBTIS-1015:
-----------------------------------
Ok - I'm using Eclipse Neon 1a
I can't load with 'Group by Category' checked. Can you try on your end selecting the check boxes that I have in !a3.png|thumbnail! and referencing your local unzipped repo. That worked okay on my end.
> Latest JBDSIS Target Platform cannot be used locally
> ----------------------------------------------------
>
> Key: JBTIS-1015
> URL: https://issues.jboss.org/browse/JBTIS-1015
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.4.1.CR2-TP
> Reporter: Aurélien Pupier
> Assignee: Paul Leacu
> Attachments: a1.png, a2.png, a3.png, a4.png, a5.png
>
>
> Current state of understanding:
> There are 2 different bugs:
> * when using local "Directory": the jars which should be exploded in folder stay in jars
> ** wondering if org.jboss.tools.tycho-plugins:target-platform-utils should be responsible to explode them or if it should be the task for P2 itself?
> ** the implication is that we can't start a CDK server with such a TP
> * when using local "Software site": the JVM packages are not recognized (javax.crypto for instance)
> ** looks like a p2 bugs
> ** the implication is that the TP doesn't resolve at all
> If one of these two bugs can be fixed, we will have a way to consume a local Target Platform.
> see [JBTIS-1008] for original discussions
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-4190) problem installing springide: eclipse.boot.dash plugin depends on slf4j 1.7.2 and ide.eclipse.quickfix depends on javax.servlet 3.1.0
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4190?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4190:
-----------------------------
Story Points: 2
> problem installing springide: eclipse.boot.dash plugin depends on slf4j 1.7.2 and ide.eclipse.quickfix depends on javax.servlet 3.1.0
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4190
> URL: https://issues.jboss.org/browse/JBDS-4190
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: central-update, rpm, upstream
> Affects Versions: 10.2.0.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.3.0.AM2
>
> Attachments: rh-eclipse46-devstudio10.2.log.20161118-1112_strict.txt, rh-eclipse46-devstudio10.2.log.20161118-1207_strict.txt, springide382.png, springide383-fixed-jbds4190-installed.png, springide383-fixed-jbds4190.png, springide383-install-feature-list-select.png
>
>
> springide 3.7.3 depends on slf4j 1.7.2 and javax.servlet 3.1.0
> {code}
> org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NoClassDefFoundError: org/springframework/ide/eclipse/beans/core/model/IProfileAwareBeansComponent)
> Caused by: java.lang.NoClassDefFoundError: org/springframework/ide/eclipse/beans/core/model/IProfileAwareBeansComponent
> at org.springframework.ide.eclipse.beans.ui.navigator.filters.NonMatchingProfilesFilter.select(NonMatchingProfilesFilter.java:24)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23678) remediation required installing jbosstools 4.4.3.AM1 on Neon.2
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23678?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23678:
-------------------------------
Sprint: devex #126 January 2017 (was: devex #125 December 2016)
> remediation required installing jbosstools 4.4.3.AM1 on Neon.2
> --------------------------------------------------------------
>
> Key: JBIDE-23678
> URL: https://issues.jboss.org/browse/JBIDE-23678
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.4.3.AM1
> Reporter: Nick Boldt
> Assignee: Victor Rubezhny
> Fix For: 4.4.3.AM2
>
> Attachments: remediation-required-jbt443am1.png, remediation-required-jbt443am1_skip_items.png, remediation-required-jbt443am1_upgrades.png
>
>
> Remediation required for installing jbosstools 4.4.3.AM1 -- seems we have newer versions of JSON/JSDT plugins in our target platform than are in Neon.2.
> Install manifest contains:
> * org.eclipse.wst.jsdt.feature 2.0.0 (4 versions),
> * 1.6.201 (2 versions), and
> * 2.0.200 (1 version) - *total 7 references*!
> Also, org.eclipse.wst.web_ui.feature.feature.group depends on org.eclipse.wst.jsdt.feature.feature.group, which pulls in another ref/requirement.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-4190) problem installing springide: eclipse.boot.dash plugin depends on slf4j 1.7.2 and ide.eclipse.quickfix depends on javax.servlet 3.1.0
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4190?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4190:
-----------------------------
Fix Version/s: 10.3.0.AM2
(was: 10.x)
> problem installing springide: eclipse.boot.dash plugin depends on slf4j 1.7.2 and ide.eclipse.quickfix depends on javax.servlet 3.1.0
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4190
> URL: https://issues.jboss.org/browse/JBDS-4190
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: central-update, rpm, upstream
> Affects Versions: 10.2.0.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.3.0.AM2
>
> Attachments: rh-eclipse46-devstudio10.2.log.20161118-1112_strict.txt, rh-eclipse46-devstudio10.2.log.20161118-1207_strict.txt, springide382.png, springide383-fixed-jbds4190-installed.png, springide383-fixed-jbds4190.png, springide383-install-feature-list-select.png
>
>
> springide 3.7.3 depends on slf4j 1.7.2 and javax.servlet 3.1.0
> {code}
> org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NoClassDefFoundError: org/springframework/ide/eclipse/beans/core/model/IProfileAwareBeansComponent)
> Caused by: java.lang.NoClassDefFoundError: org/springframework/ide/eclipse/beans/core/model/IProfileAwareBeansComponent
> at org.springframework.ide.eclipse.beans.ui.navigator.filters.NonMatchingProfilesFilter.select(NonMatchingProfilesFilter.java:24)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23678) remediation required installing jbosstools 4.4.3.AM1 on Neon.2
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23678?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-23678:
----------------------------------
Assignee: Victor Rubezhny (was: Nick Boldt)
> remediation required installing jbosstools 4.4.3.AM1 on Neon.2
> --------------------------------------------------------------
>
> Key: JBIDE-23678
> URL: https://issues.jboss.org/browse/JBIDE-23678
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.4.3.AM1
> Reporter: Nick Boldt
> Assignee: Victor Rubezhny
> Fix For: 4.4.3.AM2
>
> Attachments: remediation-required-jbt443am1.png, remediation-required-jbt443am1_skip_items.png, remediation-required-jbt443am1_upgrades.png
>
>
> Remediation required for installing jbosstools 4.4.3.AM1 -- seems we have newer versions of JSON/JSDT plugins in our target platform than are in Neon.2.
> Install manifest contains:
> * org.eclipse.wst.jsdt.feature 2.0.0 (4 versions),
> * 1.6.201 (2 versions), and
> * 2.0.200 (1 version) - *total 7 references*!
> Also, org.eclipse.wst.web_ui.feature.feature.group depends on org.eclipse.wst.jsdt.feature.feature.group, which pulls in another ref/requirement.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBTIS-1015) Latest JBDSIS Target Platform cannot be used locally
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1015?page=com.atlassian.jira.plugin... ]
Aurélien Pupier updated JBTIS-1015:
-----------------------------------
Steps to Reproduce:
for first case:
- download the zipped mirror https://10.8.63.16/view/Fuse%20Tooling/job/Fuse-Tooling-Target-Platform-B...
- unzip it
- windows->preferences->Plug-in development->Target Platform
- Add...
- check Nothing: Start with an empty target definition
- Next
- in Locations tab, click Add...
- select "Directory" and click Next
- Select the location where you unzipped the mirror
- Click finish
- Click Finish
- ensure that you select it in the list and then click Apply and then OK
- Launch an Eclipse application with all plugins
- go to Servers view
- configure access to CDK server
- Launch the CDK server
--> the JVM is crashing because the org.eclipse.cdt.core.win32.x86_64 - or the one which corresponds to your OS - is not in exploded mode
for second case:
- download the zipped mirror https://10.8.63.16/view/Fuse%20Tooling/job/Fuse-Tooling-Target-Platform-B...
- unzip it
- windows->preferences->Plug-in development->Target Platform
- Add...
- check Nothing: Start with an empty target definition
- Next
- in Locations tab, click Add...
- select "Software Site" and click Next
- point to teh folder containing the mirrored update site
--> it complains about javax.crypto packages not available, this package is provided by the JVM
was:
for first case:
- download the zipped mirror https://10.8.63.16/view/Fuse%20Tooling/job/Fuse-Tooling-Target-Platform-B...
- unzip it
- windows->preferences->Plug-in development->Target Platform
- Add...
- check Nothing: Start with an empty target definition
- Next
- in Locations tab, click Add...
- select "Directory" and click Next
- Select the location where you unzipped the mirror
- Click finish
- Click Finish
- ensure that you select it in the list and then click Apply and then OK
- Launch an Eclipse application with all plugins
- go to Servers view
- configure access to CDK server
- Launch the CDK server
--> the JVM is crashing because the org.eclipse.cdt.core.win32.x86_64 - or the one which corresponds to your OS - is not in exploded mode
for second case:
- download the zipped mirror https://10.8.63.16/view/Fuse%20Tooling/job/Fuse-Tooling-Target-Platform-B...
- unzip it
- windows->preferences->Plug-in development->Target Platform
- Add...
- check Nothing: Start with an empty target definition
- Next
- in Locations tab, click Add...
- select "Software Site" and click Next
--> it complains about javax.crypto packages not available, this package is provided by the JVM
> Latest JBDSIS Target Platform cannot be used locally
> ----------------------------------------------------
>
> Key: JBTIS-1015
> URL: https://issues.jboss.org/browse/JBTIS-1015
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.4.1.CR2-TP
> Reporter: Aurélien Pupier
> Assignee: Paul Leacu
> Attachments: a1.png, a2.png, a3.png, a4.png, a5.png
>
>
> Current state of understanding:
> There are 2 different bugs:
> * when using local "Directory": the jars which should be exploded in folder stay in jars
> ** wondering if org.jboss.tools.tycho-plugins:target-platform-utils should be responsible to explode them or if it should be the task for P2 itself?
> ** the implication is that we can't start a CDK server with such a TP
> * when using local "Software site": the JVM packages are not recognized (javax.crypto for instance)
> ** looks like a p2 bugs
> ** the implication is that the TP doesn't resolve at all
> If one of these two bugs can be fixed, we will have a way to consume a local Target Platform.
> see [JBTIS-1008] for original discussions
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBTIS-1015) Latest JBDSIS Target Platform cannot be used locally
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1015?page=com.atlassian.jira.plugin... ]
Aurélien Pupier commented on JBTIS-1015:
----------------------------------------
bq. What version of Eclipse are you using as your development platform?
I'm using Eclipse neon as my Development platform.
bq. In the second case, which radio button/check box do you have selected in the 'Add Software Site' page?
I checked all
bq. See attachments - is that similar to your set up?
in a3, a4, a5 you are using remote update sites. This is not what I want to use. I want to stay local to avoid latency when changing/switching Target platform.
> Latest JBDSIS Target Platform cannot be used locally
> ----------------------------------------------------
>
> Key: JBTIS-1015
> URL: https://issues.jboss.org/browse/JBTIS-1015
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.4.1.CR2-TP
> Reporter: Aurélien Pupier
> Assignee: Paul Leacu
> Attachments: a1.png, a2.png, a3.png, a4.png, a5.png
>
>
> Current state of understanding:
> There are 2 different bugs:
> * when using local "Directory": the jars which should be exploded in folder stay in jars
> ** wondering if org.jboss.tools.tycho-plugins:target-platform-utils should be responsible to explode them or if it should be the task for P2 itself?
> ** the implication is that we can't start a CDK server with such a TP
> * when using local "Software site": the JVM packages are not recognized (javax.crypto for instance)
> ** looks like a p2 bugs
> ** the implication is that the TP doesn't resolve at all
> If one of these two bugs can be fixed, we will have a way to consume a local Target Platform.
> see [JBTIS-1008] for original discussions
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBTIS-1015) Latest JBDSIS Target Platform cannot be used locally
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1015?page=com.atlassian.jira.plugin... ]
Paul Leacu commented on JBTIS-1015:
-----------------------------------
Need to be pedantic here. What version of Eclipse are you using as your development platform? In the second case, which radio button/check box do you have selected in the 'Add Software Site' page? See attachments - is that similar to your set up?
[~aurelien.pupier] ^^
> Latest JBDSIS Target Platform cannot be used locally
> ----------------------------------------------------
>
> Key: JBTIS-1015
> URL: https://issues.jboss.org/browse/JBTIS-1015
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.4.1.CR2-TP
> Reporter: Aurélien Pupier
> Assignee: Paul Leacu
> Attachments: a1.png, a2.png, a3.png, a4.png, a5.png
>
>
> Current state of understanding:
> There are 2 different bugs:
> * when using local "Directory": the jars which should be exploded in folder stay in jars
> ** wondering if org.jboss.tools.tycho-plugins:target-platform-utils should be responsible to explode them or if it should be the task for P2 itself?
> ** the implication is that we can't start a CDK server with such a TP
> * when using local "Software site": the JVM packages are not recognized (javax.crypto for instance)
> ** looks like a p2 bugs
> ** the implication is that the TP doesn't resolve at all
> If one of these two bugs can be fixed, we will have a way to consume a local Target Platform.
> see [JBTIS-1008] for original discussions
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
