[JBoss JIRA] (JBIDE-13561) Cannot embed cartridges
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13561?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on JBIDE-13561:
-------------------------------------------------
Dan McPherson <dmcphers(a)redhat.com> made a comment on [bug 911322|https://bugzilla.redhat.com/show_bug.cgi?id=911322]
Lili, can you make sure test cases get added for this case.
Also note the build in INT as per admiller's note is from last Friday. Given when this fix was made I don't think that's the issue here.
-Dan
> Cannot embed cartridges
> -----------------------
>
> Key: JBIDE-13561
> URL: https://issues.jboss.org/browse/JBIDE-13561
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.0.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Blocker
> Fix For: 4.1.0.Alpha1
>
> Attachments: apptype-is-embedded-cartridge.png, cartridge-type-not-embedded.png, jbds6-erroring-embedding-cartridge.png
>
>
> If you try to embed cartridges (or remove embedded cartridges) in 4.0.0 Final or JBDS6, then you wont be able to do it.
> This is an issue that shall help us track modifications on the OpenShift platform. There's nothing we can do about it, it's *OpenShift that has to hot-fix*.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBIDE-13561) Cannot embed cartridges
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13561?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on JBIDE-13561:
-------------------------------------------------
Andre Dietisheim <adietish(a)redhat.com> made a comment on [bug 911322|https://bugzilla.redhat.com/show_bug.cgi?id=911322]
This started to show up again on INT:
curl -k --user "<USER>:<PASS>" -H "Accept: application/xml; version=1.0" https://int.openshift.redhat.com/broker/rest/domains/freaky/applications/... -X GET
<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<type>cartridges</type>
<data>
<cartridge>
<name>jbossas-7</name>
<type>standalone</type>
<status-messages nil="true"></status-messages>
<properties>
</properties>
</cartridge>
</data>
<messages/>
<version>1.0</version>
<supported-api-versions>
<supported-api-version>1.0</supported-api-version>
<supported-api-version>1.1</supported-api-version>
<supported-api-version>1.2</supported-api-version>
<supported-api-version>1.3</supported-api-version>
</supported-api-versions>
</response>
> Cannot embed cartridges
> -----------------------
>
> Key: JBIDE-13561
> URL: https://issues.jboss.org/browse/JBIDE-13561
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.0.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Blocker
> Fix For: 4.1.0.Alpha1
>
> Attachments: apptype-is-embedded-cartridge.png, cartridge-type-not-embedded.png, jbds6-erroring-embedding-cartridge.png
>
>
> If you try to embed cartridges (or remove embedded cartridges) in 4.0.0 Final or JBDS6, then you wont be able to do it.
> This is an issue that shall help us track modifications on the OpenShift platform. There's nothing we can do about it, it's *OpenShift that has to hot-fix*.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBIDE-13561) Cannot embed cartridges
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13561?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on JBIDE-13561:
-------------------------------------------------
Dan McPherson <dmcphers(a)redhat.com> changed the Status of [bug 911322|https://bugzilla.redhat.com/show_bug.cgi?id=911322] from VERIFIED to ASSIGNED
> Cannot embed cartridges
> -----------------------
>
> Key: JBIDE-13561
> URL: https://issues.jboss.org/browse/JBIDE-13561
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.0.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Blocker
> Fix For: 4.1.0.Alpha1
>
> Attachments: apptype-is-embedded-cartridge.png, cartridge-type-not-embedded.png, jbds6-erroring-embedding-cartridge.png
>
>
> If you try to embed cartridges (or remove embedded cartridges) in 4.0.0 Final or JBDS6, then you wont be able to do it.
> This is an issue that shall help us track modifications on the OpenShift platform. There's nothing we can do about it, it's *OpenShift that has to hot-fix*.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBIDE-13314) Improved support for the upcoming JBossAS 7.2
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13314?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-13314.
-------------------------------
> Improved support for the upcoming JBossAS 7.2
> ---------------------------------------------
>
> Key: JBIDE-13314
> URL: https://issues.jboss.org/browse/JBIDE-13314
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: JBossAS/Servers
> Affects Versions: 4.0.0.Final
> Reporter: Juergen Zimmermann
> Assignee: Rob Stryker
> Fix For: 4.1.0.Alpha1
>
>
> JBoss Tools are already detecting a 7.2 server (compiled from upstream master). When such a 7.2 server is started, you'll see this warning:
> "WARNING: -logmodule is deprecated. Please use the system property 'java.util.logging.manager' or the 'java.util.logging.LogManager' service loader."
> The solution: In the "Open launch configuration" just remove "-logmodule org.jboss.logmanager" from the "Program arguments" and add "-Djava.util.logging.manager=org.jboss.logmanager.LogManager" to the "VM arguments".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBIDE-13548) Hibernate errors when importing projects from JBoss Central
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13548?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-13548:
---------------------------------------
Sorry if I wasn't clear - I am able to reproduce this issue - JBIDE-13548. In JBDS 7.0.0.Alpha1b (where also vpakan was able to reproduce it), but not in JBT 4.1.0.Alpha1b (where Koen was also unable to reproduce).
[~koen.aers] is looking at it right now - discussing on IRC #jbosstools.
Koen asked if it makes sense that it's JBDS-only. And Max said:
{quote}
think more its because jpa is not being enabledautomatically.
{quote}
> Hibernate errors when importing projects from JBoss Central
> -----------------------------------------------------------
>
> Key: JBIDE-13548
> URL: https://issues.jboss.org/browse/JBIDE-13548
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.1.0.Alpha1
> Reporter: Radim Hopp
> Assignee: Koen Aers
> Fix For: 4.1.0.Alpha1
>
>
> When creating projects from JBoss Central ("HTML5 Project" or "RichFaces Project" for example) lot of errors like this appears in error log:
> {noformat}java.lang.ClassCastException: org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericClassRef cannot be cast to org.jboss.tools.hibernate.jpt.core.internal.context.persistence.HibernateClassRef
> at org.jboss.tools.hibernate.jpt.core.internal.context.HibernatePersistenceUnit$2.transform(HibernatePersistenceUnit.java:1)
> at org.eclipse.jpt.common.utility.internal.iterator.TransformationIterator.next(TransformationIterator.java:54)
> at org.eclipse.jpt.common.utility.internal.iterator.FilteringIterator.loadNext(FilteringIterator.java:122)
> at org.eclipse.jpt.common.utility.internal.iterator.FilteringIterator.<init>(FilteringIterator.java:90)
> at org.eclipse.jpt.common.utility.internal.iterable.FilteringIterable.iterator(FilteringIterable.java:68)
> at org.eclipse.jpt.common.utility.internal.iterable.TransformationIterable.iterator(TransformationIterable.java:50)
> at org.eclipse.jpt.common.utility.internal.iterable.CompositeIterable.iterables(CompositeIterable.java:72)
> at org.eclipse.jpt.common.utility.internal.iterable.CompositeIterable.iterators(CompositeIterable.java:65)
> at org.eclipse.jpt.common.utility.internal.iterable.CompositeIterable.iterator(CompositeIterable.java:57)
> at org.eclipse.jpt.common.utility.internal.iterable.IterableTools$IteratorTransformer.transform(IterableTools.java:914)
> at org.eclipse.jpt.common.utility.internal.iterable.IterableTools$IteratorTransformer.transform(IterableTools.java:1)
> at org.eclipse.jpt.common.utility.internal.iterator.TransformationIterator.next(TransformationIterator.java:54)
> at org.eclipse.jpt.common.utility.internal.iterator.CompositeIterator.loadCurrentIterator(CompositeIterator.java:88)
> at org.eclipse.jpt.common.utility.internal.iterator.CompositeIterator.hasNext(CompositeIterator.java:51)
> at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.mapByName(AbstractPersistenceUnit.java:2112)
> at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.buildGenerators(AbstractPersistenceUnit.java:1527)
> at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.update(AbstractPersistenceUnit.java:294)
> at org.jboss.tools.hibernate.jpt.core.internal.context.HibernatePersistenceUnit.update(HibernatePersistenceUnit.java:92)
> at org.eclipse.jpt.jpa.core.internal.context.AbstractJpaContextNode.updateNodes(AbstractJpaContextNode.java:61)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistence.update(GenericPersistence.java:71)
> 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.GenericRootContextNode.syncPersistenceXml(GenericRootContextNode.java:126)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.GenericRootContextNode.updatePersistenceXml(GenericRootContextNode.java:160)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.GenericRootContextNode.update(GenericRootContextNode.java:76)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.update(AbstractJpaProject.java:2011)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$UpdateJobCommand.execute(AbstractJpaProject.java:1998)
> 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.jpa.core.internal.InternalJpaProjectManager.execute_(InternalJpaProjectManager.java:1202)
> at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager$ClientJobCommandWrapper.execute(InternalJpaProjectManager.java:1182)
> at org.eclipse.jpt.common.core.internal.utility.command.JobCommandJob.run(JobCommandJob.java:42)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53){noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBIDE-13548) Hibernate errors when importing projects from JBoss Central
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13548?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-13548:
---------------------------------------
Sorry, I am not sure what issue you have reproduced - this one or JBIDE-13607.
I can reproduce JBIDE-13607 in JBDS 7.0.0.Alpha1b B62, but it has been fixed upstream.
Both of these issues have been fixed in JBT master with the latest m2e-wtp/jpa.
> Hibernate errors when importing projects from JBoss Central
> -----------------------------------------------------------
>
> Key: JBIDE-13548
> URL: https://issues.jboss.org/browse/JBIDE-13548
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.1.0.Alpha1
> Reporter: Radim Hopp
> Assignee: Koen Aers
> Fix For: 4.1.0.Alpha1
>
>
> When creating projects from JBoss Central ("HTML5 Project" or "RichFaces Project" for example) lot of errors like this appears in error log:
> {noformat}java.lang.ClassCastException: org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericClassRef cannot be cast to org.jboss.tools.hibernate.jpt.core.internal.context.persistence.HibernateClassRef
> at org.jboss.tools.hibernate.jpt.core.internal.context.HibernatePersistenceUnit$2.transform(HibernatePersistenceUnit.java:1)
> at org.eclipse.jpt.common.utility.internal.iterator.TransformationIterator.next(TransformationIterator.java:54)
> at org.eclipse.jpt.common.utility.internal.iterator.FilteringIterator.loadNext(FilteringIterator.java:122)
> at org.eclipse.jpt.common.utility.internal.iterator.FilteringIterator.<init>(FilteringIterator.java:90)
> at org.eclipse.jpt.common.utility.internal.iterable.FilteringIterable.iterator(FilteringIterable.java:68)
> at org.eclipse.jpt.common.utility.internal.iterable.TransformationIterable.iterator(TransformationIterable.java:50)
> at org.eclipse.jpt.common.utility.internal.iterable.CompositeIterable.iterables(CompositeIterable.java:72)
> at org.eclipse.jpt.common.utility.internal.iterable.CompositeIterable.iterators(CompositeIterable.java:65)
> at org.eclipse.jpt.common.utility.internal.iterable.CompositeIterable.iterator(CompositeIterable.java:57)
> at org.eclipse.jpt.common.utility.internal.iterable.IterableTools$IteratorTransformer.transform(IterableTools.java:914)
> at org.eclipse.jpt.common.utility.internal.iterable.IterableTools$IteratorTransformer.transform(IterableTools.java:1)
> at org.eclipse.jpt.common.utility.internal.iterator.TransformationIterator.next(TransformationIterator.java:54)
> at org.eclipse.jpt.common.utility.internal.iterator.CompositeIterator.loadCurrentIterator(CompositeIterator.java:88)
> at org.eclipse.jpt.common.utility.internal.iterator.CompositeIterator.hasNext(CompositeIterator.java:51)
> at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.mapByName(AbstractPersistenceUnit.java:2112)
> at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.buildGenerators(AbstractPersistenceUnit.java:1527)
> at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.update(AbstractPersistenceUnit.java:294)
> at org.jboss.tools.hibernate.jpt.core.internal.context.HibernatePersistenceUnit.update(HibernatePersistenceUnit.java:92)
> at org.eclipse.jpt.jpa.core.internal.context.AbstractJpaContextNode.updateNodes(AbstractJpaContextNode.java:61)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistence.update(GenericPersistence.java:71)
> 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.GenericRootContextNode.syncPersistenceXml(GenericRootContextNode.java:126)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.GenericRootContextNode.updatePersistenceXml(GenericRootContextNode.java:160)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.GenericRootContextNode.update(GenericRootContextNode.java:76)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.update(AbstractJpaProject.java:2011)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$UpdateJobCommand.execute(AbstractJpaProject.java:1998)
> 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.jpa.core.internal.InternalJpaProjectManager.execute_(InternalJpaProjectManager.java:1202)
> at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager$ClientJobCommandWrapper.execute(InternalJpaProjectManager.java:1182)
> at org.eclipse.jpt.common.core.internal.utility.command.JobCommandJob.run(JobCommandJob.java:42)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53){noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBIDE-13715) soa-p 5.3 is incorrectly detected as 5.2
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13715?page=com.atlassian.jira.plugi... ]
Len DiMaggio updated JBIDE-13715:
---------------------------------
Attachment: Screenshot.png
> soa-p 5.3 is incorrectly detected as 5.2
> ----------------------------------------
>
> Key: JBIDE-13715
> URL: https://issues.jboss.org/browse/JBIDE-13715
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.0.0.Final, 4.1.0.Alpha1
> Reporter: Martin Malina
> Assignee: Snjezana Peco
> Fix For: 4.0.1.Final, 4.1.0.Alpha2
>
> Attachments: Screenshot.png
>
>
> When you use the runtime detection feature to add a soa-p 5.3.1 server it is detected as SOA-P version 5.2.
> When you add the server manually, there is no server type soa-p, so there you have to choose EAP 5.x anyway and so this issue is not present there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBIDE-12815) Create a JBoss Tools Orbit
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12815?page=com.atlassian.jira.plugi... ]
Paul Richardson commented on JBIDE-12815:
-----------------------------------------
Yes, Teiid Designer's [locus project|http://github.com/Teiid-Designer/locus] is designed with this in mind. So far,
* contains 4 plugins (apache-poi, jcip-annotations, mockito-1.9.5 [1], sf.saxon)
* plugins and site are built by maven
Things to do:
* incremental build - if this is preferred;
* migrate to a more appropriate and central owner (rather than [Teiid-Designer|http://github.com/Teiid-Designer])
---
[1] modified configuration to enable turning off of the cache - patch provided upstream but no response so far.
> Create a JBoss Tools Orbit
> --------------------------
>
> Key: JBIDE-12815
> URL: https://issues.jboss.org/browse/JBIDE-12815
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Build/Releng, UpStream
> Reporter: Mickael Istria
> Assignee: Paul Richardson
> Fix For: 4.1.0.Alpha2
>
>
> Since all JBoss Eclipse-based project probably share some needs for usual libraries, we should create a JBoss Tools Orbit project in which one we would provide those 3rd-party dependencies packaged as OSGi Bundle in a p2 repository.
> In a first time, we could simply create some OSGi "wrappers" around those jars.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month