December 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18558) Improve usability of up-to-date Central items

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18558?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18558: ----------------------------------- Summary: Improve usability of up-to-date Central items (was: cannot update already installed connector) > Improve usability of up-to-date Central items > --------------------------------------------- > > Key: JBIDE-18558 > URL: https://issues.jboss.org/browse/JBIDE-18558 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Labels: respin-a > Fix For: 4.2.1.Final > > > Install hybrid tools. > restart eclipse. > enable show installed, click hybrid tools. > Install/update is greyed out. > why can I not run update ? -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18558) Improve usability of up-to-date Central items

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18558?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18558: ----------------------------------- Issue Type: Enhancement (was: Bug) > Improve usability of up-to-date Central items > --------------------------------------------- > > Key: JBIDE-18558 > URL: https://issues.jboss.org/browse/JBIDE-18558 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Labels: respin-a > Fix For: 4.2.1.Final > > > Install hybrid tools. > restart eclipse. > enable show installed, click hybrid tools. > Install/update is greyed out. > why can I not run update ? -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18558) Improve usability of up-to-date Central items

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18558?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18558: ----------------------------------- Priority: Minor (was: Major) > Improve usability of up-to-date Central items > --------------------------------------------- > > Key: JBIDE-18558 > URL: https://issues.jboss.org/browse/JBIDE-18558 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Labels: respin-a > Fix For: 4.2.1.Final > > > Install hybrid tools. > restart eclipse. > enable show installed, click hybrid tools. > Install/update is greyed out. > why can I not run update ? -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3240) Provide latest EAP 6.3 / WFK 2.6 archetypes in latest JBDS 8 Central

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBDS-3240?page=com.atlassian.jira.plugin.... ] Marek Novotny commented on JBDS-3240: ------------------------------------- [~fbricon] I may overlook that option, but I haven't setup any runtime. So I guess it should be the latest greatest archetype in that case too or why it use the oldest? > Provide latest EAP 6.3 / WFK 2.6 archetypes in latest JBDS 8 Central > -------------------------------------------------------------------- > > Key: JBDS-3240 > URL: https://issues.jboss.org/browse/JBDS-3240 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.0.0.GA > Reporter: Marek Novotny > Assignee: Fred Bricon > Fix For: 8.0.1.GA > > > JBDS 8 aka JBoss Central provide by default old EAP/WFK archetype and not the latest 6.3.0.GA/2.6.0.Final by default. > For instance I click on HTML5 project in Start from Scratch in JBoss Central: > it launches wizard dialog where the archetype is org.jboss.tools.example.html5:jboss-as-kitchensink-html5-mobile:1.0.4.Final-redhat-wfk-2 version -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

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

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3208: -------------------------------------- {quote}we need to provide an update site that is a composite of multiple nightly builds, updates/*/snapshots/{quote} I don't understand why we need that. {quote}this URL must in fact be a symlink to builds/*/snapshots/ (or builds/<jobname>/) so that the N latest builds can be accessed from a single URL{quote} A symlink or a composite. My preference going for a composite. {quote}we must ensure that the cleanup script [1] is amended to perform deletes in these new folders, too.{quote} Cleaning up stuff isn't high priority and shouldn't be treated as a requirement/blocker for any change. > 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.Alpha1 > > > Be it resolved - we should reorg directories for consistency across JBT/JBDS: > {code} > download.jboss.org > <earlyaccess,updates,discovery>/mars > /snapshots [replace nightly] > /staging [rename content for QE, moves to development when approved] > /development > /stable (updates/mars/stable is a pointer back into updates/mars) > drop /integration (not used) > builds/<jobname>/<buildid> > builds/<jobname>/composite*.xml for last 2 builds > targetplatforms/<type>/<version> > {code} > and > {code} > devstudio.redhat.com > <earlyaccess,updates,discovery>/9.0 > /snapshots > /staging > /development > /stable (updates/9.0/stable is a pointer back into updates/9.0) > builds/<jobname>/<buildid> > builds/<jobname>/composite*.xml for last 2 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.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18743) write tests for download.jboss.org & devstudio.redhat.com xmlunit test cases; validate composite*.xml; *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18743?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18743: ---------------------------------------- Isn't validateCompositeSiteChildrenExist.sh a good part of the expected tests? > write tests for download.jboss.org & devstudio.redhat.com xmlunit test cases; validate composite*.xml; *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18743 > URL: https://issues.jboss.org/browse/JBIDE-18743 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Final > Reporter: Nick Boldt > Fix For: 4.3.0.Alpha1 > > > We need to write tests for download.jboss.org & devstudio.redhat.com: > * xmlunit test cases > ** validate composite*.xml > ** unit testing for discovery plugin.xml, update site category.xml (avoid bad URLs like 8.0-staging in a milestone release) > * other test cases > ** \*.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18855) Update Birt versions to 4.4.1 from 4.4.0 in the JBT unified TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18855?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18855: ---------------------------------------- I just merged the suggested PR. > Update Birt versions to 4.4.1 from 4.4.0 in the JBT unified TP > -------------------------------------------------------------- > > Key: JBIDE-18855 > URL: https://issues.jboss.org/browse/JBIDE-18855 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Reporter: Paul Leacu > Assignee: Nick Boldt > > *Reason:* You pull an updated version of Luna SR1a for use in your 4.41.x target platform, but still include the old BIRT 4.4.0 when there's a 4.4.1 version here? http://download.jboss.org/jbosstools/updates/requirements/luna/2014092610... > *Project page/sources:* ... > *Version:* 4.4.1 > *License and owner:* EPL, Eclipse.org > *Original p2 repo:* TODO > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/birt/4.4.1.v201... > *Include Sources:* No > *Affected projects:* JBTIS TP, Birt > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > suggested diff on the .target files > {code} > These features: > <unit id="org.eclipse.birt.feature.group" version="4.4.0.v201405191524-DPEp7FGixAot6DLz0hXcUqaHoLSX"/> > <unit id="org.eclipse.birt.chart.feature.group" version="4.4.0.v201405191524-829A4FQCnvK65Q9sKwwG"/> > <unit id="org.eclipse.birt.integration.wtp.feature.group" version="4.4.0.v20140521-1030-53-7w3125163202141"/> > <unit id="org.eclipse.birt.chart.integration.wtp.feature.group" version="4.4.0.v20140521-1030-53-7w3125163202141"/> > Should pick up the 4.4.1... versions as seen here: > http://download.jboss.org/jbosstools/updates/requirements/luna/2014092610... -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18855) Update Birt versions to 4.4.1 from 4.4.0 in the JBT unified TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18855?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18855: ----------------------------------- Description: *Reason:* You pull an updated version of Luna SR1a for use in your 4.41.x target platform, but still include the old BIRT 4.4.0 when there's a 4.4.1 version here? http://download.jboss.org/jbosstools/updates/requirements/luna/2014092610... *Project page/sources:* ... *Version:* 4.4.1 *License and owner:* EPL, Eclipse.org *Original p2 repo:* TODO *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/birt/4.4.1.v201... *Include Sources:* No *Affected projects:* JBTIS TP, Birt *Include in JBDS:* Yes *Type of dependency:* distribution *List of bundles added/removed:* {code} suggested diff on the .target files {code} These features: <unit id="org.eclipse.birt.feature.group" version="4.4.0.v201405191524-DPEp7FGixAot6DLz0hXcUqaHoLSX"/> <unit id="org.eclipse.birt.chart.feature.group" version="4.4.0.v201405191524-829A4FQCnvK65Q9sKwwG"/> <unit id="org.eclipse.birt.integration.wtp.feature.group" version="4.4.0.v20140521-1030-53-7w3125163202141"/> <unit id="org.eclipse.birt.chart.integration.wtp.feature.group" version="4.4.0.v20140521-1030-53-7w3125163202141"/> Should pick up the 4.4.1... versions as seen here: http://download.jboss.org/jbosstools/updates/requirements/luna/2014092610... was: *Reason:* You pull an updated version of Luna SR1a for use in your 4.41.x target platform, but still include the old BIRT 4.4.0 when there's a 4.4.1 version here? http://download.jboss.org/jbosstools/updates/requirements/luna/2014092610... *Project page/sources:* ... *Version:* 4.41.1.CR1 *License and owner:* JBoss *Original p2 repo:* http://third-party-vendor.com/path/to/updates-site/ *JBoss mirror:* http://downloads.jboss.org/jbosstools/updates/requirements/<projectName> *Include Sources:* No *Affected projects:* JBTIS TP *Include in JBDS:* Yes *Type of dependency:* distribution *List of bundles added/removed:* {code} suggested diff on the .target files {code} These features: <unit id="org.eclipse.birt.feature.group" version="4.4.0.v201405191524-DPEp7FGixAot6DLz0hXcUqaHoLSX"/> <unit id="org.eclipse.birt.chart.feature.group" version="4.4.0.v201405191524-829A4FQCnvK65Q9sKwwG"/> <unit id="org.eclipse.birt.integration.wtp.feature.group" version="4.4.0.v20140521-1030-53-7w3125163202141"/> <unit id="org.eclipse.birt.chart.integration.wtp.feature.group" version="4.4.0.v20140521-1030-53-7w3125163202141"/> Should pick up the 4.4.1... versions as seen here: http://download.jboss.org/jbosstools/updates/requirements/luna/2014092610... > Update Birt versions to 4.4.1 from 4.4.0 in the JBT unified TP > -------------------------------------------------------------- > > Key: JBIDE-18855 > URL: https://issues.jboss.org/browse/JBIDE-18855 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Reporter: Paul Leacu > Assignee: Nick Boldt > > *Reason:* You pull an updated version of Luna SR1a for use in your 4.41.x target platform, but still include the old BIRT 4.4.0 when there's a 4.4.1 version here? http://download.jboss.org/jbosstools/updates/requirements/luna/2014092610... > *Project page/sources:* ... > *Version:* 4.4.1 > *License and owner:* EPL, Eclipse.org > *Original p2 repo:* TODO > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/birt/4.4.1.v201... > *Include Sources:* No > *Affected projects:* JBTIS TP, Birt > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > suggested diff on the .target files > {code} > These features: > <unit id="org.eclipse.birt.feature.group" version="4.4.0.v201405191524-DPEp7FGixAot6DLz0hXcUqaHoLSX"/> > <unit id="org.eclipse.birt.chart.feature.group" version="4.4.0.v201405191524-829A4FQCnvK65Q9sKwwG"/> > <unit id="org.eclipse.birt.integration.wtp.feature.group" version="4.4.0.v20140521-1030-53-7w3125163202141"/> > <unit id="org.eclipse.birt.chart.integration.wtp.feature.group" version="4.4.0.v20140521-1030-53-7w3125163202141"/> > Should pick up the 4.4.1... versions as seen here: > http://download.jboss.org/jbosstools/updates/requirements/luna/2014092610... -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18860) Publish to Wildfly AS does not update files

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18860?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18860: --------------------------------------------- Also just noticed you are on Windows. This *could* explain missing updates if the file we are trying to update is somehow locked (which would be a bug) by wildfly - but it does not explain your missing lib files and this should show up in error/server log with info what went wrong. If there is anyway you can give us a copy of the project or even just its dot-metadata (files/folders starting with ., i.e. .project, .classpath, .settings/* etc.) so we could try and reproduce. > Publish to Wildfly AS does not update files > ------------------------------------------- > > Key: JBIDE-18860 > URL: https://issues.jboss.org/browse/JBIDE-18860 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Final > Environment: Windows7 64bit, JDK8u25 > Reporter: Darryl Miles > Priority: Critical > Fix For: 4.2.1.Final, 4.2.2.Final, 4.3.0.Alpha1 > > > I think I am on JBIDE product 4.2.0.Final (but features show as 3.6.0.Final and Plugins as 3.0.0.Final-v20141016) > I have an EAR Maven project published to Wildfly 8.x. > there is a file in the project TOPLEVEL/src/main/application/META-INF/jboss-deployment-structure.xml > If this file is edited and saved, and I perform publish operation on server. The change is never made to the deployments directory. > If I manually delete the file from the deployments direcory, then perform clean operation and publish operation and full publish operation, the file is never re-crearted. > The only way is to REMOVE EAR module from server, clean server, stop server, ADD EAR module to server, publish server, start server. > Now the file is updated. > I also note that I have a number of workspace JPA/JAR projects that should be included in the EAR in the lib/* folder but they are never copied there. > I have found a copy in a folder like workspace\.metadata\.plugins\org.jboss.ide.eclipse.as.core\WildFly_8.1.0.Final\tempRemoteDeploy\ in here are the JARs I expected to find in the server runtime folder wildfly-8.1.0.Final\standalone\deployments\com.company.ear\lib\** > The timestamps on the files in this directory appear to be up-to-date at each publish event. > As a workaround I use "Make As Deployable" on the file workspace\com.company.ear\target\com.company.ear-1.2.3-SNAPSHOW.ear and I use a manual Maven build profile to create this file. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18860) Publish to Wildfly AS does not update files

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18860?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-18860: ------------------------------------- any chance you could reproduce with a sample project? > Publish to Wildfly AS does not update files > ------------------------------------------- > > Key: JBIDE-18860 > URL: https://issues.jboss.org/browse/JBIDE-18860 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Final > Environment: Windows7 64bit, JDK8u25 > Reporter: Darryl Miles > Priority: Critical > Fix For: 4.2.1.Final, 4.2.2.Final, 4.3.0.Alpha1 > > > I think I am on JBIDE product 4.2.0.Final (but features show as 3.6.0.Final and Plugins as 3.0.0.Final-v20141016) > I have an EAR Maven project published to Wildfly 8.x. > there is a file in the project TOPLEVEL/src/main/application/META-INF/jboss-deployment-structure.xml > If this file is edited and saved, and I perform publish operation on server. The change is never made to the deployments directory. > If I manually delete the file from the deployments direcory, then perform clean operation and publish operation and full publish operation, the file is never re-crearted. > The only way is to REMOVE EAR module from server, clean server, stop server, ADD EAR module to server, publish server, start server. > Now the file is updated. > I also note that I have a number of workspace JPA/JAR projects that should be included in the EAR in the lib/* folder but they are never copied there. > I have found a copy in a folder like workspace\.metadata\.plugins\org.jboss.ide.eclipse.as.core\WildFly_8.1.0.Final\tempRemoteDeploy\ in here are the JARs I expected to find in the server runtime folder wildfly-8.1.0.Final\standalone\deployments\com.company.ear\lib\** > The timestamps on the files in this directory appear to be up-to-date at each publish event. > As a workaround I use "Make As Deployable" on the file workspace\com.company.ear\target\com.company.ear-1.2.3-SNAPSHOW.ear and I use a manual Maven build profile to create this file. -- 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 December 2014