[JBoss JIRA] (JBDS-3379) Error message in JBDS when installing into existing folder needs work
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3379?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3379:
-----------------------------
CDW release: + (was: ?)
> Error message in JBDS when installing into existing folder needs work
> ---------------------------------------------------------------------
>
> Key: JBDS-3379
> URL: https://issues.jboss.org/browse/JBDS-3379
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 8.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Fix For: 9.0.0.Beta1
>
> Attachments: over-the-top-message-JBDS8.1Beta1.png
>
>
> Got an error message trying to install JBDS into an existing JBDS folder:
> {quote}You can't upgrade by installing over the top (sic){quote}
> !over-the-top-message-JBDS8.1Beta1.png!
> We should consider fixing this message in JBDS 9. Perhaps something like this?
> {quote}Specified folder already contains a JBoss Developer Studio installation. One does not simply install into an existing install folder. Choose another folder or cancel this installer and run JBoss Developer Studio to perform an update.{quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBDS-3379) Error message in JBDS when installing into existing folder needs work
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3379?page=com.atlassian.jira.plugin.... ]
CDW Engine reassigned JBDS-3379:
--------------------------------
> Error message in JBDS when installing into existing folder needs work
> ---------------------------------------------------------------------
>
> Key: JBDS-3379
> URL: https://issues.jboss.org/browse/JBDS-3379
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 8.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Fix For: 9.0.0.Beta1
>
> Attachments: over-the-top-message-JBDS8.1Beta1.png
>
>
> Got an error message trying to install JBDS into an existing JBDS folder:
> {quote}You can't upgrade by installing over the top (sic){quote}
> !over-the-top-message-JBDS8.1Beta1.png!
> We should consider fixing this message in JBDS 9. Perhaps something like this?
> {quote}Specified folder already contains a JBoss Developer Studio installation. One does not simply install into an existing install folder. Choose another folder or cancel this installer and run JBoss Developer Studio to perform an update.{quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBDS-3379) Error message in JBDS when installing into existing folder needs work
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3379?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3379:
--------------------------------
CDW qa_ack: + (was: ?)
> Error message in JBDS when installing into existing folder needs work
> ---------------------------------------------------------------------
>
> Key: JBDS-3379
> URL: https://issues.jboss.org/browse/JBDS-3379
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 8.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Fix For: 9.0.0.Beta1
>
> Attachments: over-the-top-message-JBDS8.1Beta1.png
>
>
> Got an error message trying to install JBDS into an existing JBDS folder:
> {quote}You can't upgrade by installing over the top (sic){quote}
> !over-the-top-message-JBDS8.1Beta1.png!
> We should consider fixing this message in JBDS 9. Perhaps something like this?
> {quote}Specified folder already contains a JBoss Developer Studio installation. One does not simply install into an existing install folder. Choose another folder or cancel this installer and run JBoss Developer Studio to perform an update.{quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (LOCUS-42) Add jsonschema2pojo-core to locus
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/LOCUS-42?page=com.atlassian.jira.plugin.s... ]
Nick Boldt commented on LOCUS-42:
---------------------------------
Sorry, misunderstood. Thought you meant all the things you needed were already in Orbit (and therefore could be directly added to your TP).
So to confirm, you want three new jars in Locus 1.3.0:
* jsonschema2pojo-core jar,
* jaxb-xjc jar and
* jaxb-impl jar
I don't see anywhere else in this JIRA or in JBTIS-438 where you've explicitly asked for these three, so I wanted to confirm I've successfully read the tea leaves of this cryptic request. (It'd be cool if you could update your issues' descriptions/titles when they evolve to include more work . :D )
Is that correct?
> Add jsonschema2pojo-core to locus
> ---------------------------------
>
> Key: LOCUS-42
> URL: https://issues.jboss.org/browse/LOCUS-42
> Project: JBoss Tools Locus
> Issue Type: Feature Request
> Affects Versions: 1.2.0
> Reporter: Paul Leacu
>
> Fuse Data Transformation tooling relies on jsonschema2pojo to generate model classes from JSON schema and JSON instance documents. Need to capture the jar in locus for inclusion into JBTIS target platform and ultimately Data Transformation tooling (Fuse).
> https://repo1.maven.org/maven2/org/jsonschema2pojo/jsonschema2pojo-core/0... jsonschema2pojo-core-0.4.11-sources.jar
> This is needed for Mars/ 9.0.x JBDSIS target platform inclusion.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-17696) Enabling Maven Dependency Management job waits forever
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17696?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen closed JBIDE-17696.
---------------------------------------
Resolution: Cannot Reproduce Bug
from calll 2015-06-01 [~dgolovin] said to close since not been able to reproduce it.
> Enabling Maven Dependency Management job waits forever
> ------------------------------------------------------
>
> Key: JBIDE-17696
> URL: https://issues.jboss.org/browse/JBIDE-17696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.2.0.Beta2
> Environment: OpenJDK 1.7, 64b
> Ubuntu 12.04, 64b
> Reporter: Rastislav Wagner
> Assignee: Denis Golovin
> Fix For: 4.3.0.Beta1
>
> Attachments: .options, jstack1.out, jstack2.out, jstack_mvn.out, mvn.png, wait1.png, wait2.png
>
>
> I dont have exact steps to reproduce because this usually occurs after longer work. I'm testing various configurators (CDI/Seam/JAXRS..) using this scenario:
> 1. Create Dynamic Web Project
> 2. Convert to maven project (using Configure -> Convert to maven..)
> 3. Add some dependency
> 4. check if proper facet was enabled
> 5. delete project and repeat
> After trying this 10-15 times (sometimes more, sometimes less), during step 2 "Enabling Maven Dependency Management" job is waiting and never ends - see screenshot - there's always "Setting classpath containers".
> JVM thread dump attached.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19897) Remove check server type
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19897?page=com.atlassian.jira.plugi... ]
Jeff Cantrill updated JBIDE-19897:
----------------------------------
Description: (was: Modify the connection wizard so the v3 server can auto-detect the auth type and support OAuth
* Remove server type verify button
* Add v3 auth box (Auto/OAuth/Basic)
* Optional...)
> Remove check server type
> ------------------------
>
> Key: JBIDE-19897
> URL: https://issues.jboss.org/browse/JBIDE-19897
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Labels: connection_wizard
> Fix For: 4.3.0.Beta1
>
> Attachments: check-server-type-disabled.png
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years