December 2014 - jbosstools-issues

[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 updated JBIDE-18860: ---------------------------------------- Fix Version/s: 4.2.1.Final 4.2.2.Final 4.3.0.Alpha1 > 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 > 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 Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18860?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18860: ---------------------------------------- Priority: Critical (was: Major) > 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 Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18860?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18860: --------------------------------------------- How is the server setup ? is it a remote server or local running one ? Anything in the error log ? Anything in the server log ? Do you have m2e-wtp installed ? if no, then maven projects won't work properly for sure - they will only be configured for the java part, not the "web" (wtp) part and that is known to cause the issue above ;/ > 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 > > 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 Darryl Miles (JIRA)

Darryl Miles created JBIDE-18860: ------------------------------------ Summary: 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 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-18711) Cordova plugin addition and removal fails when config.xml is in a linked folder

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18711?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-18711: -------------------------------------- I think this is probably a different issue with the config.xml editor. Can you actually open a separate one. > Cordova plugin addition and removal fails when config.xml is in a linked folder > ------------------------------------------------------------------------------- > > Key: JBIDE-18711 > URL: https://issues.jboss.org/browse/JBIDE-18711 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Final > Environment: Oracle JDK 1.8.0_05, Mac OS X Mavericks > Reporter: Vineet Reynolds > Assignee: Gorkem Ercan > Fix For: 4.2.1.CR1 > > > When config.xml is present in an Eclipse Linked folder (not in a symbolic link), then attempting to add or remove plugins (and possibly other operations on config.xml) fails with a spurious NullPointerException (without a stacktrace). > This pretty much means that the Hybrid Mobile application project with a linked folder for 'www' is in a read-only state for plugin addition/removal. If any plugin should be added or removed, the linked folder must be dropped, converted to an ordinary folder (or symbolic link), and then re-created after modifications. > To verify > 1. create a new project > 2. copy www folder to an alternate location > 3. remove www folder > 4.add www folder from alternate location as a linked folder (New Folder > Advanced> Link to alternate location) > 5. add cordova plugins to the project. [Check they are added] -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18858) Update Thym release on TP [4.2.1 CR1a]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18858?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-18858: -------------------------------------- new build id = 201412020246.. We have picked up the Cordova 4.1.2 release. > Update Thym release on TP [4.2.1 CR1a] > -------------------------------------- > > Key: JBIDE-18858 > URL: https://issues.jboss.org/browse/JBIDE-18858 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, upstream > Affects Versions: 4.2.1.CR1 > Reporter: Gorkem Ercan > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.2.1.CR1, 4.3.0.Alpha1 > > > *Reason:* Update Eclipse Thym to pickup fixes to JBDS issues > *License and owner:* Eclipse > *Original p2 repo:* http://download.eclipse.org/thym/snapshots (buildId=201412020246) > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/thym/0.1.0-SNAP... > *Sources:* https://github.com/eclipse/thym > *Affected projects:* jbosstools-aerogear > *Include in JBDS:* YES > *Type of dependency:* build > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18858) Update Thym release on TP [4.2.1 CR1a]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18858?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-18858: --------------------------------- Description: *Reason:* Update Eclipse Thym to pickup fixes to JBDS issues *License and owner:* Eclipse *Original p2 repo:* http://download.eclipse.org/thym/snapshots (buildId=201412020246) *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/thym/0.1.0-SNAP... *Sources:* https://github.com/eclipse/thym *Affected projects:* jbosstools-aerogear *Include in JBDS:* YES *Type of dependency:* build *List of bundles added/removed:* {code} TODO {code} was: *Reason:* Update Eclipse Thym to pickup fixes to JBDS issues *License and owner:* Eclipse *Original p2 repo:* http://download.eclipse.org/thym/snapshots (buildId=201412012201) *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/thym/0.1.0-SNAP... *Sources:* https://github.com/eclipse/thym *Affected projects:* jbosstools-aerogear *Include in JBDS:* YES *Type of dependency:* build *List of bundles added/removed:* {code} TODO {code} > Update Thym release on TP [4.2.1 CR1a] > -------------------------------------- > > Key: JBIDE-18858 > URL: https://issues.jboss.org/browse/JBIDE-18858 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, upstream > Affects Versions: 4.2.1.CR1 > Reporter: Gorkem Ercan > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.2.1.CR1, 4.3.0.Alpha1 > > > *Reason:* Update Eclipse Thym to pickup fixes to JBDS issues > *License and owner:* Eclipse > *Original p2 repo:* http://download.eclipse.org/thym/snapshots (buildId=201412020246) > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/thym/0.1.0-SNAP... > *Sources:* https://github.com/eclipse/thym > *Affected projects:* jbosstools-aerogear > *Include in JBDS:* YES > *Type of dependency:* build > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18767) Add support for Cordova 4.1.2

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18767?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-18767: -------------------------------------- skipping 4.0.0.. > Add support for Cordova 4.1.2 > ----------------------------- > > Key: JBIDE-18767 > URL: https://issues.jboss.org/browse/JBIDE-18767 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid, cordovasim > Reporter: Gorkem Ercan > Assignee: Ilya Buziuk > Labels: respin-a > Fix For: 4.2.1.CR1 > > > Test Cordova 4.0.0 release with CordovaSim & Thym. Update the downloadable engines json -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18767) Add support for Cordova 4.1.2

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18767?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-18767: --------------------------------- Summary: Add support for Cordova 4.1.2 (was: Add support for Cordova 4.0.0) > Add support for Cordova 4.1.2 > ----------------------------- > > Key: JBIDE-18767 > URL: https://issues.jboss.org/browse/JBIDE-18767 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid, cordovasim > Reporter: Gorkem Ercan > Assignee: Ilya Buziuk > Labels: respin-a > Fix For: 4.2.1.CR1 > > > Test Cordova 4.0.0 release with CordovaSim & Thym. Update the downloadable engines json -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18837) because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18837?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-18837: --------------------------------------- I didn't test it, but it looks like jbosstools.version property is going to get value below {code}${parsedVersion.majorVersion}.${parsedVersion.minorVersion}.${parsedVersion.incrementalVersion}.Alpha1{code} because properties are immutable and set before plug-ins execution is taking place. Am i wrong? > because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18837 > URL: https://issues.jboss.org/browse/JBIDE-18837 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, central, common/jst/core, project-examples > Affects Versions: 4.2.1.CR1 > Reporter: Nick Boldt > Fix For: 4.3.0.Alpha1 > > > When updating from 4.2.0 to 4.2.1, a user might decide to only update Central or Project Examples, and NOT update Foundation.core, which means his Eclipse will still think it's 4.2.0, not 4.2.1, and he might get the wrong version of central/examples. > Therefore we need manifest-level [4.2.1,) requirements on upstream foundation.core in examples and central, to force this lock-step updating. > And we need to use the maven enforcer plugin to fail the build if these versions get out of sync. -- 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