May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-621) Rework and Finalize Article about Generating a HTML5 Web App

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-621?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-621: ------------------------------------ I've briefly reviewed the MD version of the article and the minor editorial changes to the asciidoc version a week ago (approximately) are not implement here, nor is the check box for subscribers only disabled as indicated in the checklist. > Rework and Finalize Article about Generating a HTML5 Web App > ------------------------------------------------------------ > > Key: TOOLSDOC-621 > URL: https://issues.jboss.org/browse/TOOLSDOC-621 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Priority: Minor > Attachments: generate_HTML5_web_app.adoc > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-638) JBDS-IS: Add uninstall instructions to the Install Guide

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-638?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-638: ------------------------------------ Responded to feedback request in the google doc, but the instructions are incomplete. > JBDS-IS: Add uninstall instructions to the Install Guide > -------------------------------------------------------- > > Key: TOOLSDOC-638 > URL: https://issues.jboss.org/browse/TOOLSDOC-638 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: Installation Guide > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Priority: Minor > > We need instructions for how to uninstall JBDS-IS included in the Install Guide. This should be reviewed by QE as the correct method to remove the installation from the machine and then a new revision history entry should be added to the guide. Misha will push this public once it is reviewed and ready. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-629) Publish JBT Version of HTML5 Article

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-629?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-629: ------------------------------------ Changes: * Removed redundant images/ path in references for images in doc * Changed file name and images to lowercase * Added html5_ to beginning of all image names for better sorting * Changed image names to active voice * Built locally to test * Sent PR request > Publish JBT Version of HTML5 Article > ------------------------------------ > > Key: TOOLSDOC-629 > URL: https://issues.jboss.org/browse/TOOLSDOC-629 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Components: General documentation issues > Reporter: Misha Ali > Assignee: Misha Ali > > When Supriya has converted her article to ASCIIDoc, add this to the upstream repo, review for documentation conventions and build issues and send a PR. Implement any SME feedback and release the doc. > Misha also needs to add the CSP version of this doc to the Splash Page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3431) Update JBDS support matrix to include only major version of EAP

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-3431?page=com.atlassian.jira.plugin.... ] Misha Ali commented on JBDS-3431: --------------------------------- Had a quick chat with Len and he agrees the 6.x is good to go. Pushing draft public now and closing this issue. If there is any further action required, please feel free to reopen it. > Update JBDS support matrix to include only major version of EAP > --------------------------------------------------------------- > > Key: JBDS-3431 > URL: https://issues.jboss.org/browse/JBDS-3431 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: documentation > Affects Versions: 8.1.0.GA > Reporter: Mustafa Musaji > Assignee: Misha Ali > > Update this page https://access.redhat.com/articles/427493 > So that we only include the major versions of EAP supported > I.e. 4.x, 5.x and 6.x -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3431) Update JBDS support matrix to include only major version of EAP

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-3431?page=com.atlassian.jira.plugin.... ] Misha Ali closed JBDS-3431. --------------------------- Resolution: Done > Update JBDS support matrix to include only major version of EAP > --------------------------------------------------------------- > > Key: JBDS-3431 > URL: https://issues.jboss.org/browse/JBDS-3431 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: documentation > Affects Versions: 8.1.0.GA > Reporter: Mustafa Musaji > Assignee: Misha Ali > > Update this page https://access.redhat.com/articles/427493 > So that we only include the major versions of EAP supported > I.e. 4.x, 5.x and 6.x -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3431) Update JBDS support matrix to include only major version of EAP

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-3431?page=com.atlassian.jira.plugin.... ] Misha Ali commented on JBDS-3431: --------------------------------- Updated page to s/6.0, 6.1, 6.2, 6.3, 6.4/6.x Draft for review here: https://access.redhat.com/node/427493/draft [~apodhrad] - if it looks good to you, I'll publish it. > Update JBDS support matrix to include only major version of EAP > --------------------------------------------------------------- > > Key: JBDS-3431 > URL: https://issues.jboss.org/browse/JBDS-3431 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: documentation > Affects Versions: 8.1.0.GA > Reporter: Mustafa Musaji > Assignee: Misha Ali > > Update this page https://access.redhat.com/articles/427493 > So that we only include the major versions of EAP supported > I.e. 4.x, 5.x and 6.x -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 3 months

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 commented on JBDS-3208: ---------------------------------- All remaining Master and 9.0.mars jobs have been updated to use rsync.sh instead of publish.sh. Also updated the jobs that produce target platforms so that composite*.xml files are generated to point into ./REPO/ folders like we used to have w/ the old publish.sh scripts (build-ci and target-platforms alike). I believe this JIRA might be done. **gasp** > 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, 3 months

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 commented on JBDS-3208: ---------------------------------- Per JBIDE-19758 I've moved all the old stuff out of /builds/staging/ and updated the README to alleviate some confusion around "where's my build?" and "why is this build so old?" Would prefer to not have 30 or 40 symlinks to new content when people can simply click thru the README and update their bookmarks. > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-423) Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle'

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-423?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-423. ------------------------------ Resolution: Done I looked at what angularjs did - it was not necessary to redeclare the com.jboss.jbds.central.discovery.integration-stack.bundle connector category. Removed that and changed IDs to match the release side and removed t he EA category. https://github.com/jbosstools/jbosstools-integration-stack/commit/a629d1e... [~apodhrad] - I'll catch all of this in the CR1 release - please continue testing. > Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle' > --------------------------------------------------------------------------------- > > Key: JBTIS-423 > URL: https://issues.jboss.org/browse/JBTIS-423 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.1.GA > Environment: JBDS 8.1.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Minor > Fix For: 8.0.2.GA > > Attachments: ea1.png > > > When we try to install JBDS-IS 8.0.1.GA from JBoss Central we can see the following error in Error Log > {code} > Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle': declaring sources: > com.jboss.jbds.central.discovery.integration_stack_8.0.1.GA_v20150408_1203_B104.jar_3208083343377093610.jar, > com.jboss.jbds.central.discovery.integration_stack.earlyaccess_8.0.1.GA_v20150408_1203_B104.jar_2051386990248092532.jar > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19756) jbosstools-src.zip has incomplete/misleading version info in folder names/structure

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19756?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19756: ------------------------------------ a) Do you mean you want a root folder called jbosstools-source, and then under that all the individual repo folders? Or just mush everything into the same root folder? (Also, how about just using `unzip -d /path/to/destination/folder`?) Also, since the zip is mandated to be called "jbosstools-src", do you actually want a root folder called "jbosstools-src" with the matching name, or are you intentionally requesting a different folder name? b) The zip, once released, will have the fully-qualified version of JBoss Tools (or JBDS) on it, eg., *jbosstools-4.3.0.Beta1-src.zip*, but the qualifiers _INSIDE_ the zip reflect the version of the _individual projects' versions_. This is why you should see `jbosstools-portlet_Final` and `jbosstools-freemarker_Final` (they're not being built (yet) for 4.3.0.x, so we use their 4.2.x.Final versions). So I guess you want the x.y.z.qualifier versions here, not the 4.3.0.Beta1 version. But what do we do when there are more than one version in a project? For example, jbosstools-server has sources versioned to 1.2.0, 4.3.0, 1.7.0, 3.1.0, ... Would you like me to use the largest number? (This is why I've only used the BUILD_ALIAS and not the pom.xml version(s) for the source folders within the zip. The BUILD_ALIAS is useful, IMHO, and provides information; using the same version as the zip (4.3.0.Beta1) provides no more information than simply using Beta1. And if we use the projects' versions, then as noted above... which one do we use?) > jbosstools-src.zip has incomplete/misleading version info in folder names/structure > ----------------------------------------------------------------------------------- > > Key: JBIDE-19756 > URL: https://issues.jboss.org/browse/JBIDE-19756 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > Downloading latest jbosstools-src.zip from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui... I see multiple files in root named: > <componentname>_<buildqualifier>_<sha1> > example: > jbosstools-javaee_Beta1-v20150501-0413-B767_149f9a46d5c676fd7119515e8b6aa796859955ad > A few issues with this: > a) it would have been nice unzipping would not create multiple root level folders. Maybe have a jbosstools-source folder as root ? > b) the buildqualifier is there but the version string for the component is not. Either put the full version string for that component (not overall jbosstools version) or just leave it as <component>-<sha> and have the root folder state the full version of jbosstools. since non-indulged user would not know this one had to do with 4.3.0.Beta1 or 4.2.3.Beta1 (for example). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 3 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