June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19966) Include should have hyperlink to file that is being included

by Antoni Rokitnicki (JIRA)

Antoni Rokitnicki created JBIDE-19966: ----------------------------------------- Summary: Include should have hyperlink to file that is being included Key: JBIDE-19966 URL: https://issues.jboss.org/browse/JBIDE-19966 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: freemarker Reporter: Antoni Rokitnicki Priority: Optional on ctrl+click on <#include "item.ftl"> user should be redirected to item.ftl -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19962) org.jboss.tools.cdi.extension.core.test.ExtensionCoreAllTests failure on Windows

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19962?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19962: ----------------------------------- Fix Version/s: 4.3.0.Beta2 > org.jboss.tools.cdi.extension.core.test.ExtensionCoreAllTests failure on Windows > -------------------------------------------------------------------------------- > > Key: JBIDE-19962 > URL: https://issues.jboss.org/browse/JBIDE-19962 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi, cdi-extensions > Environment: Windows 8 > Reporter: Daniel Azarov > Fix For: 4.3.0.Beta2 > > > {code} > ------------------------------------------------------------------------------- > Test set: org.jboss.tools.cdi.extension.core.test.ExtensionCoreAllTests > ------------------------------------------------------------------------------- > Tests run: 5, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.896 sec <<< FAILURE! - in org.jboss.tools.cdi.extension.core.test.ExtensionCoreAllTests > testDummy(org.jboss.tools.cdi.extension.core.test.jms.JMSContextTest) Time elapsed: 0.007 sec > testBatchInjection(org.jboss.tools.cdi.extension.core.test.batch.BatchValidationTest) Time elapsed: 0.001 sec > Batch Core Project Tests(org.jboss.tools.cdi.extension.core.test.batch.BatchCoreTestSetup) Time elapsed: 0.058 sec <<< ERROR! > org.eclipse.core.internal.resources.ResourceException: Problems encountered while deleting resources. > at org.eclipse.core.internal.resources.Resource.delete(Resource.java:794) > at org.eclipse.core.internal.resources.Project.delete(Project.java:323) > at org.jboss.tools.cdi.extension.core.test.batch.BatchCoreTestSetup.tearDown(BatchCoreTestSetup.java:48) > testExceptions(org.jboss.tools.common.base.test.validation.ValidationExceptionTest) Time elapsed: 0.001 sec > testLogging(org.jboss.tools.common.base.test.validation.ValidationExceptionTest) Time elapsed: 0.008 sec > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19962) org.jboss.tools.cdi.extension.core.test.ExtensionCoreAllTests failure on Windows

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19962?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-19962: -------------------------------------- Assignee: Daniel Azarov > org.jboss.tools.cdi.extension.core.test.ExtensionCoreAllTests failure on Windows > -------------------------------------------------------------------------------- > > Key: JBIDE-19962 > URL: https://issues.jboss.org/browse/JBIDE-19962 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi, cdi-extensions > Environment: Windows 8 > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Fix For: 4.3.0.Beta2 > > > {code} > ------------------------------------------------------------------------------- > Test set: org.jboss.tools.cdi.extension.core.test.ExtensionCoreAllTests > ------------------------------------------------------------------------------- > Tests run: 5, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.896 sec <<< FAILURE! - in org.jboss.tools.cdi.extension.core.test.ExtensionCoreAllTests > testDummy(org.jboss.tools.cdi.extension.core.test.jms.JMSContextTest) Time elapsed: 0.007 sec > testBatchInjection(org.jboss.tools.cdi.extension.core.test.batch.BatchValidationTest) Time elapsed: 0.001 sec > Batch Core Project Tests(org.jboss.tools.cdi.extension.core.test.batch.BatchCoreTestSetup) Time elapsed: 0.058 sec <<< ERROR! > org.eclipse.core.internal.resources.ResourceException: Problems encountered while deleting resources. > at org.eclipse.core.internal.resources.Resource.delete(Resource.java:794) > at org.eclipse.core.internal.resources.Project.delete(Project.java:323) > at org.jboss.tools.cdi.extension.core.test.batch.BatchCoreTestSetup.tearDown(BatchCoreTestSetup.java:48) > testExceptions(org.jboss.tools.common.base.test.validation.ValidationExceptionTest) Time elapsed: 0.001 sec > testLogging(org.jboss.tools.common.base.test.validation.ValidationExceptionTest) Time elapsed: 0.008 sec > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19919) For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Base]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19919?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-19919: ---------------------------------------- The branch was created correctly but later I accidentally pushed that beta 2 commit to the branch when was merging JBIDE-19919 from master. My fault :( I will be able to revert that commit in the branch only tomorrow. I'm traveling right now and don't have my laptop around. :( > For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Base] > -------------------------------------------------- > > Key: JBIDE-19919 > URL: https://issues.jboss.org/browse/JBIDE-19919 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core, usage > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta1 > > > For JBIDE 4.3.0.Beta1 [Base]: Please perform the following tasks: > 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta1 > [Unresolved JIRAs with fixVersion = 4.3.0.Beta1, 9.0.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100. > *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.3.0.Beta1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Beta1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Beta1; > {code} > mvn clean verify -Dtpc.version=4.50.0.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT) > or > mvn clean verify -Dtpc.version=4.50.0.Beta1 # (if the TP is already released) > {code} > 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Beta1x > git push origin jbosstools-4.3.0.Beta1x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Beta2-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Beta2-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch, and > * *{color:orange}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:orange}master{color}* bran > 7. Close (do not resolve) this JIRA when done. > 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Base task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19965) Add profiles (or enhance "rse" profile) to allow for org.eclipse.remote as remote implementation

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-19965: ----------------------------------- Summary: Add profiles (or enhance "rse" profile) to allow for org.eclipse.remote as remote implementation Key: JBIDE-19965 URL: https://issues.jboss.org/browse/JBIDE-19965 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: server Affects Versions: 4.3.0.Alpha2 Reporter: Rob Stryker As org.eclipse.remote matures, it's worthwhile to investigate whether we should allow (experimentally) users to make use of org.eclipse.remote as their implementation of choice over RSE. I suspect this should be done as a new set of profiles, but this would complicate the new streamlined profile-selection page in teh new server wizard, which has been outfitted with radio buttons to remove confusion and make all choices obvious. The presence of / support for two competing remote frameworks would definitely confuse the user in some ways, and so this should be approached delicately and with feedback from multiple parties. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19964) Wildfly 10 / EAP 7 server adapter

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-19964: ----------------------------------- Summary: Wildfly 10 / EAP 7 server adapter Key: JBIDE-19964 URL: https://issues.jboss.org/browse/JBIDE-19964 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: server Affects Versions: 4.3.0.CR1 Reporter: Rob Stryker It'd be a good idea to begin making an EAP7 / WF10 server adapter pair, or at least preparing. Looking at the versions of jars that we care about for management commands, Jars in EAP7 current DR3 are: wildfly-controller-client-2.0.0.Alpha3.jar wildfly-protocol-2.0.0.Alpha3.jar jboss-dmr-1.3.0.Final.jar jboss-logging-3.2.1.Final.jar jboss-marshalling-1.4.10.Final.jar jboss-marshalling-river-1.4.10.Final.jar jboss-marshalling-river-1.4.10.Final.jar jboss-remoting-4.0.9.Final.jar jboss-sasl-1.0.5.Final.jar jboss-threads-2.2.0.Final.jar xnio-api-3.3.1.Final.jar xnio-nio-3.3.1.Final.jar These jars are identical to those in WF9-CR1 *except* for wildfly-protocol and wildfly-controller-client, which are at 1.0.0.CR1 in wf9. So wildfly-core (repository) has undergone a 'major' version bump, and is likely undergoing significant API cleanup. It would be smart to expect that we probably will require a new management plugin on our side to compensate. Also, it's worth noting that in WF8 / WF 8.1, these jars are actually versioned 8.0 / 8.1 respectively, and so the version has actually decreased as we've moved forward. I've brought this up on wildfly-dev, though it may be a bit late since WF is already ar RC3. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19641) Big war deployment via management API gets stuck

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19641?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19641: ------------------------------------- https://github.com/jbosstools/jbosstools-server/blob/master/as/plugins/or... for reference > Big war deployment via management API gets stuck > ------------------------------------------------ > > Key: JBIDE-19641 > URL: https://issues.jboss.org/browse/JBIDE-19641 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Beta2 > > Attachments: stuck-deploy-eap-jstack-osx.log, stuck-deploy-eap-jstack-rhel.log, stuck-deploy-jstack-osx.log, stuck-deploy-jstack-rhel.log > > > When you try to deploy some really big war (~500 MB) to EAP 6.3 via management api, it will not go through. > This is a follow-up of JBIDE-19350 which previously reported this, but Rob eventually used that JIRA to fix a side issue - the stuck operation could not be canceled. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19641) Big war deployment via management API gets stuck

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19641?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19641: ------------------------------------- [~brian.stansberry] Your code differs slightly from whats in ours. You have: {code} DeploymentPlan plan = manager.newDeploymentPlan().add("kitchensink-huge.ear", f).build(); {code} While we use the following signatures: {code} DeploymentPlanBuilder builder = manager.newDeploymentPlan().add(name, file).andDeploy().build(); Or... DeploymentPlanBuilder builder = manager.newDeploymentPlan().deploy(name).build(); {code} > Big war deployment via management API gets stuck > ------------------------------------------------ > > Key: JBIDE-19641 > URL: https://issues.jboss.org/browse/JBIDE-19641 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Beta2 > > Attachments: stuck-deploy-eap-jstack-osx.log, stuck-deploy-eap-jstack-rhel.log, stuck-deploy-jstack-osx.log, stuck-deploy-jstack-rhel.log > > > When you try to deploy some really big war (~500 MB) to EAP 6.3 via management api, it will not go through. > This is a follow-up of JBIDE-19350 which previously reported this, but Rob eventually used that JIRA to fix a side issue - the stuck operation could not be canceled. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19631) Switch Tern.java dependency version range to the only version after code freeze

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19631?page=com.atlassian.jira.plugi... ] Denis Golovin reassigned JBIDE-19631: ------------------------------------- Assignee: Denis Golovin (was: Victor Rubezhny) > Switch Tern.java dependency version range to the only version after code freeze > ------------------------------------------------------------------------------- > > Key: JBIDE-19631 > URL: https://issues.jboss.org/browse/JBIDE-19631 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha1 > Reporter: Alexey Kazakov > Assignee: Denis Golovin > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta1 > > > In master tern.java dependencies have open range starting from 0.6.0 after https://github.com/jbosstools/jbosstools-jst/pull/429 was applied. > For every development/stable release the open range should be replaced to specific version. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19963) Switch Tern.java dependency version range to the only version after code freeze

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19963?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19963: ---------------------------------- Fix Version/s: 4.3.0.Beta2 (was: 4.3.0.Beta1) > Switch Tern.java dependency version range to the only version after code freeze > ------------------------------------------------------------------------------- > > Key: JBIDE-19963 > URL: https://issues.jboss.org/browse/JBIDE-19963 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha1 > Reporter: Alexey Kazakov > Assignee: Victor Rubezhny > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta2 > > > In master tern.java dependencies have open range starting from 0.6.0 after https://github.com/jbosstools/jbosstools-jst/pull/429 was applied. > For every development/stable release the open range should be replaced to specific version. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 June 2015