[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)
9 years, 11 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)
9 years, 11 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)
9 years, 11 months
[JBoss JIRA] (JBIDE-18710) Invalid generated code in JAX-RS Endpoint
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-18710:
-------------------------------------
Summary: Invalid generated code in JAX-RS Endpoint
Key: JBIDE-18710
URL: https://issues.jboss.org/browse/JBIDE-18710
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: webservices
Affects Versions: 4.2.0.Final
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 4.2.1.Final, 4.3.0.Alpha1
The generated code in the 'create' method contains something like this:
{code}
return Response.created(
UriBuilder.fromResource(Session.class)
.path(String.valueOf(session.getId())).build()).build();
{code}
but the {{Session.class}} should be {{SessionEndpoint.class}} since it must be the resource class annotated with {{@Path}}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 11 months
[JBoss JIRA] (JBIDE-18706) NPE wrt JPA when creating a new Java EE7/Maven project
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18706?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-18706:
-------------------------------------
Randomly occurring error. Must be a race condition :-/
> 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)
9 years, 11 months
[JBoss JIRA] (JBIDE-16593) JBDS6 sets lower default memory settings for SOA server start than are defined in SOA run.conf
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16593?page=com.atlassian.jira.plugi... ]
Andrej Podhradsky commented on JBIDE-16593:
-------------------------------------------
JBDS 8 still supports SOA-P 5.x (the last one is SOA-P 5.3.1.GA) where the recommended memory settings (and also specified in run.conf) are
-Xms1303m -Xmx1303m -XX:MaxPermSize=256m
but JBDS 8 sets by default lower memory settings which means that customer needs to set the settings manually.
Note that this is not a problem of SOA-P 6 (now called FSW).
> JBDS6 sets lower default memory settings for SOA server start than are defined in SOA run.conf
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-16593
> URL: https://issues.jboss.org/browse/JBIDE-16593
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Environment: Version: 5.0.2.GA
> Build id: v20130119-0035-H249-GA
> Build date: 20130119-0035
> http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.3.GA.soa-to...
> Reporter: Len DiMaggio
> Assignee: Rob Stryker
> Fix For: 4.2.x
>
>
> JBDS6:
> "-Dprogram.name=JBossTools: JBoss SOA 531_ER4 Runtime"
> -server -Xms256m -Xmx768m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true
> -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 "-Djava.endorsed.dirs=/jboss/local/SOA_servers/531_ER4/jboss-soa-p-5/jboss-as/lib/endorsed"
> SOA 5.3.1 run.conf:
> if [ "x$JAVA_OPTS" = "x" ]; then
> JAVA_OPTS="-Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Djava.awt.headless=true -Dorg.apache.xml.dtm.DTMManager=org.apache.xml.dtm.ref.DTMManagerDefault -Dorg.jboss.net.protocol.file.useURI=false -Dorg.jboss.resolver.warning
> =true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dsun.lang.ClassLoader.allowArraySyntax=true"
> fi
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 11 months
[JBoss JIRA] (JBIDE-18523) [JBDS 7.1.1] org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18523?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-18523:
--------------------------------
Affects Version/s: 4.1.2.Final
(was: 4.2.0.CR1)
> [JBDS 7.1.1] org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-18523
> URL: https://issues.jboss.org/browse/JBIDE-18523
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.2.Final
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.1.3.Final
>
>
> When working through JBIDE-16066 for the web services wizard, I discovered that EAP_61 is not included in the array provided by the ALL_JBOSS_RUNTIMES list in org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants. I can work around this on the WS side, but I would imagine that this has a broader impact to other tooling projects using the runtime framework
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 11 months
[JBoss JIRA] (JBIDE-18523) [JBDS 7.1.1] org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18523?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-18523:
--------------------------------
Fix Version/s: 4.1.3.Final
> [JBDS 7.1.1] org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-18523
> URL: https://issues.jboss.org/browse/JBIDE-18523
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.1.3.Final
>
>
> When working through JBIDE-16066 for the web services wizard, I discovered that EAP_61 is not included in the array provided by the ALL_JBOSS_RUNTIMES list in org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants. I can work around this on the WS side, but I would imagine that this has a broader impact to other tooling projects using the runtime framework
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 11 months