March 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25159) Server adapter wizard: doesnt show up but selects existing but defunct adapter after I switched CDK

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25159?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-25159: ------------------------------------------ This is still happening, unfortunately as for 4.5.3.AM3. > Server adapter wizard: doesnt show up but selects existing but defunct adapter after I switched CDK > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-25159 > URL: https://issues.jboss.org/browse/JBIDE-25159 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM3 > Reporter: Andre Dietisheim > Labels: openshift_v3, server_adapter_wizard > Fix For: 4.5.x > > Attachments: image-2017-10-06-15-23-43-428.png, image-2017-10-06-15-23-43-428.png > > > # ASSERT: have *cdk 3.1.1* installed and running > # ASSERT: have a connection, an application and a *server adapter* for this cdk (ex. an application created from nodejs-mongo-persistent template and the adapter therefore called *nodejs-mongo-persistent* > # EXEC: install cdk 3.2.0.alpha1 and launch it > # ASSERT: the new cdk is now on a different IP thant the one that cdk 3.1.1 used (ex. 192.168.42.207 for cdk 3.1.1, 192.168.42.20 for cdk 3.2.0.alpha1) > # ASSERT: *DONT* delete the server adapter for it > # EXEC: create an application from the same exmplate (ex. nodejs-mongo-persistent), do *NOT* create an adapter for it when creating the app > # EXEC: in OpenShift explorer: select service *nodejs-mongo-persistent* and pick *Server Adapter* in the context menu. > Result: > The server adapter wizard doesnt show up. Instead the "Servers" view pops up and selects the server adapter for the service that existed in the previous cdk. > Here's the screencast showing it: https://youtu.be/s772d9FMRIw > !image-2017-10-06-15-23-43-428.png! > Expected result: > The server adapter wizard should show up. The existing server adapter is not matching the service that is selected in the explorer. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25881) For JBIDE 4.5.3.Final: Prepare for 4.5.3.Final / 11.3.0.GA [hibernate]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25881?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25881: ------------------------------------ bump up to parent pom version = 4.5.3.Final-SNAPSHOT > For JBIDE 4.5.3.Final: Prepare for 4.5.3.Final / 11.3.0.GA [hibernate] > ---------------------------------------------------------------------- > > Key: JBIDE-25881 > URL: https://issues.jboss.org/browse/JBIDE-25881 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Nick Boldt > Assignee: Koen Aers > Priority: Blocker > Labels: task > Fix For: 4.5.3.Final > > > For JBIDE 4.5.3.Final [hibernate]: 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.5.3.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.3.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.3.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.71.1.Final > > {code} > mvn clean verify -Dtpc.version=4.71.1.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.73.0.AM2-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.73.0.AM2-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 hibernate 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)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25881) For JBIDE 4.5.3.Final: Prepare for 4.5.3.Final / 11.3.0.GA [hibernate]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25881?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-25881. ------------------------------ Resolution: Done > For JBIDE 4.5.3.Final: Prepare for 4.5.3.Final / 11.3.0.GA [hibernate] > ---------------------------------------------------------------------- > > Key: JBIDE-25881 > URL: https://issues.jboss.org/browse/JBIDE-25881 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Nick Boldt > Assignee: Koen Aers > Priority: Blocker > Labels: task > Fix For: 4.5.3.Final > > > For JBIDE 4.5.3.Final [hibernate]: 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.5.3.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.3.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.3.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.71.1.Final > > {code} > mvn clean verify -Dtpc.version=4.71.1.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.73.0.AM2-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.73.0.AM2-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 hibernate 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)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25165) Server Adapter Editor: pops up 2 connection dialogs if I open the editor while my connection has no pw stored

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25165?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-25165. -------------------------------------- Resolution: Done > Server Adapter Editor: pops up 2 connection dialogs if I open the editor while my connection has no pw stored > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25165 > URL: https://issues.jboss.org/browse/JBIDE-25165 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard, openshift, server_adapter_editor > Fix For: 4.5.3.Final > > > # ASSERT: make sure that you have a connection where the password is *NOT* stored > # ASSERT: have a server adapter that is using this connection > # EXEC: restart Eclipse > # EXEC: in the freshly started Eclipse: open the editor for your server adapter > # ASSERT: connection wizard pops up prompting you to provide the password > # EXEC: "Cancel" the dialog > Result: > The connection wizard pops up a 2nd time > Expected result: > I should not have to cancel the dialog a 2nd time -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25165) Server Adapter Editor: pops up 2 connection dialogs if I open the editor while my connection has no pw stored

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25165?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-25165: ---------------------------------------- Fix Version/s: 4.5.3.Final (was: 4.5.x) Assignee: Andre Dietisheim > Server Adapter Editor: pops up 2 connection dialogs if I open the editor while my connection has no pw stored > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25165 > URL: https://issues.jboss.org/browse/JBIDE-25165 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard, openshift, server_adapter_editor > Fix For: 4.5.3.Final > > > # ASSERT: make sure that you have a connection where the password is *NOT* stored > # ASSERT: have a server adapter that is using this connection > # EXEC: restart Eclipse > # EXEC: in the freshly started Eclipse: open the editor for your server adapter > # ASSERT: connection wizard pops up prompting you to provide the password > # EXEC: "Cancel" the dialog > Result: > The connection wizard pops up a 2nd time > Expected result: > I should not have to cancel the dialog a 2nd time -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25165) Server Adapter Editor: pops up 2 connection dialogs if I open the editor while my connection has no pw stored

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25165?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-25165: ------------------------------------------ This is not happening any more. Resolving as DONE. > Server Adapter Editor: pops up 2 connection dialogs if I open the editor while my connection has no pw stored > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25165 > URL: https://issues.jboss.org/browse/JBIDE-25165 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard, openshift, server_adapter_editor > Fix For: 4.5.3.Final > > > # ASSERT: make sure that you have a connection where the password is *NOT* stored > # ASSERT: have a server adapter that is using this connection > # EXEC: restart Eclipse > # EXEC: in the freshly started Eclipse: open the editor for your server adapter > # ASSERT: connection wizard pops up prompting you to provide the password > # EXEC: "Cancel" the dialog > Result: > The connection wizard pops up a 2nd time > Expected result: > I should not have to cancel the dialog a 2nd time -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25224) OpenShift maven build fails on Windows - EGit tests failures

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25224?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25224: ------------------------------------- Summary: OpenShift maven build fails on Windows - EGit tests failures (was: OpenShift maven build fails on Windows - EGIt tests failures) > OpenShift maven build fails on Windows - EGit tests failures > ------------------------------------------------------------ > > Key: JBIDE-25224 > URL: https://issues.jboss.org/browse/JBIDE-25224 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.Final > Environment: Windows 10 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Labels: openshift_v3 > Fix For: 4.5.x > > > Command *mvn clean install* fails in jbosstools-openshift repo: > {code:java} > ------------------------------------------------------- > T E S T S > ------------------------------------------------------- > Running org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest > SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". > SLF4J: Defaulting to no-operation (NOP) logger implementation > SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. > Tests run: 38, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 26.824 sec <<< FAILURE! - in org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest > shouldReturnLatestCommitInRemoteRepo(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 2.006 sec > shouldFetchAndHaveRemoteRef(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.672 sec > canGetFromSeveralRemoteConfig(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.594 sec > shouldReturnHostFromFullGitUrl(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.656 sec > shouldReturnThatCloneIsAheadOfRemote(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 1.032 sec > canGetSingleRemoteConfig(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.687 sec > pushFailsOnNonFastForward(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.719 sec > shouldReturnThatCloneIsAhead(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.719 sec > canGetRepoForFile(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.734 sec > newUntrackedFilesAreCounted(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.672 sec > shouldReturnUserFromFullGitUrl(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.64 sec > canAddRemoteRepo(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.579 sec > removedButNotCommittedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.625 sec > canCommitFileInProject(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.656 sec > shouldReturnRepositoryDoesntExists(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.547 sec > shouldConsiderSSHGitUrlValid(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.687 sec > shouldCheckoutBranch(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.735 sec > shouldUserFetchSpecInConfig(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.625 sec > shouldReturnLatestCommitInLocalRepo(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.64 sec > modifiedButNotCommittedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.706 sec > canCheckIfHasRemote(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.611 sec > originShouldBeDefaultRemoteRepo(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.581 sec > shouldReturnThatRemoteIsAhead(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.766 sec > forcedPushRemovesFileInRemote(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.703 sec <<< ERROR! > org.eclipse.core.internal.resources.ResourceException: Problems encountered while deleting resources. > at org.eclipse.core.internal.resources.Resource.delete(Resource.java:773) > at org.eclipse.core.internal.resources.Project.delete(Project.java:318) > at org.jboss.tools.openshift.egit.internal.test.util.TestProject.dispose(TestProject.java:84) > at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:116) > untrackedWhileIncludeUntrackedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.781 sec > shouldNotBeAheadAfterPush(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.782 sec > canGetRepoForProject(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.578 sec > fileAddedToCloneIsInOriginAfterPush(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.672 sec > newUntrackedFileIsNotCountedIfIgnoreUntracked(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.515 sec > shouldConsiderSCPGitUrlValid(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.594 sec > getRemoteHttpRepos(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.797 sec > addedButNotCommittedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.597 sec > untrackedWhileDontIncludeUntrackedIsNotDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.575 sec > shouldReturnHEADAsIs(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.718 sec > shouldReturnRepositoryExists(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.625 sec > shouldReturnRemoteBranchName(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.657 sec > shouldReturnLocalBranchName(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.578 sec > fileAddedToCloneIsInRemoteAfterPush(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.687 sec > Running org.jboss.tools.openshift.egit.internal.test.GitIgnoreTest > Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.578 sec - in org.jboss.tools.openshift.egit.internal.test.GitIgnoreTest > canAddEntries(org.jboss.tools.openshift.egit.internal.test.GitIgnoreTest) Time elapsed: 0 sec > writingDoesNotAlterOrdering(org.jboss.tools.openshift.egit.internal.test.GitIgnoreTest) Time elapsed: 0.125 sec > canParseExistingEntries(org.jboss.tools.openshift.egit.internal.test.GitIgnoreTest) Time elapsed: 0.125 sec > newEntriesAreAddedToTheEnd(org.jboss.tools.openshift.egit.internal.test.GitIgnoreTest) Time elapsed: 0.11 sec > addingExistingEntryDoesNotMoveItToTheEnd(org.jboss.tools.openshift.egit.internal.test.GitIgnoreTest) Time elapsed: 0.125 sec > entryIsNotAddedTwice(org.jboss.tools.openshift.egit.internal.test.GitIgnoreTest) Time elapsed: 0.093 sec > Results : > Tests in error: > EGitUtilsTest.tearDown:116 ╗ Resource Problems encountered while deleting reso... > Tests run: 44, Failures: 0, Errors: 1, Skipped: 0 > [INFO] ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] jbosstools-openshift ............................... SUCCESS [ 0.891 s] > [INFO] openshift.plugins .................................. SUCCESS [ 0.062 s] > [INFO] org.jboss.tools.openshift.egit.core ................ SUCCESS [ 21.017 s] > [INFO] org.jboss.tools.openshift.egit.ui .................. SUCCESS [ 3.453 s] > [INFO] org.jboss.tools.openshift.express.client ........... SUCCESS [ 7.301 s] > [INFO] org.jboss.tools.openshift.common.core .............. SUCCESS [ 5.125 s] > [INFO] org.jboss.tools.openshift.express.core ............. SUCCESS [ 5.039 s] > [INFO] org.jboss.tools.openshift.common.ui ................ SUCCESS [ 7.430 s] > [INFO] org.jboss.tools.openshift.express.ui ............... SUCCESS [ 13.594 s] > [INFO] org.jboss.tools.openshift.client ................... SUCCESS [ 1.328 s] > [INFO] org.jboss.tools.openshift.core ..................... SUCCESS [ 3.105 s] > [INFO] org.jboss.tools.openshift.ui ....................... SUCCESS [ 15.898 s] > [INFO] org.jboss.tools.openshift.cdk.server ............... SUCCESS [ 3.188 s] > [INFO] org.jboss.tools.openshift.js ....................... SUCCESS [ 4.179 s] > [INFO] org.jboss.tools.openshift.io.core .................. SUCCESS [ 4.453 s] > [INFO] org.jboss.tools.openshift.io.ui .................... SUCCESS [ 3.375 s] > [INFO] openshift.itests ................................... SUCCESS [ 0.047 s] > [INFO] openshift.test-framework ........................... SUCCESS [ 0.047 s] > [INFO] org.jboss.tools.openshift.reddeer .................. SUCCESS [ 2.535 s] > [INFO] org.jboss.tools.openshift.ui.bot.test .............. SUCCESS [ 2.766 s] > [INFO] openshift.tests .................................... SUCCESS [ 0.063 s] > [INFO] org.jboss.tools.openshift.egit.test ................ FAILURE [ 42.365 s] > [INFO] org.jboss.tools.openshift.express.test ............. SKIPPED > [INFO] org.jboss.tools.openshift.test ..................... SKIPPED > [INFO] org.jboss.tools.openshift.cdk.server.test .......... SKIPPED > [INFO] org.jboss.tools.openshift.io.test .................. SKIPPED > [INFO] org.jboss.tools.cdk.reddeer ........................ SKIPPED > [INFO] openshift.features ................................. SKIPPED > [INFO] org.jboss.tools.openshift.feature .................. SKIPPED > [INFO] org.jboss.tools.openshift.test.feature ............. SKIPPED > [INFO] org.jboss.tools.openshift.egit.integration.feature . SKIPPED > [INFO] org.jboss.tools.openshift.egit.integration.test.feature SKIPPED > [INFO] org.jboss.tools.openshift.express.feature .......... SKIPPED > [INFO] org.jboss.tools.openshift.express.test.feature ..... SKIPPED > [INFO] org.jboss.tools.openshift.cdk.feature .............. SKIPPED > [INFO] org.jboss.tools.openshift.cdk.test.feature ......... SKIPPED > [INFO] org.jboss.tools.openshift.integration.tests.feature SKIPPED > [INFO] org.jboss.tools.openshift.js.feature ............... SKIPPED > [INFO] org.jboss.tools.openshift.io.feature ............... SKIPPED > [INFO] org.jboss.tools.openshift.io.test.feature .......... SKIPPED > [INFO] openshift.site ..................................... SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 03:31 min > [INFO] Finished at: 2017-10-12T10:41:22+02:00 > [INFO] Final Memory: 216M/1534M > [INFO] ------------------------------------------------------------------------ > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25890) For JBIDE 4.5.3.Final: Prepare for 4.5.3.Final / 11.3.0.GA [updatesite]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25890?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-25890: ---------------------------------- Assignee: Nick Boldt > For JBIDE 4.5.3.Final: Prepare for 4.5.3.Final / 11.3.0.GA [updatesite] > ----------------------------------------------------------------------- > > Key: JBIDE-25890 > URL: https://issues.jboss.org/browse/JBIDE-25890 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.5.3.Final > > > For JBIDE 4.5.3.Final [updatesite]: 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.5.3.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.3.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.3.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.71.1.Final > > {code} > mvn clean verify -Dtpc.version=4.71.1.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.73.0.AM2-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.73.0.AM2-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 updatesite 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)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25890) For JBIDE 4.5.3.Final: Prepare for 4.5.3.Final / 11.3.0.GA [updatesite]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-25890: ---------------------------------- Summary: For JBIDE 4.5.3.Final: Prepare for 4.5.3.Final / 11.3.0.GA [updatesite] Key: JBIDE-25890 URL: https://issues.jboss.org/browse/JBIDE-25890 Project: Tools (JBoss Tools) Issue Type: Task Components: updatesite Reporter: Nick Boldt Priority: Blocker Fix For: 4.5.3.Final For JBIDE 4.5.3.Final [updatesite]: 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.5.3.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.5.3.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.5.3.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.71.1.Final {code} mvn clean verify -Dtpc.version=4.71.1.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.73.0.AM2-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.73.0.AM2-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 updatesite 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)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25891) For JBIDE 4.5.3.Final: Prepare for 4.5.3.Final / 11.3.0.GA [central-update]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25891?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-25891: ---------------------------------- Assignee: Nick Boldt > For JBIDE 4.5.3.Final: Prepare for 4.5.3.Final / 11.3.0.GA [central-update] > --------------------------------------------------------------------------- > > Key: JBIDE-25891 > URL: https://issues.jboss.org/browse/JBIDE-25891 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central-update > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.5.3.Final > > > For JBIDE 4.5.3.Final [central-update]: 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.5.3.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.3.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.3.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.71.1.Final > > {code} > mvn clean verify -Dtpc.version=4.71.1.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.73.0.AM2-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.73.0.AM2-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 central-update 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)

8 years, 3 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 March 2018