[JBoss JIRA] (JBIDE-22721) FileNotFoundException below ArquillianSearchEngine.getTypeBinding (thrown in FileInputStream.open0)
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22721?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-22721:
----------------------------------
Fix Version/s: 4.4.2.AM2
(was: 4.4.2.AM1)
> FileNotFoundException below ArquillianSearchEngine.getTypeBinding (thrown in FileInputStream.open0)
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22721
> URL: https://issues.jboss.org/browse/JBIDE-22721
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: arquillian
> Affects Versions: 4.4.0.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Snjezana Peco
> Fix For: 4.4.2.AM2
>
>
> The following problem was reported via the automated error reporting:
> Message: File not found: '/jms-common/src/main/java/uk/co/defra/proposal/entity/ProposedHedge.java'
> {noformat}
> java.io.FileNotFoundException: D:\Users\golukoju\workspace\fa2jms-solution\jms-common\src\main\java\uk\co\defra\proposal\entity\ProposedHedge.java (The system cannot find the file specified)
> at java.io.FileInputStream.open0(null:-2)
> at java.io.FileInputStream.open(null:-1)
> at java.io.FileInputStream.<init>(null:-1)
> at org.eclipse.core.internal.filesystem.local.LocalFile.openInputStream(LocalFile.java:382)
> at org.eclipse.core.internal.localstore.FileSystemResourceManager.read(FileSystemResourceManager.java:834)
> at org.eclipse.core.internal.resources.File.getContents(File.java:269)
> at org.eclipse.jdt.internal.core.util.Util.getResourceContentsAsCharArray(Util.java:1190)
> at org.eclipse.jdt.internal.core.CompilationUnit.getContents(CompilationUnit.java:652)
> at org.eclipse.jdt.core.dom.ASTParser.internalCreateAST(ASTParser.java:1125)
> at org.eclipse.jdt.core.dom.ASTParser.createAST(ASTParser.java:812)
> at org.jboss.tools.arquillian.core.internal.util.ArquillianSearchEngine.getTypeBinding(ArquillianSearchEngine.java:311)
> at org.jboss.tools.arquillian.core.internal.util.ArquillianSearchEngine.isArquillianJUnitTest(ArquillianSearchEngine.java:284)
> at org.jboss.tools.arquillian.core.internal.util.ArquillianSearchEngine.isArquillianJUnitTest(ArquillianSearchEngine.java:236)
> at org.jboss.tools.arquillian.core.internal.util.ArquillianSearchEngine.isArquillianJUnitTest(ArquillianSearchEngine.java:208)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder$1.visit(ArquillianBuilder.java:177)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:63)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:74)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:74)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:74)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:74)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:74)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:74)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:74)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:74)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:47)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.buildDelta(ArquillianBuilder.java:128)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.build(ArquillianBuilder.java:112)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> Bundles:
> | org.eclipse.core.filesystem | 1.5.0.v20150725-1910 | 1.5.0.v20150725-1910 |
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.7.0.v20150330-2103 |
> | org.eclipse.core.resources | 3.10.1.v20150725-1910 | 3.10.1.v20150725-1910 |
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 |
> | org.eclipse.jdt.core | 3.11.2.v20160128-0629 | 3.11.2.v20160128-0629 |
> | org.jboss.tools.arquillian.core | 1.2.1.Final-v20160331-0142-B69 | 1.2.1.Final-v20160331-0142-B69 |
> Operating Systems:
> | Windows | 6.1.0 | 6.1.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5742ea03e4b0138d62...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-3867) CDK file name should include version, match file name on RHCP
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3867?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3867:
--------------------------------
Fix Version/s: 10.2.0.AM2
(was: 10.2.0.AM1)
> CDK file name should include version, match file name on RHCP
> -------------------------------------------------------------
>
> Key: JBDS-3867
> URL: https://issues.jboss.org/browse/JBDS-3867
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.Beta1
> Environment: Windows 7/64 bit
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 10.2.0.AM2
>
>
> The platform installer uses a file name for the CDK box with no version information making it difficult to tell if you have the latest CDK box or not.
> The downloaded box file is saved in \cdk\boxes\rhel-vagrant-virtualbox.box.
> It should use the same file name as the Red Hat Customer Portal to make it easy to identify that it is the same file: rhel-cdk-kubernetes-7.2-23.x86_64.vagrant-virtualbox.box
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-3865) Platform installer should warn about known bad versions of Vagrant.
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3865?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3865:
--------------------------------
Fix Version/s: 10.2.0.AM2
(was: 10.2.0.AM1)
> Platform installer should warn about known bad versions of Vagrant.
> -------------------------------------------------------------------
>
> Key: JBDS-3865
> URL: https://issues.jboss.org/browse/JBDS-3865
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.Beta1
> Environment: Windows 7/64 bit.
> Vagrant 1.8.1 installed
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 10.2.0.AM2
>
>
> The platform installer should flag versions of Vagrant (and possibly other software) that are known to be bad. There should possibly be a black list.
> Vagrant 1.8.0 and 1.8.1 have a bunch of bugs, so they aren't recommended for CDK.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-22720) ResourceException below ArquillianProjectConfigurator.configureInternal (thrown in Project.checkAccessible)
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22720?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-22720:
----------------------------------
Fix Version/s: 4.4.2.AM2
(was: 4.4.2.AM1)
> ResourceException below ArquillianProjectConfigurator.configureInternal (thrown in Project.checkAccessible)
> -----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22720
> URL: https://issues.jboss.org/browse/JBIDE-22720
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: arquillian
> Affects Versions: 4.4.0.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Snjezana Peco
> Fix For: 4.4.2.AM2
>
>
> The following problem was reported via the automated error reporting:
> Message: Resource '/Roentgen-import-service' is not open.
> {noformat}
> org.eclipse.core.internal.resources.ResourceException: Resource '/Roentgen-import-service' is not open.
> at org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:144)
> at org.eclipse.core.internal.resources.Project.hasNature(Project.java:516)
> at org.jboss.tools.arquillian.maven.configurator.ArquillianProjectConfigurator.configureInternal(ArquillianProjectConfigurator.java:43)
> at org.jboss.tools.arquillian.maven.configurator.ArquillianProjectConfigurator.mavenProjectChanged(ArquillianProjectConfigurator.java:72)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.mavenProjectChanged(ProjectConfigurationManager.java:1000)
> at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.notifyProjectChangeListeners(ProjectRegistryManager.java:783)
> at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.applyMutableProjectRegistry(ProjectRegistryManager.java:930)
> at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryRefreshJob$1.call(ProjectRegistryRefreshJob.java:98)
> at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryRefreshJob$1.call(ProjectRegistryRefreshJob.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1355)
> at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryRefreshJob.run(ProjectRegistryRefreshJob.java:81)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160319-0610 |
> | org.eclipse.core.resources | 3.10.1.v20150725-1910 | 3.11.0.v20160422-0304 |
> | org.eclipse.m2e.core | 1.6.3.20160209-1446 | 1.7.0.20160504-0322 |
> | org.jboss.tools.arquillian.maven.configurator | 1.2.1.Final-v20160331-0142-B69 | 1.2.1.Final-v20160331-0142-B69 |
> Operating Systems:
> | MacOSX | 10.11.5 | 10.11.5 |
> | Windows | 6.1.0 | 6.3.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5742c4fae4b0138d62...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-3871) installer credentials misleading/incomplete information.
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3871?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3871:
--------------------------------
Fix Version/s: 10.2.0.AM2
(was: 10.2.0.AM1)
> installer credentials misleading/incomplete information.
> --------------------------------------------------------
>
> Key: JBDS-3871
> URL: https://issues.jboss.org/browse/JBDS-3871
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.Beta1
> Environment: Win 7/64 bit
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Priority: Minor
> Labels: ui
> Fix For: 10.2.0.AM2
>
>
> There are several problems a with the information on the platform installer's login screen:
> # "Your developers.redhat.com credentials" is misleading, Should probably be "Your Red Hat username" to be consistent with RHDeveloper registration process.
> # The register link points to the login page, not the register page.
> # Registering on RHDevelopers isn't sufficient. (A registered user gets " Terms and Conditions for CDK have not been signed."
> # There should probably be a link to a page on RHDev with more info/FAQ about credentials, the registration process, and obtaining a (no-cost) subscription.
> The platform installer description of the credentials to use are misleading. Currently it says " Try it now by providing your developers.redhat.com credentials to get access."
> Users can log into RHDevelopers via other accounts (github, linkedin, stack overflow, etc. using OAUTH). They can not log into access.redhat.com (the customer portal) or other Red Hat sites with their developer.redhat.com "credentials".
> During registration on RHDevelopers, a simple developers account is created. (Note: At this point, a Red Hat username hasn't been created yet.
> Currently, when the user clicks a download link that goes through RHDev download manager, their account is "upgraded", which creates a Red Hat user than can be used to log into RHCP. Terms & conditions are presented. A no-cost RHEL Developer suite subscription is added to the user's Red Hat account.
> Their Red Hat username and password which could be different from the RHDeveloper credentials. They will need their Red Hat username for the CDK box to attach to their subscription. Without it the CDK box won't start up correctly as it can't download software.
> Some of this is covered for external users in the No-cost RHEL Dev. Suite FAQ. http://developers.redhat.com/articles/no-cost-rhel-faq/ We might need to do a version of that for CDK and JBDS platform installer..
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-3871) installer credentials misleading/incomplete information.
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3871?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3871:
--------------------------------
Labels: ui (was: )
> installer credentials misleading/incomplete information.
> --------------------------------------------------------
>
> Key: JBDS-3871
> URL: https://issues.jboss.org/browse/JBDS-3871
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.Beta1
> Environment: Win 7/64 bit
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Priority: Minor
> Labels: ui
> Fix For: 10.2.0.AM2
>
>
> There are several problems a with the information on the platform installer's login screen:
> # "Your developers.redhat.com credentials" is misleading, Should probably be "Your Red Hat username" to be consistent with RHDeveloper registration process.
> # The register link points to the login page, not the register page.
> # Registering on RHDevelopers isn't sufficient. (A registered user gets " Terms and Conditions for CDK have not been signed."
> # There should probably be a link to a page on RHDev with more info/FAQ about credentials, the registration process, and obtaining a (no-cost) subscription.
> The platform installer description of the credentials to use are misleading. Currently it says " Try it now by providing your developers.redhat.com credentials to get access."
> Users can log into RHDevelopers via other accounts (github, linkedin, stack overflow, etc. using OAUTH). They can not log into access.redhat.com (the customer portal) or other Red Hat sites with their developer.redhat.com "credentials".
> During registration on RHDevelopers, a simple developers account is created. (Note: At this point, a Red Hat username hasn't been created yet.
> Currently, when the user clicks a download link that goes through RHDev download manager, their account is "upgraded", which creates a Red Hat user than can be used to log into RHCP. Terms & conditions are presented. A no-cost RHEL Developer suite subscription is added to the user's Red Hat account.
> Their Red Hat username and password which could be different from the RHDeveloper credentials. They will need their Red Hat username for the CDK box to attach to their subscription. Without it the CDK box won't start up correctly as it can't download software.
> Some of this is covered for external users in the No-cost RHEL Dev. Suite FAQ. http://developers.redhat.com/articles/no-cost-rhel-faq/ We might need to do a version of that for CDK and JBDS platform installer..
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-3868) Document (and check) required disk space before beginning install
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3868?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3868:
--------------------------------
Labels: ui (was: )
> Document (and check) required disk space before beginning install
> -----------------------------------------------------------------
>
> Key: JBDS-3868
> URL: https://issues.jboss.org/browse/JBDS-3868
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.Beta1
> Environment: Windows 7/64 bit
> Reporter: Robert Terzi
> Priority: Minor
> Labels: ui
> Fix For: 10.2.0.AM2
>
>
> The installer and it's documentation should indicate the minimum required disk space before beginning the download and installation process.
> Between temporary files, and download/installs going on in parallel. I'm guessing at least 10-15 GB free is needed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-3868) Document (and check) required disk space before beginning install
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3868?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3868:
--------------------------------
Fix Version/s: 10.2.0.AM2
(was: 10.2.0.AM1)
> Document (and check) required disk space before beginning install
> -----------------------------------------------------------------
>
> Key: JBDS-3868
> URL: https://issues.jboss.org/browse/JBDS-3868
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.Beta1
> Environment: Windows 7/64 bit
> Reporter: Robert Terzi
> Priority: Minor
> Labels: ui
> Fix For: 10.2.0.AM2
>
>
> The installer and it's documentation should indicate the minimum required disk space before beginning the download and installation process.
> Between temporary files, and download/installs going on in parallel. I'm guessing at least 10-15 GB free is needed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-3914) Build zip distribution for Mac OS X and Linux
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3914?page=com.atlassian.jira.plugin.... ]
Denis Golovin closed JBDS-3914.
-------------------------------
Resolution: Won't Fix
This issue is not relevant anmore, because we are going to create MAc OS X installer for this release train.
> Build zip distribution for Mac OS X and Linux
> ---------------------------------------------
>
> Key: JBDS-3914
> URL: https://issues.jboss.org/browse/JBDS-3914
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 10.0.0.GA
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 10.2.0.AM2
>
> Attachments: zip in exe fails.png
>
>
> We need to check if self extracting 7zip understands zip format and instead of creating .7z archive use zip archve for bundled installer. that would let us release the same zip as Linux and Mac OS X distribution. The only change is creating readme.md in the archive root with link to installation guide (see trelo card for details).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months