November 2014 - jbosstools-issues

[JBoss JIRA] (JBTIS-360) earlyaccess setup leaks jboss.org and development urls into stable/devstudio urls

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-360?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-360: ---------------------------------- So... we need to add a line #80: {code} jboss.discovery.site.integration-stack.url|devstudio|8.0.0.GA=https://dev... {code} And fix line #44: {code} jboss.discovery.site.integration-stack.url|jbosstools|4.2.0.Final=http://... {code} > earlyaccess setup leaks jboss.org and development urls into stable/devstudio urls > --------------------------------------------------------------------------------- > > Key: JBTIS-360 > URL: https://issues.jboss.org/browse/JBTIS-360 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > Fix For: 8.0.0.Beta1 > > Attachments: ea-jbdsis.png, ea-jbtis.png > > > using IS earlyacces from jbosstools stable release I get: > http://download.jboss.org/jbosstools/updates/development/luna/central/int... > That should never get into stable. > Only the earlyaccess site should be added here. > For developer studio it gets even messier. > https://www.dropbox.com/s/3wlmw9hd6pey4mc > /Screenshot%202014-11-12%2013.13.34.png?dl=0 > https://devstudio.redhat.com/earlyaccess/8.0/ is correct, but then there are these two added sites that should not be present: > http://download.jboss.org/jbosstools/updates/development/luna/central/int... > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/ > This should be rolledback ASAP since users that install these will now get all the latest development updates instead of just the tested and verified to be in earlyaccess bits. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-360) earlyaccess setup leaks jboss.org and development urls into stable/devstudio urls

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-360?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBTIS-360: ------------------------------------------- the line missing is jboss.discovery.site.integration-stack.url|devstudio|8.0.0.GA=https://dev... > earlyaccess setup leaks jboss.org and development urls into stable/devstudio urls > --------------------------------------------------------------------------------- > > Key: JBTIS-360 > URL: https://issues.jboss.org/browse/JBTIS-360 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > Fix For: 8.0.0.Beta1 > > Attachments: ea-jbdsis.png, ea-jbtis.png > > > using IS earlyacces from jbosstools stable release I get: > http://download.jboss.org/jbosstools/updates/development/luna/central/int... > That should never get into stable. > Only the earlyaccess site should be added here. > For developer studio it gets even messier. > https://www.dropbox.com/s/3wlmw9hd6pey4mc > /Screenshot%202014-11-12%2013.13.34.png?dl=0 > https://devstudio.redhat.com/earlyaccess/8.0/ is correct, but then there are these two added sites that should not be present: > http://download.jboss.org/jbosstools/updates/development/luna/central/int... > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/ > This should be rolledback ASAP since users that install these will now get all the latest development updates instead of just the tested and verified to be in earlyaccess bits. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-360) earlyaccess setup leaks jboss.org and development urls into stable/devstudio urls

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-360?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBTIS-360: ------------------------------------------- earlyaccess = NOT final/GA already. We got stabledevelopment/nightly etc. streams to make clean separations. When we do 8.0-development we want a place to put 8.0-development earlyaccess content for testing. Thus stable should not be mixed with development. > earlyaccess setup leaks jboss.org and development urls into stable/devstudio urls > --------------------------------------------------------------------------------- > > Key: JBTIS-360 > URL: https://issues.jboss.org/browse/JBTIS-360 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > Fix For: 8.0.0.Beta1 > > Attachments: ea-jbdsis.png, ea-jbtis.png > > > using IS earlyacces from jbosstools stable release I get: > http://download.jboss.org/jbosstools/updates/development/luna/central/int... > That should never get into stable. > Only the earlyaccess site should be added here. > For developer studio it gets even messier. > https://www.dropbox.com/s/3wlmw9hd6pey4mc > /Screenshot%202014-11-12%2013.13.34.png?dl=0 > https://devstudio.redhat.com/earlyaccess/8.0/ is correct, but then there are these two added sites that should not be present: > http://download.jboss.org/jbosstools/updates/development/luna/central/int... > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/ > This should be rolledback ASAP since users that install these will now get all the latest development updates instead of just the tested and verified to be in earlyaccess bits. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-8874) Support XML documents for XSLT compliant browser

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8874?page=com.atlassian.jira.plugin... ] Konstantin Marmalyukov commented on JBIDE-8874: ----------------------------------------------- [~maxandersen] I thought about it and cannot find the answer. We have to show users that our product can open xml files and show the result. On the other hand, we should not decide for user. But in this case we need a blog. One more problem: we already have JBoss Tools XML editor. AFAIU it is just a stub, except cases of opening web.xml file('special implementation' for this case). Maybe [~dgolovin], [~akazakov], [~vrubezhny] knows something about it? If it is just a renamed eclipse xml editor - it should me removed. > Support XML documents for XSLT compliant browser > ------------------------------------------------ > > Key: JBIDE-8874 > URL: https://issues.jboss.org/browse/JBIDE-8874 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core > Affects Versions: 3.3.0.M1 > Reporter: Denis Golovin > Assignee: Konstantin Marmalyukov > Priority: Minor > Fix For: 4.3.0.Alpha1 > > Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png, screenshot59.png, wecandoit.png, xml-xsl.png > > > Would be good to have support to show documents for XSLT compliant browser like > {code:title=cdcatalog.xsl|borderStyle=solid} > <?xml version="1.0" encoding="ISO-8859-1"?> >  > <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> > <xsl:template match="/"> > <html> > <body> > <h2>My CD Collection</h2> > <table border="1"> > <tr bgcolor="#9acd32"> > <th>Title</th> > <th>Artist</th> > </tr> > <xsl:for-each select="catalog/cd"> > <tr> > <td><xsl:value-of select="title"/></td> > <td><xsl:value-of select="artist"/></td> > </tr> > </xsl:for-each> > </table> > </body> > </html> > </xsl:template> > </xsl:stylesheet> > {code} > {code:title=page.xml|borderStyle=solid} > <?xml version="1.0" encoding="ISO-8859-1"?> > <?xml-stylesheet type="text/xsl" href="cdcatalog.xsl"?> >  > <catalog> > <cd> > <title>Empire Burlesque</title> > <artist>Bob Dylan</artist> > <country>USA</country> > <company>Columbia</company> > <price>10.90</price> > <year>1985</year> > </cd> > <cd> > <title>Hide your heart</title> > <artist>Bonnie Tyler</artist> > <country>UK</country> > <company>CBS Records</company> > <price>9.90</price> > <year>1988</year> > </cd> > <cd> > <title>Greatest Hits</title> > <artist>Dolly Parton</artist> > <country>USA</country> > <company>RCA</company> > <price>9.90</price> > <year>1982</year> > </cd> > </catalog> > {code} > Visual part of editor would look like: > !screenshot59.png! -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18745) Separate Eclipse Marketplace entry for Hybrid Mobile

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18745?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18745: ------------------------------------ My comma reference was in reference to "just for info, this bug was created to get the list of features defined and then the entry should be created by the same jbosstools users as the other marketplace entries and before we actually go create it need to actually test the install." which refers to multiple "jbosstools users" (plural) and was, for me, incomprehensible. #jetlag And yes, I'd forgotten that these are now group-owned. So new entries need to be created by tools(a)jboss.org, not specific eclipse users. > Separate Eclipse Marketplace entry for Hybrid Mobile > ---------------------------------------------------- > > Key: JBIDE-18745 > URL: https://issues.jboss.org/browse/JBIDE-18745 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.2.0.Final > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Priority: Blocker > > Create a new marketplace entry for JBoss tools Hybrid Mobile which should include the following features. > - org.jboss.tools.aerogear.thym.feature > - org.jboss.tools.vpe.cordovasim.feature > - org.jboss.tools.jst.angularjs.feature > - org.jboss.tools.livereload.feature > And central > - org.jboss.tools.community.central.feature > - org.jboss.tools.community.project.examples.feature -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18377) Automatically add the dependencies specified in jboss-deployment-structure.xml to build path

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18377?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-18377: ----------------------------------- Assignee: Rob Stryker > Automatically add the dependencies specified in jboss-deployment-structure.xml to build path > -------------------------------------------------------------------------------------------- > > Key: JBIDE-18377 > URL: https://issues.jboss.org/browse/JBIDE-18377 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Gary Hu > Assignee: Rob Stryker > Fix For: 4.3.0.Alpha1 > > > I am deploying a dynamic web project to EAP 6 using JBDS 6+. My project's build path includes the JRE System Library, EAP 6 Runtime, and Web App Libraries (the WEB-INF/lib folder). I also have a jboss-deployment-structure.xml file that defines additional module dependencies such as the following: > <jboss-deployment-structure> > <deployment> > <dependencies> > <module name="org.slf4j" /> > <module name="org.apache.log4j" /> > </dependencies> > </deployment> > </jboss-deployment-structure> > The problem is, the slf4j and log4j modules are not included in the project's build path. While the server resolves them correctly at runtime because of the jboss-deployment-structure.xml file, Eclipse doesn't include them. So the following declaration in the Java code would result in a build error because org.apache.log4j cannot be resolved to a type: > private static final org.apache.log4j.Logger log = org.apache.log4j.Logger.getLogger(Example.class); > Please note that the project has configured correctly the JBoss Server Runtime which points to a valid JBoss directory, and the module dependencies are properly installed in the server. > The dependencies specified in the jboss-deployment-structure.xml are some private modules installed at the server side but not included in the server runtime by default. > So, is there a way to automatically add the jboss-deployment-structure module dependencies to the Eclipse build path? So far, I've been unable to find a way to do this. > I have found a few workarounds, but none of them are ideal, and they seem to completely miss the point of module-based dependencies: > - Customize the Default Classpath Entries for the server runtime. This is not acceptable because it must be done in each developer's workspace – and possibly per project since projects may have different, conflicting dependencies. > - Add the libraries to WEB-INF/lib. This is not acceptable because it defeats the purpose of server modules. > - Add the libraries to a user library for the project. This could work, but it's very inconvenient, because each developer on the team would have to add the jars to the user libraries in their workspaces. > Here can find the discussion of exact same issue https://developer.jboss.org/thread/203309?tstart=0 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-360) earlyaccess setup leaks jboss.org and development urls into stable/devstudio urls

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-360?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-360: ---------------------------------- Max said: {quote} http://download.jboss.org/jbosstools/configuration/ide-config.properties seem to have the 8.0.0.GA settings commented out. {quote} If you look carefully, you'll see that's not true: https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... I guess JBT/JBDS users only need to see ONE early access URL in the Available sites, which means they'll be getting their pre-GA EA content from the /stable/ or 8.0/ URL, instead of the /development/ or /8.0-development/ URL. Thus we would reserve the /development/ and /8.0-development/ URLs for JBDS pre-GA milestones (8.0.1.CR1 will be the next one) and never link a JBT Final or JBDS GA user to the /development/ or /8.0-development/ sites. > earlyaccess setup leaks jboss.org and development urls into stable/devstudio urls > --------------------------------------------------------------------------------- > > Key: JBTIS-360 > URL: https://issues.jboss.org/browse/JBTIS-360 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > Fix For: 8.0.0.Beta1 > > Attachments: ea-jbdsis.png, ea-jbtis.png > > > using IS earlyacces from jbosstools stable release I get: > http://download.jboss.org/jbosstools/updates/development/luna/central/int... > That should never get into stable. > Only the earlyaccess site should be added here. > For developer studio it gets even messier. > https://www.dropbox.com/s/3wlmw9hd6pey4mc > /Screenshot%202014-11-12%2013.13.34.png?dl=0 > https://devstudio.redhat.com/earlyaccess/8.0/ is correct, but then there are these two added sites that should not be present: > http://download.jboss.org/jbosstools/updates/development/luna/central/int... > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/ > This should be rolledback ASAP since users that install these will now get all the latest development updates instead of just the tested and verified to be in earlyaccess bits. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-360) earlyaccess setup leaks jboss.org and development urls into stable/devstudio urls

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-360?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-360: ---------------------------------- Hey Max - I did test these - its behaving the way I thought it would. We're pulling in Beta1 IS components as early access - it didn't make sense (to me) to push that to the stable URLs. Users are asking to install early access integration stack components into a GA JBDS. We don't want to mix the development and stable streams but it makes sense if it's under the "earlyaccess" URL. I think users would expect to see: https://devstudio.redhat.com/earlyaccess/8.0-development/ or http://download.jboss.org/jbosstools/earlyaccess/development/luna/ for the Beta IS. We're not mixing stable and development - we're mixing stable and earlyaccess. [~nickboldt] - wdyt > earlyaccess setup leaks jboss.org and development urls into stable/devstudio urls > --------------------------------------------------------------------------------- > > Key: JBTIS-360 > URL: https://issues.jboss.org/browse/JBTIS-360 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > Fix For: 8.0.0.Beta1 > > Attachments: ea-jbdsis.png, ea-jbtis.png > > > using IS earlyacces from jbosstools stable release I get: > http://download.jboss.org/jbosstools/updates/development/luna/central/int... > That should never get into stable. > Only the earlyaccess site should be added here. > For developer studio it gets even messier. > https://www.dropbox.com/s/3wlmw9hd6pey4mc > /Screenshot%202014-11-12%2013.13.34.png?dl=0 > https://devstudio.redhat.com/earlyaccess/8.0/ is correct, but then there are these two added sites that should not be present: > http://download.jboss.org/jbosstools/updates/development/luna/central/int... > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/ > This should be rolledback ASAP since users that install these will now get all the latest development updates instead of just the tested and verified to be in earlyaccess bits. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18692) Jenkins build for jbosstools-incubator-ripple

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18692?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18692: ---------------------------------------- Next eng-ops request: https://engineering.redhat.com/rt/Ticket/Display.html?id=324732 > Jenkins build for jbosstools-incubator-ripple > --------------------------------------------- > > Key: JBIDE-18692 > URL: https://issues.jboss.org/browse/JBIDE-18692 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Gorkem Ercan > Assignee: Mickael Istria > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > > We need a jenkins job to build for jbosstools-incubator-ripple, and have it > invoking "./configure && jake" and distribute the builds to Nexus so that cordovasim can start using ripple from this repo. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18564) Provide a default connection to in-memory database

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18564?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-18564. --------------------------------- Resolution: Duplicate Issue Duplicate of /JBIDE-18564 Closing this issue since /JBIDE-18564 has the discussion on it. > Provide a default connection to in-memory database > -------------------------------------------------- > > Key: JBIDE-18564 > URL: https://issues.jboss.org/browse/JBIDE-18564 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Arun Gupta > Fix For: 4.3.x > > > If WildFly is chosen as the application server to run the project, then show a default connection to the in-memory database. Otherwise user will have to figure it out by googling. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 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 November 2014