[JBoss JIRA] (JBDS-3200) Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3200?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3200:
-----------------------------
Component/s: build
> Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning
> --------------------------------------------------------------------------------------------
>
> Key: JBDS-3200
> URL: https://issues.jboss.org/browse/JBDS-3200
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 8.0.0.GA
> Environment: Mac OS X 10.10, JDK 1.8.0
> Reporter: Manuel Blechschmidt
> Assignee: Max Rydahl Andersen
> Priority: Minor
> Attachments: Screen Shot 2014-10-26 at 11.10.30.png, Screen Shot 2014-10-26 at 11.11.53.png
>
>
> Hello,
> I just downloaded the new installer for JBoss Developer Studio 8.0.0.GA from here:
> https://access.cdn.redhat.com/content/origin/files/sha256/9f/9f3fab096014...
> Download was very fast. Afterwards I double clicked on the installer. Unfortunately it showed me a message that I can only install applications from the mac app store.
> {panel}
> "jboss-devstudio-8.0.0.GA-v20141020-1042-B317-installer-eap.jar" can't be opened because it is from an unidentified developer.
> Your security preferences allow installation of only app from the Mac App Store and identified developers.
> {panel}
> Right click on the file and then selecting open gives me the opportunity to ignore this warning.
> Nevertheless it might happen that users don't know this solution.
> Hope that helps
> Manuel
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBDS-3200) Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3200?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3200:
-----------------------------
Assignee: Max Rydahl Andersen
> Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning
> --------------------------------------------------------------------------------------------
>
> Key: JBDS-3200
> URL: https://issues.jboss.org/browse/JBDS-3200
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Environment: Mac OS X 10.10, JDK 1.8.0
> Reporter: Manuel Blechschmidt
> Assignee: Max Rydahl Andersen
> Priority: Minor
> Attachments: Screen Shot 2014-10-26 at 11.10.30.png, Screen Shot 2014-10-26 at 11.11.53.png
>
>
> Hello,
> I just downloaded the new installer for JBoss Developer Studio 8.0.0.GA from here:
> https://access.cdn.redhat.com/content/origin/files/sha256/9f/9f3fab096014...
> Download was very fast. Afterwards I double clicked on the installer. Unfortunately it showed me a message that I can only install applications from the mac app store.
> {panel}
> "jboss-devstudio-8.0.0.GA-v20141020-1042-B317-installer-eap.jar" can't be opened because it is from an unidentified developer.
> Your security preferences allow installation of only app from the Mac App Store and identified developers.
> {panel}
> Right click on the file and then selecting open gives me the opportunity to ignore this warning.
> Nevertheless it might happen that users don't know this solution.
> Hope that helps
> Manuel
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBTIS-349) Installing JBDSIS 8.0.alpha2 from external site fails - this is successful from internal test site
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-349?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky edited comment on JBTIS-349 at 10/27/14 11:56 AM:
--------------------------------------------------------------------
Moreover, why the zip files differ between internal (248M) and external (165M) site?
I supposed that both update sites are identical (both are labeled as Alpha2)
was (Author: apodhrad):
Moreover, why the zip files differ between internal (248M) and external (165M) site?
> Installing JBDSIS 8.0.alpha2 from external site fails - this is successful from internal test site
> --------------------------------------------------------------------------------------------------
>
> Key: JBTIS-349
> URL: https://issues.jboss.org/browse/JBTIS-349
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 4.2.0.Alpha2
> Reporter: Len DiMaggio
> Assignee: Paul Leacu
> Priority: Blocker
> Fix For: 4.2.0.Beta1
>
>
> Installing the JDV tooling from the internal site -
> http://download.englab.brq.redhat.com/pub/rhel/jbossqa/services/http/bina... - is successful
> Installing from the external site - https://devstudio.redhat.com/updates/8.0-development/integration-stack/ - fails with this error:
> Cannot complete the install because one or more required items could not be found.
> Software being installed: Teiid Designer Runtime 8.6.1.Alpha1-v20140918-1404-B186 (org.teiid.designer.runtime.feature.feature.group 8.6.1.Alpha1-v20140918-1404-B186)
> Missing requirement: org.teiid.datatools.connectivity.ui 8.6.1.Alpha1-v20140918-1404-B186 (org.teiid.datatools.connectivity.ui 8.6.1.Alpha1-v20140918-1404-B186) requires 'bundle org.eclipse.birt.report.data.oda.hive.ui [4.3.2,5.0.0)' but it could not be found
> Cannot satisfy dependency:
> From: DQP Ui Plug-in 8.6.1.Alpha1-v20140918-1404-B186 (org.teiid.designer.dqp.ui 8.6.1.Alpha1-v20140918-1404-B186)
> To: bundle org.teiid.datatools.connectivity.ui [8.1.0,9.0.0)
> Cannot satisfy dependency:
> From: Teiid Designer Runtime 8.6.1.Alpha1-v20140918-1404-B186 (org.teiid.designer.runtime.feature.feature.group 8.6.1.Alpha1-v20140918-1404-B186)
> To: org.teiid.designer.dqp.ui [8.1.0,9.0.0)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBTIS-349) Installing JBDSIS 8.0.alpha2 from external site fails - this is successful from internal test site
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-349?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky commented on JBTIS-349:
-----------------------------------------
Moreover, why the zip files differ between internal (248M) and external (165M) site?
> Installing JBDSIS 8.0.alpha2 from external site fails - this is successful from internal test site
> --------------------------------------------------------------------------------------------------
>
> Key: JBTIS-349
> URL: https://issues.jboss.org/browse/JBTIS-349
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 4.2.0.Alpha2
> Reporter: Len DiMaggio
> Assignee: Paul Leacu
> Priority: Blocker
> Fix For: 4.2.0.Beta1
>
>
> Installing the JDV tooling from the internal site -
> http://download.englab.brq.redhat.com/pub/rhel/jbossqa/services/http/bina... - is successful
> Installing from the external site - https://devstudio.redhat.com/updates/8.0-development/integration-stack/ - fails with this error:
> Cannot complete the install because one or more required items could not be found.
> Software being installed: Teiid Designer Runtime 8.6.1.Alpha1-v20140918-1404-B186 (org.teiid.designer.runtime.feature.feature.group 8.6.1.Alpha1-v20140918-1404-B186)
> Missing requirement: org.teiid.datatools.connectivity.ui 8.6.1.Alpha1-v20140918-1404-B186 (org.teiid.datatools.connectivity.ui 8.6.1.Alpha1-v20140918-1404-B186) requires 'bundle org.eclipse.birt.report.data.oda.hive.ui [4.3.2,5.0.0)' but it could not be found
> Cannot satisfy dependency:
> From: DQP Ui Plug-in 8.6.1.Alpha1-v20140918-1404-B186 (org.teiid.designer.dqp.ui 8.6.1.Alpha1-v20140918-1404-B186)
> To: bundle org.teiid.datatools.connectivity.ui [8.1.0,9.0.0)
> Cannot satisfy dependency:
> From: Teiid Designer Runtime 8.6.1.Alpha1-v20140918-1404-B186 (org.teiid.designer.runtime.feature.feature.group 8.6.1.Alpha1-v20140918-1404-B186)
> To: org.teiid.designer.dqp.ui [8.1.0,9.0.0)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBTIS-349) Installing JBDSIS 8.0.alpha2 from external site fails - this is successful from internal test site
by Len DiMaggio (JIRA)
Len DiMaggio created JBTIS-349:
----------------------------------
Summary: Installing JBDSIS 8.0.alpha2 from external site fails - this is successful from internal test site
Key: JBTIS-349
URL: https://issues.jboss.org/browse/JBTIS-349
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: distribution
Affects Versions: 4.2.0.Alpha2
Reporter: Len DiMaggio
Assignee: Paul Leacu
Priority: Blocker
Fix For: 4.2.0.Beta1
Installing the JDV tooling from the internal site -
http://download.englab.brq.redhat.com/pub/rhel/jbossqa/services/http/bina... - is successful
Installing from the external site - https://devstudio.redhat.com/updates/8.0-development/integration-stack/ - fails with this error:
Cannot complete the install because one or more required items could not be found.
Software being installed: Teiid Designer Runtime 8.6.1.Alpha1-v20140918-1404-B186 (org.teiid.designer.runtime.feature.feature.group 8.6.1.Alpha1-v20140918-1404-B186)
Missing requirement: org.teiid.datatools.connectivity.ui 8.6.1.Alpha1-v20140918-1404-B186 (org.teiid.datatools.connectivity.ui 8.6.1.Alpha1-v20140918-1404-B186) requires 'bundle org.eclipse.birt.report.data.oda.hive.ui [4.3.2,5.0.0)' but it could not be found
Cannot satisfy dependency:
From: DQP Ui Plug-in 8.6.1.Alpha1-v20140918-1404-B186 (org.teiid.designer.dqp.ui 8.6.1.Alpha1-v20140918-1404-B186)
To: bundle org.teiid.datatools.connectivity.ui [8.1.0,9.0.0)
Cannot satisfy dependency:
From: Teiid Designer Runtime 8.6.1.Alpha1-v20140918-1404-B186 (org.teiid.designer.runtime.feature.feature.group 8.6.1.Alpha1-v20140918-1404-B186)
To: org.teiid.designer.dqp.ui [8.1.0,9.0.0)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-18699) Angular.js is present in both supported and Early Access
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18699?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18699:
---------------------------------------------
Each connector does not map 1-to-1 to eclipse features, a connector covers 1 to many related to what the connector is about.
Thus AngularJS is present in both since we provide angularjs ionic palette tooling and then in early access we add in eclipse angularjs in addition.
This is there so when you as a user go and install angularjs you do not need to have to know which exact features are there related to angularjs.
> Angular.js is present in both supported and Early Access
> --------------------------------------------------------
>
> Key: JBIDE-18699
> URL: https://issues.jboss.org/browse/JBIDE-18699
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.Final
> Environment: JBDS 8.0.0.GA
> Reporter: Karel Piwko
> Assignee: Max Rydahl Andersen
> Attachments: early-access.png, no-early-access.png
>
>
> If I click on enable early access in JBoss Central page Software/Update tab, Angular JS is in Early access.
> However, it is in supported as well. I guess only Arquillian should pop up in early access.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-18706) NPE wrt JPA when creating a new Java EE7/Maven project
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18706?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-18706:
---------------------------------------
[~fbricon], I agree with you, I didn't get it the second time I created a project with the same settings.
> NPE wrt JPA when creating a new Java EE7/Maven project
> ------------------------------------------------------
>
> Key: JBIDE-18706
> URL: https://issues.jboss.org/browse/JBIDE-18706
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate, maven
> Affects Versions: 4.2.0.Final
> Reporter: Xavier Coulon
>
> I got the following error when creating a new Maven project using the 'wildfly-javaee7-blank-archetype' archetype:
> {code}
> java.lang.NullPointerException
> at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetInstallDelegate.defaultResourceLocation(JpaFacetInstallDelegate.java:123)
> at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetInstallDelegate.createPersistenceXml(JpaFacetInstallDelegate.java:107)
> at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetInstallDelegate.createProjectXml(JpaFacetInstallDelegate.java:100)
> at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetInstallDelegate.execute_(JpaFacetInstallDelegate.java:61)
> at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetActionDelegate.execute(JpaFacetActionDelegate.java:35)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.callDelegate(FacetedProject.java:1477)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:441)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChangesInternal(FacetedProject.java:1181)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:1117)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$1.run(FacetedProject.java:324)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:339)
> at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.configureFacets(JpaProjectConfigurator.java:154)
> at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.configure(JpaProjectConfigurator.java:109)
> at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:120)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:477)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:470)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProjects(ProjectConfigurationManager.java:250)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:163)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:109)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:96)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1348)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:133)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.createArchetypeProjects0(ProjectConfigurationManager.java:789)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$5.call(ProjectConfigurationManager.java:719)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$5.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:96)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1348)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.createArchetypeProjects(ProjectConfigurationManager.java:717)
> at org.eclipse.m2e.core.ui.internal.wizards.MavenProjectWizard$5.doCreateMavenProjects(MavenProjectWizard.java:244)
> at org.eclipse.m2e.core.ui.internal.wizards.AbstactCreateMavenProjectJob$1.doCreateMavenProjects(AbstactCreateMavenProjectJob.java:46)
> at org.eclipse.m2e.core.ui.internal.wizards.AbstractCreateMavenProjectsOperation.run(AbstractCreateMavenProjectsOperation.java:62)
> at org.eclipse.m2e.core.ui.internal.wizards.AbstactCreateMavenProjectJob.runInWorkspace(AbstactCreateMavenProjectJob.java:50)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months