[JBoss JIRA] (JBDS-3411) have installer build actually use M6 p2 product build
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3411?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3411:
--------------------------------
Story Points: 5
> have installer build actually use M6 p2 product build
> -----------------------------------------------------
>
> Key: JBDS-3411
> URL: https://issues.jboss.org/browse/JBDS-3411
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build, installer, updatesite
> Reporter: Max Rydahl Andersen
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 9.0.0.Beta1
>
>
> talking with [~prapicault] I learned that since M6 the following changes are required for proper working p2 product/osx build:
> {code}
> <products>
> <product>
> ...
> <rootFolders>
> <macosx>MyProduct.app</macosx>
> </rootFolders>
> </product>
> {code}
> And to use tycho 0.23-snapshot
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBDS-3410) devstudio not reading jbdevstudio.ini on osx
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3410?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3410:
--------------------------------
Story Points: 1
> devstudio not reading jbdevstudio.ini on osx
> --------------------------------------------
>
> Key: JBDS-3410
> URL: https://issues.jboss.org/browse/JBDS-3410
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 8.0.0.Alpha2
> Reporter: Max Rydahl Andersen
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 9.0.0.Beta1
>
>
> When starting on OSX it has noticable larger fonts than previous versions.
> It seems to be ignoring -Dorg.eclipse.swt.internal.carbon.smallFonts set in jbdevstudio.ini.
> comparing jbdevstudio8 vs 9 I see that in 8 the location was:
> studio/jbdevstudio.app/Contents/MacOS/jbdevstudio.ini
> but in 9 we have it at
> studio/jbdevstudio.ini
> so that could explain why it wont get picked up ?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-17696) Enabling Maven Dependency Management job waits forever
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17696?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-17696:
----------------------------------
Sprint: Sprint 20141112, Sprint to CR1 Release, Sprint #4 May 2015 (was: Sprint 20141112, Sprint to CR1 Release)
> 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)
10 years, 11 months
[JBoss JIRA] (JBDS-3411) have installer build actually use M6 p2 product build
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3411?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3411:
--------------------------------
Sprint: Sprint #2 April 2015
> have installer build actually use M6 p2 product build
> -----------------------------------------------------
>
> Key: JBDS-3411
> URL: https://issues.jboss.org/browse/JBDS-3411
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build, installer, updatesite
> Reporter: Max Rydahl Andersen
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 9.0.0.Beta1
>
>
> talking with [~prapicault] I learned that since M6 the following changes are required for proper working p2 product/osx build:
> {code}
> <products>
> <product>
> ...
> <rootFolders>
> <macosx>MyProduct.app</macosx>
> </rootFolders>
> </product>
> {code}
> And to use tycho 0.23-snapshot
--
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:
----------------------------------
Sprint: Sprint #3 May 2015
> 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