May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18820) define how to handle ide.properties and avoid parent pom to always change

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18820?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18820: ---------------------------------------- Sprint: Sprint #3 May 2015, Sprint #4 May 2015 (was: Sprint #3 May 2015) > define how to handle ide.properties and avoid parent pom to always change > ------------------------------------------------------------------------- > > Key: JBIDE-18820 > URL: https://issues.jboss.org/browse/JBIDE-18820 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 4.3.0.Beta1 > > > As illustrated in JBIDE-18806 our current setup of how ide.properties and project versioning are not working or at least we seem to not get it updated right. > Current workaround applied is that parent pom now again defines the global version even though this is not reliable at all since not all plugins will be rebuilt. (see JBIDE-13452 for earlier attempts on this) > Opening this jira to make sure we walkthrough and write down which values should be in ide.properties and what level (4.2.0.CR1, 4.2.0 or 4.2. etc), when they get updated (hopefully rarely) and how to avoid parent pom from always having to respin because of a maintanence release. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14610) Design http://download.jboss.org/jbosstools structure

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14610?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-14610: ---------------------------------------- Sprint: Sprint #3 May 2015, Sprint #4 May 2015 (was: Sprint #3 May 2015) > Design http://download.jboss.org/jbosstools structure > ----------------------------------------------------- > > Key: JBIDE-14610 > URL: https://issues.jboss.org/browse/JBIDE-14610 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, updatesite > Affects Versions: 4.1.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.0.Beta1 > > > We have several types of objects which names should be presented in site stucture: > # Project: jbosstools > # Project Version: 4.1.0.Beta2,4.1.0.CR1, 4.1.0.Final > # Subproject: core, soatools > # Module: base, javaee, central, freemarker and etc. > # Distribution Type: updates|builds > # Bits Type: stable|development|nightly > # Targeted Eclipse: indigo|juno|kepler > # You name it ... > Now we mostly use following patterns to publish nightly bits, but not always and not for every project: > # aggregated update sites: $\{Project Name\}/updates/$\{Bits Type\}/$\{Subproject Name\}/$\{Targeted Eclipse\} > # jbosstools modules composite nightly update sites are in $\{Project Name\}/builds/staging and it has no structure > # jbosstools modules builds are published to $\{Project Name\}/builds/$\{Bits Type\} and it seems strategy of publishing is always being changed here, there is folder that match subcomponent name 'core' that was updated last time in February and 'trunk' folder that contains recent bits -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17989) keyword used for plugin tracking is missing majority of times on GA

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17989?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-17989: ---------------------------------------- Sprint: Sprint #3 May 2015, Sprint #4 May 2015 (was: Sprint #3 May 2015) > keyword used for plugin tracking is missing majority of times on GA > ------------------------------------------------------------------- > > Key: JBIDE-17989 > URL: https://issues.jboss.org/browse/JBIDE-17989 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: usage > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Beta1 > > Attachments: devstudio-january.png, graphformissingstats.png, jbds.png, scr.png > > > looking at tracking numbers i'm seeing more and more requests where the keywords are not making it into the result. > Meaning we can't see how many have installed the various plugins. > What is weird *some* do and others do not have it. > Need to track down the reason for that being missed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3367?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3367: -------------------------------------- Sprint: Sprint #3 May 2015, Sprint #4 May 2015 (was: Sprint #3 May 2015) > 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)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19706) Refactor the hibernate service provider implementations

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19706?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19706: ---------------------------------------- Sprint: Sprint #3 May 2015, Sprint #4 May 2015 (was: Sprint #3 May 2015) > Refactor the hibernate service provider implementations > -------------------------------------------------------- > > Key: JBIDE-19706 > URL: https://issues.jboss.org/browse/JBIDE-19706 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.3.0.Alpha2 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.3.0.Beta1 > > > The SPI implementation "proxy" classes need a common superclass that can implement most of the functionality using introspection. In this way probably 70% of the code can be eliminated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19431) Cannot generate ddl when hibernate console is used

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19431?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19431: ---------------------------------------- Sprint: Sprint #3 May 2015, Sprint #4 May 2015 (was: Sprint #3 May 2015) > Cannot generate ddl when hibernate console is used > -------------------------------------------------- > > Key: JBIDE-19431 > URL: https://issues.jboss.org/browse/JBIDE-19431 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.3.Beta1 > Environment: JBDS 8.1.0.Beta1 > Reporter: Jiri Peterka > Assignee: Koen Aers > Priority: Critical > Fix For: 4.3.0.Beta1 > > > Cannot generate ddl when hibernate console is used. I will investigate further, it worked for 4.3 (and didn't work for lower hibernate versions) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19795) Bower support

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19795?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19795: ---------------------------------------- Sprint: Sprint #3 May 2015, Sprint #4 May 2015 (was: Sprint #3 May 2015) > Bower support > ------------- > > Key: JBIDE-19795 > URL: https://issues.jboss.org/browse/JBIDE-19795 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Affects Versions: 4.3.0.Alpha2 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.3.0.Final > > > Need to have initial [Bower|http://bower.io/] tools support: > *The gist* > Bower tooling should initially support several bower API commands : > |Command||Description| > | *bower init* |creates a *bower.json* file| > |*bower install <package>*|installs packages to *bower_components* folder| > |*bower uninstall <package>*|uninstalls a package locally from *bower_components* directory| > |*bower update* |updates installed packages to their newest version according to *bower.json*| > Basically, the main idea of the implementation is the following: > Eclipse plugin that will execute *external* bower commands - implementation will fall back on *native* bower installation via *ILaunchConfiguration* > Native bower tools must be preinstalled > *The main questions & proposals:* > 1. https://github.com/jbosstools/jbosstools-playground is probably the best place for initial implementation of bower stuff (infrastructure / build etc.) > 2. UI. should it be ILaunchShortcuts ("bower init" / "bower update" etc.) + launch configuration enabled for projects with js nature? > 3. Implementation details: > - the way of detecting bower? Should user point to it's installation dir and this location will be used for IExternalToolConstants.ATTR_LOCATION (windows case: *\user\AppData\Roaming\npm\node_modules\bower* ) > - if bower was not detected / installed - "Error message with a link to the bower website with installation details depending on the platform" -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16970) create p2diff job to verify that nightly build is different from previous milestone

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16970?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-16970: ---------------------------------------- Sprint: Sprint #3 May 2015, Sprint #4 May 2015 (was: Sprint #3 May 2015) > create p2diff job to verify that nightly build is different from previous milestone > ----------------------------------------------------------------------------------- > > Key: JBIDE-16970 > URL: https://issues.jboss.org/browse/JBIDE-16970 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > After the discovery site build job is done, we should: > * get a list of JIRAs for a given target fixversion, eg., 4.2.0.Beta1 or 8.0.0.Beta1 *job param* milestone = Beta1, Beta2, CR1, Final/GA (special case) > * for respins, use *job param* label = "respin-a" or "respin-b" in jira query > * filter query to only show the components and map those to actual project names - see https://github.com/jbdevstudio/jbdevstudio-ci/blob/master/bin/createTaskJ... for mappings > * install Eclipse from *job param* eclipseBundleVersion = luna.M6 > * install last milestone from *job param* oldURL = http://download.jboss.org/jbosstools/updates/staging/JBossTools-4.2.0.Bet... > * install Eclipse from *job param* eclipseBundleVersion = luna.M6 (in a different folder) > * install new nightly from *job param* oldURL = http://download.jboss.org/jbosstools/updates/nightlycore/4.2.luna/ > * compare installed footprints - see https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/instal... > * run p2diff on the two repos - see https://github.com/irbull/p2diff -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19704?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19704: ---------------------------------------- Sprint: Sprint #3 May 2015, Sprint #4 May 2015 (was: Sprint #3 May 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: Konstantin Marmalyukov > Fix For: 4.3.0.Beta1 > > > 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)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19387) improve integration of integration stack jars into staged JBT / JBDS sites

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19387?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19387: ---------------------------------------- Sprint: Sprint #3 May 2015, Sprint #4 May 2015 (was: Sprint #3 May 2015) > improve integration of integration stack jars into staged JBT / JBDS sites > -------------------------------------------------------------------------- > > Key: JBIDE-19387 > URL: https://issues.jboss.org/browse/JBIDE-19387 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, updatesite > Affects Versions: 4.2.3.Beta1 > Reporter: Radim Hopp > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > I have this error in error log after startup of JBT: > {noformat:title=Cannot download bundle at http://download.jboss.org/jbosstools/discovery/staging/4.2.3.Beta1/plugin...: http://download.jboss.org/jbosstools/discovery/staging/4.2.3.Beta1/plugin...: http://download.jboss.org/jbosstools/discovery/staging/4.2.3.Beta1/plugin... > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryStatusHelper.checkFileNotFound(RepositoryStatusHelper.java:297) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.checkException(FileReader.java:441) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.sendRetrieveRequest(FileReader.java:398) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:322) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > 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:483) > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.project.examples.internal.discovery.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.project.examples.internal.discovery.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {noformat} > http://download.jboss.org/jbosstools/discovery/staging/4.2.3.Beta1/jbosst... is pointing to non-existing http://download.jboss.org/jbosstools/discovery/staging/4.2.3.Beta1/plugin... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

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