[JBoss JIRA] (JBIDE-21025) hibernate querying nor content assist is broken
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21025?page=com.atlassian.jira.plugi... ]
Jiri Peterka updated JBIDE-21025:
---------------------------------
Priority: Critical (was: Blocker)
Lower to critical as query execution works for me when project is properly configured. However there might be some scenario when it doesn't work (more details are needed though). Code completion is also partial bug and not feature blocker IMHO.
> hibernate querying nor content assist is broken
> -----------------------------------------------
>
> Key: JBIDE-21025
> URL: https://issues.jboss.org/browse/JBIDE-21025
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Reporter: Max Rydahl Andersen
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> using html5-kitchensink I cannot get basic content assist to work.
> "from Member m where m.|" gives no content assist at all.
> And trying to run the query results in:
> {code}
> java.lang.NullPointerException
> at org.hibernate.cfg.Configuration.buildTypeRegistrations(Configuration.java:1888)
> at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1845)
> at org.jboss.tools.hibernate.runtime.v_4_3.internal.ConfigurationFacadeImpl.buildTargetSessionFactory(ConfigurationFacadeImpl.java:24)
> at org.jboss.tools.hibernate.runtime.common.AbstractConfigurationFacade.buildSessionFactory(AbstractConfigurationFacade.java:169)
> at org.hibernate.console.ConsoleConfiguration$5.execute(ConsoleConfiguration.java:285)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108)
> at org.hibernate.console.ConsoleConfiguration.buildSessionFactory(ConsoleConfiguration.java:280)
> at org.hibernate.eclipse.console.actions.ExecuteQueryAction.execute(ExecuteQueryAction.java:81)
> at org.hibernate.eclipse.console.actions.ExecuteQueryAction.run(ExecuteQueryAction.java:55)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
> at org.hibernate.eclipse.console.actions.ExecuteQueryAction.runWithEvent(ExecuteQueryAction.java:59)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:462)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBTIS-531) Bouncy Castle causes Fuse Tooling full source TP build failure.
by Lars Heinemann (JIRA)
[ https://issues.jboss.org/browse/JBTIS-531?page=com.atlassian.jira.plugin.... ]
Lars Heinemann edited comment on JBTIS-531 at 11/4/15 9:07 AM:
---------------------------------------------------------------
Yep, moving it out of Teiid sounds like the way to go. Locus sounds fine.
was (Author: lhein):
Yep, moving it out of Teeid sounds like the way to go. Locus sounds fine.
> Bouncy Castle causes Fuse Tooling full source TP build failure.
> ---------------------------------------------------------------
>
> Key: JBTIS-531
> URL: https://issues.jboss.org/browse/JBTIS-531
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 9.0.0.Alpha2, 8.0.4.CR2
> Reporter: Paul Leacu
>
> Here is the issue. The JBTIS TP has a reliance on bouncycastle that was introduced as an indirect dependency by Teiid Designer because they needed the Apache directory features including the org.apache.directory.studio.connection.ui feature. The bcprov feature was removed from the JBTIS TP and Teiid Designer added a dummy feature to satisfy maven. This was built and everything in the IS builds and installs fine - no one directly needed bouncycastle.
> Fuse Tooling builds a local development-only full source target platform based on the JBTIS TP. This causes all dependencies to be fully resolved which causes them to fail their target platform development-only build:
> {code}
> mvn -Pmultiple2repo -U -Dmirror-target-to-repo.includeSources=true clean install
> ...
> [ERROR] Software being installed: org.apache.directory.studio.connection.ui 2.0.0.v20150618
> [ERROR] Missing requirement: org.apache.directory.studio.connection.ui 2.0.0.v20150618 requires 'package org.bouncycastle.x509.extension 0.0.0' but it could not be found
> {code}
> you may also see this error:
> {code}
> [ERROR] Software being installed: org.apache.directory.studio.connection.ui 2.0.0.v20150618
> [ERROR] Missing requirement: org.apache.directory.studio.connection.ui 2.0.0.v20150618 requires 'package org.bouncycastle.asn1 0.0.0' but it could not be found
> {code}
> Both of these plugins can be found (in stub form) here:
> http://download.jboss.org/jbosstools/updates/stable/luna/integration-stac...
> How should this be fixed? Both Teiid Designer and Fuse Tooling use the JBTIS TP. Fuse needs this development TP to debug Fuse and SAP issues. They shouldn't have to incur a dependency that has nothing to do with them. If we pull the entire Apache directory dependency block out of the IS TP then Teiid Des will have to go back to creating their own merged TP.
> WDYT?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-20600) document how to use Deploy to OpenShift (Docker integration)
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20600?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-20600.
---------------------------------
Verified.
> document how to use Deploy to OpenShift (Docker integration)
> ------------------------------------------------------------
>
> Key: JBIDE-20600
> URL: https://issues.jboss.org/browse/JBIDE-20600
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Max Rydahl Andersen
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 4.3.0.Final
>
>
> Trying to use the Deploy to OpenShift dialog I found a few issues and i'm a bit stuck figuring out how it works.
> What I did was trying to just take jboss/wildfly:latest and deploy to openshift.
> First off, the first page of Deploy to openshift wont let me create a connection or project so I have as a user to have done that *before* starting the dialog.
> Once I have done that the dialog is asking for a lot of questions but very little hints about what they are.
> One example is "Add Route" on services ports page - that page can have multiple services so which does "Add Route" refer to and should it not need to know which port needed to use ?
> But worst issue is that once all that is filled out then I do not seem to be able to get any logs or info on why wildfly is not started.
> neither in webconsole nor in eclipse views.
> Should there not be access to some console logs or similar to things created by a project ?
> anyway - long description to point out we need some docs on how to actually use this if we cannot fix the UI before GA.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBTIS-531) Bouncy Castle causes Fuse Tooling full source TP build failure.
by Lars Heinemann (JIRA)
[ https://issues.jboss.org/browse/JBTIS-531?page=com.atlassian.jira.plugin.... ]
Lars Heinemann commented on JBTIS-531:
--------------------------------------
Yep, moving it out of Teeid sounds like the way to go. Locus sounds fine.
> Bouncy Castle causes Fuse Tooling full source TP build failure.
> ---------------------------------------------------------------
>
> Key: JBTIS-531
> URL: https://issues.jboss.org/browse/JBTIS-531
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 9.0.0.Alpha2, 8.0.4.CR2
> Reporter: Paul Leacu
>
> Here is the issue. The JBTIS TP has a reliance on bouncycastle that was introduced as an indirect dependency by Teiid Designer because they needed the Apache directory features including the org.apache.directory.studio.connection.ui feature. The bcprov feature was removed from the JBTIS TP and Teiid Designer added a dummy feature to satisfy maven. This was built and everything in the IS builds and installs fine - no one directly needed bouncycastle.
> Fuse Tooling builds a local development-only full source target platform based on the JBTIS TP. This causes all dependencies to be fully resolved which causes them to fail their target platform development-only build:
> {code}
> mvn -Pmultiple2repo -U -Dmirror-target-to-repo.includeSources=true clean install
> ...
> [ERROR] Software being installed: org.apache.directory.studio.connection.ui 2.0.0.v20150618
> [ERROR] Missing requirement: org.apache.directory.studio.connection.ui 2.0.0.v20150618 requires 'package org.bouncycastle.x509.extension 0.0.0' but it could not be found
> {code}
> you may also see this error:
> {code}
> [ERROR] Software being installed: org.apache.directory.studio.connection.ui 2.0.0.v20150618
> [ERROR] Missing requirement: org.apache.directory.studio.connection.ui 2.0.0.v20150618 requires 'package org.bouncycastle.asn1 0.0.0' but it could not be found
> {code}
> Both of these plugins can be found (in stub form) here:
> http://download.jboss.org/jbosstools/updates/stable/luna/integration-stac...
> How should this be fixed? Both Teiid Designer and Fuse Tooling use the JBTIS TP. Fuse needs this development TP to debug Fuse and SAP issues. They shouldn't have to incur a dependency that has nothing to do with them. If we pull the entire Apache directory dependency block out of the IS TP then Teiid Des will have to go back to creating their own merged TP.
> WDYT?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBTIS-531) Bouncy Castle causes Fuse Tooling full source TP build failure.
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-531?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBTIS-531:
----------------------------------
Shared 3rd party requirements should be in the shared TP, so that all parts of IS can use the same TP.
If there's something in one project's needs which CONFLICTS with another project's needs, those projects need to sort that out (eg., depending on incompatible versions of the same IU, which would prevent co-installation).
If you need a way to build the "dummy" plugin outside of the TP so that it can be consumed by the TP, then by Fuse/Teiid/others, I would suggest we move that plugin to the Locus project and build it there along with all the other stuff that the IS requires.
So, then, the process for building in the IS is:
a) find dependency in JBT, Eclipse Orbit, Eclipse Mars/Neon, another Eclipse project, etc. and mirror that onto download.jboss.org/jbosstools/updates/requirements/<upstream-project>/<version>/; or
b) create dependency in JBoss Locus, build it, and publish to JBoss Nexus; then
c) add dependency to IS TP
d) build IS project(s)
e) build IS aggregations
> Bouncy Castle causes Fuse Tooling full source TP build failure.
> ---------------------------------------------------------------
>
> Key: JBTIS-531
> URL: https://issues.jboss.org/browse/JBTIS-531
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 9.0.0.Alpha2, 8.0.4.CR2
> Reporter: Paul Leacu
>
> Here is the issue. The JBTIS TP has a reliance on bouncycastle that was introduced as an indirect dependency by Teiid Designer because they needed the Apache directory features including the org.apache.directory.studio.connection.ui feature. The bcprov feature was removed from the JBTIS TP and Teiid Designer added a dummy feature to satisfy maven. This was built and everything in the IS builds and installs fine - no one directly needed bouncycastle.
> Fuse Tooling builds a local development-only full source target platform based on the JBTIS TP. This causes all dependencies to be fully resolved which causes them to fail their target platform development-only build:
> {code}
> mvn -Pmultiple2repo -U -Dmirror-target-to-repo.includeSources=true clean install
> ...
> [ERROR] Software being installed: org.apache.directory.studio.connection.ui 2.0.0.v20150618
> [ERROR] Missing requirement: org.apache.directory.studio.connection.ui 2.0.0.v20150618 requires 'package org.bouncycastle.x509.extension 0.0.0' but it could not be found
> {code}
> you may also see this error:
> {code}
> [ERROR] Software being installed: org.apache.directory.studio.connection.ui 2.0.0.v20150618
> [ERROR] Missing requirement: org.apache.directory.studio.connection.ui 2.0.0.v20150618 requires 'package org.bouncycastle.asn1 0.0.0' but it could not be found
> {code}
> Both of these plugins can be found (in stub form) here:
> http://download.jboss.org/jbosstools/updates/stable/luna/integration-stac...
> How should this be fixed? Both Teiid Designer and Fuse Tooling use the JBTIS TP. Fuse needs this development TP to debug Fuse and SAP issues. They shouldn't have to incur a dependency that has nothing to do with them. If we pull the entire Apache directory dependency block out of the IS TP then Teiid Des will have to go back to creating their own merged TP.
> WDYT?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21051) JPA project building crashes
by Jesper Skov (JIRA)
Jesper Skov created JBIDE-21051:
-----------------------------------
Summary: JPA project building crashes
Key: JBIDE-21051
URL: https://issues.jboss.org/browse/JBIDE-21051
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Affects Versions: 4.3.0.Final
Environment: Mars SR1 (running on java8), Windows 7
Reporter: Jesper Skov
Priority: Minor
We have been using the 'generic' platform for JPA projects for a long time.
With Mars.Sr1 and latest jbosstools release, I figured I should give the Hibernate platform a chance again.
Unfortunately, it fails with the below stacktrace.
It is a in a EAP5 project (yes, I know. we have started migration to EAP6) with JPA 1.0 facet.
The project has many JPA annotated files, so I can't easily figure out which one may contain the trigger.
Can I enable logging in the hibernate plugin somehow to help pin point the file and its annotations?
{code}
!ENTRY org.eclipse.jpt.jpa.core 4 0 2015-11-04 14:36:10.235
!MESSAGE
!STACK 0
java.lang.NullPointerException
at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaPersistentAttribute.updateMapping(AbstractJavaPersistentAttribute.java:408)
at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaPersistentAttribute.update(AbstractJavaPersistentAttribute.java:109)
at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaPersistentType.syncFieldAttributes(AbstractJavaPersistentType.java:581)
at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaPersistentType.syncFieldAccessAttributes(AbstractJavaPersistentType.java:508)
at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaPersistentType.updateAttributes(AbstractJavaPersistentType.java:493)
at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaPersistentType.update(AbstractJavaPersistentType.java:101)
at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericClassRef.updateJavaManagedType(GenericClassRef.java:192)
at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericClassRef.update(GenericClassRef.java:123)
at org.jboss.tools.hibernate.jpt.core.internal.context.persistence.HibernateClassRef.update(HibernateClassRef.java:88)
at org.eclipse.jpt.jpa.core.internal.context.AbstractJpaContextModel.updateModels(AbstractJpaContextModel.java:73)
at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.update(AbstractPersistenceUnit.java:290)
at org.jboss.tools.hibernate.jpt.core.internal.context.HibernatePersistenceUnit.update(HibernatePersistenceUnit.java:94)
at org.eclipse.jpt.jpa.core.internal.context.AbstractJpaContextModel.updateModels(AbstractJpaContextModel.java:73)
at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistence.update(GenericPersistence.java:75)
at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistenceXml.syncPersistence(GenericPersistenceXml.java:140)
at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistenceXml.updatePersistence(GenericPersistenceXml.java:97)
at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistenceXml.update(GenericPersistenceXml.java:93)
at org.eclipse.jpt.jpa.core.internal.jpa1.context.GenericContextRoot.syncPersistenceXml(GenericContextRoot.java:128)
at org.eclipse.jpt.jpa.core.internal.jpa1.context.GenericContextRoot.updatePersistenceXml(GenericContextRoot.java:162)
at org.eclipse.jpt.jpa.core.internal.jpa1.context.GenericContextRoot.update(GenericContextRoot.java:78)
at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.update(AbstractJpaProject.java:1994)
at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$UpdateJobCommand.execute(AbstractJpaProject.java:1981)
at org.eclipse.jpt.common.core.internal.utility.command.RepeatingJobCommandWrapper.executeCommand(RepeatingJobCommandWrapper.java:207)
at org.eclipse.jpt.common.core.internal.utility.command.NotifyingRepeatingJobCommandWrapper.executeCommand(NotifyingRepeatingJobCommandWrapper.java:68)
at org.eclipse.jpt.common.core.internal.utility.command.RepeatingJobCommandWrapper.execute_(RepeatingJobCommandWrapper.java:192)
at org.eclipse.jpt.common.core.internal.utility.command.RepeatingJobCommandWrapper$StartJobCommand.execute(RepeatingJobCommandWrapper.java:172)
at org.eclipse.jpt.common.core.internal.utility.command.DefaultJobCommandContext.execute(DefaultJobCommandContext.java:38)
at org.eclipse.jpt.common.core.internal.utility.command.RepeatingJobCommandWrapper.executeStartCommand(RepeatingJobCommandWrapper.java:157)
at org.eclipse.jpt.common.core.internal.utility.command.RepeatingJobCommandWrapper.execute(RepeatingJobCommandWrapper.java:147)
at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.update(AbstractJpaProject.java:1973)
at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.initializeContextModel(AbstractJpaProject.java:303)
at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.<init>(AbstractJpaProject.java:264)
at org.jboss.tools.hibernate.jpt.core.internal.HibernateJpaProject.<init>(HibernateJpaProject.java:71)
at org.jboss.tools.hibernate.jpt.core.internal.HibernateAbstractJpaFactory.buildJpaProject(HibernateAbstractJpaFactory.java:107)
at org.jboss.tools.hibernate.jpt.core.internal.jpa2.HibernateJpaFactory2_0.buildJpaProject(HibernateJpaFactory2_0.java:89)
at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.buildJpaProject(InternalJpaProjectManager.java:647)
at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.buildJpaProject(InternalJpaProjectManager.java:635)
at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.buildJpaProject(InternalJpaProjectManager.java:628)
at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.addJpaProject(InternalJpaProjectManager.java:609)
at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.buildJpaProject_(InternalJpaProjectManager.java:312)
at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager$BuildJpaProjectCommand.execute(InternalJpaProjectManager.java:306)
at org.eclipse.jpt.common.core.internal.utility.command.CommandJobCommandAdapter.execute(CommandJobCommandAdapter.java:50)
at org.eclipse.jpt.common.core.internal.utility.command.JobCommandJob.run(JobCommandJob.java:42)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
!ENTRY org.eclipse.jpt.jpa.core 4 0 2015-11-04 14:36:33.814
!MESSAGE
!STACK 0
java.lang.UnsupportedOperationException
at org.jboss.tools.hibernate.jpt.core.internal.resource.java.GenericGeneratorAnnotationDefinition.buildAnnotation(GenericGeneratorAnnotationDefinition.java:51)
at org.eclipse.jpt.jpa.core.internal.JpaAnnotationProvider.buildAnnotation(JpaAnnotationProvider.java:78)
at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryAnnotatedElement.buildAnnotation(BinaryAnnotatedElement.java:236)
at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryAnnotatedElement$AnnotationContainer.addAnnotation(BinaryAnnotatedElement.java:360)
at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryAnnotatedElement$AnnotationContainer.initializeFromStandaloneAnnotation(BinaryAnnotatedElement.java:356)
at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryAnnotatedElement.addAnnotation(BinaryAnnotatedElement.java:106)
at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryAnnotatedElement.initializeAnnotations(BinaryAnnotatedElement.java:71)
at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryAnnotatedElement.<init>(BinaryAnnotatedElement.java:65)
at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryMember.<init>(BinaryMember.java:44)
at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryAttribute.<init>(BinaryAttribute.java:35)
at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryField.<init>(BinaryField.java:35)
at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryField.<init>(BinaryField.java:31)
at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryType.buildField(BinaryType.java:281)
at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryType$FieldTransformer.transform(BinaryType.java:264)
at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryType$FieldTransformer.transform(BinaryType.java:1)
at org.eclipse.jpt.common.utility.internal.iterator.TransformationIterator.next(TransformationIterator.java:54)
at org.eclipse.jpt.common.utility.internal.collection.CollectionTools.addAll_(CollectionTools.java:72)
at org.eclipse.jpt.common.utility.internal.collection.CollectionTools.addAll(CollectionTools.java:63)
at org.eclipse.jpt.common.utility.internal.collection.CollectionTools.addAll(CollectionTools.java:44)
at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryType.<init>(BinaryType.java:79)
at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryType.<init>(BinaryType.java:70)
at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryTypeCache.buildType(BinaryTypeCache.java:87)
at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryTypeCache.buildEntry(BinaryTypeCache.java:80)
at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryTypeCache.addType(BinaryTypeCache.java:73)
at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.buildBinaryExternalJavaResourceType(AbstractJpaProject.java:686)
at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.buildExternalJavaResourceType(AbstractJpaProject.java:681)
at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.buildExternalJavaResourceType(AbstractJpaProject.java:660)
at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.getJavaResourceType(AbstractJpaProject.java:904)
at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericClassRef.resolveJavaResourceType(GenericClassRef.java:207)
at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericClassRef.<init>(GenericClassRef.java:83)
at org.jboss.tools.hibernate.jpt.core.internal.context.persistence.HibernateClassRef.<init>(HibernateClassRef.java:52)
at org.jboss.tools.hibernate.jpt.core.internal.context.persistence.HibernatePersistenceXmlContextNodeFactory.buildClassRef(HibernatePersistenceXmlContextNodeFactory.java:46)
at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.buildClassRef(AbstractPersistenceUnit.java:869)
at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit$SpecifiedClassRefContainerAdapter.buildContextElement(AbstractPersistenceUnit.java:914)
at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit$SpecifiedClassRefContainerAdapter.buildContextElement(AbstractPersistenceUnit.java:1)
at org.eclipse.jpt.jpa.core.internal.context.AbstractJpaContextModel$Container.initialize(AbstractJpaContextModel.java:319)
at org.eclipse.jpt.jpa.core.internal.context.AbstractJpaContextModel$SpecifiedContextListContainer.<init>(AbstractJpaContextModel.java:732)
at org.eclipse.jpt.jpa.core.internal.context.AbstractJpaContextModel.buildSpecifiedContextListContainer(AbstractJpaContextModel.java:737)
at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.buildSpecifiedClassRefContainer(AbstractPersistenceUnit.java:904)
at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.<init>(AbstractPersistenceUnit.java:238)
at org.jboss.tools.hibernate.jpt.core.internal.context.HibernatePersistenceUnit.<init>(HibernatePersistenceUnit.java:77)
at org.jboss.tools.hibernate.jpt.core.internal.context.persistence.HibernatePersistenceXmlContextNodeFactory.buildPersistenceUnit(HibernatePersistenceXmlContextNodeFactory.java:32)
at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistence.buildPersistenceUnit(GenericPersistence.java:195)
at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistence.initializePersistenceUnits(GenericPersistence.java:153)
at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistence.<init>(GenericPersistence.java:59)
at org.jboss.tools.hibernate.jpt.core.internal.context.persistence.HibernatePersistence.<init>(HibernatePersistence.java:29)
at org.jboss.tools.hibernate.jpt.core.internal.context.persistence.HibernatePersistenceXmlContextNodeFactory.buildPersistence(HibernatePersistenceXmlContextNodeFactory.java:40)
at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistenceXml.buildRoot(GenericPersistenceXml.java:160)
at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistenceXml.<init>(GenericPersistenceXml.java:68)
at org.eclipse.jpt.jpa.core.internal.AbstractJpaFactory.buildPersistenceXml(AbstractJpaFactory.java:198)
at org.eclipse.jpt.jpa.core.internal.jpa1.context.GenericContextRoot.buildPersistenceXml(GenericContextRoot.java:158)
at org.eclipse.jpt.jpa.core.internal.jpa1.context.GenericContextRoot.buildPersistenceXml(GenericContextRoot.java:96)
at org.eclipse.jpt.jpa.core.internal.jpa1.context.GenericContextRoot.<init>(GenericContextRoot.java:63)
at org.eclipse.jpt.jpa.core.internal.AbstractJpaFactory.buildContextRoot(AbstractJpaFactory.java:191)
at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.buildContextRoot(AbstractJpaProject.java:290)
at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.<init>(AbstractJpaProject.java:261)
at org.jboss.tools.hibernate.jpt.core.internal.HibernateJpaProject.<init>(HibernateJpaProject.java:71)
at org.jboss.tools.hibernate.jpt.core.internal.HibernateAbstractJpaFactory.buildJpaProject(HibernateAbstractJpaFactory.java:107)
at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.buildJpaProject(InternalJpaProjectManager.java:647)
at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.buildJpaProject(InternalJpaProjectManager.java:635)
at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.buildJpaProject(InternalJpaProjectManager.java:628)
at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.addJpaProject(InternalJpaProjectManager.java:609)
at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.rebuildJpaProject_(InternalJpaProjectManager.java:541)
at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager$RebuildJpaProjectCommand.execute(InternalJpaProjectManager.java:529)
at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.waitToExecute(InternalJpaProjectManager.java:1097)
at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.waitToExecute(InternalJpaProjectManager.java:1076)
at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.rebuildJpaProject(InternalJpaProjectManager.java:512)
at org.eclipse.jpt.jpa.core.internal.ProjectAdapterFactory$JpaProjectReference.rebuild(ProjectAdapterFactory.java:117)
at org.eclipse.jpt.jpa.ui.internal.properties.JpaProjectPropertiesPage.rebuildProject_(JpaProjectPropertiesPage.java:869)
at org.eclipse.jpt.jpa.ui.internal.properties.JpaProjectPropertiesPage.rebuildProject(JpaProjectPropertiesPage.java:860)
at org.eclipse.jpt.common.ui.internal.properties.JptProjectPropertiesPage.performOk_(JptProjectPropertiesPage.java:339)
at org.eclipse.jpt.common.ui.internal.properties.JptProjectPropertiesPage$OkRunnableWithProgress$OkWorkspaceRunnable.run(JptProjectPropertiesPage.java:322)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241)
at org.eclipse.jpt.common.ui.internal.properties.JptProjectPropertiesPage$OkRunnableWithProgress.run(JptProjectPropertiesPage.java:302)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBTIS-531) Bouncy Castle causes Fuse Tooling full source TP build failure.
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-531?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-531:
----------------------------------
Hey Paul -
This is indeed a valid option. I'd say we should create a separate repo in o.j.t that contains just this (to avoid the IS TP from referring to a component repo). Then if another component wants to do what Fuse Tooling is doing in creating a development debug TP they could. Any opinions from the watchers??
> Bouncy Castle causes Fuse Tooling full source TP build failure.
> ---------------------------------------------------------------
>
> Key: JBTIS-531
> URL: https://issues.jboss.org/browse/JBTIS-531
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 9.0.0.Alpha2, 8.0.4.CR2
> Reporter: Paul Leacu
>
> Here is the issue. The JBTIS TP has a reliance on bouncycastle that was introduced as an indirect dependency by Teiid Designer because they needed the Apache directory features including the org.apache.directory.studio.connection.ui feature. The bcprov feature was removed from the JBTIS TP and Teiid Designer added a dummy feature to satisfy maven. This was built and everything in the IS builds and installs fine - no one directly needed bouncycastle.
> Fuse Tooling builds a local development-only full source target platform based on the JBTIS TP. This causes all dependencies to be fully resolved which causes them to fail their target platform development-only build:
> {code}
> mvn -Pmultiple2repo -U -Dmirror-target-to-repo.includeSources=true clean install
> ...
> [ERROR] Software being installed: org.apache.directory.studio.connection.ui 2.0.0.v20150618
> [ERROR] Missing requirement: org.apache.directory.studio.connection.ui 2.0.0.v20150618 requires 'package org.bouncycastle.x509.extension 0.0.0' but it could not be found
> {code}
> you may also see this error:
> {code}
> [ERROR] Software being installed: org.apache.directory.studio.connection.ui 2.0.0.v20150618
> [ERROR] Missing requirement: org.apache.directory.studio.connection.ui 2.0.0.v20150618 requires 'package org.bouncycastle.asn1 0.0.0' but it could not be found
> {code}
> Both of these plugins can be found (in stub form) here:
> http://download.jboss.org/jbosstools/updates/stable/luna/integration-stac...
> How should this be fixed? Both Teiid Designer and Fuse Tooling use the JBTIS TP. Fuse needs this development TP to debug Fuse and SAP issues. They shouldn't have to incur a dependency that has nothing to do with them. If we pull the entire Apache directory dependency block out of the IS TP then Teiid Des will have to go back to creating their own merged TP.
> WDYT?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21046) Need to implement "Bower Install" launch shortcut
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21046?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-21046:
--------------------------------
Description:
[Bower Install|http://bower.io/docs/api/#install] - Installs the project dependencies
>From the user perspective it will be a launch shortcut just like existing "Bower Update"
> Need to implement "Bower Install" launch shortcut
> -------------------------------------------------
>
> Key: JBIDE-21046
> URL: https://issues.jboss.org/browse/JBIDE-21046
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: nodejs
> Affects Versions: 4.3.0.Final
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Labels: new_and_noteworthy
> Fix For: 4.4.0.Alpha1
>
>
> [Bower Install|http://bower.io/docs/api/#install] - Installs the project dependencies
> From the user perspective it will be a launch shortcut just like existing "Bower Update"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months