[JBoss JIRA] (JBDS-3719) Initial search for an existing JBDS is present but disabled
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3719?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-3719.
-----------------------------
Resolution: Won't Fix
After some thought, it seems like a bad idea to actually search for existing devstudio. Closing as won't fix.
> Initial search for an existing JBDS is present but disabled
> -----------------------------------------------------------
>
> Key: JBDS-3719
> URL: https://issues.jboss.org/browse/JBDS-3719
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 10.3.0.AM2
>
>
> The installer calls the functionality to search for an existing JBDS when the confirm page loads, but the method has a built-in check that just interrupts it. Meaning - checking an existing installation will only proceed if a folder was selected by the user, the initial search will not.
> Is this by design? If it is there is no point in initiating the search automatically.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-3728) Assign IDs to UI elements
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3728?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-3728.
-----------------------------
Resolution: Done
Closing since we've already covered the elements we are using.
> Assign IDs to UI elements
> -------------------------
>
> Key: JBDS-3728
> URL: https://issues.jboss.org/browse/JBDS-3728
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: platform-installer
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Fix For: 10.3.0.AM2
>
>
> The use of IDs greatly improves the lookup times and makes automated testing a lot easier. So please do include IDs in elements you create + we should add them to already existing elements that don't have any.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-3947) Some older versions of vagrant skip version validation
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3947?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-3947.
-----------------------------
Resolution: Done
Closing since we are getting rid of vagrant.
> Some older versions of vagrant skip version validation
> ------------------------------------------------------
>
> Key: JBDS-3947
> URL: https://issues.jboss.org/browse/JBDS-3947
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.0.0.GA
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Fix For: 10.3.0.AM2
>
> Attachments: vagrant.png
>
>
> Some older versions (so far found 1.7.0, 1.6.5) will not have their version reckognized. As seen on the screenshot, it doesn't show the version it detected and the UI looks like it is going to be used. The installer tries to download and install its own though.
> !vagrant.png|thumbnail!
> The issue might be connected to the fact that with these versions the command
> {noformat}where vagrant{noformat}
> in fact returns 2 files
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-4087) Mark as invalid Vagrant versions known to be not working
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-4087?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-4087.
-----------------------------
Resolution: Out of Date
Vagrant is being removed in 1.3, closing as outdated.
> Mark as invalid Vagrant versions known to be not working
> --------------------------------------------------------
>
> Key: JBDS-4087
> URL: https://issues.jboss.org/browse/JBDS-4087
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 1.1.0.GA
> Reporter: Aurélien Pupier
> Assignee: Denis Golovin
> Fix For: 10.3.0.AM2
>
>
> Vagrant version superior to 1.8.4 are known to be non-working, please mark them as invalid during installation of the components isntead of saying that there is a newer version.
> For my part there was no clue on what was the issue, i was based on the latest at the moment 1.8.6.
> When using JBDS, I had a timeout when trying to launch the Container in Server view and the console starting the server was displaying no errors
--
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 edited comment on JBTIS-1015 at 1/11/17 4:54 AM:
-----------------------------------------------------------------
when unchecking "include required software" as you are doing allows me to go further :-)
Unfortunately, after that it seems that some plugins that are in the folder are not available from the update site such as org.apache.commonc.io:
available in folder:
!commons.io available in folder.png|thumbnail!
but not visible in update site:
!commons.io not visible in update site.png|thumbnail!
EDIT:
list of other plugins in same situation:
- com.fasterxml.jackson.core.jackson-databind_2.5.0.v201504151636
- org.jboss.tools.locus.jsonschema2pojo.jsonschema2pojo-core
- org.jboss.tools.locus.jaxb-core
- org.jboss.tools.locus.jaxb-impl
- org.jboss.tools.locus.jaxb-xjc
- javax.xml.bind
- org.eclipse.gemini.management
- org.eclipse.tm.terminal.view.core
- org.eclipse.tm.terminal.view.ui
- org.jboss.tools.as.test.core
- org.assertj.core
- org.jboss.tools.locus.mockito
was (Author: aurelien.pupier):
when unchecking "include required software" as you are doing allows me to go further :-)
Unfortunatley, after that it seems that some plugins that are in the folder are not available from the update site such as org.apache.commonc.io:
available in folder:
!commons.io available in folder.png|thumbnail!
but not visible in update site:
!commons.io not visible in update site.png|thumbnail!
EDIT:
list of other plugins in same situation:
- com.fasterxml.jackson.core.jackson-databind_2.5.0.v201504151636
- org.jboss.tools.locus.jsonschema2pojo.jsonschema2pojo-core
- org.jboss.tools.locus.jaxb-core
- org.jboss.tools.locus.jaxb-impl
- org.jboss.tools.locus.jaxb-xjc
- javax.xml.bind
- org.eclipse.gemini.management
- org.eclipse.tm.terminal.view.core
- org.eclipse.tm.terminal.view.ui
- org.jboss.tools.as.test.core
- org.assertj.core
- org.jboss.tools.locus.mockito
> 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, commons.io available in folder.png, commons.io not visible in update site.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 edited comment on JBTIS-1015 at 1/11/17 4:54 AM:
-----------------------------------------------------------------
when unchecking "include required software" as you are doing allows me to go further :-)
Unfortunatley, after that it seems that some plugins that are in the folder are not available from the update site such as org.apache.commonc.io:
available in folder:
!commons.io available in folder.png|thumbnail!
but not visible in update site:
!commons.io not visible in update site.png|thumbnail!
EDIT:
list of other plugins in same situation:
- com.fasterxml.jackson.core.jackson-databind_2.5.0.v201504151636
- org.jboss.tools.locus.jsonschema2pojo.jsonschema2pojo-core
- org.jboss.tools.locus.jaxb-core
- org.jboss.tools.locus.jaxb-impl
- org.jboss.tools.locus.jaxb-xjc
- javax.xml.bind
- org.eclipse.gemini.management
- org.eclipse.tm.terminal.view.core
- org.eclipse.tm.terminal.view.ui
- org.jboss.tools.as.test.core
- org.assertj.core
- org.jboss.tools.locus.mockito
was (Author: aurelien.pupier):
when unchecking "include required software" as you are doing allows me to go further :-)
Unfortunatley, after that it seems that some plugins that are in the folder are not available from the update site such as org.apache.commonc.io:
available in folder:
!commons.io available in folder.png|thumbnail!
but not visible in update site:
!commons.io not visible in update site.png|thumbnail!
> 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, commons.io available in folder.png, commons.io not visible in update site.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 updated JBTIS-1015:
-----------------------------------
Attachment: commons.io not visible in update site.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, commons.io available in folder.png, commons.io not visible in update site.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:
----------------------------------------
when unchecking "include required software" as you are doing allows me to go further :-)
Unfortunatley, after that it seems that some plugins that are in the folder are not available from the update site such as org.apache.commonc.io:
available in folder:
!commons.io available in folder.png|thumbnail!
but not visible in update site:
!commons.io not visible in update site.png|thumbnail!
> 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, commons.io available in folder.png, commons.io not visible in update site.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 updated JBTIS-1015:
-----------------------------------
Attachment: commons.io available in folder.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, commons.io available in folder.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