June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22446) Release process can include snapshots artifacts

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22446?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22446: ----------------------------------- Fix Version/s: (was: 4.4.0.Final) > Release process can include snapshots artifacts > ----------------------------------------------- > > Key: JBIDE-22446 > URL: https://issues.jboss.org/browse/JBIDE-22446 > Project: Tools (JBoss Tools) > Issue Type: Release > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Jeff MAURY > Fix For: 4.4.x > > > 4.4.0.Alpha2 was generated with a SNAPSHOT dependency. This should be avoided in future releases even for Alpha ones > Update: This issues is for adding some automated test/check to detect situation when our release includes a snapshot dependency. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22446) Release process can include snapshots artifacts

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22446?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22446: ----------------------------------- Labels: (was: respin-a) > Release process can include snapshots artifacts > ----------------------------------------------- > > Key: JBIDE-22446 > URL: https://issues.jboss.org/browse/JBIDE-22446 > Project: Tools (JBoss Tools) > Issue Type: Release > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Jeff MAURY > Fix For: 4.4.x > > > 4.4.0.Alpha2 was generated with a SNAPSHOT dependency. This should be avoided in future releases even for Alpha ones > Update: This issues is for adding some automated test/check to detect situation when our release includes a snapshot dependency. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-729) Teiid Designer depends on bundle in JBT/devstudio TP which no longer exists

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-729?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-729: ---------------------------------- Since the org.eclipse.core.runtime.compatibility 3.2.300.v20150423-0821 plugin exists in http://download.jboss.org/jbosstools/updates/requirements/birt/4.5.0.v201... it can now be accessed when installing Teiid 10.0.0.Beta3 from the Mars-based Integration Stack sites. Therefore it doesn't need to be in the 4.60.0.Final-SNAPSHOT target platform for JBT 4.4.0.Final / 10.0.0.GA, and I've re-removed it. The patchfix to the IS 4.3.x / 9.x EA composite sites allows the old Mars-based Teiid 10.0.0.Beta3 to be installable on BOTH JBT 4.3.x and 4.4.0, and BOTH devstudio 9.x and 10.0.0. Eventually, I would hope that something newer than Teiid 10.0.0.Beta3-v20160218-1807-B4076 will be updated to NOT depend on the runtime.compatibility plugin. But making that change no longer blocks the release of JBT 4.4.0.Final / devstudio 10.0.0.GA. > Teiid Designer depends on bundle in JBT/devstudio TP which no longer exists > --------------------------------------------------------------------------- > > Key: JBTIS-729 > URL: https://issues.jboss.org/browse/JBTIS-729 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: target-platform, teiid > Affects Versions: 4.4.0.Alpha1-TP, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Barry LaFond > Fix For: 4.4.0.Alpha1-TP > > > org.eclipse.core.runtime.compatibility was removed from the JBT and devstudio target platforms because nothing in JBT/devstudio requires it any more. > As a result, when you try to install Teiid Designer into the staged JBT 4.4.0.Final or devstudio 10.0.0.GA via Central, you get this error: > {code} > !MESSAGE Missing requirement: Teiid DataTools Connectivity 10.0.0.Beta3-v20160218-1807-B4076 (org.teiid.datatools.connectivity.feature.feature.group 10.0.0.Beta3-v20160218-1807-B4076) requires 'org.eclipse.core.runtime.compatibility [3.2.200,4.0.0)' but it could not be found > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22464) Jax-RS validation and browser doesn't understand mulitple jax-rs applicaitons in same project

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22464?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-22464: ---------------------------------------- I'll try to share an example. Also, see this SO discussion you contributed to: http://stackoverflow.com/questions/22929499/multiple-jax-rs-applications-... . I just happened to try this in a WildFly 9, and it actually works: I have multiple jax-rs root URL, one for each application defined. > Jax-RS validation and browser doesn't understand mulitple jax-rs applicaitons in same project > --------------------------------------------------------------------------------------------- > > Key: JBIDE-22464 > URL: https://issues.jboss.org/browse/JBIDE-22464 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.4.0.Alpha2 > Reporter: Mickael Istria > Assignee: Xavier Coulon > Fix For: 4.4.x > > > I'm testing an application with 2 Jax-RS application servlets. I've defined then in the web.xml as follows (I'm not using annotations): > {code:xml} > <servlet-mapping> > <servlet-name>my.app.services.RestServices</servlet-name> > <url-pattern>/api/*</url-pattern> > </servlet-mapping> > <servlet-mapping> > <servlet-name>my.app.pages.WebPages</servlet-name> > <url-pattern>/pages/*</url-pattern> > </servlet-mapping> > {code} > This cause a few issues: > * in web.xml "Multiple JAX-RS Activators are defined for the project." (error by default, I set it to warning) > * in the RestfulServices class, "The Application Path should be configured with an @ApplicationPath annotation or in the web deployment descriptor." error. It seems like the validator ignores a part of the web.xml > * In Project Explorer, the "Jax-RS Services" node shows incorrect children: it shows api/ endpoints under pages/api/... whereas pages and api are "siblings". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3924) Installation looks incomplete but is actually completed

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3924?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3924: --------------------------------- Affects Version/s: 10.0.0.GA > Installation looks incomplete but is actually completed > ------------------------------------------------------- > > Key: JBDS-3924 > URL: https://issues.jboss.org/browse/JBDS-3924 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.0.0.GA > Environment: Fedora 23 > Using devstudio-10.0.0.GA-v20160603-1025-B5510-installer-standalone.jar > Reporter: Misha Ali > Assignee: Denis Golovin > Labels: install, installation, installer > Attachments: devstudio10install.png > > > Running the standalone installer file starts the devstudio install as expected, but twice I have noticed that the Next button is available to click (indicating that the installation has completed) when the status shows that only 2/3 of the installation steps are concluded. (see screenshot for this screen). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22545) Application Wizard: Default values in template parameters table are in italics

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22545?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich reassigned JBIDE-22545: --------------------------------------------- Assignee: Viacheslav Kabanovich > Application Wizard: Default values in template parameters table are in italics > ------------------------------------------------------------------------------ > > Key: JBIDE-22545 > URL: https://issues.jboss.org/browse/JBIDE-22545 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Minor > Labels: application_wizard, openshift_v3 > > In New OpenShift Application wizard on Template Parameters wizard page there is a table containing template parameters key:value pairs. Default values are in italic, but they are not supposed to be. Once user change default value to something different and then reset the value, it gets normal (not italic). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3924) Installation looks incomplete but is actually completed

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3924?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-3924: ------------------------------------ Assignee: Denis Golovin > Installation looks incomplete but is actually completed > ------------------------------------------------------- > > Key: JBDS-3924 > URL: https://issues.jboss.org/browse/JBDS-3924 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Environment: Fedora 23 > Using devstudio-10.0.0.GA-v20160603-1025-B5510-installer-standalone.jar > Reporter: Misha Ali > Assignee: Denis Golovin > Labels: install, installation, installer > Attachments: devstudio10install.png > > > Running the standalone installer file starts the devstudio install as expected, but twice I have noticed that the Next button is available to click (indicating that the installation has completed) when the status shows that only 2/3 of the installation steps are concluded. (see screenshot for this screen). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13671) Replace build timestamp in qualifier by last-mod-timestamp from git

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13671: ---------------------------------------- {quote}1. Enable 'compare with baselines' for every build's previous /latest/ CI, to ensure that a TP change shows an API break, hopefully{quote} Reading carefully https://wiki.eclipse.org/Tycho/Reproducible_Version_Qualifiers: {quote}If baseline repositories contain artifacts with the same id and version but different contents, depending on <baselineMode> configuration parameter the build will either fail or generated artifacts will be replaced with baseline version. {quote} So it seems like the comparison with baseline and failure in case of duplicate is included in the tycho-packaging-plugin. So we only need to enable baseline replacement in tycho-packaging-plugin using the previous build as a baseline. Note that the tycho-packaging-plugin baseline can be enabled independently of the jgit-timestamp-buildqualifier thing. > Replace build timestamp in qualifier by last-mod-timestamp from git > ------------------------------------------------------------------- > > Key: JBIDE-13671 > URL: https://issues.jboss.org/browse/JBIDE-13671 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Fix For: 4.4.x > > Attachments: jbide13671-before-and-after.png > > > This needs to be added to master parent pom: > {code} > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>tycho-packaging-plugin</artifactId> > <version>${tycho.version}</version> > <dependencies> > <dependency> > <groupId>org.eclipse.tycho.extras</groupId> > <artifactId>tycho-buildtimestamp-jgit</artifactId> > <version>${tycho-extras.version}</version> > </dependency> > </dependencies> > <configuration> > <strictBinIncludes>false</strictBinIncludes> > <format>'v'yyyyMMdd-HHmm</format> > <timestampProvider>jgit</timestampProvider> > <jgit.ignore> > </jgit.ignore> > </configuration> > </plugin> > {code} > Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20915) HTML Page is not refreshed after page is changed in web browser with enabled LiveReload

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20915?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20915: ----------------------------------- Fix Version/s: 4.4.0.Final (was: 4.4.x) > HTML Page is not refreshed after page is changed in web browser with enabled LiveReload > --------------------------------------------------------------------------------------- > > Key: JBIDE-20915 > URL: https://issues.jboss.org/browse/JBIDE-20915 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.3.0.CR2 > Environment: JBDS 9.0.0.GA-v20150925-1252-B116 > Reporter: Vlado Pakan > Assignee: Xavier Coulon > Labels: documentation > Fix For: 4.4.0.Final > > > 1. Import HTML 5 project from JBoss Central > 2. Run it on server > 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server' > ASSERT: index.html page is opened in system web browser > 4. Make some changes to opened page and save them. > ASSERT: Page is redisplayed in web browser and changes made to page are visible in web browser. > Repeat step 4. couple of times > ERROR: Page in web browser blinked seems to be redisplayed but content of page displayed in web browser is not changed -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3739) Docker connection does not work after cdk restart

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3739?page=com.atlassian.jira.plugin.... ] Xavier Coulon updated JBDS-3739: -------------------------------- Fix Version/s: 10.0.0.GA > Docker connection does not work after cdk restart > ------------------------------------------------- > > Key: JBDS-3739 > URL: https://issues.jboss.org/browse/JBDS-3739 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: cdk, upstream > Affects Versions: 9.1.0.CR1 > Reporter: Martin Malina > Assignee: Xavier Coulon > Priority: Blocker > Labels: havoc > Fix For: 10.0.0.GA > > Attachments: docker-frozen.txt > > > When you set up cdk and start it for the first time, docker connection is properly set up and functioning. But when you restart cdk in the servers view, docker connection will no longer work. > This is caused by a bug in vagrant-service-manager 0.0.4: > https://github.com/projectatomic/vagrant-service-manager/issues/80 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 June 2016