November 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-20795) canonical form is required(project=arquillian-test)

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20795?page=com.atlassian.jira.plugi... ] Lucia Jelinkova closed JBIDE-20795. ----------------------------------- Ok, since no work on JBT side is needed, closing the issue. > canonical form is required(project=arquillian-test) > --------------------------------------------------- > > Key: JBIDE-20795 > URL: https://issues.jboss.org/browse/JBIDE-20795 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: arquillian > Reporter: Aslak Knutsen > Assignee: Snjezana Peco > Fix For: 4.3.1.Beta1 > > > This code: > {code} > @RunWith(Arquillian.class) > public class SimpleTestCase { > @Deployment > public static WebArchive test() { > return ShrinkWrap.create(WebArchive.class) > .addAsLibraries(Maven.resolver().resolve("").withoutTransitivity().asFile()); > } > > @Test > public void shouldX() {} > } > {code} > produce the following warning: > {code} > null > org.jboss.tools.arquillian.core > Warning > Wed Sep 23 23:16:17 CEST 2015 > canonical form is required(project=arquillian-test) > {code} > On top of my head I have no idea what that means. The warning contains no stack trace so hard to tell where it comes from. > With a little digging it's due to the resolve("") failing since the String input is not in the correct format. > The warning is marked on the Method line, not on the line where the Resolver is called. > Would it be possible to re position this somehow? At least get a stack trace or something in the warning? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3560) Arbitrary remote code execution with InvokerTransformer (COLLECTIONS-580)

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3560?page=com.atlassian.jira.plugin.... ] Fred Bricon edited comment on JBDS-3560 at 11/18/15 9:26 AM: ------------------------------------------------------------- commons-collections 3.2.2 is now available from Eclipse Orbit: https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg12654.html was (Author: fbricon): commos-collections 3.2.2 is now available from Eclipse Orbit: https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg12654.html > Arbitrary remote code execution with InvokerTransformer (COLLECTIONS-580) > ------------------------------------------------------------------------- > > Key: JBDS-3560 > URL: https://issues.jboss.org/browse/JBDS-3560 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: upstream > Affects Versions: 8.1.0.GA, 9.0.0.GA, 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Attachments: apache-commons-collections-in-JBDS7,8,9,10.png, apache-commons-collections-in-JBDS7,8,9,10_refs1.png, apache-commons-collections-in-JBDS7,8,9,10_refs10.png, apache-commons-collections-in-JBDS7,8,9,10_refs7.png, apache-commons-collections-in-JBDS7,8,9,10_refs8-IS-fuse.png, apache-commons-collections-in-JBDS7,8,9,10_refs8.png, apache-commons-collections-in-JBDS7,8,9,10_refs9.png > > > This is a container issue to wrap & track https://issues.apache.org/jira/browse/COLLECTIONS-580 > Problem is that JBDS 9 (and probably 8 and 10 too) include org.apache.commons.collections 3.2.0.v2013030210310, which is affected by COLLECTIONS-580 - Arbitrary remote code execution with InvokerTransformer -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3560) Arbitrary remote code execution with InvokerTransformer (COLLECTIONS-580)

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3560?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3560: ----------------------------------- commos-collections 3.2.2 is now available from Eclipse Orbit: https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg12654.html > Arbitrary remote code execution with InvokerTransformer (COLLECTIONS-580) > ------------------------------------------------------------------------- > > Key: JBDS-3560 > URL: https://issues.jboss.org/browse/JBDS-3560 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: upstream > Affects Versions: 8.1.0.GA, 9.0.0.GA, 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Attachments: apache-commons-collections-in-JBDS7,8,9,10.png, apache-commons-collections-in-JBDS7,8,9,10_refs1.png, apache-commons-collections-in-JBDS7,8,9,10_refs10.png, apache-commons-collections-in-JBDS7,8,9,10_refs7.png, apache-commons-collections-in-JBDS7,8,9,10_refs8-IS-fuse.png, apache-commons-collections-in-JBDS7,8,9,10_refs8.png, apache-commons-collections-in-JBDS7,8,9,10_refs9.png > > > This is a container issue to wrap & track https://issues.apache.org/jira/browse/COLLECTIONS-580 > Problem is that JBDS 9 (and probably 8 and 10 too) include org.apache.commons.collections 3.2.0.v2013030210310, which is affected by COLLECTIONS-580 - Arbitrary remote code execution with InvokerTransformer -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-488) JBTIS/JBDSIS target platform contains old version of org.jboss.tools.foundation.security.linux.feature; needs update to latest

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-488?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-488. ------------------------------ Fix Version/s: 4.3.0.Beta1 9.0.0.Beta1 Resolution: Done Picked up the mars native Teiid Designer which uses the correct foundation security jar. This is fixed in the Mars Beta1 IS. https://github.com/jbosstools/jbosstools-integration-stack/commit/7f7e0cd... > JBTIS/JBDSIS target platform contains old version of org.jboss.tools.foundation.security.linux.feature; needs update to latest > ------------------------------------------------------------------------------------------------------------------------------ > > Key: JBTIS-488 > URL: https://issues.jboss.org/browse/JBTIS-488 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.Alpha1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Minor > Fix For: 4.3.0.Beta1, 9.0.0.Beta1 > > > Update site at > http://www.qa.jboss.com/binaries/RHDS/mars/development/updates/integratio... > contains > org.jboss.tools.foundation.security.linux_1.1.2.Final-v20150325-0456-B99 > but JBDS 9 contains org.jboss.tools.foundation.security.linux_1.2.0.Beta2-v20150724-1456-B25. So, if we try to install all features (uncheck 'Group items by category'), we will get an error > Cannot complete the request. See the error log for details. > "JBoss Tools Foundation Security for Linux" will be ignored because a newer version is already installed. > This feature is required by Teiid Designer and it was included in JBTIS-112 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3489) Publishing existing eclipse project to OpenShift

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3489?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3489: ----------------------------------- the weird path contains the workspace variable. So if you reopen the workspace browser, the proper file will be selected. I found m2e uses the same behavior in Maven launch configs. And I just switched back to server templates because I was showing a nodejs app, so I had to use a nodejs template. The local templates were based on EAP > Publishing existing eclipse project to OpenShift > ------------------------------------------------ > > Key: JBDS-3489 > URL: https://issues.jboss.org/browse/JBDS-3489 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift, requirements > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Critical > Labels: openshift_v3 > Fix For: 9.1.0.Beta1 > > Attachments: project-selection.bmml, project-selection.png > > > As a developer I would like to take an existing eclipse web project and deploy to my existing openshift v3 connection. > * This is equivalent to 'oc new-app' -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20215) Version property is not replaced with a value defined in parent pom

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20215?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-20215. ------------------------------------ > Version property is not replaced with a value defined in parent pom > ------------------------------------------------------------------- > > Key: JBIDE-20215 > URL: https://issues.jboss.org/browse/JBIDE-20215 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, upstream > Affects Versions: 4.3.0.Alpha1 > Environment: JBDS 9.0.0.Alpha1 > Reporter: Matous Jobanek > Fix For: 4.3.x > > Attachments: parent.zip > > > Consider this situation: > There is a parent pom where a version property is defined. > {code:xml} > <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> > <modelVersion>4.0.0</modelVersion> > <groupId>jira</groupId> > <artifactId>jira-reproducer-parent</artifactId> > <version>1.0</version> > <packaging>pom</packaging> > <properties> > <reproducer.child.version>1.1.Final</reproducer.child.version> > </properties> > </project> > {code} > Then there is a child pom and version of this pom is the property defined in the parent pom. > {code:xml} > <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> > <modelVersion>4.0.0</modelVersion> > <parent> > <groupId>jira</groupId> > <artifactId>jira-reproducer-parent</artifactId> > <version>1.0</version> > <relativePath>../pom.xml</relativePath> > </parent> > <artifactId>jira-reproducer-child</artifactId> > <version>${reproducer.child.version}</version> > </project> > {code} > Then the generated pom at target/classes/META-INF/maven/jira/jira-reproducer-child/pom.xml doesn't contain the replaced value from the parent pom, but the original property: > {code:xml} > <version>${reproducer.child.version}</version> > {code} > should be: > {code:xml} > <version>1.1.Final</version> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21060) Upgrade Forge Runtime to 2.20.1.Final

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21060?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-21060. ------------------------------ Verified in 4.3.1-SNAPSHOT (Beta1-v20151116-1009-B138), and 4.4.0-SNAPSHOT (Alpha1-v20151115-1028-B11081) > Upgrade Forge Runtime to 2.20.1.Final > ------------------------------------- > > Key: JBIDE-21060 > URL: https://issues.jboss.org/browse/JBIDE-21060 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.3.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20970) Upgrade Forge Runtime to 2.20.0.Final

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20970?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-20970. ------------------------------ JBIDE-21060 upgrades runtime to 2.20.1. Closing this one. > Upgrade Forge Runtime to 2.20.0.Final > ------------------------------------- > > Key: JBIDE-20970 > URL: https://issues.jboss.org/browse/JBIDE-20970 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.3.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21026) New hibernate configuration wizard controls invisible in Unix

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21026?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-21026. -------------------------------- Verified with Build JBDS 9.0.1.Beta1-v20151110-2316-B137 > New hibernate configuration wizard controls invisible in Unix > ------------------------------------------------------------- > > Key: JBIDE-21026 > URL: https://issues.jboss.org/browse/JBIDE-21026 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.3.0.CR1 > Reporter: Dmitry Bocharov > Assignee: Koen Aers > Priority: Minor > Fix For: 4.3.1.Beta1 > > Attachments: Fedora22.png, Windows7.png > > > Screenshots from Fefora22 and Windows7 are attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21078) [bower] invalid numbers of parameters

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21078?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-21078. ------------------------------ Verified in Mars.1, JBossTools Latest Build: 4.3.1-SNAPSHOT (Beta1-v20151116-1009-B138) > [bower] invalid numbers of parameters > ------------------------------------- > > Key: JBIDE-21078 > URL: https://issues.jboss.org/browse/JBIDE-21078 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: nodejs > Affects Versions: 4.3.1.Beta1 > Environment: windows > Reporter: Pavol Srna > Assignee: Ilya Buziuk > Priority: Blocker > Fix For: 4.3.1.Beta1 > > Attachments: screen.png > > > {code} > C:\Users\Pali:1 > (function (exports, require, module, __filename, __dirname) { Invalid number of parameters > ^^^^^^ > SyntaxError: Unexpected identifier > at exports.runInThisContext (vm.js:53:16) > at Module._compile (module.js:414:25) > at Object.Module._extensions..js (module.js:442:10) > at Module.load (module.js:356:32) > at Function.Module._load (module.js:311:12) > at Function.Module.runMain (module.js:467:10) > at startup (node.js:136:18) > at node.js:963:3 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 November 2015