February 2015 - jbosstools-issues

[JBoss JIRA] (JBDS-3273) JBoss Central: Automatic upstream quickstart integration

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/JBDS-3273?page=com.atlassian.jira.plugin.... ] Rafael Benevides commented on JBDS-3273: ---------------------------------------- In this case we can involve [~paul.robinson] and [~lightguard]. They may assist you on that. > JBoss Central: Automatic upstream quickstart integration > --------------------------------------------------------- > > Key: JBDS-3273 > URL: https://issues.jboss.org/browse/JBDS-3273 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Fix For: 9.0.0.Alpha2 > > > Support a more dynamic JBoss Central with direct access to the upstream quickstarts - no longer requiring a fork and tweak to the current quickstarts. We will need some form of 'search UI' as the total list of quickstarts has grown dramatically. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

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

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18860?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-18860. --------------------------------- Rejected, thus closing. Feel free to reopen if still relevant. > 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.3.Final, 4.3.0.Alpha1 > > Attachments: org.example.jbide18860.tar.gz, org.example.jbide18860_v2.tar.gz, org.example.jbide18860_v3.zip > > > 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.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19322) NPE when opening central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19322?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-19322: ------------------------------------- mmm I guess I changed the internal file format when I reworked all the xml parsing, which makes old workspaces incompatible. Can you try on a new workspace? > NPE when opening central > ------------------------- > > Key: JBIDE-19322 > URL: https://issues.jboss.org/browse/JBIDE-19322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, project-examples > Affects Versions: 4.3.0.Alpha1 > Reporter: Rastislav Wagner > Assignee: Fred Bricon > Fix For: 4.3.0.Alpha2 > > Attachments: Preferences _002.png > > > I opened central via JBoss Central toolbar item and this NPE occured - An internal error occurred during: "Refreshing JBoss Tutorials...". Not always, but every second time. > {code} > java.lang.NullPointerException > at java.util.AbstractCollection.addAll(AbstractCollection.java:343) > at org.jboss.tools.project.examples.model.ProjectExampleUtil.getUserSites(ProjectExampleUtil.java:210) > at org.jboss.tools.project.examples.model.ProjectExampleUtil.getSites(ProjectExampleUtil.java:221) > at org.jboss.tools.project.examples.model.ProjectExampleUtil.getProjects(ProjectExampleUtil.java:257) > at org.jboss.tools.central.jobs.RefreshTutorialsJob.run(RefreshTutorialsJob.java:52) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3356) Upgrade to newer JBoss Forge

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3356?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3356: ------------------------------------------- but having latest forge in JBDS 8.1 is important since we don't plan on doing more JBDS 8 releaess after that if can be avoided ;) [~koen.aers] can you say what version we can/will have in JBDS 8.1? > Upgrade to newer JBoss Forge > ---------------------------- > > Key: JBDS-3356 > URL: https://issues.jboss.org/browse/JBDS-3356 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: forge > Reporter: Claus Ibsen > Priority: Minor > Fix For: 8.1.0.Beta1, 9.0.0.Alpha2 > > > Using latest JBDS download, and I did a Software/update, and there was a bunch of upgrades. > It upgraded forge to 2.13.0.Final. > As we work on some middleware tooling that would rely on a newer release of forge with bugfixes, then we would request to upgrade to 2.14.1 or newer when its released from the jboss forge team. > If there is some deadline, then upgrading to 2.14.0 is better than nothing. But we could maybe ask the forge team to do a quick 2.14.1 release. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3356) Upgrade to newer JBoss Forge

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3356?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3356: ------------------------------------------- so this relates to OpenShift3 - probably mainly make sense for JBDS 9 then. > Upgrade to newer JBoss Forge > ---------------------------- > > Key: JBDS-3356 > URL: https://issues.jboss.org/browse/JBDS-3356 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: forge > Reporter: Claus Ibsen > Priority: Minor > Fix For: 8.1.0.Beta1, 9.0.0.Alpha2 > > > Using latest JBDS download, and I did a Software/update, and there was a bunch of upgrades. > It upgraded forge to 2.13.0.Final. > As we work on some middleware tooling that would rely on a newer release of forge with bugfixes, then we would request to upgrade to 2.14.1 or newer when its released from the jboss forge team. > If there is some deadline, then upgrading to 2.14.0 is better than nothing. But we could maybe ask the forge team to do a quick 2.14.1 release. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19092) jbosstools-maven-plugins uses non-opensource json library

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19092?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-19092. --------------------------------- I checked that https://github.com/jbosstools/jbosstools-maven-plugins/blob/master/tycho-... now uses jboss dmr. > jbosstools-maven-plugins uses non-opensource json library > --------------------------------------------------------- > > Key: JBIDE-19092 > URL: https://issues.jboss.org/browse/JBIDE-19092 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.0.Alpha1 > > > if JBIDE-19090 is correct the maven plugins uses json library that is under a non-opensource license and thus we need to upgrade to a library version that has proper license or move to different library. > i.e. dmr has basic read/write of json support and used in many places of jbosstools - would that work ? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3356) Upgrade to newer JBoss Forge

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3356?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3356: -------------------------------------- Fix Version/s: 8.1.0.Beta1 9.0.0.Alpha2 > Upgrade to newer JBoss Forge > ---------------------------- > > Key: JBDS-3356 > URL: https://issues.jboss.org/browse/JBDS-3356 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: forge > Reporter: Claus Ibsen > Priority: Minor > Fix For: 8.1.0.Beta1, 9.0.0.Alpha2 > > > Using latest JBDS download, and I did a Software/update, and there was a bunch of upgrades. > It upgraded forge to 2.13.0.Final. > As we work on some middleware tooling that would rely on a newer release of forge with bugfixes, then we would request to upgrade to 2.14.1 or newer when its released from the jboss forge team. > If there is some deadline, then upgrading to 2.14.0 is better than nothing. But we could maybe ask the forge team to do a quick 2.14.1 release. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3357) Investigate implications of Forge 1 removal

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBDS-3357?page=com.atlassian.jira.plugin.... ] Koen Aers updated JBDS-3357: ---------------------------- Affects Version/s: 9.0.0.Alpha1 (was: 8.0.2.GA) > Investigate implications of Forge 1 removal > ------------------------------------------- > > Key: JBDS-3357 > URL: https://issues.jboss.org/browse/JBDS-3357 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: forge > Affects Versions: 9.0.0.Alpha1 > Reporter: Koen Aers > Assignee: Koen Aers > Priority: Critical > Fix For: 9.0.0.Alpha2 > > > F1 was removed in 9.0.0.Alpha1 (see JBIDE-19101). Investigation is needed to see if any additional action is needed for the quickstarts and ticket monster to continue to work properly. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3357) Investigate implications of Forge 1 removal

