February 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-3608) update devstudio.redhat.com branding

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3608?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3608: ---------------------------------- Need to invoke the mighty UX powers of [~crobson] and co on this one. Current pages look like this: https://devstudio.jboss.com/9.0/stable/updates/ https://devstudio.jboss.com/9.0/development/updates/ https://devstudio.jboss.com/9.0/stable/updates/integration-stack/ etc. Meanwhile the root page [1] redirects here [2]. [1] https://devstudio.jboss.com/ [2] https://www.jboss.org/products/devstudio/overview/ Should we reskin [2] too? or redirect it to http://developers.redhat.com/products/devstudio/overview/ ? > update devstudio.redhat.com branding > ------------------------------------ > > Key: JBDS-3608 > URL: https://issues.jboss.org/browse/JBDS-3608 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: website > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.1.0.CR1 > > > update branding for developers.redhat.com -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3608) update devstudio.redhat.com branding

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3608?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3608: ----------------------------- Fix Version/s: 9.1.0.CR1 > update devstudio.redhat.com branding > ------------------------------------ > > Key: JBDS-3608 > URL: https://issues.jboss.org/browse/JBDS-3608 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: website > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > Fix For: 9.1.0.CR1 > > > update branding for developers.redhat.com -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3608) update devstudio.redhat.com branding

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3608?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3608: ----------------------------- Priority: Blocker (was: Critical) > update devstudio.redhat.com branding > ------------------------------------ > > Key: JBDS-3608 > URL: https://issues.jboss.org/browse/JBDS-3608 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: website > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.1.0.CR1 > > > update branding for developers.redhat.com -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3598) Error while building Jboss developer studio 9.1.0 Beta 2 from source

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3598?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3598: ---------------------------------- I've tested the "just use git init" solution and this is what happens: {code} wget http://download.jboss.org/jbosstools/static/mars/development/updates/core... unzip -d jboss-devstudio-9.1.0.Beta2-src jboss-devstudio-9.1.0.Beta2-src.zip cd jboss-devstudio-9.1.0.Beta2-src/jboss-devstudio-9.1.0.Beta2-src/jbdevstudio-product-e313a21b1694f8635fa056390641aeef6d44f198/ mvn clean install -Djbosstools-site=jar:file:///home/nboldt/tmp/jbosstools-4.3.1.Beta2-updatesite-core.zip\!/ ... [INFO] com.jboss.devstudio.core ........................... FAILURE [ 3.400 s] [ERROR] Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin (default-package-plugin) on project com.jboss.devstudio.core: Execution default-package-plugin of goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin failed. NullPointerException -> [Help 1] {code} So... git init doesn't work, even if you can use an offline JBT zip to resolve missing deps in the build reactor (eg., foundation.license.feature is required). > Error while building Jboss developer studio 9.1.0 Beta 2 from source > -------------------------------------------------------------------- > > Key: JBDS-3598 > URL: https://issues.jboss.org/browse/JBDS-3598 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.1.0.Beta2 > Environment: RHEL 7.1 PPC64le and Ubuntu x86_64 > Maven - 3.3.9 > JDK - 1.8 > Reporter: Deepali Chourasia > Assignee: Nick Boldt > Fix For: 9.1.0.CR1, 10.0.0.Alpha1 > > Attachments: Jboss_devstudio_9.1.0_Beta2_buildlog.txt > > > I have downloaded jboss-devstudio-9.1.0.Beta2-src.zip and am building it from source. > The build fails with the following error: > [ERROR] Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin (default-package-plugin) on project com.jboss.devstudio.core: Execution default-package-plugin of goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin failed: One of setGitDir or setWorkTree must be called. -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin (default-package-plugin) on project com.jboss.devstudio.core: Execution default-package-plugin of goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin failed: One of setGitDir or setWorkTree must be called. > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-package-plugin of goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin failed: One of setGitDir or setWorkTree must be called. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-471) Unify component versions

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-471?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBTIS-471 at 2/26/16 12:32 PM: ------------------------------------------------------------ In https://github.com/droolsjbpm/droolsjbpm-tools/commit/d96ca9479a8a70c8fe3... you hard coded a build number of "212" which is not a recommended practice. Either you omit that or you include a REAL value. Here's how you can omit it for local builds and include it for Jenkins builds: https://github.com/droolsjbpm/droolsjbpm-tools/pull/45 https://github.com/droolsjbpm/droolsjbpm-tools/pull/46 To build locally, just do: mvn clean install To build in Jenkins, you would configure the job to use a "hudson" profile; you can mock that up locally like this: mvn clean install -Phudson -DBUILD_NUMBER=1234 I'm assuming your job is http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/SOATo... but since the job is currently disabled I'm not sure if that's the correct job. Let me know if you need assistance reconfiguring the job after the above PRs are applied was (Author: nickboldt): In https://github.com/droolsjbpm/droolsjbpm-tools/commit/d96ca9479a8a70c8fe3... you hard coded a build number of "212" which is not a recommended practice. Either you omit that or you include a REAL value. Here's how you can omit it for local builds and include it for Jenkins builds: https://github.com/droolsjbpm/droolsjbpm-tools/pull/45 https://github.com/droolsjbpm/droolsjbpm-tools/pull/46 To build locally, just do: mvn clean install To build in Jenkins, you would configure the job to use a "hudson" profile; you can mock that up locally like this: mvn clean install -Phudson -DBUILD_NUMBER=1234 I'm assuming your job is http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/SOATo... so reconfiguring the job after the above PRs are applied should be pretty simple. Let me know if you need assistance with that. > Unify component versions > ------------------------ > > Key: JBTIS-471 > URL: https://issues.jboss.org/browse/JBTIS-471 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Affects Versions: 8.0.3.GA > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > Fix For: 4.3.0.Beta1 > > Attachments: junit4.8vs4.12.png > > > Currently, JBDS-IS 8.0.3.CR2 contains components with different version format such as > BPMN2 1.1.3.Final > Fuse 7.3.1.v20150728-1330-H54-Final > Teiid Designer 9.0.3.Final-v20150728-2029-B1148 > I suggest to use the format used by Teiid Designer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-471) Unify component versions

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-471?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-471: ---------------------------------- In https://github.com/droolsjbpm/droolsjbpm-tools/commit/d96ca9479a8a70c8fe3... you hard coded a build number of "212" which is not a recommended practice. Either you omit that or you include a REAL value. Here's how you can omit it for local builds and include it for Jenkins builds: https://github.com/droolsjbpm/droolsjbpm-tools/pull/45 https://github.com/droolsjbpm/droolsjbpm-tools/pull/46 To build locally, just do: mvn clean install To build in Jenkins, you would configure the job to use a "hudson" profile; you can mock that up locally like this: mvn clean install -Phudson -DBUILD_NUMBER=1234 I'm assuming your job is http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/SOATo... so reconfiguring the job after the above PRs are applied should be pretty simple. Let me know if you need assistance with that. > Unify component versions > ------------------------ > > Key: JBTIS-471 > URL: https://issues.jboss.org/browse/JBTIS-471 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Affects Versions: 8.0.3.GA > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > Fix For: 4.3.0.Beta1 > > Attachments: junit4.8vs4.12.png > > > Currently, JBDS-IS 8.0.3.CR2 contains components with different version format such as > BPMN2 1.1.3.Final > Fuse 7.3.1.v20150728-1330-H54-Final > Teiid Designer 9.0.3.Final-v20150728-2029-B1148 > I suggest to use the format used by Teiid Designer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3642) Installer is too opaque - need a debug/verbose mode to track progress and debug failures

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3642?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3642: ------------------------------- Target Release: 9.1.0.GA > Installer is too opaque - need a debug/verbose mode to track progress and debug failures > ---------------------------------------------------------------------------------------- > > Key: JBDS-3642 > URL: https://issues.jboss.org/browse/JBDS-3642 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > > The install.log created by the installer does not contain a detailed listing of all actions performed by the installer. Setting the install browser into a debug mode ( "set PDKI_DEBUG=true" ) generated additional information, but it is still node a detailed dump of all actions. Can we add a debug/verbose/trace mode? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3642) Installer is too opaque - need a debug/verbose mode to track progress and debug failures

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3642?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3642: ----------------------------- > Installer is too opaque - need a debug/verbose mode to track progress and debug failures > ---------------------------------------------------------------------------------------- > > Key: JBDS-3642 > URL: https://issues.jboss.org/browse/JBDS-3642 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > > The install.log created by the installer does not contain a detailed listing of all actions performed by the installer. Setting the install browser into a debug mode ( "set PDKI_DEBUG=true" ) generated additional information, but it is still node a detailed dump of all actions. Can we add a debug/verbose/trace mode? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3643) Installer - Should display a unique build identifier

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3643?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3643: ----------------------------- > Installer - Should display a unique build identifier > ----------------------------------------------------- > > Key: JBDS-3643 > URL: https://issues.jboss.org/browse/JBDS-3643 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > > This affects QE immediately, and may affect customers too. The installer UI should display a unique identifier (version number). Having a build number displayed in the UI will assist QE in testing as we iterate through the various versions of the installer. Thx! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3643) Installer - Should display a unique build identifier

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-3643: ---------------------------------- Summary: Installer - Should display a unique build identifier Key: JBDS-3643 URL: https://issues.jboss.org/browse/JBDS-3643 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Affects Versions: 9.1.0.GA Reporter: Len DiMaggio This affects QE immediately, and may affect customers too. The installer UI should display a unique identifier (version number). Having a build number displayed in the UI will assist QE in testing as we iterate through the various versions of the installer. Thx! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2016