[JBoss JIRA] (JBIDE-22436) Intermittent NullPointerException upon opening helloworld, kitchensink cheat sheets in JBDS
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22436?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22436:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Intermittent NullPointerException upon opening helloworld, kitchensink cheat sheets in JBDS
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-22436
> URL: https://issues.jboss.org/browse/JBIDE-22436
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples, upstream
> Affects Versions: 4.3.1.Final
> Reporter: Michal Jurc
> Assignee: Snjezana Peco
> Priority: Minor
> Fix For: 4.6.x
>
> Attachments: JBIDE-22436-10.0-helloworld.log, JBIDE-22436-9.1-helloworld.log, helloworld-cheatsheet.xml, jbds104-cheat-sheet-npe.log, kitchensink-cheatsheet.xml, npe-jbds11-fedora26-x64.log, npe-jbds11ga-fedora26-x64.log, org.jboss.tools.cheatsheet.test.zip
>
>
> After finishing the import of {{helloworld}} and {{kitchensink}} quickstarts, the user is prompted whether the cheat sheet for the project should be opened. Upon opening it, JBDS 9.0 and 9.1 produces the following error message:
> {quote}An error has occurred. See error log for more details.
> java.lang.NullPointerException{quote}
> The detailed error log produces the same message.
> The quickstarts and their cheat sheets work even after the prompt with NullPointerException message.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-15480) Keep data for ICategoryProvider in KB model
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15480?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-15480:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Keep data for ICategoryProvider in KB model
> -------------------------------------------
>
> Key: JBIDE-15480
> URL: https://issues.jboss.org/browse/JBIDE-15480
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: common
> Reporter: Viacheslav Kabanovich
> Assignee: Jeff MAURY
> Fix For: 4.6.x
>
>
> Interface ICategoryProvider was created to sort attributes in Property View by categories and by priority. Currently, there is just one implementation for JQuery, but it was designed to have more implementations for other HTML 5 libraries. The first experience showed that this approach is resulting in repeating attribute data that otherwise could be encapsulated in KB model.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-22051) Redesing route prompting in server adapter wizard, show in browser etc.
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22051?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22051:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Redesing route prompting in server adapter wizard, show in browser etc.
> -----------------------------------------------------------------------
>
> Key: JBIDE-22051
> URL: https://issues.jboss.org/browse/JBIDE-22051
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Jeff MAURY
> Labels: openshift_v3, server_adapter, server_adapter_wizard
> Fix For: 4.6.x
>
>
> We currently allow the user NOT to choose a route for a server adapter. This might result in an adapter without proper host (since the host is derived from the route). In 4.3.1 we worked around it by always using the 1st available route as host, even though we possibly prompt the user and let it choose the route when he does Show In > Browser.
> According to [~rob.stryker] WTP adapters are designed to sit on a proper host. We should follow this pattern and use available WTP API to still allow the user to use different routes with an adapter.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25224) OpenShift maven build fails on Windows - EGit tests failures
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25224?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25224:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> 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.6.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)
7 years, 11 months
[JBoss JIRA] (JBIDE-18131) Split the org.jboss.tools.common.validation plugin in 'core' + 'ui'
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18131?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-18131:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Split the org.jboss.tools.common.validation plugin in 'core' + 'ui'
> -------------------------------------------------------------------
>
> Key: JBIDE-18131
> URL: https://issues.jboss.org/browse/JBIDE-18131
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: common
> Affects Versions: 4.2.0.Beta3
> Reporter: Xavier Coulon
> Assignee: Jeff MAURY
> Fix For: 4.6.x
>
>
> IMHO, it would make sense to split the {{org.jboss.tools.common.validation}} plugin in two separate ones: {{core}} + {{ui}}:
> - the {{core}} part would deal with performing the validation (based on the WST Validation Framework)
> - the {{ui}} part would deal for the preference pages and configuration.
> ATM, the CDI validation is performed in the {{org.jboss.tools.cdi.core}} plugin, but this drags a log of _.ui_ dependencies, which is somehow wrong.
> OTOH, the JAX-RS validation is performed in the {{org.jboss.tools.ws.jaxrs.ui}} plugin to avoid having _*.ui_ dependencies in the {{org.jboss.tools.ws.jaxrs.core}} plugin, but this is somehow wrong, too (I had to move the {{marker}} declaration in the {{org.jboss.tools.ws.jaxrs.core}} plugin to be able to remove all markers when the JAX-RS support is removed from a project, whatever the way it is removed (nature, facet, etc.)
> Can we discuss about that change for JBoss Tools 4.3 ?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months