June 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26123) For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [forge]

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26123?page=com.atlassian.jira.plugi... ] George Gastaldi closed JBIDE-26123. ----------------------------------- Resolution: Done > For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [forge] > ------------------------------------------------------------------ > > Key: JBIDE-26123 > URL: https://issues.jboss.org/browse/JBIDE-26123 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: forge > Reporter: Nick Boldt > Assignee: George Gastaldi > Priority: Blocker > Labels: task > Fix For: 4.6.0.Final > > > For JBIDE 4.6.0.Final [forge]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.6.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.6.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.6.0.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.0.Final-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] 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 forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26139) openshift does not compile anymore

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26139?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-26139 at 6/20/18 11:09 AM: -------------------------------------------------------------------- Latest JGit Repository marked #getRef as deprecated and tells users to use #findRef instead {code} /** * Get a ref by name. * * @param name * the name of the ref to lookup. May be a short-hand form, e.g. * "master" which is is automatically expanded to * "refs/heads/master" if "refs/heads/master" already exists. * @return the Ref with the given name, or {@code null} if it does not exist * @throws java.io.IOException * @deprecated Use {@link #exactRef(String)} or {@link #findRef(String)} * instead. */ @Deprecated @Nullable public Ref getRef(final String name) throws IOException { return findRef(name); } {code} was (Author: adietish): TestRepository marked #getRef as deprecated and tells users to use #extractRef instead {code} /** * Get a ref by name. * * @param name * the name of the ref to lookup. May be a short-hand form, e.g. * "master" which is is automatically expanded to * "refs/heads/master" if "refs/heads/master" already exists. * @return the Ref with the given name, or {@code null} if it does not exist * @throws java.io.IOException * @deprecated Use {@link #exactRef(String)} or {@link #findRef(String)} * instead. */ @Deprecated @Nullable public Ref getRef(final String name) throws IOException { return findRef(name); } {code} > openshift does not compile anymore > ---------------------------------- > > Key: JBIDE-26139 > URL: https://issues.jboss.org/browse/JBIDE-26139 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.AM3 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Fix For: 4.6.0.Final > > > Since a change in the target platform, jbosstools openshift does not compile anymore. an unknown method is used in org.jboss.tools.openshift.egit.test > {code} > [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:1.1.0:compile (default-compile) on project org.jboss.tools.openshift.egit.test: Compilation failure: Compilation failure: > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift-Pull-Request/tests/org.jboss.tools.openshift.egit.test/src/org/jboss/tools/openshift/egit/internal/test/util/TestRepository.java:[477] > [ERROR] Ref ref = repository.getRef(Constants.HEAD); > [ERROR] ^^^^^^ > [ERROR] The method getRef(String) is undefined for the type Repository > [ERROR] 1 problem (1 error) > [ERROR] -> [Help 1] > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26020) Find cause of CDI 1.0 and 1.1 itests instability

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26020?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-26020: --------------------------------------- and by Java compliance warning -> Needed to change Java Facet set up to Java 1.8. > Find cause of CDI 1.0 and 1.1 itests instability > ------------------------------------------------ > > Key: JBIDE-26020 > URL: https://issues.jboss.org/browse/JBIDE-26020 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi, integration-tests > Affects Versions: 4.6.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Fix For: 4.6.0.Final > > > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... and https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... shows that there are some dirty editor states, etc. Review tests and find errors. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25199) Integration Tests: OpenNewApplicationWizardTest

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25199?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-25199: ---------------------------------- Story Points: 8 > Integration Tests: OpenNewApplicationWizardTest > ----------------------------------------------- > > Key: JBIDE-25199 > URL: https://issues.jboss.org/browse/JBIDE-25199 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM3 > Reporter: Andre Dietisheim > Assignee: Josef Kopriva > Labels: integration_tests > Fix For: 4.6.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25201) Integration Tests: CreateApplicationOnBuilderImageTest

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25201?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-25201: ---------------------------------- Story Points: 8 > Integration Tests: CreateApplicationOnBuilderImageTest > ------------------------------------------------------ > > Key: JBIDE-25201 > URL: https://issues.jboss.org/browse/JBIDE-25201 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM3 > Reporter: Andre Dietisheim > Assignee: Josef Kopriva > Labels: integration_tests > Fix For: 4.6.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26138) Integration Tests: NodeJSAppDebugTest

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26138?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-26138: ---------------------------------- Story Points: 13 > Integration Tests: NodeJSAppDebugTest > ------------------------------------- > > Key: JBIDE-26138 > URL: https://issues.jboss.org/browse/JBIDE-26138 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests, openshift > Affects Versions: 4.6.0.AM3 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: 4.6.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25546) Explorer: context menu has "Delete Resource" available even if there's nothing selected

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25546?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25546: ------------------------------------- Story Points: 2 > Explorer: context menu has "Delete Resource" available even if there's nothing selected > --------------------------------------------------------------------------------------- > > Key: JBIDE-25546 > URL: https://issues.jboss.org/browse/JBIDE-25546 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Labels: explorer > Fix For: 4.6.0.Final > > Attachments: explorer-context-menu.png > > > # ASSERT: have Properties view visible > # ASSERT: have nothing selected in OpenShift Explorer > # EXEC: open the context menu in OpenShift Explorer > Result: > !explorer-context-menu.png! > The context menu in OpenShift Explorer holds New > Connection which is right, but also a "Delete Resource" entry which makes no sense at all -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25866) Schema files for WildFly 12 are missing

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25866?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25866: ------------------------------- Sprint: devex #151 June 2018 > Schema files for WildFly 12 are missing > --------------------------------------- > > Key: JBIDE-25866 > URL: https://issues.jboss.org/browse/JBIDE-25866 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.3.AM3 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.6.x > > > I accidentally found out that schema files that are new in WildFly 12 haven't been added to org.jboss.tools.as.catalog plugin, for instance jboss-web_12_0.xsd (I'm not sure if there are more). > Why I found out is that I was just trying to verify and close this older JIRA: > JBIDE-25102 Add "jboss-web-11_0.xsd" to catalog > And since then we now have WildFly 12 too. > So this is something to keep in mind when adding a new server adapter. > Also, please check if this needs to be added to https://github.com/robstryker/jboss.org.schema too. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26071) Add server adapter for WildFly 13

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26071?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26071: ------------------------------- Sprint: devex #151 June 2018 > Add server adapter for WildFly 13 > --------------------------------- > > Key: JBIDE-26071 > URL: https://issues.jboss.org/browse/JBIDE-26071 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.6.0.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.6.0.Final > > > It turns out WildFly 13 was released yesterday. They're on a quarterly release cadence now apparently. So I wonder how we should deal with this. Perhaps should group some of the versions if there are no breaking changes for us? Or do you think it's better to stick with our current model of always adding a new adapter and that way you can always update the libs? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22138) Server adapter: doesn't respect openshift maven profile

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22138: ------------------------------------- Story Points: 16 > Server adapter: doesn't respect openshift maven profile > ------------------------------------------------------- > > Key: JBIDE-22138 > URL: https://issues.jboss.org/browse/JBIDE-22138 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477 > Openshift plugin 3.1.0.Final-v20160401-2357-B263 > Reporter: Rafael Benevides > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.6.0.Final > > > This is a follow up on JBIDE-22128. > The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes > steps: > # EXEC: follow steps outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... (deploying with fabric8 maven plugin doesn't work, you end up having the pod failing with ImagePullBack error. You need to take the alternative road where you deploy via "oc new-build", "oc new-app", "oc expose" etc.) > # EXEC: import the app into your Eclipse workspace > # EXEC: "hello" (workspace) project: Properties > Maven > Active Maven Profile: set "openshift" > # EXEC: create a server adapter and start it > # ASSERT: adapter starts syncing, verify what war is used > Result: > The war that's created locally and then synced to the pod is "hello.war" even though the profile specifies "ROOT.war" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 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 June 2018