by Koen Aers (JIRA)

Koen Aers created JBDS-3357: ------------------------------- Summary: Investigate implications of Forge 1 removal Key: JBDS-3357 URL: https://issues.jboss.org/browse/JBDS-3357 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Components: forge Affects Versions: 8.0.2.GA Reporter: Koen Aers Assignee: Koen Aers Priority: Critical Fix For: 9.0.0.Alpha2 F1 was removed in 9.0.0.Alpha1 (see JBIDE-19101). Investigation is needed to see if any additional action is needed for the quickstarts and ticket monster to continue to work properly. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3356) Upgrade to newer JBoss Forge

by Claus Ibsen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3356?page=com.atlassian.jira.plugin.... ] Claus Ibsen commented on JBDS-3356: ----------------------------------- In the forge shell I can see the version listed as: 2.13.0.Final. > Upgrade to newer JBoss Forge > ---------------------------- > > Key: JBDS-3356 > URL: https://issues.jboss.org/browse/JBDS-3356 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: forge > Reporter: Claus Ibsen > Priority: Minor > > Using latest JBDS download, and I did a Software/update, and there was a bunch of upgrades. > It upgraded forge to 2.13.0.Final. > As we work on some middleware tooling that would rely on a newer release of forge with bugfixes, then we would request to upgrade to 2.14.1 or newer when its released from the jboss forge team. > If there is some deadline, then upgrading to 2.14.0 is better than nothing. But we could maybe ask the forge team to do a quick 2.14.1 release. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 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 February 2015