December 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18355) Unexpected chars in freemarker editor

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18355?page=com.atlassian.jira.plugi... ] Jiri Peterka commented on JBIDE-18355: -------------------------------------- [~maxandersen] Yes, I mean a quick diff char or mark. If you compare status from 0:21 with the state of the beginning there there is no diff but quick diff mark is still present. It shouldn't be there IMO. When playing with that more quick diff has some other bugs for example it reports removed line when it is not (not part of the video). I've tried with with plain txt editor with the same file and it worked good there. > Unexpected chars in freemarker editor > ------------------------------------- > > Key: JBIDE-18355 > URL: https://issues.jboss.org/browse/JBIDE-18355 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.2.0.CR1 > Environment: JBDS 8.0.0.CR1b, L64 > Reporter: Jiri Peterka > Assignee: Peter Palaga > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > Attachments: freemarker-strange-char.ogv, html-template.ftl > > > Strange characters occurs when editing ftl file (check the screencast) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18712) Add wildfly archetypes to JBoss Central

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18712?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-18712. ------------------------------ Verified in JBDS 8.0.1.CR1. > Add wildfly archetypes to JBoss Central > --------------------------------------- > > Key: JBIDE-18712 > URL: https://issues.jboss.org/browse/JBIDE-18712 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.2.1.CR1 > > > JBoss Central doesn't propose the Wildfly archetypes when a Wildfly runtime is selected, even though they have been released in Maven Central : http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.wildfly.archetype%22 > They should be added to stacks.yaml, with environment: web-ee7 for the pure webapp and environment: full-ee7 for the EAR -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18864) Upgrade Forge Runtime to 2.12.3.Final

by George Gastaldi (JIRA)

George Gastaldi created JBIDE-18864: --------------------------------------- Summary: Upgrade Forge Runtime to 2.12.3.Final Key: JBIDE-18864 URL: https://issues.jboss.org/browse/JBIDE-18864 Project: Tools (JBoss Tools) Issue Type: Component Upgrade Components: forge Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 4.2.1.CR1 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18777) Ensure features and plugins have upversioned since 4.2.0.Final release [Central]

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18777?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-18777. ------------------------------ Verified in JBDS 8.0.1.CR1 > Ensure features and plugins have upversioned since 4.2.0.Final release [Central] > -------------------------------------------------------------------------------- > > Key: JBIDE-18777 > URL: https://issues.jboss.org/browse/JBIDE-18777 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Affects Versions: 4.2.1.CR1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 4.2.1.CR1 > > > You have commits in your 4.2.x branch which happened AFTER 4.2.0.Final. Yet your root pom is still at version 4.2.0, and your affected plugins' versions are not incremented. > https://github.com/jbosstools/jbosstools-central/commits/jbosstools-4.2.x > Please bump your stuff to a .1 version to reflect the fact you're doing maintenance in the 4.2.x branch. -- 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 Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18858?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18858: ------------------------------------ +1 for PRs. [~mickael_istria] should we also rename this target platform from CR2-SNAPSHOT to Final-SNAPSHOT so it's ready for the release of 4.2.1/8.0.1 in 2 weeks? > 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] (JBDS-3240) Provide latest EAP 6.3 / WFK 2.6 archetypes in latest JBDS 8 Central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3240?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3240: ----------------------------------- archetype versions depend on selected runtimes. By default, we fallback on the lowest common denominator (EE6 app that deploys on AS7) > Provide latest EAP 6.3 / WFK 2.6 archetypes in latest JBDS 8 Central > -------------------------------------------------------------------- > > Key: JBDS-3240 > URL: https://issues.jboss.org/browse/JBDS-3240 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.0.0.GA > Reporter: Marek Novotny > Assignee: Fred Bricon > Fix For: 8.0.1.GA > > > JBDS 8 aka JBoss Central provide by default old EAP/WFK archetype and not the latest 6.3.0.GA/2.6.0.Final by default. > For instance I click on HTML5 project in Start from Scratch in JBoss Central: > it launches wizard dialog where the archetype is org.jboss.tools.example.html5:jboss-as-kitchensink-html5-mobile:1.0.4.Final-redhat-wfk-2 version -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18863) Duplicate deployment scanner on Windows if set to custom

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18863?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-18863: ---------------------------------- Environment: JBDS 8.0.1.CR1 B333 Windows 7 > Duplicate deployment scanner on Windows if set to custom > -------------------------------------------------------- > > Key: JBIDE-18863 > URL: https://issues.jboss.org/browse/JBIDE-18863 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.1.CR1 > Environment: JBDS 8.0.1.CR1 B333 > Windows 7 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: respin-a > Fix For: 4.2.1.CR1 > > > Today I tried to verify a bug on Windows (JBIDE-18697) and in doing so, I noticed this bug: > I tried deploying a dynamic web project to a custom folder with eap 6.3 on Windows 7. And I ended up with two custom deployment scanners in standalone.xml: > {code} > <subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1"> > <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000"/> > <deployment-scanner name="jbosstoolsscanner1" path="E:/deployments/deploy" scan-interval="5000" deployment-timeout="600"/> > <deployment-scanner name="jbosstoolsscanner2" path="E:\deployments\deploy" scan-interval="5000" deployment-timeout="600"/> > </subsystem> > {code} > Notice that those two added scanners are the same except for file delimiters - "/" vs. "\" -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18863) Duplicate deployment scanner on Windows if set to custom

by Martin Malina (JIRA)

Martin Malina created JBIDE-18863: ------------------------------------- Summary: Duplicate deployment scanner on Windows if set to custom Key: JBIDE-18863 URL: https://issues.jboss.org/browse/JBIDE-18863 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.2.1.CR1 Reporter: Martin Malina Assignee: Rob Stryker Fix For: 4.2.1.CR1 Today I tried to verify a bug on Windows (JBIDE-18697) and in doing so, I noticed this bug: I tried deploying a dynamic web project to a custom folder with eap 6.3 on Windows 7. And I ended up with two custom deployment scanners in standalone.xml: {code} <subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1"> <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000"/> <deployment-scanner name="jbosstoolsscanner1" path="E:/deployments/deploy" scan-interval="5000" deployment-timeout="600"/> <deployment-scanner name="jbosstoolsscanner2" path="E:\deployments\deploy" scan-interval="5000" deployment-timeout="600"/> </subsystem> {code} Notice that those two added scanners are the same except for file delimiters - "/" vs. "\" -- 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 Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13904?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-13904: -------------------------------- Fix Version/s: (was: 4.2.1.Final) > 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.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] (JBTIS-350) Missing BPEL source plugins

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-350?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-350: ---------------------------------- Bob - Can you use what we did for BPMN2 source bundling as a guide for bpel source bundling?? This is needed for the Luna IS. Thanks, --paul > 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2014