December 2014 - jbosstools-issues

[JBoss JIRA] (JBTIS-350) Missing BPEL source plugins

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-350?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-350: ----------------------------- Assignee: Robert (Bob) Brodt (was: Paul Leacu) > Missing BPEL source plugins > --------------------------- > > Key: JBTIS-350 > URL: https://issues.jboss.org/browse/JBTIS-350 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.0.Beta1 > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > > After installing all components included in Beta1 there are only the following souce plugins for BPEL > org.jboss.tools.bpel.runtimes.source_1.2.101.Final-v20140108-1353-B1045.jar > org.switchyard.tools.ui.bpel.source_2.0.0.v20141011-0508-H499-Alpha3.jar > but there are much more BPEL plugins such as > org.eclipse.bpel.ui, org.eclipse.bpel.ui.validator -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3162) Change "jboss-eap" to "JBoss Enterprise Application Platform"

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3162?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3162: -------------------------------------- Fix Version/s: (was: 8.0.1.GA) > Change "jboss-eap" to "JBoss Enterprise Application Platform" > ------------------------------------------------------------- > > Key: JBDS-3162 > URL: https://issues.jboss.org/browse/JBDS-3162 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: runtime-detection, server, ui/branding > Reporter: Burr Sutter > Assignee: Rob Stryker > Labels: f2f2014 > Fix For: 9.0.0.Alpha1 > > > When installing JBDS+EAP (same installer), the default name under the Servers tab is "jboss-eap". This is a request to have that default server name changed to "JBoss Enterprise Application Platform". > And the default runtime name to "JBoss EAP Runtime". > http://www.screencast.com/t/POpKcyHjhtlP > http://www.screencast.com/t/LZdFW0rJu0 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3162) Change "jboss-eap" to "JBoss Enterprise Application Platform"

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3162?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3162: ------------------------------------------- push off, not critical enough to risk breaking examples and docs that might rely on existing naming scheme. > Change "jboss-eap" to "JBoss Enterprise Application Platform" > ------------------------------------------------------------- > > Key: JBDS-3162 > URL: https://issues.jboss.org/browse/JBDS-3162 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: runtime-detection, server, ui/branding > Reporter: Burr Sutter > Assignee: Rob Stryker > Labels: f2f2014 > Fix For: 9.0.0.Alpha1 > > > When installing JBDS+EAP (same installer), the default name under the Servers tab is "jboss-eap". This is a request to have that default server name changed to "JBoss Enterprise Application Platform". > And the default runtime name to "JBoss EAP Runtime". > http://www.screencast.com/t/POpKcyHjhtlP > http://www.screencast.com/t/LZdFW0rJu0 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3162) Change "jboss-eap" to "JBoss Enterprise Application Platform"

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-3162?page=com.atlassian.jira.plugin.... ] Rob Stryker commented on JBDS-3162: ----------------------------------- Hi: This is targeted to 8.0.1 but there has been no agreement yet on a naming scheme. Should I push this off? Or will we come to an agreement here? > Change "jboss-eap" to "JBoss Enterprise Application Platform" > ------------------------------------------------------------- > > Key: JBDS-3162 > URL: https://issues.jboss.org/browse/JBDS-3162 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: runtime-detection, server, ui/branding > Reporter: Burr Sutter > Assignee: Rob Stryker > Labels: f2f2014 > Fix For: 8.0.1.GA, 9.0.0.Alpha1 > > > When installing JBDS+EAP (same installer), the default name under the Servers tab is "jboss-eap". This is a request to have that default server name changed to "JBoss Enterprise Application Platform". > And the default runtime name to "JBoss EAP Runtime". > http://www.screencast.com/t/POpKcyHjhtlP > http://www.screencast.com/t/LZdFW0rJu0 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 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: -------------------------------------- There are no changes on jbosstools-aerogear > 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)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13904) Minor UI issues in "Configure Repositories" wizard

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13904?page=com.atlassian.jira.plugi... ] Snjezana Peco reassigned JBIDE-13904: ------------------------------------- Assignee: Fred Bricon (was: Snjezana Peco) Could you, please, review the PR. > Minor UI issues in "Configure Repositories" wizard > -------------------------------------------------- > > Key: JBIDE-13904 > URL: https://issues.jboss.org/browse/JBIDE-13904 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.1.0.Alpha2 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Minor > Labels: uxp > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > > In the Window > Preferences > JBoss Tools > JBoss Maven Integration > Configure Maven Repositories... > * The repo viewer should have a horizontal scroller, since adding the (inactive) suffix can make a pretty long label and you have to resize the whole dialog to be able to read the labels > * Edit a repo, switching the profile activation status : it reorders the repositories/profiles in settings.xml. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13904) Minor UI issues in "Configure Repositories" wizard

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13904?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-13904: --------------------------------------- {quote} * The repo viewer should have a horizontal scroller, since adding the (inactive) suffix can make a pretty long label and you have to resize the whole dialog to be able to read the labels {quote} I have added a horizontal and vertical scrollbar. {quote} * Edit a repo, switching the profile activation status : it reorders the repositories/profiles in settings.xml. {quote} Earlier, the wizard was editing a repository by removing/creating a new one. Now, it edits elements in an existing repository. > Minor UI issues in "Configure Repositories" wizard > -------------------------------------------------- > > Key: JBIDE-13904 > URL: https://issues.jboss.org/browse/JBIDE-13904 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.1.0.Alpha2 > Reporter: Fred Bricon > Assignee: Snjezana Peco > Priority: Minor > Labels: uxp > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > > In the Window > Preferences > JBoss Tools > JBoss Maven Integration > Configure Maven Repositories... > * The repo viewer should have a horizontal scroller, since adding the (inactive) suffix can make a pretty long label and you have to resize the whole dialog to be able to read the labels > * Edit a repo, switching the profile activation status : it reorders the repositories/profiles in settings.xml. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18862) when removing a module from AS runtime marker files are not removed automatically

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18862?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18862: --------------------------------------------- I can confirm I end up with a .dodeploy file after having removed the module while the server was stopped. We should definitely remove the .dodeploy either when we remove or before we start publishing, maybe in both cases just to be safe. > when removing a module from AS runtime marker files are not removed automatically > --------------------------------------------------------------------------------- > > Key: JBIDE-18862 > URL: https://issues.jboss.org/browse/JBIDE-18862 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Environment: Windiws7 64bit, JDK 8u25 > Reporter: Darryl Miles > Priority: Minor > > module removal does not delete the various marker files relating to it: > *.undeployed > *.dodeploy > The same should be true when ADDING a module, it should clean out any marker files. > Setup an deploy-inhibiting marker file to ensure it won't try to deploy it before the *.ear is full written. > Write out the*.ear file. > Then adjust the marker files as necessary to reflect the intended state of the module (if it should be started then remove the inhibiting marker file in the previous step). -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

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

