[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 devel_ack: + (was: ?)
Story Points: 1
> 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)
10 years, 11 months
[JBoss JIRA] (JBDS-2635) Installation sometimes fail with bundle was not found on Windows
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2635?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-2635:
--------------------------------
Sprint: Sprint 20141112, Sprint to CR1 Release (was: Sprint 20141112, Sprint to CR1 Release, Sprint #3 May 2015)
> Installation sometimes fail with bundle was not found on Windows
> ----------------------------------------------------------------
>
> Key: JBDS-2635
> URL: https://issues.jboss.org/browse/JBDS-2635
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 7.0.0.Beta1
> Environment: JBDS 7.0.0.Beta1, W8_64, Java 1.7.0_07
> Reporter: Jiri Peterka
> Assignee: Denis Golovin
> Fix For: 9.0.0.Beta1
>
> Attachments: 1369261136479.log, 1372203584223.log, 1372203590931.bak_0.log, 1372203590931.bak_1.log, 1372203590931.bak_2.log, 1372203590931.log, 1372355790692.log
>
>
> For the first time JBDS 7.0.0.Beta1 failed on windows8:
> {code}
> An error occurred while installing the items
> session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null --> [R]org.eclipse.jst.common.frameworks 1.1.601.v201208160700, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction).
> The artifact file for osgi.bundle,org.eclipse.jst.common.frameworks,1.1.601.v201208160700 was not found.
> Application failed, log file location: C:\vw\jbds-7.0.0-beta1\studio\p2\director\configuration\1369261136579.log
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-17281) parent/pom.xml build/plugins should reference plugins defined build/pluginManagement
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17281?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-17281:
----------------------------------
Story Points: 1
> parent/pom.xml build/plugins should reference plugins defined build/pluginManagement
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-17281
> URL: https://issues.jboss.org/browse/JBIDE-17281
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.2.0.Beta2
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Optional
> Fix For: 4.3.x
>
>
> The Idea is to move all what we have in build/plugins to build/pluginManagement and leave only plugins with groupId and artifactid in build/plugins. It would let to do further clean up and dcluttering in jbosstools modules like:
> - remove <version>${tychoVersion}</version>
> - move jacoco plugin to tests/pom.xml
> - move update site manipulations to site/pom.xml
> - etc
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19590) Update module's README.md files with information about dependencies to other modules
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19590?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-19590:
----------------------------------
Story Points: 3
> Update module's README.md files with information about dependencies to other modules
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-19590
> URL: https://issues.jboss.org/browse/JBIDE-19590
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Affects Versions: 4.3.0.Alpha2
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 4.3.0.Beta1
>
>
> For almost every JBoss Tools module there are three major steps to configure eclipse workspace for development:
> 1. Set up target platform in preferences
> 2. Import JBT module sources into workspace
> 3. Import required JBT module sources into worksapce
> (1) and (2) are well documented in README.md files, but (3) is not (see forum reference for jbosstools-hibernate as an example).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-18815) Include freemarker.jar in FreeMarker IDE as maven dependency
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18815?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-18815:
----------------------------------
Story Points: 1
> Include freemarker.jar in FreeMarker IDE as maven dependency
> ------------------------------------------------------------
>
> Key: JBIDE-18815
> URL: https://issues.jboss.org/browse/JBIDE-18815
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: freemarker
> Affects Versions: 4.2.0.Final
> Reporter: Daniel Dekany
> Assignee: Denis Golovin
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Beta1
>
>
> FreeMarker IDE still comes with FreeMarker 2.3.18 from 2011. As the plugin uses FreeMarker for parsing templates (for error markers), this means that no constructs introduced since then are recognized by it (there's a quite a few), and also that it doesn't benefit from the error message fixes/improvements made since then.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months