[JBoss JIRA] (JBIDE-14780) Add ShrinkWrap Archive name/type validation
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14780?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-14780:
---------------------------------------
{quote}
Does this contain a quick fix for 'set correct extension' as well?
{quote}
No, it doesn't. I have created JBIDE-15657 for that issue.
> Add ShrinkWrap Archive name/type validation
> -------------------------------------------
>
> Key: JBIDE-14780
> URL: https://issues.jboss.org/browse/JBIDE-14780
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: testing-tools
> Reporter: Aslak Knutsen
> Assignee: Snjezana Peco
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Alpha1
>
>
> *Given*
> {code}
> ShrinkWrap.create(WebArchive.class, "test.jar")
> ShrinkWrap.create(WebArchive.class, "test.ear")
> ShrinkWrap.create(JavaArchive.class, "test.ear")
> ShrinkWrap.create(WebArchive.class, "test")
> {code}
> *When*
> User is creating a Archive
> *Then*
> The known Archive types should match given archive name extensions.
> *Expected*
> Warning; Creating an archive of type WebArchive but given name does not match to predefined name extension; .war
> *Actual*
> Nothing.. waits for Arquillian to fail.
> This is a very common and annoying user error. The Container/Server will 99% of the time rely on the deployment file extension to determine what type of archive this is. While our 'WebArchive' Archive types are only convenience views on how to add data to correct locations within the target archive and can be any type; we choose to validate this runtime in Arquillian core to warn that 'hey, this is probably not what you intended to do' to hopefully save users from a few hours pointless debugging.
> See https://github.com/arquillian/arquillian-core/blob/master/container/spi/s... for our extension type mapping.
> Our validation logic is; if extension does not match, but Archive is of Type then warn.
> That allows users to use Custom views without warning.
--
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
12 years, 6 months
[JBoss JIRA] (JBIDE-12574) Support multiple domains in OpenShift UI
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12574?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12574:
-------------------------------------
Attachment: (was: application-wizard-manage-domain.png)
> Support multiple domains in OpenShift UI
> ----------------------------------------
>
> Key: JBIDE-12574
> URL: https://issues.jboss.org/browse/JBIDE-12574
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.0.0.Alpha2
> Reporter: Xavier Coulon
> Assignee: Andre Dietisheim
> Fix For: 4.2.0.Alpha1
>
> Attachments: application-wizard-manage-domain.png, multi-domain-in-explorer.png, properties-multi-domain.png
>
>
> The OpenShift Explorer view should display a node for the domain between the user and his applications (relevant is support for multiple domains was added)
--
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
12 years, 6 months
[JBoss JIRA] (JBIDE-12574) Support multiple domains in OpenShift UI
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12574?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12574:
-------------------------------------
Attachment: application-wizard-manage-domain.png
> Support multiple domains in OpenShift UI
> ----------------------------------------
>
> Key: JBIDE-12574
> URL: https://issues.jboss.org/browse/JBIDE-12574
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.0.0.Alpha2
> Reporter: Xavier Coulon
> Assignee: Andre Dietisheim
> Fix For: 4.2.0.Alpha1
>
> Attachments: application-wizard-manage-domain.png, application-wizard-manage-domain.png, multi-domain-in-explorer.png, properties-multi-domain.png
>
>
> The OpenShift Explorer view should display a node for the domain between the user and his applications (relevant is support for multiple domains was added)
--
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
12 years, 6 months
[JBoss JIRA] (JBIDE-15656) package-info.java in managed package in persistence.xml causes StackOverflowError
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15656?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-15656:
--------------------------------
Description:
A customer reported stackoverflow errors occuring when importing one of his maven projects.
After investigation, it appears the SO is caused by HibernatePackageInfoImpl
{ noformat}
java.lang.StackOverflowError
at org.eclipse.core.runtime.Path.computeSegmentCount(Path.java:450)
at org.eclipse.core.runtime.Path.computeSegments(Path.java:467)
at org.eclipse.core.runtime.Path.initialize(Path.java:602)
at org.eclipse.core.runtime.Path.<init>(Path.java:163)
at org.eclipse.jdt.internal.core.PackageFragment.resource(PackageFragment.java:326)
at org.eclipse.jdt.internal.core.CompilationUnit.resource(CompilationUnit.java:894)
at org.eclipse.jdt.internal.core.Openable.getResource(Openable.java:453)
at org.eclipse.jpt.common.core.internal.resource.java.source.SourceCompilationUnit.getFile(SourceCompilationUnit.java:95)
at org.eclipse.jpt.common.core.internal.resource.java.AbstractJavaResourceModel.getFile(AbstractJavaResourceModel.java:98)
at org.jboss.tools.hibernate.jpt.core.internal.context.java.HibernatePackageInfoImpl.validate(HibernatePackageInfoImpl.java:238)
at org.jboss.tools.hibernate.jpt.core.internal.context.java.HibernatePackageInfoImpl.validate(HibernatePackageInfoImpl.java:245)
at org.jboss.tools.hibernate.jpt.core.internal.context.java.HibernatePackageInfoImpl.validate(HibernatePackageInfoImpl.java:245)
{noformat}
The simplest setup to reproduce, involves creating a JPA project (Hibernate Platform 2), and adding the following files :
{code:title=persistence.xml }
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">
<persistence-unit name="jpa">
<class>foo.bar.model</class>
</persistence-unit>
</persistence>
{code}
{code:title=package-info.java}
package foo.bar.model;
{code}
was:
A customer reported stackoverflow errors occuring when importing one of his maven projects.
After investigation, it appears the SO is caused by HibernatePackageInfoImpl
{ noformat}
java.lang.StackOverflowError
at org.eclipse.core.runtime.Path.computeSegmentCount(Path.java:450)
at org.eclipse.core.runtime.Path.computeSegments(Path.java:467)
at org.eclipse.core.runtime.Path.initialize(Path.java:602)
at org.eclipse.core.runtime.Path.<init>(Path.java:163)
at org.eclipse.jdt.internal.core.PackageFragment.resource(PackageFragment.java:326)
at org.eclipse.jdt.internal.core.CompilationUnit.resource(CompilationUnit.java:894)
at org.eclipse.jdt.internal.core.Openable.getResource(Openable.java:453)
at org.eclipse.jpt.common.core.internal.resource.java.source.SourceCompilationUnit.getFile(SourceCompilationUnit.java:95)
at org.eclipse.jpt.common.core.internal.resource.java.AbstractJavaResourceModel.getFile(AbstractJavaResourceModel.java:98)
at org.jboss.tools.hibernate.jpt.core.internal.context.java.HibernatePackageInfoImpl.validate(HibernatePackageInfoImpl.java:238)
at org.jboss.tools.hibernate.jpt.core.internal.context.java.HibernatePackageInfoImpl.validate(HibernatePackageInfoImpl.java:245)
at org.jboss.tools.hibernate.jpt.core.internal.context.java.HibernatePackageInfoImpl.validate(HibernatePackageInfoImpl.java:245)
{noformat}
The simplest setup to reproduce, involves creating a JPA project (Hibernate Platform 2), and adding the following files :
{code:title=persistence.xml }
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">
<persistence-unit name="jpa">
<class>foo.bar.model</class>
</persistence-unit>
</persistence>
{code}
{code:package-info.java}
package foo.bar.model;
{code}
> package-info.java in managed package in persistence.xml causes StackOverflowError
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-15656
> URL: https://issues.jboss.org/browse/JBIDE-15656
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.1.0.Final
> Reporter: Fred Bricon
> Priority: Blocker
> Fix For: 4.1.1.Beta1
>
>
> A customer reported stackoverflow errors occuring when importing one of his maven projects.
> After investigation, it appears the SO is caused by HibernatePackageInfoImpl
> { noformat}
> java.lang.StackOverflowError
> at org.eclipse.core.runtime.Path.computeSegmentCount(Path.java:450)
> at org.eclipse.core.runtime.Path.computeSegments(Path.java:467)
> at org.eclipse.core.runtime.Path.initialize(Path.java:602)
> at org.eclipse.core.runtime.Path.<init>(Path.java:163)
> at org.eclipse.jdt.internal.core.PackageFragment.resource(PackageFragment.java:326)
> at org.eclipse.jdt.internal.core.CompilationUnit.resource(CompilationUnit.java:894)
> at org.eclipse.jdt.internal.core.Openable.getResource(Openable.java:453)
> at org.eclipse.jpt.common.core.internal.resource.java.source.SourceCompilationUnit.getFile(SourceCompilationUnit.java:95)
> at org.eclipse.jpt.common.core.internal.resource.java.AbstractJavaResourceModel.getFile(AbstractJavaResourceModel.java:98)
> at org.jboss.tools.hibernate.jpt.core.internal.context.java.HibernatePackageInfoImpl.validate(HibernatePackageInfoImpl.java:238)
> at org.jboss.tools.hibernate.jpt.core.internal.context.java.HibernatePackageInfoImpl.validate(HibernatePackageInfoImpl.java:245)
> at org.jboss.tools.hibernate.jpt.core.internal.context.java.HibernatePackageInfoImpl.validate(HibernatePackageInfoImpl.java:245)
> {noformat}
> The simplest setup to reproduce, involves creating a JPA project (Hibernate Platform 2), and adding the following files :
> {code:title=persistence.xml }
> <?xml version="1.0" encoding="UTF-8"?>
> <persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">
> <persistence-unit name="jpa">
> <class>foo.bar.model</class>
> </persistence-unit>
> </persistence>
> {code}
> {code:title=package-info.java}
> package foo.bar.model;
> {code}
--
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
12 years, 6 months
[JBoss JIRA] (JBIDE-14780) Add ShrinkWrap Archive name/type validation
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14780?page=com.atlassian.jira.plugi... ]
Aslak Knutsen commented on JBIDE-14780:
---------------------------------------
Does this contain a quick fix for 'set correct extension' as well?
> Add ShrinkWrap Archive name/type validation
> -------------------------------------------
>
> Key: JBIDE-14780
> URL: https://issues.jboss.org/browse/JBIDE-14780
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: testing-tools
> Reporter: Aslak Knutsen
> Assignee: Snjezana Peco
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Alpha1
>
>
> *Given*
> {code}
> ShrinkWrap.create(WebArchive.class, "test.jar")
> ShrinkWrap.create(WebArchive.class, "test.ear")
> ShrinkWrap.create(JavaArchive.class, "test.ear")
> ShrinkWrap.create(WebArchive.class, "test")
> {code}
> *When*
> User is creating a Archive
> *Then*
> The known Archive types should match given archive name extensions.
> *Expected*
> Warning; Creating an archive of type WebArchive but given name does not match to predefined name extension; .war
> *Actual*
> Nothing.. waits for Arquillian to fail.
> This is a very common and annoying user error. The Container/Server will 99% of the time rely on the deployment file extension to determine what type of archive this is. While our 'WebArchive' Archive types are only convenience views on how to add data to correct locations within the target archive and can be any type; we choose to validate this runtime in Arquillian core to warn that 'hey, this is probably not what you intended to do' to hopefully save users from a few hours pointless debugging.
> See https://github.com/arquillian/arquillian-core/blob/master/container/spi/s... for our extension type mapping.
> Our validation logic is; if extension does not match, but Archive is of Type then warn.
> That allows users to use Custom views without warning.
--
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
12 years, 6 months
[JBoss JIRA] (JBIDE-14780) Add ShrinkWrap Archive name/type validation
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14780?page=com.atlassian.jira.plugi... ]
Aslak Knutsen commented on JBIDE-14780:
---------------------------------------
Oh yea, and Nice! :)
> Add ShrinkWrap Archive name/type validation
> -------------------------------------------
>
> Key: JBIDE-14780
> URL: https://issues.jboss.org/browse/JBIDE-14780
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: testing-tools
> Reporter: Aslak Knutsen
> Assignee: Snjezana Peco
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Alpha1
>
>
> *Given*
> {code}
> ShrinkWrap.create(WebArchive.class, "test.jar")
> ShrinkWrap.create(WebArchive.class, "test.ear")
> ShrinkWrap.create(JavaArchive.class, "test.ear")
> ShrinkWrap.create(WebArchive.class, "test")
> {code}
> *When*
> User is creating a Archive
> *Then*
> The known Archive types should match given archive name extensions.
> *Expected*
> Warning; Creating an archive of type WebArchive but given name does not match to predefined name extension; .war
> *Actual*
> Nothing.. waits for Arquillian to fail.
> This is a very common and annoying user error. The Container/Server will 99% of the time rely on the deployment file extension to determine what type of archive this is. While our 'WebArchive' Archive types are only convenience views on how to add data to correct locations within the target archive and can be any type; we choose to validate this runtime in Arquillian core to warn that 'hey, this is probably not what you intended to do' to hopefully save users from a few hours pointless debugging.
> See https://github.com/arquillian/arquillian-core/blob/master/container/spi/s... for our extension type mapping.
> Our validation logic is; if extension does not match, but Archive is of Type then warn.
> That allows users to use Custom views without warning.
--
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
12 years, 6 months
[JBoss JIRA] (JBIDE-15656) package-info.java in managed package in persistence.xml causes StackOverflowError
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-15656:
-----------------------------------
Summary: package-info.java in managed package in persistence.xml causes StackOverflowError
Key: JBIDE-15656
URL: https://issues.jboss.org/browse/JBIDE-15656
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Affects Versions: 4.1.0.Final
Reporter: Fred Bricon
Priority: Blocker
Fix For: 4.1.1.Beta1
A customer reported stackoverflow errors occuring when importing one of his maven projects.
After investigation, it appears the SO is caused by HibernatePackageInfoImpl
{ noformat}
java.lang.StackOverflowError
at org.eclipse.core.runtime.Path.computeSegmentCount(Path.java:450)
at org.eclipse.core.runtime.Path.computeSegments(Path.java:467)
at org.eclipse.core.runtime.Path.initialize(Path.java:602)
at org.eclipse.core.runtime.Path.<init>(Path.java:163)
at org.eclipse.jdt.internal.core.PackageFragment.resource(PackageFragment.java:326)
at org.eclipse.jdt.internal.core.CompilationUnit.resource(CompilationUnit.java:894)
at org.eclipse.jdt.internal.core.Openable.getResource(Openable.java:453)
at org.eclipse.jpt.common.core.internal.resource.java.source.SourceCompilationUnit.getFile(SourceCompilationUnit.java:95)
at org.eclipse.jpt.common.core.internal.resource.java.AbstractJavaResourceModel.getFile(AbstractJavaResourceModel.java:98)
at org.jboss.tools.hibernate.jpt.core.internal.context.java.HibernatePackageInfoImpl.validate(HibernatePackageInfoImpl.java:238)
at org.jboss.tools.hibernate.jpt.core.internal.context.java.HibernatePackageInfoImpl.validate(HibernatePackageInfoImpl.java:245)
at org.jboss.tools.hibernate.jpt.core.internal.context.java.HibernatePackageInfoImpl.validate(HibernatePackageInfoImpl.java:245)
{noformat}
The simplest setup to reproduce, involves creating a JPA project (Hibernate Platform 2), and adding the following files :
{code:title=persistence.xml }
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">
<persistence-unit name="jpa">
<class>foo.bar.model</class>
</persistence-unit>
</persistence>
{code}
{code:package-info.java}
package foo.bar.model;
{code}
--
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
12 years, 6 months
[JBoss JIRA] (JBIDE-14555) Wrong warning "Could not initialize class my.pkg.ArchiveBuilder" by Arquillian
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14555?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-14555:
---------------------------------------
I believe this issue has been fixed within JBIDE-14523.
If you face the issue again, please reopen it.
> Wrong warning "Could not initialize class my.pkg.ArchiveBuilder" by Arquillian
> ------------------------------------------------------------------------------
>
> Key: JBIDE-14555
> URL: https://issues.jboss.org/browse/JBIDE-14555
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.1.0.Beta1
> Reporter: Juergen Zimmermann
> Assignee: Snjezana Peco
> Priority: Critical
> Fix For: 4.2.0.Alpha1
>
>
> I'm using JBoss Tools 41-Update-2013-05-19_01-13-51-B207 having the new Arquillian component.
> I'm getting a warning "Could not initialize class my.pkg.ArchiveBuilder" in all Arquillian-based test classes.
> In fact my ArchiveBuilder isn't a regular class, but it's an enum:
> public enum ArchiveBuilder {
> INSTANCE;
> private final WebArchive archive = ShrinkWrap.create(WebArchive.class, "shop.war");
> private ArchiveBuilder() {...}
> public static ArchiveBuilder getInstance() { return INSTANCE; }
> public Archive<? extends Archive<?>> getArchive() { return archive; }
--
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
12 years, 6 months