July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3076) Move JMX/JVM Monitoring features from Fuse Tools to server core

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-3076?page=com.atlassian.jira.plugin.... ] Rob Stryker closed JBDS-3076. ----------------------------- Resolution: Done This has been completed > Move JMX/JVM Monitoring features from Fuse Tools to server core > --------------------------------------------------------------- > > Key: JBDS-3076 > URL: https://issues.jboss.org/browse/JBDS-3076 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Security Level: Public(Everyone can see) > Components: requirements, server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 8.0.0.Beta3 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17536) JBoss Tools Core Nightly update site fails to install if a new build is published during install

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17536?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-17536. --------------------------------- Too bad. Maybe I'll make noise when this happens to me again :) > JBoss Tools Core Nightly update site fails to install if a new build is published during install > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-17536 > URL: https://issues.jboss.org/browse/JBIDE-17536 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Beta2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.2.0.Beta3 > > > When you install JBT nightly from http://download.jboss.org/jbosstools/updates/nightly/core/master/ into Eclipse and during the build, a new nightly build replaces the old one, you can get a failure like this: > {code}http://download.jboss.org/jbosstools/updates/nightly/core/master/features/org.jboss.tools.wtp.runtimes.tomcat.feature_1.1.0.Beta3-v20140603-0027-B526.jar cannot be found{code} > This is because during your install, the old jars were replaced with the new jars, i.e. different filenames. > I'm not sure if it's something we really need to fix, it's open for discussion. But it happened to me yesterday and it wasn't the first time, so I'm throwing it on the table. > Nick offered this alternative: > install from a specific build folder instead of the "latest nightly" > http://download.jboss.org/jbosstools/builds/nightly/core/master/2014-06-0... > http://download.jboss.org/jbosstools/builds/nightly/core/master/2014-06-0... > But obviously that's just a workaround, not a real solution. > One way this could be achieved is this: plugins/ and features/ would contain jars from both the latest and previous builds. This way if you start installing (latest=build N) and in the middle of your installation there is a new build (N+1), there would still be jars for both N and N+1 builds. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17700) Cannot deploy jsf war with eclipse luna and jboss 7.1.x

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17700?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17700: ------------------------------------- So what's the next step here? I can pretty much be certain this isn't any error in ASTools because we don't have access to plexus or set its classloaders anywhere, and the bug is directly caused by the wrong classloader... so... any ideas? > Cannot deploy jsf war with eclipse luna and jboss 7.1.x > ------------------------------------------------------- > > Key: JBIDE-17700 > URL: https://issues.jboss.org/browse/JBIDE-17700 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge, maven, server > Environment: Win 7, Eclilpse Luna, JBoss Tools (via market place) > Reporter: Oliver Pfau > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.0.Beta3 > > Attachments: pom.xml > > > When I publish my war to jboss 7.1 the following error occurs: > An internal error occurred during: "Publishing to JBoss AS 7.1...". > Could not initialize class de.schlichtherle.io.ArchiveControllers -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17393) Show on main Central page the "Early Access" status

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17393?page=com.atlassian.jira.plugi... ] Michelle Murray commented on JBIDE-17393: ----------------------------------------- Is there a reason to have both? Can it not just be 'Early Access Enabled' to match the checkbox on the Updated tab? > Show on main Central page the "Early Access" status > --------------------------------------------------- > > Key: JBIDE-17393 > URL: https://issues.jboss.org/browse/JBIDE-17393 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Affects Versions: 4.2.0.Beta2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Labels: early-access > Fix For: 4.2.0.Beta3 > > > The main Central page (not Software one) should show the "Early Access" status. It can be one of > * No Early Access component installed, no Early Access enabled (shows nothing) > * No Early Access component installed, Early Access enabled (shows Early Access enabled) > * at least 1 Early Access component installed, Early Access Enabled > * at least 1 Early Access component installed, Early Access not Enabled -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12370) Add a video that shows how to handle missing requirements on New Project Example screen

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12370?page=com.atlassian.jira.plugi... ] Michelle Murray commented on JBIDE-12370: ----------------------------------------- Documented for JBDS 7.1: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > Add a video that shows how to handle missing requirements on New Project Example screen > --------------------------------------------------------------------------------------- > > Key: JBIDE-12370 > URL: https://issues.jboss.org/browse/JBIDE-12370 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: project-examples > Affects Versions: 3.3.0.Final > Reporter: Pete Muir > Assignee: Michelle Murray > Priority: Critical > Labels: doc'ed > Fix For: 4.2.0.CR1 > > > If the user clicks on _JBoss Central | Java EE Web Project_ they are presented with this screen http://www.jboss.org/jdf/stage/quickstarts/jboss-as-quickstart/guide//gfx... - it would be nice to have a short video showing how people can solve missing requirements, e.g. by clicking the Install button. This can then be linked to from tutorials that use these wizards. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17025) Patching EAP 6.2 breaks classpath jar files

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17025?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17025: ------------------------------------ If it helps to ease the migration effort, you can use OUR target platforms for Kepler [1] and Luna [2], and compare their contents using the p2diff [3] and p2browser [4] tools. [1] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... [2] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... [3] https://github.com/irbull/p2diff [4] https://github.com/ifedorenko/p2-browser/ I also recommend a visual diff tool like Beyond Compare [5] if you want to see what files appear in two target platform folders on disk. [5] http://www.scootersoftware.com/moreinfo.php And, if you want some tooling to create & validate a target platform you're building for your RCP app, have a look at this stuff [6], [7]: [6] https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ... [7] https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/verify... > Patching EAP 6.2 breaks classpath jar files > ------------------------------------------- > > Key: JBIDE-17025 > URL: https://issues.jboss.org/browse/JBIDE-17025 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.2.Final > Environment: Windows 7, Kepler SR2 > Reporter: Jesper Skov > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.2.0.Beta2 > > > Using the JBoss CLI command 'patch apply .../eap-6.2.2.zip' breaks some of the module jars (the files become invalid ZIP-archives). > This is apparently done as a way to mark the modules off-limits for the container, while still allowing roll-back if necessary. > See https://access.redhat.com/site/discussions/726623 > Unfortunately, Eclipse includes these jars in the JBossTools-defined classpath. When scanned, these will be found corrupt, and the project classpath marked as broken. > On my installation, the first few files to trigger this problem are: > * modules/system/layers/base/javax/el/api/main/jboss-el-api_2.2_spec-1.0.2.Final-redhat-1.jar > * modules/system/layers/base/javax/el/api/main/jboss-el-api_2.2_spec-1.0.2.Final-redhat-1.jar > I guess it might be possible to adjust the server definition's Default Classpath Entries in Eclipse preferences. But I decided to just copy the original EAP 6.2 files on top of the runtime and get on with work... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17803) Remove GateIn quickstart extension point

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17803?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-17803: ------------------------------- Assignee: Burr Sutter > Remove GateIn quickstart extension point > ---------------------------------------- > > Key: JBIDE-17803 > URL: https://issues.jboss.org/browse/JBIDE-17803 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: project-examples > Reporter: Peter Palaga > Assignee: Burr Sutter > Fix For: 4.2.0.Beta3 > > > This is motivated by the fact that GateIn quickstarts were abandoned. Only quickstarts for JBoss Portal are maintained as of JBoss Portal 6.2. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17803) Remove GateIn quickstart extension point

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17803?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-17803. ------------------------------ Resolution: Rejected Set assignee, component, and fix version so jiralint will stfu. > Remove GateIn quickstart extension point > ---------------------------------------- > > Key: JBIDE-17803 > URL: https://issues.jboss.org/browse/JBIDE-17803 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: project-examples > Reporter: Peter Palaga > Assignee: Burr Sutter > Fix For: 4.2.0.Beta3 > > > This is motivated by the fact that GateIn quickstarts were abandoned. Only quickstarts for JBoss Portal are maintained as of JBoss Portal 6.2. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17803) Remove GateIn quickstart extension point

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17803?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-17803: ------------------------------- Fix Version/s: 4.2.0.Beta3 > Remove GateIn quickstart extension point > ---------------------------------------- > > Key: JBIDE-17803 > URL: https://issues.jboss.org/browse/JBIDE-17803 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: project-examples > Reporter: Peter Palaga > Fix For: 4.2.0.Beta3 > > > This is motivated by the fact that GateIn quickstarts were abandoned. Only quickstarts for JBoss Portal are maintained as of JBoss Portal 6.2. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17803) Remove GateIn quickstart extension point

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17803?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-17803: ------------------------------- Component/s: project-examples > Remove GateIn quickstart extension point > ---------------------------------------- > > Key: JBIDE-17803 > URL: https://issues.jboss.org/browse/JBIDE-17803 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: project-examples > Reporter: Peter Palaga > > This is motivated by the fact that GateIn quickstarts were abandoned. Only quickstarts for JBoss Portal are maintained as of JBoss Portal 6.2. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 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 July 2014