April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3425) Disable Unintsaller generation for Mac OS X

by Denis Golovin (JIRA)

Denis Golovin created JBDS-3425: ----------------------------------- Summary: Disable Unintsaller generation for Mac OS X Key: JBDS-3425 URL: https://issues.jboss.org/browse/JBDS-3425 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: installer Affects Versions: 9.0.0.Alpha2 Reporter: Denis Golovin Assignee: Denis Golovin Uninstaller doesn't make sense for Mac platform, because it is literally just removing .app package. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[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 edited comment on JBDS-3411 at 4/27/15 3:55 PM: -------------------------------------------------------------- Removing uninstaller for Mac sounds good to me (see JBDS-3425). I can suppress Unintsaller generation for Mac platform. Izpack has configuration for that according to documentation. was (Author: dgolovin): Removing uninstaller for Mac sounds good to me. I can suppress Unintsaller generation for Mac platform. Izpack has configuration for that according to documentation. > 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)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3425) Disable Unintsaller generation for Mac OS X

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3425?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3425: ----------------------------- CDW pm_ack: ? CDW release: ? > Disable Unintsaller generation for Mac OS X > ------------------------------------------- > > Key: JBDS-3425 > URL: https://issues.jboss.org/browse/JBDS-3425 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > > Uninstaller doesn't make sense for Mac platform, because it is literally just removing .app package. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[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 commented on JBDS-3411: ------------------------------------- Removing uninstaller for Mac sounds good to me. I can suppress Unintsaller generation for Mac platform. Izpack has configuration for that according to documentation. > 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)

11 years

1
0
0 / 0

[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 commented on JBDS-3411: ------------------------------------- we can override tychoVersion for product build only so other jbt modulew would not be affected > 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)

11 years

1
0
0 / 0

[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 commented on JBDS-3411: ------------------------------------- It should probably be "/Library/Application Support/jbdevstudio" without .app suffix, I see all other apps have folders without it. But before we switch to using it I would go ahead and applied PR to have studio working under mac. Then we fix issues that requires fixes on installer and jddevstudio sides: 1. change runtimes folder location to "~/Library/Application Support/jbdevstudio9/runtimes" requires to change installer and runtime detection plugins 2. change runtime-locations.properties file and put it in the "~/Library/Application Support/jbdevstudio9/" requires to change installer and runtime detection plugins 3. Remove files none relevant for Mac installation form ibdevstudio.app 4. Move relevant files (as readme.txt" inside jbdevstudio.app as root files (?) > 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)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19717) Visual (diagram) editor for JSR-352 batch job files.

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19717?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19717: ----------------------------------- Labels: new_and_noteworthy (was: ) > Visual (diagram) editor for JSR-352 batch job files. > ---------------------------------------------------- > > Key: JBIDE-19717 > URL: https://issues.jboss.org/browse/JBIDE-19717 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: batch > Affects Versions: 4.3.0.Alpha1 > Reporter: Tomáš Milata > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.3.x > > > A *visual* editor which allows users to *graphically draw* structure of a JSR-352 batch job xml file. > Existing Sapphire model makes it easy to create a new Sapphire diagram editor that works together with the existing tree editor. > While the existing tree editor is efficient for editing properties of *single element*, the diagram editor should serve as a useful *visualization* tool that helps with orientation in complex flow *strucures*. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19717) Visual (diagram) editor for JSR-352 batch job files.

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19717?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-19717: -------------------------------------- Assignee: Alexey Kazakov > Visual (diagram) editor for JSR-352 batch job files. > ---------------------------------------------------- > > Key: JBIDE-19717 > URL: https://issues.jboss.org/browse/JBIDE-19717 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: batch > Affects Versions: 4.3.0.Alpha1 > Reporter: Tomáš Milata > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.3.x > > > A *visual* editor which allows users to *graphically draw* structure of a JSR-352 batch job xml file. > Existing Sapphire model makes it easy to create a new Sapphire diagram editor that works together with the existing tree editor. > While the existing tree editor is efficient for editing properties of *single element*, the diagram editor should serve as a useful *visualization* tool that helps with orientation in complex flow *strucures*. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-429) JBDSIS 8.0.2 component updates

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBTIS-429?page=com.atlassian.jira.plugin.... ] Brian Fitzpatrick commented on JBTIS-429: ----------------------------------------- Thanks Paul. > JBDSIS 8.0.2 component updates > ------------------------------ > > Key: JBTIS-429 > URL: https://issues.jboss.org/browse/JBTIS-429 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 8.0.1.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 8.0.2.GA > > > Update components for JBDSIS 8.0.2/ JBTIS 4.2.2 (Luna). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19717) Visual (diagram) editor for JSR-352 batch job files.

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19717?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19717: ----------------------------------- Fix Version/s: 4.3.x > Visual (diagram) editor for JSR-352 batch job files. > ---------------------------------------------------- > > Key: JBIDE-19717 > URL: https://issues.jboss.org/browse/JBIDE-19717 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: batch > Affects Versions: 4.3.0.Alpha1 > Reporter: Tomáš Milata > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.3.x > > > A *visual* editor which allows users to *graphically draw* structure of a JSR-352 batch job xml file. > Existing Sapphire model makes it easy to create a new Sapphire diagram editor that works together with the existing tree editor. > While the existing tree editor is efficient for editing properties of *single element*, the diagram editor should serve as a useful *visualization* tool that helps with orientation in complex flow *strucures*. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19717) Visual (diagram) editor for JSR-352 batch job files.

by Tomáš Milata (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19717?page=com.atlassian.jira.plugi... ] Tomáš Milata commented on JBIDE-19717: -------------------------------------- I already have a prototype and will be able to provide a pull request by 29/4. > Visual (diagram) editor for JSR-352 batch job files. > ---------------------------------------------------- > > Key: JBIDE-19717 > URL: https://issues.jboss.org/browse/JBIDE-19717 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: batch > Affects Versions: 4.3.0.Alpha1 > Reporter: Tomáš Milata > > A *visual* editor which allows users to *graphically draw* structure of a JSR-352 batch job xml file. > Existing Sapphire model makes it easy to create a new Sapphire diagram editor that works together with the existing tree editor. > While the existing tree editor is efficient for editing properties of *single element*, the diagram editor should serve as a useful *visualization* tool that helps with orientation in complex flow *strucures*. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19718) No source zip produced when buildinfo.json can't be resolved

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-19718: ---------------------------------- Summary: No source zip produced when buildinfo.json can't be resolved Key: JBIDE-19718 URL: https://issues.jboss.org/browse/JBIDE-19718 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.3.0.Alpha2 Reporter: Nick Boldt >From the latest master build: http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui... {code} [INFO] --- repository-utils:0.22.1-SNAPSHOT:generate-repository-facade (generate-facade) @ org.jboss.tools.site.core --- [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bas... [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-ser... [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-ope... [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-jst... [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bro... [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-aer... [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-jav... [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-web... [WARNING] Could not access build info at http://download.jboss.org/jbosstools/updates/stable/luna/core/portlet/bui... [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-vpe... [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-arq... [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-for... [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-liv... [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-cen... [WARNING] Could not access build info at http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2... [WARNING] Could not access build info at http://download.jboss.org/jbosstools/updates/stable/luna/core/freemarker/... [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bir... [WARNING] Could not access build info at http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... [INFO] Building zip: /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/org.jboss.tools.site.core-4.3.0-SNAPSHOT.zip {code} Seems the problem is twofold: a) when no json files are found, we should fall back to another URL. (I think I might have an open PR for this.) For example, instead of http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-ope... we should be looking at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-ope... b) the generated sources zip needs to exist even it's empty (?) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19718) No source zip produced when buildinfo.json can't be resolved

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19718?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-19718: ---------------------------------- Assignee: Nick Boldt > No source zip produced when buildinfo.json can't be resolved > ------------------------------------------------------------ > > Key: JBIDE-19718 > URL: https://issues.jboss.org/browse/JBIDE-19718 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > From the latest master build: > http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui... > {code} > [INFO] --- repository-utils:0.22.1-SNAPSHOT:generate-repository-facade (generate-facade) @ org.jboss.tools.site.core --- > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bas... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-ser... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-ope... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-jst... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bro... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-aer... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-jav... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-web... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/updates/stable/luna/core/portlet/bui... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-vpe... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-arq... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-for... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-liv... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-cen... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/updates/stable/luna/core/freemarker/... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bir... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... > [INFO] Building zip: /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/org.jboss.tools.site.core-4.3.0-SNAPSHOT.zip > {code} > Seems the problem is twofold: > a) when no json files are found, we should fall back to another URL. (I think I might have an open PR for this.) > For example, instead of http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-ope... we should be looking at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-ope... > b) the generated sources zip needs to exist even it's empty (?) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19718) No source zip produced when buildinfo.json can't be resolved

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19718?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19718: ------------------------------- Fix Version/s: 4.3.0.Beta1 > No source zip produced when buildinfo.json can't be resolved > ------------------------------------------------------------ > > Key: JBIDE-19718 > URL: https://issues.jboss.org/browse/JBIDE-19718 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > From the latest master build: > http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui... > {code} > [INFO] --- repository-utils:0.22.1-SNAPSHOT:generate-repository-facade (generate-facade) @ org.jboss.tools.site.core --- > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bas... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-ser... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-ope... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-jst... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bro... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-aer... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-jav... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-web... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/updates/stable/luna/core/portlet/bui... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-vpe... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-arq... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-for... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-liv... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-cen... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/updates/stable/luna/core/freemarker/... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bir... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... > [INFO] Building zip: /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/org.jboss.tools.site.core-4.3.0-SNAPSHOT.zip > {code} > Seems the problem is twofold: > a) when no json files are found, we should fall back to another URL. (I think I might have an open PR for this.) > For example, instead of http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-ope... we should be looking at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-ope... > b) the generated sources zip needs to exist even it's empty (?) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19718) No source zip produced when buildinfo.json can't be resolved

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19718?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19718: ------------------------------- Priority: Blocker (was: Major) > No source zip produced when buildinfo.json can't be resolved > ------------------------------------------------------------ > > Key: JBIDE-19718 > URL: https://issues.jboss.org/browse/JBIDE-19718 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.0.Beta1 > > > From the latest master build: > http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui... > {code} > [INFO] --- repository-utils:0.22.1-SNAPSHOT:generate-repository-facade (generate-facade) @ org.jboss.tools.site.core --- > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bas... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-ser... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-ope... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-jst... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bro... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-aer... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-jav... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-web... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/updates/stable/luna/core/portlet/bui... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-vpe... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-arq... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-for... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-liv... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-cen... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/updates/stable/luna/core/freemarker/... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bir... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... > [INFO] Building zip: /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/org.jboss.tools.site.core-4.3.0-SNAPSHOT.zip > {code} > Seems the problem is twofold: > a) when no json files are found, we should fall back to another URL. (I think I might have an open PR for this.) > For example, instead of http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-ope... we should be looking at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-ope... > b) the generated sources zip needs to exist even it's empty (?) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19717) Visual (diagram) editor for JSR-352 batch job files.

by Tomáš Milata (JIRA)