by Darryl Miles (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18860?page=com.atlassian.jira.plugi... ] Darryl Miles updated JBIDE-18860: --------------------------------- Attachment: org.example.jbide18860_v2.tar.gz Version 2 corrected Java1.7 usage in WAR/EJB projects. corrected XSD location in web.xml > 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 > > Attachments: org.example.jbide18860.tar.gz, org.example.jbide18860_v2.tar.gz > > > 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)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18700) EAP 6.x Configuration shows Servlet 3.1 as a valid choice

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18700?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-18700. --------------------------------- You didn't answer my question about the java facet, but as I said, I'm fine with how this works in JBDS 8.0.1.CR1 so I'm closing this JIRA ;) > EAP 6.x Configuration shows Servlet 3.1 as a valid choice > --------------------------------------------------------- > > Key: JBIDE-18700 > URL: https://issues.jboss.org/browse/JBIDE-18700 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Final > Reporter: Fred Bricon > Assignee: Rob Stryker > Fix For: 4.2.1.CR1, 4.3.0.Alpha1 > > > - Create a new EAP 6.3 server > - Create a new Dynamic Web Project > - Select the EAP runtime > => An error is shown : "Dynamic Web Module 3.1 requires Java 1.7 or newer." > !http://content.screencast.com/users/fbricon/folders/Jing/media/ee20c272-5761-40ab-8fe8-1004533501c7/00000025.png! > The EAP 6 Default Configuration should -have the Java 1.7 Facet set by default- not have the Web 3.1 option, which is part of JavaEE 7. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2014