July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22626) Updating deployed docker image on OpenShift does not work

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22626?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22626: ----------------------------------- Fix Version/s: 4.4.1.AM2 (was: 4.4.1.AM1) > Updating deployed docker image on OpenShift does not work > --------------------------------------------------------- > > Key: JBIDE-22626 > URL: https://issues.jboss.org/browse/JBIDE-22626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Priority: Critical > Labels: docker, openshift_v3 > Fix For: 4.4.1.AM2 > > > In JBIDE-22515 was fixed use case when user have an image with specific tag. That works now ok. > But if user deploys image with tag e.g. 0.8 to OpenShift, resources are created for this specific tag. When I am trying to push image with tag 0.9 afterwards, everything finish without an error. No new resources are created, but no existing resources are modified to contain this new image. Deployment config still contains tag 0.8 and thus new deployment is not done. > Basically we need to modify deployment config in such cases to contains newer tag and let OpenShift do all magic and redeploy it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22594) Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22594?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22594: ----------------------------------- Fix Version/s: 4.4.1.AM2 (was: 4.4.1.AM1) > Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22594 > URL: https://issues.jboss.org/browse/JBIDE-22594 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Assignee: Dmitry Bocharov > Labels: connection_wizard, deploy_docker_wizard, openshift_v3 > Fix For: 4.4.1.AM2 > > Attachments: out-2.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22578) Publishing sometimes recursively deletes parent to deploy directory

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22578?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22578: ----------------------------------- Fix Version/s: 4.4.1.AM2 (was: 4.4.1.AM1) > Publishing sometimes recursively deletes parent to deploy directory > ------------------------------------------------------------------- > > Key: JBIDE-22578 > URL: https://issues.jboss.org/browse/JBIDE-22578 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.1.Final > Environment: Eclipse Mars.2 Release (4.5.2) > Java 1.8.0_91 > Windows 7 64-bit > JBoss EAP 6.4.0 > Reporter: Daniel Atallah > Assignee: Martin Malina > Priority: Blocker > Fix For: 4.4.1.AM2 > > Attachments: jboss_deployment.jpg, jboss_tools.20160630.stdout.log, servers.xml > > > For a number of weeks we've had a number of occurrences where a eclipse workspace will get corrupted due to the deletion of all files in it. > It seems to have started happening at the time we updated to the 4.3.1 JBoss Tools from the 4.3.0 JBoss Tools. > We've been able to track the process doing the deleting to the Eclipse process by using Sysinternals Process Monitor tool (https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx). > Our workspaces are structured as follows: > {noformat} > WORKSPACEROOT=$DEVROOT\workspacename > # Custom deploy folder (as specified in the "Deployment" settings for the configured "Red Hat JBoss Enterprise Application Platform 6.1+") Server > $WORKSPACEROOT\deploy > # Version Control (Mercurial) working directory containing various Eclipse projects that get published to the Server by the tooling > $WORKSPACEROOT\src > # value specified as a "jboss.server.data.dir" property in the Server launch configuration VM arguments > $WORKSPACEROOT/server/data > # value specified as a "jboss.server.temp.dir" property in the Server launch configuration VM arguments > $WORKSPACEROOT/server/tmp > {noformat} > The Server is configured to "Automatically publish when resources change". > What we're seeing is that occasionally when the Server is running and the Mercurial working copy receives updates, the Incremental Publishing that results from these updates somehow tries to recursively delete $WORKSPACEROOT. > The eclipse log includes the following: > {noformat} > !ENTRY org.eclipse.core.resources 4 1 2016-06-07 16:05:57.795 > !MESSAGE Problems occurred refreshing resources > !SUBENTRY 1 org.eclipse.core.resources 4 1 2016-06-07 16:05:57.795 > !MESSAGE Problem finding next change, code: 5 > !ENTRY org.jboss.ide.eclipse.as.core 4 1644298244 2016-06-07 16:06:09.207 > !MESSAGE Incremental publish failed for module $MODULENAME > !SUBENTRY 1 org.jboss.ide.eclipse.as.wtp.core 4 1644298251 2016-06-07 16:06:09.207 > !MESSAGE Could not delete $WORKSPACEROOT. May be locked by another process. > {noformat} > Any idea what might be happening? > Is there some debug logging we can enable to get better visibility to what's going on? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22552) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22552?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22552: ----------------------------------- Fix Version/s: 4.4.1.AM2 (was: 4.4.1.AM1) > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 > ------------------------------------------------ > > Key: JBIDE-22552 > URL: https://issues.jboss.org/browse/JBIDE-22552 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.4.1.AM2 > > > For JBIDE 4.4.1.Alpha1: 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{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-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.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > See also: JBDS-3930 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22562) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Playground]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22562?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22562: ----------------------------------- Fix Version/s: 4.4.1.AM2 (was: 4.4.1.AM1) > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Playground] > ------------------------------------------------------------- > > Key: JBIDE-22562 > URL: https://issues.jboss.org/browse/JBIDE-22562 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: playground > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Labels: task > Fix For: 4.4.1.AM2 > > > For JBIDE 4.4.1.Alpha1 [Playground]: 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{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-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.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Playground task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22593) New application wizard: preselect v3 connection that I most recently used

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22593?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22593: ----------------------------------- Fix Version/s: 4.4.1.AM2 (was: 4.4.1.AM1) > New application wizard: preselect v3 connection that I most recently used > ------------------------------------------------------------------------- > > Key: JBIDE-22593 > URL: https://issues.jboss.org/browse/JBIDE-22593 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Labels: application_wizard, connection_wizard, openshift_v2, openshift_v3 > Fix For: 4.4.1.AM2 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > # ASSERT: make sure that you have used a v3 connection (ex. import an application from your OpenShift server to your workspace) > # EXEC: launch openshift wizard via File->New->OpenShift Application > # ASSERT: connection dialog shows up > Result: > Connection dialog shows up with <New Connection> and connection type "OpenShift 2" pre-selected. > Expected result: > Connection dialog has my v3 connection preselected, that I recently used. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22554) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Central Discovery]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22554?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22554: ----------------------------------- Fix Version/s: 4.4.1.AM2 (was: 4.4.1.AM1) > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Central Discovery] > -------------------------------------------------------------------- > > Key: JBIDE-22554 > URL: https://issues.jboss.org/browse/JBIDE-22554 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central-update > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.4.1.AM2 > > > For JBIDE 4.4.1.Alpha1 [Central Discovery]: 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{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-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.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central Discovery task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22557) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22557?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22557: ----------------------------------- Fix Version/s: 4.4.1.AM2 (was: 4.4.1.AM1) > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch] > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22557 > URL: https://issues.jboss.org/browse/JBIDE-22557 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.4.1.AM2 > > > For JBIDE 4.4.1.Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]: 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{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-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.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22550) Prepare parent pom for 4.4.1 / 10.1

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22550?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22550: ----------------------------------- Fix Version/s: 4.4.1.AM2 (was: 4.4.1.AM1) > Prepare parent pom for 4.4.1 / 10.1 > ----------------------------------- > > Key: JBIDE-22550 > URL: https://issues.jboss.org/browse/JBIDE-22550 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.AM2 > > > * upversion parent pom to 4.4.1.Alpha1 > * set new lastStableRepository = http://download.jboss.org/jbosstools/neon/staging/updates/ to ensure baseline checks look at 4.4.0.Final instead of 4.3.x versions -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22657) smart import nullpointer

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22657?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22657: ----------------------------------- Fix Version/s: 4.4.1.AM2 (was: 4.4.1.AM1) > smart import nullpointer > ------------------------ > > Key: JBIDE-22657 > URL: https://issues.jboss.org/browse/JBIDE-22657 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.4.1.AM2, 4.5.0.AM1 > > > when using smartimport to import https://github.com/maxandersen/imapfilter-docker.git from disk I got a NPE in jaxrs: > {code} > java.lang.NullPointerException > at org.jboss.tools.ws.jaxrs.ui.internal.importer.JaxRsConfigurator.canConfigure(JaxRsConfigurator.java:66) > at org.eclipse.ui.internal.wizards.datatransfer.SmartImportJob.importProjectAndChildrenRecursively(SmartImportJob.java:466) > at org.eclipse.ui.internal.wizards.datatransfer.SmartImportJob.run(SmartImportJob.java:242) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 2016