Tomáš Milata created JBIDE-19717: ------------------------------------ Summary: Visual (diagram) editor for JSR-352 batch job files. Key: JBIDE-19717 URL: https://issues.jboss.org/browse/JBIDE-19717 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: batch Affects Versions: 4.3.0.Alpha1 Reporter: Tomáš Milata A *visual* editor which allows users to *graphically draw* structure of a JSR-352 batch job xml file. Existing Sapphire model makes it easy to create a new Sapphire diagram editor that works together with the existing tree editor. While the existing tree editor is efficient for editing properties of *single element*, the diagram editor should serve as a useful *visualization* tool that helps with orientation in complex flow *strucures*. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19601) Explorer: Resources cannot be listed when using latest OpenShift origin v3 code

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19601?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19601: ------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > Explorer: Resources cannot be listed when using latest OpenShift origin v3 code > ------------------------------------------------------------------------------- > > Key: JBIDE-19601 > URL: https://issues.jboss.org/browse/JBIDE-19601 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.3.0.Beta1 > > Attachments: connection-refused.png > > > When using the latest origin code from github one can connect but once the connection wizard is closed an error dialog pops up telling you that the connection was refused -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19705) [FeedHenry] Cordova App is not a valid application id, cannot run on android

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19705?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19705: ------------------------------------ Assign to Gorkem and slip to Beta1. > [FeedHenry] Cordova App is not a valid application id, cannot run on android > ---------------------------------------------------------------------------- > > Key: JBIDE-19705 > URL: https://issues.jboss.org/browse/JBIDE-19705 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Pavol Srna > Assignee: Gorkem Ercan > Priority: Critical > Fix For: 4.3.0.Beta1 > > Attachments: Screenshot 2015-04-24 13.01.07.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19705) [FeedHenry] Cordova App is not a valid application id, cannot run on android

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19705?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19705: ------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > [FeedHenry] Cordova App is not a valid application id, cannot run on android > ---------------------------------------------------------------------------- > > Key: JBIDE-19705 > URL: https://issues.jboss.org/browse/JBIDE-19705 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Pavol Srna > Assignee: Gorkem Ercan > Priority: Critical > Fix For: 4.3.0.Beta1 > > Attachments: Screenshot 2015-04-24 13.01.07.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19705) [FeedHenry] Cordova App is not a valid application id, cannot run on android

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19705?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-19705: ---------------------------------- Assignee: Gorkem Ercan > [FeedHenry] Cordova App is not a valid application id, cannot run on android > ---------------------------------------------------------------------------- > > Key: JBIDE-19705 > URL: https://issues.jboss.org/browse/JBIDE-19705 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Pavol Srna > Assignee: Gorkem Ercan > Priority: Critical > Fix For: 4.3.0.Beta1 > > Attachments: Screenshot 2015-04-24 13.01.07.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19190) migrate VersionWatch to jbosstools-* repo

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19190?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19190: ------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > migrate VersionWatch to jbosstools-* repo > ----------------------------------------- > > Key: JBIDE-19190 > URL: https://issues.jboss.org/browse/JBIDE-19190 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Jiri Peterka > Priority: Minor > Fix For: 4.3.0.Beta1 > > > 0. decide where to put this... under jbosstools-ci or some new repo? Create a new component in JIRA accordingly. > 1. remove all refs to QA Jenkins file paths to make this more generic > 2. migrate those internal file paths into jenkins config.xml files > 3. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches -- pre-existing doc here: > http://download.jboss.org/jbosstools/updates/scripted-installation/ > https://devstudio.redhat.com/download/scripted-install/ > 4. test #3 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3357) Investigate implications of Forge 1 removal

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3357?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3357: ----------------------------- Fix Version/s: 9.0.0.Beta1 (was: 9.0.0.Alpha2) > Investigate implications of Forge 1 removal > ------------------------------------------- > > Key: JBDS-3357 > URL: https://issues.jboss.org/browse/JBDS-3357 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: forge > Affects Versions: 9.0.0.Alpha1 > Reporter: Koen Aers > Assignee: Koen Aers > Priority: Critical > Fix For: 9.0.0.Beta1 > > > F1 was removed in 9.0.0.Alpha1 (see JBIDE-19101). Investigation is needed to see if any additional action is needed for the quickstarts and ticket monster to continue to work properly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3208) reorg/refactor directories for consistency across JBT/JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3208: ----------------------------- Fix Version/s: (was: 9.0.0.Alpha2) > reorg/refactor directories for consistency across JBT/JBDS > ---------------------------------------------------------- > > Key: JBDS-3208 > URL: https://issues.jboss.org/browse/JBDS-3208 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.0.0.Beta1 > > > Be it resolved - we should reorg directories for consistency across JBT/JBDS: > Latest suggestion: > * /\{mars,9.0}/ > ** /\{{color:red}snapshots{color},{color:orange}staging{color},{color:blue}development{color},{color:green}stable{color}\}/ > *** /*updates*/ > **** /\{requirements, jbosstoolstarget,jbdevstudiotarget, core,coretests,webtools,hibernatetools, discovery, central,earlyaccess, integration-stack,integration-stack-earlyaccess}/ > ***** /<build-version = 4.3.0.Alpha1, 4.3.0.Final, 4.41.\*, 4.50.\*...>/ > *** /*builds*/ > **** /<job-name>/ > ***** /{<pull-request-version = PR123, PR124, PR125...>, <build-version = B123, B124, B125...>}/ > --- > Older idea: > {code} > <download.jboss.org,devstudio.redhat.com> > <earlyaccess,updates,discovery>/<mars,9.0> > /snapshots [replace nightly] > /staging [rename content for QE, moves to development when approved] > /development > /stable (updates/<mars,9.0>/stable is a pointer back into parent folder so published URL can be simpler > drop /integration (not used) > builds/<jobname>/<buildid> > builds/<jobname>/composite*.xml for last N builds > targetplatforms/<type>/<version> > {code} > Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112 > This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970. > [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2.... > [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3384) Investigate how the terminal changes in Mars will/should affect us

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3384?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3384: ----------------------------- Fix Version/s: 9.0.0.Beta1 (was: 9.0.0.Alpha2) > Investigate how the terminal changes in Mars will/should affect us > ------------------------------------------------------------------- > > Key: JBDS-3384 > URL: https://issues.jboss.org/browse/JBDS-3384 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: build, forge, openshift > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Blocker > Fix For: 9.0.0.Beta1 > > > Terminal (console) support in eclipse mars is changing and we should > make sure we adjust for it. > Some changes this is doing at eclipse is documented at https://dev.eclipse.org/mhonarc/lists/epp-dev/msg03448.html > Hopefully this can be used to remove redundant/duplicate terminals and just have *one* instead of the 2.5 we got now. > This *probably* going to affect not only packaging of JBDS (remove old terminals, add the new one), but Forge ([~koen.aers]) probably could benefit from this and Fuse ([~lhein]) should stop extending the old terminals and use the new. > As we find what it entails we should link those issues to this jira. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19670) Webservices and Rest New and Noteworthy for 4.3.0.Alpha2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19670?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-19670. ------------------------------------ Resolution: Rejected Looks like no N&N for Alpha2. > Webservices and Rest New and Noteworthy for 4.3.0.Alpha2 > -------------------------------------------------------- > > Key: JBIDE-19670 > URL: https://issues.jboss.org/browse/JBIDE-19670 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Alexey Kazakov > Assignee: Brian Fitzpatrick > Priority: Critical > Fix For: 4.3.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Webservices and Rest is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Webservices and Rest by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19670) Webservices and Rest New and Noteworthy for 4.3.0.Alpha2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19670?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-19670. ---------------------------------- > Webservices and Rest New and Noteworthy for 4.3.0.Alpha2 > -------------------------------------------------------- > > Key: JBIDE-19670 > URL: https://issues.jboss.org/browse/JBIDE-19670 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Alexey Kazakov > Assignee: Brian Fitzpatrick > Priority: Critical > Fix For: 4.3.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Webservices and Rest is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Webservices and Rest by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19716) JBoss Tools 4.3.0.Alpha2 does not recognize an installed Android SDK

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19716?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-19716: --------------------------------- Attachment: Android_SDK.png > JBoss Tools 4.3.0.Alpha2 does not recognize an installed Android SDK > -------------------------------------------------------------------- > > Key: JBIDE-19716 > URL: https://issues.jboss.org/browse/JBIDE-19716 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Attachments: Android_SDK.png > > > With 4.3.0.Alpha2: > * Install Android SDK from: http://dl.google.com/android/android-sdk_r24.1.2-linux.tgz > * Attempt to configure the installed SDK in Perferences->Hybrid Mobile->Android > * See the attached screen shot for the "Not a valid Android SDK directory" error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19716) JBoss Tools 4.3.0.Alpha2 does not recognize an installed Android SDK

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19716?page=com.atlassian.jira.plugi... ] Len DiMaggio reassigned JBIDE-19716: ------------------------------------ Assignee: Mickael Istria > JBoss Tools 4.3.0.Alpha2 does not recognize an installed Android SDK > -------------------------------------------------------------------- > > Key: JBIDE-19716 > URL: https://issues.jboss.org/browse/JBIDE-19716 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Mickael Istria > Attachments: Android_SDK.png > > > With 4.3.0.Alpha2: > * Install Android SDK from: http://dl.google.com/android/android-sdk_r24.1.2-linux.tgz > * Attempt to configure the installed SDK in Perferences->Hybrid Mobile->Android > * See the attached screen shot for the "Not a valid Android SDK directory" error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19716) JBoss Tools 4.3.0.Alpha2 does not recognize an installed Android SDK

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-19716: ------------------------------------ Summary: JBoss Tools 4.3.0.Alpha2 does not recognize an installed Android SDK Key: JBIDE-19716 URL: https://issues.jboss.org/browse/JBIDE-19716 Project: Tools (JBoss Tools) Issue Type: Bug Components: cordovasim Affects Versions: 4.3.0.Alpha2 Reporter: Len DiMaggio With 4.3.0.Alpha2: * Install Android SDK from: http://dl.google.com/android/android-sdk_r24.1.2-linux.tgz * Attempt to configure the installed SDK in Perferences->Hybrid Mobile->Android * See the attached screen shot for the "Not a valid Android SDK directory" error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19049) Enable JBoss servers to run with java 9

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19049?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19049: ------------------------------------- Correct. Step 0) Use latest code from master. I do worry, however, that this will lead to conflicting requests from downstream consumers (like Lars) who only want compatible VMs present, and want these non-supported JRE's removed from the list. For this reason, I added a protected boolean method where subclasses can override this support and only show strictly compatible ones. See AbstractJREComposite.includeIncompatibleJREs(). So Fuse / etc can override this and return false if they wish. > Enable JBoss servers to run with java 9 > --------------------------------------- > > Key: JBIDE-19049 > URL: https://issues.jboss.org/browse/JBIDE-19049 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.2.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: Java9 > Fix For: 4.3.0.Beta1 > > > I briefly tried to use java 9 for our tooling and to run servers. > I downloaded it from here: > https://jdk9.java.net/download/ > {code} > nattura:8.0.2 rasp$ java -version > java version "1.9.0-ea" > Java(TM) SE Runtime Environment (build 1.9.0-ea-b45) > Java HotSpot(TM) 64-Bit Server VM (build 1.9.0-ea-b45, mixed mode) > {code} > I use OS X 10.10 Yosemite. > There are a couple of problems: > 1. When I add a WildFly 8.2 server into JBDS 8.0.2, I cannot change the runtime to use java 9 - it seems we restrict that. > 2. Even if I could, we need to make sure -XX:MaxPermSize is not used in the server launch command. When I tried to run WildFly 8.2 from the terminal, it wouldn't work unless I removed the max perm size argument. Apparently java 9 does not just ignore this parameter (as java 8 did), but it does not allow it at all. > {code} > nattura:bin rasp$ ./standalone.sh > ========================================================================= > JBoss Bootstrap Environment > JBOSS_HOME: /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final > JAVA: /Library/Java/JavaVirtualMachines/jdk1.9.0.jdk/Contents/Home/bin/java > JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true > ========================================================================= > Unrecognized VM option 'MaxPermSize=256m' > Error: Could not create the Java Virtual Machine. > Error: A fatal exception has occurred. Program will exit. > {code} > Of course it's questionable if we should allow java 9 for current servers at all as they don't support it officially. But I would say there is no need to restrict it if it works. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19049) Enable JBoss servers to run with java 9

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19049?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19049: --------------------------------------------- I assume you are missing a step 0) use latest code from master, right ? If the above works thats great! > Enable JBoss servers to run with java 9 > --------------------------------------- > > Key: JBIDE-19049 > URL: https://issues.jboss.org/browse/JBIDE-19049 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.2.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: Java9 > Fix For: 4.3.0.Beta1 > > > I briefly tried to use java 9 for our tooling and to run servers. > I downloaded it from here: > https://jdk9.java.net/download/ > {code} > nattura:8.0.2 rasp$ java -version > java version "1.9.0-ea" > Java(TM) SE Runtime Environment (build 1.9.0-ea-b45) > Java HotSpot(TM) 64-Bit Server VM (build 1.9.0-ea-b45, mixed mode) > {code} > I use OS X 10.10 Yosemite. > There are a couple of problems: > 1. When I add a WildFly 8.2 server into JBDS 8.0.2, I cannot change the runtime to use java 9 - it seems we restrict that. > 2. Even if I could, we need to make sure -XX:MaxPermSize is not used in the server launch command. When I tried to run WildFly 8.2 from the terminal, it wouldn't work unless I removed the max perm size argument. Apparently java 9 does not just ignore this parameter (as java 8 did), but it does not allow it at all. > {code} > nattura:bin rasp$ ./standalone.sh > ========================================================================= > JBoss Bootstrap Environment > JBOSS_HOME: /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final > JAVA: /Library/Java/JavaVirtualMachines/jdk1.9.0.jdk/Contents/Home/bin/java > JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true > ========================================================================= > Unrecognized VM option 'MaxPermSize=256m' > Error: Could not create the Java Virtual Machine. > Error: A fatal exception has occurred. Program will exit. > {code} > Of course it's questionable if we should allow java 9 for current servers at all as they don't support it officially. But I would say there is no need to restrict it if it works. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19681) OpenShift New and Noteworthy for 4.3.0.Alpha2

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19681?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19681: ------------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-website/pull/383, https://github.com/jbosstools/jbosstools-website/pull/385 (was: https://github.com/jbosstools/jbosstools-website/pull/383) > OpenShift New and Noteworthy for 4.3.0.Alpha2 > --------------------------------------------- > > Key: JBIDE-19681 > URL: https://issues.jboss.org/browse/JBIDE-19681 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Alexey Kazakov > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.3.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If OpenShift is not listed here check if there are issues that should be added and add them. > Document the ones relevant for OpenShift by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3424) EasyImport is missing from JBDS 9.0.0.Alpha2

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3424?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3424: ------------------------------- Attachment: JBT_423_Alpha2_easyimport3.png JBT_423_Alpha2_easyimport2.png JBT_430_Alpha2_easyimport1.png > EasyImport is missing from JBDS 9.0.0.Alpha2 > -------------------------------------------- > > Key: JBDS-3424 > URL: https://issues.jboss.org/browse/JBDS-3424 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha2 > Environment: Version: 9.0.0.Alpha2 > Build id: Alpha2-v20150405-1144-B2918 > Build date: 20150405-1144 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Attachments: JBT_423_Alpha2_easyimport2.png, JBT_423_Alpha2_easyimport3.png, JBT_430_Alpha2_easyimport1.png > > > See attached screenshots from JBoss Tools 4.3.0.Alpha2 - the corresponding import menu entries are missing from JBDS 9.0.0.Alpha2 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3424) EasyImport is missing from JBDS 9.0.0.Alpha2

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3424?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3424: ----------------------------- CDW docs_ack: ? CDW devel_ack: ? CDW pm_ack: + CDW qa_ack: ? CDW release: ? > EasyImport is missing from JBDS 9.0.0.Alpha2 > -------------------------------------------- > > Key: JBDS-3424 > URL: https://issues.jboss.org/browse/JBDS-3424 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Nick Boldt > > See attached screenshots from JBoss Tools 4.3.0.Alpha2 - the corresponding import menu entries are missing from JBDS 9.0.0.Alpha2 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3424) EasyImport is missing from JBDS 9.0.0.Alpha2

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-3424: ---------------------------------- Summary: EasyImport is missing from JBDS 9.0.0.Alpha2 Key: JBDS-3424 URL: https://issues.jboss.org/browse/JBDS-3424 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: build Affects Versions: 9.0.0.Alpha2 Reporter: Len DiMaggio Assignee: Nick Boldt See attached screenshots from JBoss Tools 4.3.0.Alpha2 - the corresponding import menu entries are missing from JBDS 9.0.0.Alpha2 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3424) EasyImport is missing from JBDS 9.0.0.Alpha2

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3424?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3424: ------------------------------- Environment: Version: 9.0.0.Alpha2 Build id: Alpha2-v20150405-1144-B2918 Build date: 20150405-1144 > EasyImport is missing from JBDS 9.0.0.Alpha2 > -------------------------------------------- > > Key: JBDS-3424 > URL: https://issues.jboss.org/browse/JBDS-3424 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha2 > Environment: Version: 9.0.0.Alpha2 > Build id: Alpha2-v20150405-1144-B2918 > Build date: 20150405-1144 > Reporter: Len DiMaggio > Assignee: Nick Boldt > > See attached screenshots from JBoss Tools 4.3.0.Alpha2 - the corresponding import menu entries are missing from JBDS 9.0.0.Alpha2 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-429) JBDSIS 8.0.2 component updates

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-429?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-429: ---------------------------------- You're still good [~bfitzpat] for 8.0.2 - this is just a first build. I'll pick up SwitchYard for the 8.0.2.CR1 later on. > JBDSIS 8.0.2 component updates > ------------------------------ > > Key: JBTIS-429 > URL: https://issues.jboss.org/browse/JBTIS-429 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 8.0.1.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 8.0.2.GA > > > Update components for JBDSIS 8.0.2/ JBTIS 4.2.2 (Luna). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-429) JBDSIS 8.0.2 component updates

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBTIS-429?page=com.atlassian.jira.plugin.... ] Brian Fitzpatrick commented on JBTIS-429: ----------------------------------------- It's been held up to at least the end of the week. Go ahead without me and let's shoot for a SY update for an 8.0.3? > JBDSIS 8.0.2 component updates > ------------------------------ > > Key: JBTIS-429 > URL: https://issues.jboss.org/browse/JBTIS-429 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 8.0.1.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 8.0.2.GA > > > Update components for JBDSIS 8.0.2/ JBTIS 4.2.2 (Luna). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19665) hibernate New and Noteworthy for 4.3.0.Alpha2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19665?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-19665: -------------------------------------- Assignee: Koen Aers > hibernate New and Noteworthy for 4.3.0.Alpha2 > --------------------------------------------- > > Key: JBIDE-19665 > URL: https://issues.jboss.org/browse/JBIDE-19665 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Alexey Kazakov > Assignee: Koen Aers > Priority: Critical > Fix For: 4.3.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If hibernate is not listed here check if there are issues that should be added and add them. > Document the ones relevant for hibernate by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19680) server New and Noteworthy for 4.3.0.Alpha2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19680?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-19680: -------------------------------------- Assignee: Rob Stryker > server New and Noteworthy for 4.3.0.Alpha2 > ------------------------------------------ > > Key: JBIDE-19680 > URL: https://issues.jboss.org/browse/JBIDE-19680 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives, jmx, server > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.3.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If server is not listed here check if there are issues that should be added and add them. > Document the ones relevant for server by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19602) "Warning: NLS unused message" in org.jboss.tools.common.jdt.debug

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19602?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-19602. --------------------------------- Fix Version/s: 4.3.0.Beta1 Resolution: Done Cleaned up the rogue strings. > "Warning: NLS unused message" in org.jboss.tools.common.jdt.debug > ----------------------------------------------------------------- > > Key: JBIDE-19602 > URL: https://issues.jboss.org/browse/JBIDE-19602 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.Alpha2 > Reporter: Denis Golovin > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > {code}Warning: NLS unused message: updatePeriodNotEnteredMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: illegalUpdatePeriodMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: updatePeriodOutOfRangeMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: loadAgentFailedMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: agentJarNotFoundMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: agentJarFoundMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: corePluginNoFoundMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: charsetNotSupportedMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: readInputStreamFailedMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: updateTimerCanceledMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: getMonitoredJvmFailedMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: getLocalConnectorAddressFailedMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: connectTargetJvmFailedMsg in: org.jboss.tools.common.jdt.debug.messages > Warning: NLS unused message: fileNotFoundMsg in: org.jboss.tools.common.jdt.debug.messages > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18570) Creating EJB 3.x bean is asking EJB 2.x values

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18570?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-18570. --------------------------------- Resolution: Won't Fix I've misidentified the cause here. These are actually the WTP wizards, not our JBT wizards which have already been removed. The section is an optional dropdown. It is clearly labeled EJB 2.x and is designed in such a way to be minimally intrusive. We won't be fixing this. > Creating EJB 3.x bean is asking EJB 2.x values > ---------------------------------------------- > > Key: JBIDE-18570 > URL: https://issues.jboss.org/browse/JBIDE-18570 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: ejb3, upstream > Reporter: Arun Gupta > Assignee: Rob Stryker > Fix For: 4.3.x > > Attachments: Screen Shot 2014-10-09 at 9.41.39 pm.png > > > Creating a singleton EJB using 3.x wizard and its asking for home and component interfaces from 2.x. This is confusing and redundant. > Image coming in attachment next. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18772: ------------------------------------ {quote}Why do we need to override these things - can't those few ones be customized to have that set properly ?{quote} You say "customized" I say "overridden". Same thing - in either case there's a default in parent pom, and a new value in the special root poms that need something else. Like we do for jbdevstudio-product/pom.xml, for example. {quote}About copy-or-rename stuff, we do we even have such step ? why don't we actually produce what we want/need ? {quote} Yes. Please re-read all the links to example I provided above, 4 days ago. https://issues.jboss.org/browse/JBIDE-18772?focusedCommentId=13061673&pag... > Include publish.sh in parent pom as versioned maven dependency > -------------------------------------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.0.Beta1 > > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19049) Enable JBoss servers to run with java 9

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19049?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-19049. --------------------------------- Fix Version/s: 4.3.0.Beta1 (was: LATER) Resolution: Done To properly run a wf 8.x server using Java9: 1) Open server wizard 2) Create new server 3) Select new runtime 4) Note that java9 comes up in the list now. 5) Note that selecting the Java9 JRE / JDK will also show a warning about compatibility 6) Complete creating your server 7) Open the server editor 8) Open the launch configuration 9) Remove the flags for -XX:MaxPermSize from the VM Args 10) Save the launch config 11) Start the server. Everything works. woohoo. > Enable JBoss servers to run with java 9 > --------------------------------------- > > Key: JBIDE-19049 > URL: https://issues.jboss.org/browse/JBIDE-19049 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.2.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: Java9 > Fix For: 4.3.0.Beta1 > > > I briefly tried to use java 9 for our tooling and to run servers. > I downloaded it from here: > https://jdk9.java.net/download/ > {code} > nattura:8.0.2 rasp$ java -version > java version "1.9.0-ea" > Java(TM) SE Runtime Environment (build 1.9.0-ea-b45) > Java HotSpot(TM) 64-Bit Server VM (build 1.9.0-ea-b45, mixed mode) > {code} > I use OS X 10.10 Yosemite. > There are a couple of problems: > 1. When I add a WildFly 8.2 server into JBDS 8.0.2, I cannot change the runtime to use java 9 - it seems we restrict that. > 2. Even if I could, we need to make sure -XX:MaxPermSize is not used in the server launch command. When I tried to run WildFly 8.2 from the terminal, it wouldn't work unless I removed the max perm size argument. Apparently java 9 does not just ignore this parameter (as java 8 did), but it does not allow it at all. > {code} > nattura:bin rasp$ ./standalone.sh > ========================================================================= > JBoss Bootstrap Environment > JBOSS_HOME: /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final > JAVA: /Library/Java/JavaVirtualMachines/jdk1.9.0.jdk/Contents/Home/bin/java > JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true > ========================================================================= > Unrecognized VM option 'MaxPermSize=256m' > Error: Could not create the Java Virtual Machine. > Error: A fatal exception has occurred. Program will exit. > {code} > Of course it's questionable if we should allow java 9 for current servers at all as they don't support it officially. But I would say there is no need to restrict it if it works. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-15884) Allow the runBrowserSim command to accept a URL as a parameter

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15884?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-15884: ------------------------------------- Pushed to master. Steps to verify: - BrowserSim command (with and without *url* parameter - @see comment above) must work with cheat sheets on every perspective > Allow the runBrowserSim command to accept a URL as a parameter > -------------------------------------------------------------- > > Key: JBIDE-15884 > URL: https://issues.jboss.org/browse/JBIDE-15884 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 4.1.0.Final > Reporter: Vineet Reynolds > Assignee: Ilya Buziuk > Priority: Minor > Fix For: 4.3.0.Beta1 > > > Apologies for not setting the Affect version; I'm not sure which JBIDE version is affected. > When creating a cheatsheet in JBDS 7.0.1.GA (for JDF-497), I'm using the {{org.jboss.tools.vpe.browsersim.eclipse.commands.runBrowserSim}} command in the cheatsheet. This launches BrowserSim successfully (when I'm in the correct perspective). However, BrowserSim navigates to about:blank so the cheatsheet requires users to manually key in the URL. It would be nice to have the launch URL specified as a configurable value. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19715) Get rid of "fullSite", stick with "repository"

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19715?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19715: ---------------------------------------- Branding and references are part of the generate-repository-facade mojo, which is not related to fullSite. The create-full-site mojo doesn't produce anything that isn't in the buildinfo.json. I'd be in favour of getting rid of it, and put metadata and zips directly in the repository/ folder, instead of maintaining an overhead hierarchy besides of the repostory.. I checked Mojos and scripts and the only references to fullSite are only in unused or useless mojos, and in comments in rsync.sh. It seems to be used only in CI job configuration, where we could publish repository/ as easily. > Get rid of "fullSite", stick with "repository" > ---------------------------------------------- > > Key: JBIDE-19715 > URL: https://issues.jboss.org/browse/JBIDE-19715 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Mickael Istria > > Currently, some builds such as aggregate create a "site/target/fullSite" folder, which is aimed at being deployed. However, it would be simpler to populate the site/target/repository folder, so it would be only one directory to move, and the same one for all builds. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3423) JBDS update site has blue JBT branding instead of red JBDS branding

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3423?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3423: -------------------------------------- Actually, it's not the create-full-site mojo which generates the index.html, but the generate-repository-facade mojo, which can be customized to use other index.html and CSS resource remplate. The create-full-site mojo doesn't produce anything that isn't in the buildinfo.json. I'd be in favour of getting rid of it, and put metadata directly in the repository/ folder, instead of maintaining an overhead hierarchy besides of the repostory. > JBDS update site has blue JBT branding instead of red JBDS branding > ------------------------------------------------------------------- > > Key: JBDS-3423 > URL: https://issues.jboss.org/browse/JBDS-3423 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 9.0.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 9.0.0.Beta1 > > > Comparing these sites: > http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_ma... (published w/ publish.sh) > https://devstudio.redhat.com/9.0/snapshots/updates/core/master/ (published w/ rsync.sh) > We see that some time after build 3003, the branding for the site was lost. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19681) OpenShift New and Noteworthy for 4.3.0.Alpha2

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19681?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-19681. ------------------------------------ > OpenShift New and Noteworthy for 4.3.0.Alpha2 > --------------------------------------------- > > Key: JBIDE-19681 > URL: https://issues.jboss.org/browse/JBIDE-19681 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Alexey Kazakov > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.3.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If OpenShift is not listed here check if there are issues that should be added and add them. > Document the ones relevant for OpenShift by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-429) JBDSIS 8.0.2 component updates

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-429?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-429: ---------------------------------- Hey [~bfitzpat] - I've got what I need to spin an initial JBTIS 4.2.2. Do you think you'll have a SwitchYard update soon? > JBDSIS 8.0.2 component updates > ------------------------------ > > Key: JBTIS-429 > URL: https://issues.jboss.org/browse/JBTIS-429 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 8.0.1.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 8.0.2.GA > > > Update components for JBDSIS 8.0.2/ JBTIS 4.2.2 (Luna). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19679) Forge New and Noteworthy for 4.3.0.Alpha2

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19679?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-19679. ------------------------------ Verified. > Forge New and Noteworthy for 4.3.0.Alpha2 > ----------------------------------------- > > Key: JBIDE-19679 > URL: https://issues.jboss.org/browse/JBIDE-19679 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Alexey Kazakov > Assignee: George Gastaldi > Priority: Critical > Fix For: 4.3.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Forge is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Forge by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19671) Aerogear New and Noteworthy for 4.3.0.Alpha2

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19671?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-19671. ------------------------------ Verified. > Aerogear New and Noteworthy for 4.3.0.Alpha2 > -------------------------------------------- > > Key: JBIDE-19671 > URL: https://issues.jboss.org/browse/JBIDE-19671 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid > Reporter: Alexey Kazakov > Assignee: Gorkem Ercan > Priority: Critical > Fix For: 4.3.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Aerogear is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Aerogear by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19462) [FeedHenry] Cannot cancel import

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19462?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-19462. ------------------------------ Verified in JBT 4.3.0.Alpha2 build. > [FeedHenry] Cannot cancel import > -------------------------------- > > Key: JBIDE-19462 > URL: https://issues.jboss.org/browse/JBIDE-19462 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.3.CR1 > Reporter: Pavol Srna > Assignee: Gorkem Ercan > Fix For: 4.3.0.Alpha2 > > Attachments: not-cancelable-import.png > > > With many projects on FeedHenry it takes too long to get/parse the response from server. Therefore a user should be able to cancel the import operation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (LOCUS-23) New version of Saxon-HE required in locus

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/LOCUS-23?page=com.atlassian.jira.plugin.s... ] Mickael Istria reassigned LOCUS-23: ----------------------------------- Assignee: Mickael Istria > New version of Saxon-HE required in locus > ----------------------------------------- > > Key: LOCUS-23 > URL: https://issues.jboss.org/browse/LOCUS-23 > Project: JBoss Tools Locus > Issue Type: Feature Request > Affects Versions: 1.1.0 > Reporter: Paul Richardson > Assignee: Mickael Istria > Fix For: 1.2.0 > > > The Teiid Server project has updated their dependencies, including increasing the Saxon-HE version to 9.1.5-6j. > Since Teiid Designer takes a cut of the Teiid Server's client, it is necessary to update the Saxon-HE dependency in the former in order to remain in sync. Designer gets it Saxon library from the Locus repository. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19527) [FeedHenry] UnknownHostException should be handled in UI/wizard and displayed to user with an error message

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19527?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-19527. ------------------------------ > [FeedHenry] UnknownHostException should be handled in UI/wizard and displayed to user with an error message > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19527 > URL: https://issues.jboss.org/browse/JBIDE-19527 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.3.CR1 > Reporter: Pavol Srna > Assignee: Gorkem Ercan > Fix For: 4.3.0.Alpha2 > > > {code} > org.jboss.tools.feedhenry.ui.model.FeedHenryException: Error occured while communicating with the FeedHenry server > at org.jboss.tools.feedhenry.ui.model.FeedHenry.doAPICall(FeedHenry.java:102) > at org.jboss.tools.feedhenry.ui.model.FeedHenry.listProjects(FeedHenry.java:44) > at org.jboss.tools.feedhenry.ui.internal.FeedHenryApplicationSelector.prepareInput(FeedHenryApplicationSelector.java:220) > at org.jboss.tools.feedhenry.ui.internal.FeedHenryApplicationSelector.access$0(FeedHenryApplicationSelector.java:208) > at org.jboss.tools.feedhenry.ui.internal.FeedHenryApplicationSelector$1.run(FeedHenryApplicationSelector.java:109) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122) > Caused by: java.net.UnknownHostException: aerogear-t.sandbox.feedhenry.cz: nodename nor servname provided, or not known > at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method) > at java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:901) > at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1293) > at java.net.InetAddress.getAllByName0(InetAddress.java:1246) > at java.net.InetAddress.getAllByName(InetAddress.java:1162) > at java.net.InetAddress.getAllByName(InetAddress.java:1098) > at org.apache.http.impl.conn.SystemDefaultDnsResolver.resolve(SystemDefaultDnsResolver.java:44) > at org.apache.http.impl.conn.DefaultClientConnectionOperator.resolveHostname(DefaultClientConnectionOperator.java:259) > at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:159) > at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:304) > at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611) > at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446) > at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863) > at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) > at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106) > at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57) > at org.jboss.tools.feedhenry.ui.model.FeedHenry.doAPICall(FeedHenry.java:84) > ... 5 more > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19453) Remote host information does not fit in the server editor

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19453?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19453: --------------------------------------------- I get same UI, but when making screen wider it does get shown eventually. > Remote host information does not fit in the server editor > --------------------------------------------------------- > > Key: JBIDE-19453 > URL: https://issues.jboss.org/browse/JBIDE-19453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > Attachments: remote-runtime-does-not-fit.png, server-editor-2.png > > > Today I noticed this. When I set up a remote server and then open it in the Server editor, the part under Server Behavior where it shows the remote host configuration (e.g. Remote Server Home) does not fix - it needs more space to the right, but it's hidden and there is no way to scroll to view it. > !remote-runtime-does-not-fit.png! > The same problem applies to both JBDS 8.1.0.Beta1 and JBDS 9.0.0.Alpha1. So you may want to clone this for 4.3.x. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (LOCUS-15) Set version on exported packages

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/LOCUS-15?page=com.atlassian.jira.plugin.s... ] Mickael Istria commented on LOCUS-15: ------------------------------------- Orbit usually sets the package version to be equal to the one of bundle. However, there are some cases (such as com.google.inject) where the versions are different, without any obvious reason. There is a risk of putting wrong versions in there. Indeed, versioning package has a strict semantic meaning and package version can often be lower than bundle version, so if we arbitrarily put a too high version on a package and that the project uses package versioning (without OSGi, but documented somewhere), then we can have our version conflicting with real ones... > Set version on exported packages > -------------------------------- > > Key: LOCUS-15 > URL: https://issues.jboss.org/browse/LOCUS-15 > Project: JBoss Tools Locus > Issue Type: Enhancement > Affects Versions: 1.1.0 > Reporter: Mickael Istria > Fix For: 1.2.0 > > > Locus bundles don't specify version for their exports, so they cannot be consumed by other bundles that use Import-Package with a version. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19715) Get rid of "fullSite", stick with "repository"

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19715?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19715: ------------------------------------ TODOs: * update all the jobs that currently rely on a /fullSite/ path to use /repository/ instead * update repo-utils and jbosstools-build-ci *.sh scripts to use new path * update jbosstools-discovery and ide-config.properties to ensure no references to /fullSite/ remain * update JBT/JBDS release guides * release new version of repo-utils and build-ci scripts > Get rid of "fullSite", stick with "repository" > ---------------------------------------------- > > Key: JBIDE-19715 > URL: https://issues.jboss.org/browse/JBIDE-19715 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Mickael Istria > > Currently, some builds such as aggregate create a "site/target/fullSite" folder, which is aimed at being deployed. However, it would be simpler to populate the site/target/repository folder, so it would be only one directory to move, and the same one for all builds. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18583) pong index.html no longer works on cordovasim (Mac OS specific)

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18583?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-18583: -------------------------------- Summary: pong index.html no longer works on cordovasim (Mac OS specific) (was: pong index.html no longer works on cordovasim ) > pong index.html no longer works on cordovasim (Mac OS specific) > --------------------------------------------------------------- > > Key: JBIDE-18583 > URL: https://issues.jboss.org/browse/JBIDE-18583 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.2.0.CR2 > Environment: Mac Os > Reporter: Max Rydahl Andersen > Assignee: Ilya Buziuk > Fix For: 4.3.x > > Attachments: index.html.zip > > > This works in previous versions. > replace the index.html into a hybrid app - it works when using ios simulator but not with cordovasim. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19715) Get rid of "fullSite", stick with "repository"

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19715?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19715: ------------------------------------ Caveats: * make sure the contents generated to /fullSite are the same as those in /repository today, so we're not losing functionality when generating over top in the same folder * make sure branding and <references> removal in JBDS site continue to work correctly - see JBDS-3423, JBDS-3408 > Get rid of "fullSite", stick with "repository" > ---------------------------------------------- > > Key: JBIDE-19715 > URL: https://issues.jboss.org/browse/JBIDE-19715 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Mickael Istria > > Currently, some builds such as aggregate create a "site/target/fullSite" folder, which is aimed at being deployed. However, it would be simpler to populate the site/target/repository folder, so it would be only one directory to move, and the same one for all builds. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (LOCUS-15) Set version on exported packages

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/LOCUS-15?page=com.atlassian.jira.plugin.s... ] Max Rydahl Andersen commented on LOCUS-15: ------------------------------------------ what does orbit do? > Set version on exported packages > -------------------------------- > > Key: LOCUS-15 > URL: https://issues.jboss.org/browse/LOCUS-15 > Project: JBoss Tools Locus > Issue Type: Enhancement > Affects Versions: 1.1.0 > Reporter: Mickael Istria > Fix For: 1.2.0 > > > Locus bundles don't specify version for their exports, so they cannot be consumed by other bundles that use Import-Package with a version. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19715) Get rid of "fullSite", stick with "repository"

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-19715: -------------------------------------- Summary: Get rid of "fullSite", stick with "repository" Key: JBIDE-19715 URL: https://issues.jboss.org/browse/JBIDE-19715 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: build Affects Versions: 4.3.0.Alpha1 Reporter: Mickael Istria Currently, some builds such as aggregate create a "site/target/fullSite" folder, which is aimed at being deployed. However, it would be simpler to populate the site/target/repository folder, so it would be only one directory to move, and the same one for all builds. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19703) Offline script is unable to resolve dependencies (error grabbing Grapes)

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19703?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-19703: ------------------------------------- Works for me :/ {noformat} ➜ JBIDE-19703 rm -rf offline ➜ JBIDE-19703 rm -rf ~/.groovy ➜ JBIDE-19703 groovy -v Groovy Version: 2.4.3 JVM: 1.8.0_45 Vendor: Oracle Corporation OS: Mac OS X ➜ JBIDE-19703 groovy "/Users/fbricon/Dev/workspaces/javaeeM6/.metadata/.plugins/org.jboss.tools.project.examples/offline/go_offline_3.0.0.Beta1_v20150426_0456_B682.groovy" http://download.jboss.org/jbosstools/examples/4.3/project-examples-catego... http://download.jboss.org/jbosstools/examples/4.3/project-examples-shared... http://download.jboss.org/jbosstools/examples/4.3/project-examples-commun... http://download.jboss.org/gatein/quickstarts/jboss-portal-6.2/project-exa... http://download.jboss.org/jbosstools/examples/4.3/project-examples-maven-... -c -e Quiet mode : false Descriptors : [http://download.jboss.org/jbosstools/examples/4.3/project-examples-catego..., http://download.jboss.org/jbosstools/examples/4.3/project-examples-shared..., http://download.jboss.org/jbosstools/examples/4.3/project-examples-commun..., http://download.jboss.org/gatein/quickstarts/jboss-portal-6.2/project-exa..., http://download.jboss.org/jbosstools/examples/4.3/project-examples-maven-...] creating offline/.jbosstools/cache parsing buildfile jar:file:/Users/fbricon/.gvm/groovy/current/lib/ant-1.9.4.jar!/org/apache/tools/ant/antlib.xml with URI = jar:file:/Users/fbricon/.gvm/groovy/current/lib/ant-1.9.4.jar!/org/apache/tools/ant/antlib.xml from a zip file Current OS is Mac OS X Error redirected to property: cmdErr Executing 'mvn' with arguments: 'io.takari:maven:wrapper' '-N' '-Dmaven.repo.local=/Users/fbricon/Dev/JBIDE-19703/offline/.m2/repository' {noformat} > Offline script is unable to resolve dependencies (error grabbing Grapes) > ------------------------------------------------------------------------ > > Key: JBIDE-19703 > URL: https://issues.jboss.org/browse/JBIDE-19703 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.Alpha2 > Environment: JBDS 9.0.0.Alpha2 > Reporter: Radim Hopp > Assignee: Fred Bricon > Fix For: 4.3.0.Beta1 > > > When user has empty .groovy/grapes, offline script is not working: > {noformat}groovy "/home/rhopp/workspace-tests/.metadata/.plugins/org.jboss.tools.project.examples/offline/go_offline_3.0.0.Alpha2_v20150417_1854_B11.groovy" http://download.jboss.org/jbosstools/examples/4.3/project-examples-catego... http://download.jboss.org/jbosstools/examples/4.3/project-examples-shared... http://download.jboss.org/jbosstools/examples/4.3/project-examples-jbds90... http://download.jboss.org/gatein/quickstarts/jboss-portal-6.2/project-exa... -e |tee output > org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: > General error during conversion: Error grabbing Grapes -- [download failed: org.jboss.logging#jboss-logging;3.1.2.GA!jboss-logging.jar] > java.lang.RuntimeException: Error grabbing Grapes -- [download failed: org.jboss.logging#jboss-logging;3.1.2.GA!jboss-logging.jar] > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:422) > at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:77) > at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:71) > at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:81) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:57) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:230) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:242) > at groovy.grape.GrapeIvy.getDependencies(GrapeIvy.groovy:418) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite$PogoCachedMethodSite.invoke(PogoMetaMethodSite.java:166) > at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.callCurrent(PogoMetaMethodSite.java:56) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:49) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:149) > at groovy.grape.GrapeIvy.resolve(GrapeIvy.groovy:563) > at groovy.grape.GrapeIvy$resolve$1.callCurrent(Unknown Source) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:49) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:149) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185) > at groovy.grape.GrapeIvy.resolve(GrapeIvy.groovy:532) > at groovy.grape.GrapeIvy$resolve$0.callCurrent(Unknown Source) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:49) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:149) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:177) > at groovy.grape.GrapeIvy.grab(GrapeIvy.groovy:254) > at groovy.grape.Grape.grab(Grape.java:163) > at groovy.grape.GrabAnnotationTransformation.visit(GrabAnnotationTransformation.java:358) > at org.codehaus.groovy.transform.ASTTransformationVisitor$3.call(ASTTransformationVisitor.java:319) > at org.codehaus.groovy.control.CompilationUnit.applyToSourceUnits(CompilationUnit.java:928) > at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:590) > at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:566) > at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:543) > at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:297) > at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:267) > at groovy.lang.GroovyShell.parseClass(GroovyShell.java:692) > at groovy.lang.GroovyShell.run(GroovyShell.java:521) > at groovy.lang.GroovyShell.run(GroovyShell.java:511) > at groovy.ui.GroovyMain.processOnce(GroovyMain.java:650) > at groovy.ui.GroovyMain.run(GroovyMain.java:381) > at groovy.ui.GroovyMain.process(GroovyMain.java:367) > at groovy.ui.GroovyMain.processArgs(GroovyMain.java:126) > at groovy.ui.GroovyMain.main(GroovyMain.java:106) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.codehaus.groovy.tools.GroovyStarter.rootLoader(GroovyStarter.java:106) > at org.codehaus.groovy.tools.GroovyStarter.main(GroovyStarter.java:128) > 1 error > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19681) OpenShift New and Noteworthy for 4.3.0.Alpha2

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19681?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19681: ------------------------------------------ this was merged and pushed. > OpenShift New and Noteworthy for 4.3.0.Alpha2 > --------------------------------------------- > > Key: JBIDE-19681 > URL: https://issues.jboss.org/browse/JBIDE-19681 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Alexey Kazakov > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.3.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If OpenShift is not listed here check if there are issues that should be added and add them. > Document the ones relevant for OpenShift by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19597) add google tag manager to website

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19597?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen closed JBIDE-19597. --------------------------------------- verified by [~elliottkoppel] via email that it is working. thus closing. > add google tag manager to website > --------------------------------- > > Key: JBIDE-19597 > URL: https://issues.jboss.org/browse/JBIDE-19597 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 4.3.0.Alpha2 > > > Asked by jboss.org to add the following: > {code} > Option 1: You have an existing GA (Google Analytics) account you want to keep using. You should upgrade your GA account to use UA (Universal Analytics). > <script>dataLayer = [{'channel' : ‘<insert project name here>’, ‘additional_tracking_code’ : ‘<insert optional additional GA tracking code here>'}];</script> >  > <noscript><iframe src="//www.googletagmanager.com/ns.html?id=GTM-NJWS5L" > height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript> > <script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start': > new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0], > j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src= > '//www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f); > })(window,document,'script','dataLayer','GTM-NJWS5L');</script> > <!-- End Google Tag Manager —> > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3285) Easy Import of non-eclipse projects

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-3285: ------------------------------ Labels: new_and_noteworthy usability (was: usability) > Easy Import of non-eclipse projects > ----------------------------------- > > Key: JBDS-3285 > URL: https://issues.jboss.org/browse/JBDS-3285 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, upstream > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Len DiMaggio > Labels: new_and_noteworthy, usability > Fix For: 9.0.0.Alpha2 > > Attachments: import-me.zip > > > As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance. > The mission here is to make the Git experience much more user friendly. > Progress/Status (updated progressively): https://wiki.eclipse.org/E4/UI/Smart_Import -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19712) Application wizard: Add create from template details pane

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19712?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19712: ------------------------------------- Labels: application_wizard (was: ) > Application wizard: Add create from template details pane > --------------------------------------------------------- > > Key: JBIDE-19712 > URL: https://issues.jboss.org/browse/JBIDE-19712 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: application_wizard > Fix For: 4.3.0.Beta1 > > > Add details pane similiar to v2 where you get template details when you select an individual template. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19712) Application wizard: Add create from template details pane

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19712?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19712: ------------------------------------- Summary: Application wizard: Add create from template details pane (was: Add create from template details pane) > Application wizard: Add create from template details pane > --------------------------------------------------------- > > Key: JBIDE-19712 > URL: https://issues.jboss.org/browse/JBIDE-19712 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: application_wizard > Fix For: 4.3.0.Beta1 > > > Add details pane similiar to v2 where you get template details when you select an individual template. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19711) WTP servertools integration with CDT launchbar

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19711?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-19711: ----------------------------------- Assignee: Rob Stryker > WTP servertools integration with CDT launchbar > ---------------------------------------------- > > Key: JBIDE-19711 > URL: https://issues.jboss.org/browse/JBIDE-19711 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server, upstream > Reporter: Rob Stryker > Assignee: Rob Stryker > > CDT has a new framework called Launchbar https://wiki.eclipse.org/CDT/LaunchBar > Integrating this with servertools, proof of concept, to see how feasible it is. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19478) Application wizard: Add template filtering by tag

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19478?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19478: ------------------------------------- Summary: Application wizard: Add template filtering by tag (was: Add template filtering by tag) > Application wizard: Add template filtering by tag > ------------------------------------------------- > > Key: JBIDE-19478 > URL: https://issues.jboss.org/browse/JBIDE-19478 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Blocker > Labels: application_wizard > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19478) Application wizard: Add template filtering by tag

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19478?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19478: ------------------------------------- Labels: application_wizard (was: ) > Application wizard: Add template filtering by tag > ------------------------------------------------- > > Key: JBIDE-19478 > URL: https://issues.jboss.org/browse/JBIDE-19478 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Blocker > Labels: application_wizard > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19682) JBoss Central New and Noteworthy for 4.3.0.Alpha2

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19682?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-19682: ----------------------------------- Assignee: Fred Bricon > JBoss Central New and Noteworthy for 4.3.0.Alpha2 > ------------------------------------------------- > > Key: JBIDE-19682 > URL: https://issues.jboss.org/browse/JBIDE-19682 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Reporter: Alexey Kazakov > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If JBoss Central is not listed here check if there are issues that should be added and add them. > Document the ones relevant for JBoss Central by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19677) Project Examples New and Noteworthy for 4.3.0.Alpha2

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19677?page=com.atlassian.jira.plugi... ] Fred Bricon closed JBIDE-19677. ------------------------------- Assignee: Fred Bricon Resolution: Rejected Not applicable for Alpha2 > Project Examples New and Noteworthy for 4.3.0.Alpha2 > ---------------------------------------------------- > > Key: JBIDE-19677 > URL: https://issues.jboss.org/browse/JBIDE-19677 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: project-examples > Reporter: Alexey Kazakov > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Project Examples is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Project Examples by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19675) Maven New and Noteworthy for 4.3.0.Alpha2

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19675?page=com.atlassian.jira.plugi... ] Fred Bricon closed JBIDE-19675. ------------------------------- Assignee: Fred Bricon Resolution: Rejected Not applicable for Alpha2 > Maven New and Noteworthy for 4.3.0.Alpha2 > ----------------------------------------- > > Key: JBIDE-19675 > URL: https://issues.jboss.org/browse/JBIDE-19675 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: maven > Reporter: Alexey Kazakov > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Maven is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Maven by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19190) migrate VersionWatch to jbosstools-* repo

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19190?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19190: --------------------------------------------- The old location does not seem deleted to me. https://github.com/jbdevstudio/jbdevstudio-qa/tree/master/vwatch is still there. > migrate VersionWatch to jbosstools-* repo > ----------------------------------------- > > Key: JBIDE-19190 > URL: https://issues.jboss.org/browse/JBIDE-19190 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Jiri Peterka > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > 0. decide where to put this... under jbosstools-ci or some new repo? Create a new component in JIRA accordingly. > 1. remove all refs to QA Jenkins file paths to make this more generic > 2. migrate those internal file paths into jenkins config.xml files > 3. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches -- pre-existing doc here: > http://download.jboss.org/jbosstools/updates/scripted-installation/ > https://devstudio.redhat.com/download/scripted-install/ > 4. test #3 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3386) add org.eclipse.wst.jsdt.feature.patch into both JBT 4.2 and JBDS 8 (Luna) Eclipse Marketplace connectors

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBDS-3386?page=com.atlassian.jira.plugin.... ] Rastislav Wagner closed JBDS-3386. ---------------------------------- So I installed both JBT and JBDS from marketplace and patch is included. Closing. > add org.eclipse.wst.jsdt.feature.patch into both JBT 4.2 and JBDS 8 (Luna) Eclipse Marketplace connectors > --------------------------------------------------------------------------------------------------------- > > Key: JBDS-3386 > URL: https://issues.jboss.org/browse/JBDS-3386 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Components: target-platform > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 8.1.0.GA > > > When we release JBT 4.2.3 and JBDS 8.1.0, we need to remember to add 1 new feature, org.eclipse.wst.jsdt.feature.patch, into both the JBT 4.2 and JBDS 8 (Luna) Eclipse Marketplace connectors. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19704) Visual part of Visual/Source tab is empty for HTML page when JSF support enabled

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19704?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-19704: -------------------------------- Sprint: Sprint #2 April 2015 > Visual part of Visual/Source tab is empty for HTML page when JSF support enabled > -------------------------------------------------------------------------------- > > Key: JBIDE-19704 > URL: https://issues.jboss.org/browse/JBIDE-19704 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.3.0.Alpha2 > Environment: Fedora 19 64bit, JBDS 9.0.0.Alpha2-v20150421-1151-B25, Oracle JDK 1.7 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > > 1. Set Visual Editor to use JSF support > 2. Create simple HTML page like this and open it in VPE editor > {code:html} > <!DOCTYPE html> > <html> > <body> > <h1>test heading</h1> > </body> > </html> > {code} > ERROR: Visual part of Visual/Source tab of VPE is empty. > Visual tab of VPE renders page properly. > When HTML support is enabled it works fine. > I'm not sure if this is issue or expected behavior so if it's not an issue just mark it as won't fix please. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19190) migrate VersionWatch to jbosstools-* repo

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19190?page=com.atlassian.jira.plugi... ] Jiri Peterka commented on JBIDE-19190: -------------------------------------- Thanks Max. [~maxandersen], It would probably be suitable to add me and Nick (but he's already there I assume) as a contributors so we can push our PR each other if needed. Except me no one else from QE needs permissions right now. Also the old location repo was already deleted and my jobs updated. From my POV this task can be closed. Not sure about Nick's jobs. [~nickboldt], are your jobs updated for a new repo location? > migrate VersionWatch to jbosstools-* repo > ----------------------------------------- > > Key: JBIDE-19190 > URL: https://issues.jboss.org/browse/JBIDE-19190 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Jiri Peterka > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > 0. decide where to put this... under jbosstools-ci or some new repo? Create a new component in JIRA accordingly. > 1. remove all refs to QA Jenkins file paths to make this more generic > 2. migrate those internal file paths into jenkins config.xml files > 3. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches -- pre-existing doc here: > http://download.jboss.org/jbosstools/updates/scripted-installation/ > https://devstudio.redhat.com/download/scripted-install/ > 4. test #3 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-15884) Allow the runBrowserSim command to accept a URL as a parameter

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15884?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-15884: ------------------------------------- PR was updated - https://github.com/jbosstools/jbosstools-browsersim/pull/63 Basically, now there is only one command with optional url parameter (*org.jboss.tools.vpe.browsersim.eclipse.commands.runBrowserSim*) Cheat Sheets usage: {code} <command required="false" serialization="org.jboss.tools.vpe.browsersim.eclipse.commands.runBrowserSim(url=http://..."/> {code} > Allow the runBrowserSim command to accept a URL as a parameter > -------------------------------------------------------------- > > Key: JBIDE-15884 > URL: https://issues.jboss.org/browse/JBIDE-15884 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 4.1.0.Final > Reporter: Vineet Reynolds > Assignee: Ilya Buziuk > Priority: Minor > Fix For: 4.3.0.Beta1 > > > Apologies for not setting the Affect version; I'm not sure which JBIDE version is affected. > When creating a cheatsheet in JBDS 7.0.1.GA (for JDF-497), I'm using the {{org.jboss.tools.vpe.browsersim.eclipse.commands.runBrowserSim}} command in the cheatsheet. This launches BrowserSim successfully (when I'm in the correct perspective). However, BrowserSim navigates to about:blank so the cheatsheet requires users to manually key in the URL. It would be nice to have the launch URL specified as a configurable value. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19712) Add create from template details pane

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19712?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-19712: ---------------------------------- Summary: Add create from template details pane (was: Add create from template details pain) > Add create from template details pane > ------------------------------------- > > Key: JBIDE-19712 > URL: https://issues.jboss.org/browse/JBIDE-19712 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Beta1 > > > Add details pain similiar to v2 where you get template details when you select an individual template -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19712) Add create from template details pane

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19712?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-19712: ---------------------------------- Description: Add details pane similiar to v2 where you get template details when you select an individual template. (was: Add details pain similiar to v2 where you get template details when you select an individual template) > Add create from template details pane > ------------------------------------- > > Key: JBIDE-19712 > URL: https://issues.jboss.org/browse/JBIDE-19712 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Beta1 > > > Add details pane similiar to v2 where you get template details when you select an individual template. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-15884) Allow the runBrowserSim command to accept a URL as a parameter

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15884?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15884: --------------------------------------------- thanks [~vineet.reynolds] for confirming we got usage of the command and thanks [~ibuziuk] for updating PR to retain compatibility (releasing the archetype wouldn't fix you opening the already generated project in newer jbt version). > Allow the runBrowserSim command to accept a URL as a parameter > -------------------------------------------------------------- > > Key: JBIDE-15884 > URL: https://issues.jboss.org/browse/JBIDE-15884 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 4.1.0.Final > Reporter: Vineet Reynolds > Assignee: Ilya Buziuk > Priority: Minor > Fix For: 4.3.0.Beta1 > > > Apologies for not setting the Affect version; I'm not sure which JBIDE version is affected. > When creating a cheatsheet in JBDS 7.0.1.GA (for JDF-497), I'm using the {{org.jboss.tools.vpe.browsersim.eclipse.commands.runBrowserSim}} command in the cheatsheet. This launches BrowserSim successfully (when I'm in the correct perspective). However, BrowserSim navigates to about:blank so the cheatsheet requires users to manually key in the URL. It would be nice to have the launch URL specified as a configurable value. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-15884) Allow the runBrowserSim command to accept a URL as a parameter

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15884?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-15884: ------------------------------------- Ok, lets fall back on *org.jboss.tools.vpe.browsersim.eclipse.commands.runBrowserSim* with optional url parameter to avoid API breakages for cheat sheets for now. Will update PR > Allow the runBrowserSim command to accept a URL as a parameter > -------------------------------------------------------------- > > Key: JBIDE-15884 > URL: https://issues.jboss.org/browse/JBIDE-15884 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 4.1.0.Final > Reporter: Vineet Reynolds > Assignee: Ilya Buziuk > Priority: Minor > Fix For: 4.3.0.Beta1 > > > Apologies for not setting the Affect version; I'm not sure which JBIDE version is affected. > When creating a cheatsheet in JBDS 7.0.1.GA (for JDF-497), I'm using the {{org.jboss.tools.vpe.browsersim.eclipse.commands.runBrowserSim}} command in the cheatsheet. This launches BrowserSim successfully (when I'm in the correct perspective). However, BrowserSim navigates to about:blank so the cheatsheet requires users to manually key in the URL. It would be nice to have the launch URL specified as a configurable value. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-15884) Allow the runBrowserSim command to accept a URL as a parameter

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15884?page=com.atlassian.jira.plugi... ] Vineet Reynolds commented on JBIDE-15884: ----------------------------------------- [~maxandersen], [~ibuziuk] As far as I know, there are only a few cheatsheets that use the runBrowserSim command. This is one such usage: https://github.com/jbosstools/jbosstools-archetypes/blob/master/jboss-for... It may be ok to change the command used, since it is consumed by JBT; a release of the archetype is required. However, there is a second use in WFK: https://github.com/jboss-developer/jboss-wfk-quickstarts/blob/2.7.x/kitch... and I'm not sure when these would be updated and released and in what project. I think a backward compatible solution may be required now. > Allow the runBrowserSim command to accept a URL as a parameter > -------------------------------------------------------------- > > Key: JBIDE-15884 > URL: https://issues.jboss.org/browse/JBIDE-15884 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 4.1.0.Final > Reporter: Vineet Reynolds > Assignee: Ilya Buziuk > Priority: Minor > Fix For: 4.3.0.Beta1 > > > Apologies for not setting the Affect version; I'm not sure which JBIDE version is affected. > When creating a cheatsheet in JBDS 7.0.1.GA (for JDF-497), I'm using the {{org.jboss.tools.vpe.browsersim.eclipse.commands.runBrowserSim}} command in the cheatsheet. This launches BrowserSim successfully (when I'm in the correct perspective). However, BrowserSim navigates to about:blank so the cheatsheet requires users to manually key in the URL. It would be nice to have the launch URL specified as a configurable value. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-17686) get TCF and RSE terminals to coexist without bad UX of multiple terminals

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Lars Heinemann commented on JBIDE-17686: ---------------------------------------- Thanks Max. Will look at the new Mars TP soon. > get TCF and RSE terminals to coexist without bad UX of multiple terminals > ------------------------------------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.0.Beta1 > > Attachments: eclipse-can-has-many-consoles.png > > > luna has new Eclipse TCF terminal that brings better Terminal support. > I would assume it is in there but I couldn't find a way to actually open it. Maybe we havent included the full set of plugins. > http://marketplace.eclipse.org/content/tcf-terminals#.U6sJ92Vp7wV > http://eclipsesource.com/blogs/2014/06/17/tcf-terminal-top-eclipse-luna-f... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3411) have installer build actually use M6 p2 product build

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3411?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3411: ------------------------------------------- we also wouldn't have the runtimes in the same location. What we *could* consider is to use "~/Library/Application Support/jbdevstudio.app" (Actually, we should probably move to jbevstudio9.app to avoid version overlap in future) which I believe is the "proper" way to put user specific content. Also its worth noting that on Mac uninstalling is to just delete the .app folder so maybe uninstaller does not make sense here ? > 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)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19711) WTP servertools integration with CDT launchbar

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19711?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19711: ---------------------------------------- Sprint: Sprint #2 April 2015 putting this into the JavaEE epic for improvements for now and in active sprint since you are currently working or been working on it. > WTP servertools integration with CDT launchbar > ---------------------------------------------- > > Key: JBIDE-19711 > URL: https://issues.jboss.org/browse/JBIDE-19711 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server, upstream > Reporter: Rob Stryker > > CDT has a new framework called Launchbar https://wiki.eclipse.org/CDT/LaunchBar > Integrating this with servertools, proof of concept, to see how feasible it is. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19683) Create a user visible location for downloading tutorial metadata

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19683?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen closed JBIDE-19683. --------------------------------------- Resolution: Out of Date > Create a user visible location for downloading tutorial metadata > ---------------------------------------------------------------- > > Key: JBIDE-19683 > URL: https://issues.jboss.org/browse/JBIDE-19683 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: project-examples > Reporter: Jane Murphey > > Need to modify jbosstools-download.jboss.org to establish a directory to be used by documentation tutorials. Fuse Tooling will be the first. I will generate a PR soon. Please assign to me (jmurphey). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19683) Create a user visible location for downloading tutorial metadata

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19683?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen closed JBIDE-19683. --------------------------------------- > Create a user visible location for downloading tutorial metadata > ---------------------------------------------------------------- > > Key: JBIDE-19683 > URL: https://issues.jboss.org/browse/JBIDE-19683 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: project-examples > Reporter: Jane Murphey > > Need to modify jbosstools-download.jboss.org to establish a directory to be used by documentation tutorials. Fuse Tooling will be the first. I will generate a PR soon. Please assign to me (jmurphey). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19683) Create a user visible location for downloading tutorial metadata

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19683?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen resolved JBIDE-19683. ----------------------------------------- Resolution: Done okey - just please note that the example I showed and made gave you a place to download files from in a working and proper versioned way (just link to specific githug tagged zip file) and you would not need any download.jboss.org etc. involvement. Its IMO simpler and more future proof than the current approach. but on your request closing this. > Create a user visible location for downloading tutorial metadata > ---------------------------------------------------------------- > > Key: JBIDE-19683 > URL: https://issues.jboss.org/browse/JBIDE-19683 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: project-examples > Reporter: Jane Murphey > > Need to modify jbosstools-download.jboss.org to establish a directory to be used by documentation tutorials. Fuse Tooling will be the first. I will generate a PR soon. Please assign to me (jmurphey). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18772: --------------------------------------------- Why do we need to override these things - can't those *few* ones be customized to have that set properly ? About copy-or-rename stuff, we do we even have such step ? why don't we actually produce what we want/need ? > Include publish.sh in parent pom as versioned maven dependency > -------------------------------------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.0.Beta1 > > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-17686) get TCF and RSE terminals to coexist without bad UX of multiple terminals

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17686: --------------------------------------------- Mentioning [~lhein] so he gets notified. See Rob's comment please. > get TCF and RSE terminals to coexist without bad UX of multiple terminals > ------------------------------------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.0.Beta1 > > Attachments: eclipse-can-has-many-consoles.png > > > luna has new Eclipse TCF terminal that brings better Terminal support. > I would assume it is in there but I couldn't find a way to actually open it. Maybe we havent included the full set of plugins. > http://marketplace.eclipse.org/content/tcf-terminals#.U6sJ92Vp7wV > http://eclipsesource.com/blogs/2014/06/17/tcf-terminal-top-eclipse-luna-f... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-15884) Allow the runBrowserSim command to accept a URL as a parameter

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15884?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15884: --------------------------------------------- why not just use the old name - then there is only one not two ? > Allow the runBrowserSim command to accept a URL as a parameter > -------------------------------------------------------------- > > Key: JBIDE-15884 > URL: https://issues.jboss.org/browse/JBIDE-15884 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 4.1.0.Final > Reporter: Vineet Reynolds > Assignee: Ilya Buziuk > Priority: Minor > Fix For: 4.3.0.Beta1 > > > Apologies for not setting the Affect version; I'm not sure which JBIDE version is affected. > When creating a cheatsheet in JBDS 7.0.1.GA (for JDF-497), I'm using the {{org.jboss.tools.vpe.browsersim.eclipse.commands.runBrowserSim}} command in the cheatsheet. This launches BrowserSim successfully (when I'm in the correct perspective). However, BrowserSim navigates to about:blank so the cheatsheet requires users to manually key in the URL. It would be nice to have the launch URL specified as a configurable value. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19190) migrate VersionWatch to jbosstools-* repo

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19190?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen edited comment on JBIDE-19190 at 4/27/15 4:04 AM: ---------------------------------------------------------------------- Merged! [~nickboldt] and [~jpeterka] let me know how you want to do the permissions for this repo and I can set that up. Right now only Build team has push access to it. Should I add "Integration-tests" team to it too ? Also, [~jpeterka] you should get the old location deleted and the jobs updated to use this new location. One that is done we should be ok to close this. Thanks! was (Author: maxandersen): Merged! [~nickboldt] and [~jpeterka] let me know how you want to do the permissions for this repo and I can set that up. Right now only Build team has push access to it. Should I add "Integration-tests" team to it too ? Also, we should get the old location deleted and the jobs updated. > migrate VersionWatch to jbosstools-* repo > ----------------------------------------- > > Key: JBIDE-19190 > URL: https://issues.jboss.org/browse/JBIDE-19190 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Jiri Peterka > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > 0. decide where to put this... under jbosstools-ci or some new repo? Create a new component in JIRA accordingly. > 1. remove all refs to QA Jenkins file paths to make this more generic > 2. migrate those internal file paths into jenkins config.xml files > 3. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches -- pre-existing doc here: > http://download.jboss.org/jbosstools/updates/scripted-installation/ > https://devstudio.redhat.com/download/scripted-install/ > 4. test #3 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19190) migrate VersionWatch to jbosstools-* repo

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19190?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19190: --------------------------------------------- Merged! [~nickboldt] and [~jpeterka] let me know how you want to do the permissions for this repo and I can set that up. Right now only Build team has push access to it. Should I add "Integration-tests" team to it too ? Also, we should get the old location deleted and the jobs updated. > migrate VersionWatch to jbosstools-* repo > ----------------------------------------- > > Key: JBIDE-19190 > URL: https://issues.jboss.org/browse/JBIDE-19190 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Jiri Peterka > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > 0. decide where to put this... under jbosstools-ci or some new repo? Create a new component in JIRA accordingly. > 1. remove all refs to QA Jenkins file paths to make this more generic > 2. migrate those internal file paths into jenkins config.xml files > 3. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches -- pre-existing doc here: > http://download.jboss.org/jbosstools/updates/scripted-installation/ > https://devstudio.redhat.com/download/scripted-install/ > 4. test #3 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19190) migrate VersionWatch to jbosstools-* repo

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19190?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen edited comment on JBIDE-19190 at 4/27/15 3:59 AM: ---------------------------------------------------------------------- but that is not what https://github.com/jpeterka/jbosstools-vwatch/commits/master shows. so this was moved without retaining git history and attributions ;/ Jiri - I've created https://github.com/jbosstools/jbosstools-versionwatch which *retains* the proper git history as it is in https://github.com/jbdevstudio/jbdevstudio-qa. This was created by running: {code} git filter-branch --prune-empty --subdirectory-filter vwatch -- --all git remote add vwatch https://github.com/jbosstools/jbosstools-versionwatch git push vwatch master jbosstools-4.2.x {code} That means jbosstools-versionwatch now have the proper history *but* missing whatever changes you made in jpeterka. It looks like this can just be cherry-picked over but I think it is best you do it rather than me doing it blindly. Can you make that and submit a PR for it ? was (Author: maxandersen): but that is not what https://github.com/jpeterka/jbosstools-vwatch/commits/master shows. so this was moved without retaining git history and attributions ;/ Jiri - I've created https://github.com/jbosstools/jbosstools-versionwatch which *retains* the proper git history as it is in https://github.com/jbdevstudio/jbdevstudio-qa. This was created by running: {{{ git filter-branch --prune-empty --subdirectory-filter vwatch -- --all git remote add vwatch https://github.com/jbosstools/jbosstools-versionwatch git push vwatch master jbosstools-4.2.x }}} That means jbosstools-versionwatch now have the proper history *but* missing whatever changes you made in jpeterka. It looks like this can just be cherry-picked over but I think it is best you do it rather than me doing it blindly. Can you make that and submit a PR for it ? > migrate VersionWatch to jbosstools-* repo > ----------------------------------------- > > Key: JBIDE-19190 > URL: https://issues.jboss.org/browse/JBIDE-19190 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Jiri Peterka > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > 0. decide where to put this... under jbosstools-ci or some new repo? Create a new component in JIRA accordingly. > 1. remove all refs to QA Jenkins file paths to make this more generic > 2. migrate those internal file paths into jenkins config.xml files > 3. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches -- pre-existing doc here: > http://download.jboss.org/jbosstools/updates/scripted-installation/ > https://devstudio.redhat.com/download/scripted-install/ > 4. test #3 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3367) Offline update from 8.0.x fails in installing FeedHenry

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3367?page=com.atlassian.jira.plugin.... ] Jan Richter commented on JBDS-3367: ----------------------------------- [~nickboldt] With internet connection it fetches everything and completes nicely. When I force it to run offline it's the same old story, but I sort of expected that when I saw it downloading dependencies. > Offline update from 8.0.x fails in installing FeedHenry > ------------------------------------------------------- > > Key: JBDS-3367 > URL: https://issues.jboss.org/browse/JBDS-3367 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, installer > Affects Versions: 8.1.0.Beta1 > Reporter: Jan Richter > Assignee: Nick Boldt > Fix For: 9.0.0.Beta1 > > > Updating from 8.0.0, 8.0.1 and 8.0.2 from the update zip causes the following error: > Cannot complete the install because one or more required items could not be found. > Software being installed: JBoss Tools FeedHenry Integration 1.0.0.Beta1-v20150225-2159-B85 (org.jboss.tools.feedhenry.feature.group 1.0.0.Beta1-v20150225-2159-B85) > Missing requirement: org.jboss.tools.feedhenry.ui 1.0.0.Beta1-v20150225-2159-B85 requires 'bundle org.jboss.tools.vpe.cordovasim.eclipse 3.6.2' but it could not be found > Cannot satisfy dependency: > From: JBoss Tools FeedHenry Integration 1.0.0.Beta1-v20150225-2159-B85 (org.jboss.tools.feedhenry.feature.group 1.0.0.Beta1-v20150225-2159-B85) > To: org.jboss.tools.feedhenry.ui [1.0.0.Beta1-v20150225-2159-B85] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19703) Offline script is unable to resolve dependencies (error grabbing Grapes)

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19703?page=com.atlassian.jira.plugi... ] Rastislav Wagner commented on JBIDE-19703: ------------------------------------------ And I also tried with groovy 2.1.9 > Offline script is unable to resolve dependencies (error grabbing Grapes) > ------------------------------------------------------------------------ > > Key: JBIDE-19703 > URL: https://issues.jboss.org/browse/JBIDE-19703 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.Alpha2 > Environment: JBDS 9.0.0.Alpha2 > Reporter: Radim Hopp > Assignee: Fred Bricon > Fix For: 4.3.0.Beta1 > > > When user has empty .groovy/grapes, offline script is not working: > {noformat}groovy "/home/rhopp/workspace-tests/.metadata/.plugins/org.jboss.tools.project.examples/offline/go_offline_3.0.0.Alpha2_v20150417_1854_B11.groovy" http://download.jboss.org/jbosstools/examples/4.3/project-examples-catego... http://download.jboss.org/jbosstools/examples/4.3/project-examples-shared... http://download.jboss.org/jbosstools/examples/4.3/project-examples-jbds90... http://download.jboss.org/gatein/quickstarts/jboss-portal-6.2/project-exa... -e |tee output > org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: > General error during conversion: Error grabbing Grapes -- [download failed: org.jboss.logging#jboss-logging;3.1.2.GA!jboss-logging.jar] > java.lang.RuntimeException: Error grabbing Grapes -- [download failed: org.jboss.logging#jboss-logging;3.1.2.GA!jboss-logging.jar] > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:422) > at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:77) > at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:71) > at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:81) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:57) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:230) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:242) > at groovy.grape.GrapeIvy.getDependencies(GrapeIvy.groovy:418) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite$PogoCachedMethodSite.invoke(PogoMetaMethodSite.java:166) > at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.callCurrent(PogoMetaMethodSite.java:56) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:49) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:149) > at groovy.grape.GrapeIvy.resolve(GrapeIvy.groovy:563) > at groovy.grape.GrapeIvy$resolve$1.callCurrent(Unknown Source) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:49) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:149) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185) > at groovy.grape.GrapeIvy.resolve(GrapeIvy.groovy:532) > at groovy.grape.GrapeIvy$resolve$0.callCurrent(Unknown Source) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:49) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:149) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:177) > at groovy.grape.GrapeIvy.grab(GrapeIvy.groovy:254) > at groovy.grape.Grape.grab(Grape.java:163) > at groovy.grape.GrabAnnotationTransformation.visit(GrabAnnotationTransformation.java:358) > at org.codehaus.groovy.transform.ASTTransformationVisitor$3.call(ASTTransformationVisitor.java:319) > at org.codehaus.groovy.control.CompilationUnit.applyToSourceUnits(CompilationUnit.java:928) > at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:590) > at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:566) > at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:543) > at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:297) > at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:267) > at groovy.lang.GroovyShell.parseClass(GroovyShell.java:692) > at groovy.lang.GroovyShell.run(GroovyShell.java:521) > at groovy.lang.GroovyShell.run(GroovyShell.java:511) > at groovy.ui.GroovyMain.processOnce(GroovyMain.java:650) > at groovy.ui.GroovyMain.run(GroovyMain.java:381) > at groovy.ui.GroovyMain.process(GroovyMain.java:367) > at groovy.ui.GroovyMain.processArgs(GroovyMain.java:126) > at groovy.ui.GroovyMain.main(GroovyMain.java:106) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.codehaus.groovy.tools.GroovyStarter.rootLoader(GroovyStarter.java:106) > at org.codehaus.groovy.tools.GroovyStarter.main(GroovyStarter.java:128) > 1 error > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19703) Offline script is unable to resolve dependencies (error grabbing Grapes)

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19703?page=com.atlassian.jira.plugi... ] Rastislav Wagner commented on JBIDE-19703: ------------------------------------------ {code} java version "1.8.0_45" Java(TM) SE Runtime Environment (build 1.8.0_45-b14) Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode) {code} {code} Groovy Version: 2.4.0 JVM: 1.8.0_45 Vendor: Oracle Corporation OS: Linux {code} > Offline script is unable to resolve dependencies (error grabbing Grapes) > ------------------------------------------------------------------------ > > Key: JBIDE-19703 > URL: https://issues.jboss.org/browse/JBIDE-19703 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.Alpha2 > Environment: JBDS 9.0.0.Alpha2 > Reporter: Radim Hopp > Assignee: Fred Bricon > Fix For: 4.3.0.Beta1 > > > When user has empty .groovy/grapes, offline script is not working: > {noformat}groovy "/home/rhopp/workspace-tests/.metadata/.plugins/org.jboss.tools.project.examples/offline/go_offline_3.0.0.Alpha2_v20150417_1854_B11.groovy" http://download.jboss.org/jbosstools/examples/4.3/project-examples-catego... http://download.jboss.org/jbosstools/examples/4.3/project-examples-shared... http://download.jboss.org/jbosstools/examples/4.3/project-examples-jbds90... http://download.jboss.org/gatein/quickstarts/jboss-portal-6.2/project-exa... -e |tee output > org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: > General error during conversion: Error grabbing Grapes -- [download failed: org.jboss.logging#jboss-logging;3.1.2.GA!jboss-logging.jar] > java.lang.RuntimeException: Error grabbing Grapes -- [download failed: org.jboss.logging#jboss-logging;3.1.2.GA!jboss-logging.jar] > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:422) > at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:77) > at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:71) > at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:81) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:57) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:230) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:242) > at groovy.grape.GrapeIvy.getDependencies(GrapeIvy.groovy:418) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite$PogoCachedMethodSite.invoke(PogoMetaMethodSite.java:166) > at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.callCurrent(PogoMetaMethodSite.java:56) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:49) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:149) > at groovy.grape.GrapeIvy.resolve(GrapeIvy.groovy:563) > at groovy.grape.GrapeIvy$resolve$1.callCurrent(Unknown Source) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:49) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:149) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185) > at groovy.grape.GrapeIvy.resolve(GrapeIvy.groovy:532) > at groovy.grape.GrapeIvy$resolve$0.callCurrent(Unknown Source) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:49) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:149) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:177) > at groovy.grape.GrapeIvy.grab(GrapeIvy.groovy:254) > at groovy.grape.Grape.grab(Grape.java:163) > at groovy.grape.GrabAnnotationTransformation.visit(GrabAnnotationTransformation.java:358) > at org.codehaus.groovy.transform.ASTTransformationVisitor$3.call(ASTTransformationVisitor.java:319) > at org.codehaus.groovy.control.CompilationUnit.applyToSourceUnits(CompilationUnit.java:928) > at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:590) > at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:566) > at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:543) > at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:297) > at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:267) > at groovy.lang.GroovyShell.parseClass(GroovyShell.java:692) > at groovy.lang.GroovyShell.run(GroovyShell.java:521) > at groovy.lang.GroovyShell.run(GroovyShell.java:511) > at groovy.ui.GroovyMain.processOnce(GroovyMain.java:650) > at groovy.ui.GroovyMain.run(GroovyMain.java:381) > at groovy.ui.GroovyMain.process(GroovyMain.java:367) > at groovy.ui.GroovyMain.processArgs(GroovyMain.java:126) > at groovy.ui.GroovyMain.main(GroovyMain.java:106) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.codehaus.groovy.tools.GroovyStarter.rootLoader(GroovyStarter.java:106) > at org.codehaus.groovy.tools.GroovyStarter.main(GroovyStarter.java:128) > 1 error > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19703) Offline script is unable to resolve dependencies (error grabbing Grapes)

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19703?page=com.atlassian.jira.plugi... ] Radim Hopp commented on JBIDE-19703: ------------------------------------ Sorry for not mentioning that: {noformat}➜ ~ java -version openjdk version "1.8.0_40" OpenJDK Runtime Environment (build 1.8.0_40-b25) OpenJDK 64-Bit Server VM (build 25.40-b25, mixed mode) ➜ ~ groovy -version Groovy Version: 2.4.0 JVM: 1.8.0_40 Vendor: Oracle Corporation OS: Linux {noformat} [~rawagner] what was your setup? > Offline script is unable to resolve dependencies (error grabbing Grapes) > ------------------------------------------------------------------------ > > Key: JBIDE-19703 > URL: https://issues.jboss.org/browse/JBIDE-19703 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.Alpha2 > Environment: JBDS 9.0.0.Alpha2 > Reporter: Radim Hopp > Assignee: Fred Bricon > Fix For: 4.3.0.Beta1 > > > When user has empty .groovy/grapes, offline script is not working: > {noformat}groovy "/home/rhopp/workspace-tests/.metadata/.plugins/org.jboss.tools.project.examples/offline/go_offline_3.0.0.Alpha2_v20150417_1854_B11.groovy" http://download.jboss.org/jbosstools/examples/4.3/project-examples-catego... http://download.jboss.org/jbosstools/examples/4.3/project-examples-shared... http://download.jboss.org/jbosstools/examples/4.3/project-examples-jbds90... http://download.jboss.org/gatein/quickstarts/jboss-portal-6.2/project-exa... -e |tee output > org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: > General error during conversion: Error grabbing Grapes -- [download failed: org.jboss.logging#jboss-logging;3.1.2.GA!jboss-logging.jar] > java.lang.RuntimeException: Error grabbing Grapes -- [download failed: org.jboss.logging#jboss-logging;3.1.2.GA!jboss-logging.jar] > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:422) > at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:77) > at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:71) > at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:81) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:57) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:230) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:242) > at groovy.grape.GrapeIvy.getDependencies(GrapeIvy.groovy:418) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite$PogoCachedMethodSite.invoke(PogoMetaMethodSite.java:166) > at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.callCurrent(PogoMetaMethodSite.java:56) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:49) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:149) > at groovy.grape.GrapeIvy.resolve(GrapeIvy.groovy:563) > at groovy.grape.GrapeIvy$resolve$1.callCurrent(Unknown Source) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:49) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:149) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185) > at groovy.grape.GrapeIvy.resolve(GrapeIvy.groovy:532) > at groovy.grape.GrapeIvy$resolve$0.callCurrent(Unknown Source) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:49) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:149) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:177) > at groovy.grape.GrapeIvy.grab(GrapeIvy.groovy:254) > at groovy.grape.Grape.grab(Grape.java:163) > at groovy.grape.GrabAnnotationTransformation.visit(GrabAnnotationTransformation.java:358) > at org.codehaus.groovy.transform.ASTTransformationVisitor$3.call(ASTTransformationVisitor.java:319) > at org.codehaus.groovy.control.CompilationUnit.applyToSourceUnits(CompilationUnit.java:928) > at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:590) > at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:566) > at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:543) > at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:297) > at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:267) > at groovy.lang.GroovyShell.parseClass(GroovyShell.java:692) > at groovy.lang.GroovyShell.run(GroovyShell.java:521) > at groovy.lang.GroovyShell.run(GroovyShell.java:511) > at groovy.ui.GroovyMain.processOnce(GroovyMain.java:650) > at groovy.ui.GroovyMain.run(GroovyMain.java:381) > at groovy.ui.GroovyMain.process(GroovyMain.java:367) > at groovy.ui.GroovyMain.processArgs(GroovyMain.java:126) > at groovy.ui.GroovyMain.main(GroovyMain.java:106) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.codehaus.groovy.tools.GroovyStarter.rootLoader(GroovyStarter.java:106) > at org.codehaus.groovy.tools.GroovyStarter.main(GroovyStarter.java:128) > 1 error > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19697) org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19697?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19697: --------------------------------------- OK, yes, that would explain it. But your paths to runtime_locations.properties are not exactly correct, right? There must be * somewhere in there - meaning it will try to search in all the directories up from $ECLIPSE_HOME. In my case I have this kind of directory tree: /Users/rasp/jbossqa/JBDS/9.0.0 /Users/rasp/jbossqa/JBDS/9.0.0/Eclipse-runtime-test.app /Users/rasp/jbossqa/JBDS/9.0.0/Eclipse-runtime-test.app/Contents/MacOS/eclipse /Users/rasp/jbossqa/JBDS/9.0.0/jbdevstudio-9.0.0.Alpha1-java8/studio/runtime_locations.properties /Users/rasp/jbossqa/JBDS/9.0.0/jbdevstudio-9.0.0.Alpha2-24/studio/runtime_locations.properties > org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-19697 > URL: https://issues.jboss.org/browse/JBIDE-19697 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Snjezana Peco > > When I install JBDs 9.0.0.Alpha2 B24 BYOE into new Eclipse Mars M6 and new workspace, during the installation, suddenly the runtime detection config appears inside my Eclipse isntall dir: > {code} > $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs' > Eclipse-runtime-test.app//Contents/Eclipse/configuration/.settings/org.jboss.tools.runtime.ui.prefs > {code} > This is inside the file: > {code} > $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'|xargs cat > eclipse.preferences.version=1 > runtimePaths=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?>\n<runtimePaths version\="2">\n <runtimePath path\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" scanOnEveryStartup\="false" timestamp\="-1">\n <serverDefinitions>\n <serverDefinition description\="" enabled\="true" location\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" name\="JBoss EAP 6.3" type\="EAP" version\="6.3">\n <included/>\n </serverDefinition>\n </serverDefinitions>\n </runtimePath>\n</runtimePaths>\n > {code} > It contains /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0 which I use regularly when testing server tooling. But how did this happen? > I looked for the pref file before I started BYOE installation. Then a bit later, a few minutes into the installation, I checked again and the file is there now. > Can somebody explain what's going on? > Note: This happened to me yesterday and it surprised me, but I wasn't sure if it wasn't my mistake somehow. But Max preferred I try again, so I did. And it is happening again now. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

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 April 2015