[JBoss JIRA] Created: (JBDS-1642) RichFaces based JSF Portlet doesn't deploy correctly
by Jan Jamrich (JIRA)
RichFaces based JSF Portlet doesn't deploy correctly
----------------------------------------------------
Key: JBDS-1642
URL: https://issues.jboss.org/browse/JBDS-1642
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Affects Versions: 4.0.0.GA
Environment: JBoss EPP 5.1.1.DEV1, JBDS-4.0.0.GA
Reporter: Jan Jamrich
When create JSF portlet and add richfaces into pages (declare namespace and write some richfaces tags into JSP page), an error appear on deploy.
Its caused by missing RichFaces libraries in deployed WAR file (discovered by exporting to WAR and checking for basic dependencies) even I have checked option "Add/Change Richfaces Libraries" in "JBoss JSF Portlet Capabilities" dialog which appear after added "JSF capabilities" in "Project Facets" project's properties.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (JBIDE-9218) JPA: Null text range in HibernateQuery validation process
by Dmitry Geraskov (JIRA)
JPA: Null text range in HibernateQuery validation process
---------------------------------------------------------
Key: JBIDE-9218
URL: https://issues.jboss.org/browse/JBIDE-9218
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 3.3.0.M2
Reporter: Dmitry Geraskov
Assignee: Dmitry Geraskov
Priority: Critical
Fix For: 3.3.0.M2, 3.3.0.M3
Test case:
create an entity with 2 queries:
@javax.persistence.NamedQuery(name="nn", query = "SELECT qq.id3 FROM JustData qq")
@org.hibernate.annotations.NamedQuery(name = "nn", query = "")
Observe the exception:
java.lang.NullPointerException: Null text range for message ID: QUERY_STATEMENT_UNDEFINED
at org.eclipse.jpt.jpa.core.internal.validation.DefaultJpaValidationMessages.buildMessage(DefaultJpaValidationMessages.java:52)
at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaQuery.validateQuery(AbstractJavaQuery.java:236)
at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaQuery.validate(AbstractJavaQuery.java:216)
at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.validate(AbstractPersistenceUnit.java:2433)
at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.validateQueries(AbstractPersistenceUnit.java:2398)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (JBIDE-9216) JPA: Null text range in GenericGenerator validation process
by Dmitry Geraskov (JIRA)
JPA: Null text range in GenericGenerator validation process
-----------------------------------------------------------
Key: JBIDE-9216
URL: https://issues.jboss.org/browse/JBIDE-9216
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 3.3.0.M2
Reporter: Dmitry Geraskov
Assignee: Dmitry Geraskov
Priority: Critical
Fix For: 3.3.0.M3
Test Case:
Create entity with 2 generator annotations: @GenericGenerator, @SequesnceGenerator with the same name
Observe exception:
java.lang.NullPointerException: Null text range for message ID: GENERATOR_DUPLICATE_NAME
at org.eclipse.jpt.jpa.core.internal.validation.DefaultJpaValidationMessages.buildMessage(DefaultJpaValidationMessages.java:52)
at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.checkForDuplicateGenerators(AbstractPersistenceUnit.java:2362)
at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.validateGenerators(AbstractPersistenceUnit.java:2350)
at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.validate(AbstractPersistenceUnit.java:2232)
at org.jboss.tools.hibernate.jpt.core.internal.context.HibernatePersistenceUnit.validate(HibernatePersistenceUnit.java:174)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (JBIDE-9007) Why composite update site for component builds http://download.jboss.org/jbosstools/builds/staging/_composite_/3.3.indigo should not be used by default for local builds
by Denis Golovin (JIRA)
Why composite update site for component builds http://download.jboss.org/jbosstools/builds/staging/_composite_/3.3.indigo should not be used by default for local builds
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-9007
URL: https://issues.jboss.org/browse/JBIDE-9007
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M2
Reporter: Denis Golovin
Assignee: Nick Boldt
Priority: Blocker
Fix For: 3.3.0.M2
[1] http://download.jboss.org/jbosstools/builds/staging/_composite_/3.3.indigo/
should not be used by default in local builds like
mvn clean install
[2] OSGI Java doc says about version.compareTo() method:
"A version is considered to be <b>less than </b> another version if its
major component is less than the other version's major component, or the
major components are equal and its minor component is less than the other
version's minor component, or the major and minor components are equal
and its micro component is less than the other version's micro component,
or the major, minor and micro components are equal and it's qualifier
component is less than the other version's qualifier component (using
<code>String.compareTo</code>"
It means for developers in concord, which has 3 hours difference with hudson host on east coast, that sometimes component built locally considered as having older version and component from composite repo [1] mentioned above picked up instead.
For example, I added new method "test()" in class from common.core plugin, built it and then wrote test for this new method in test plugin. In my case, when I compile my test, it fails with compilation error: "The method test() is undefined for ...". It happens because update site [1] contains common component built by hudson 12 minutes ago and its qualifier is "v20110525-1854-H267-M2". At the same time I have my locally built component in my local maven repo with qualifier "v20110525-1606-M2".
According [2] when major, minor and micro versions are equal all depends on qualifier string comparation. Which basically means for my case
System.out.println("v20110525-1606-M2".compareTo("v20110525-1854-H267-M2"));
which returns -2 and that's why version from [1] is picked up instead one in my local maven repo, which I just built.
At the same time it worked when I tried to verify that with cdi component on different desktop. It worked, because last published build on [1] for cdi has qualifier "v20110524-2226-H289-M2", which is less then my local one "v20110525-1646-M2", because
System.out.println("v20110525-1646-M2".compareTo("v20110524-2226-H289-M2"));
returns 1.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (JBIDE-7052) The import org.hibernate cannot be resolved in org/jboss/tools/birt/oda/impl/ConsoleConfigurationOdaFactory.java (at line 17)
by Nick Boldt (JIRA)
The import org.hibernate cannot be resolved in org/jboss/tools/birt/oda/impl/ConsoleConfigurationOdaFactory.java (at line 17)
-----------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-7052
URL: https://jira.jboss.org/browse/JBIDE-7052
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: birt
Affects Versions: 3.2.0.Beta
Reporter: Nick Boldt
Assignee: Snjezana Peco
Priority: Blocker
[ERROR] Failed to execute goal org.sonatype.tycho:maven-osgi-compiler-plugin:0.9.0:compile (default-compile) on project org.jboss.tools.birt.oda: Compilation failure: Compilation failure:
/mnt/hudson_workspace/workspace/jbosstools-3.2.0.Beta1.continuous/sources/birt/plugins/org.jboss.tools.birt.oda/src/org/jboss/tools/birt/oda/impl/ConsoleConfigurationOdaFactory.java (at line 17):[-1,-1]
import org.hibernate.HibernateException;
^^^^^^^^^^^^^
The import org.hibernate cannot be resolved
/mnt/hudson_workspace/workspace/jbosstools-3.2.0.Beta1.continuous/sources/birt/plugins/org.jboss.tools.birt.oda/src/org/jboss/tools/birt/oda/impl/ConsoleConfigurationOdaFactory.java (at line 18):[-1,-1]
import org.hibernate.SessionFactory;
^^^^^^^^^^^^^
The import org.hibernate cannot be resolved
/mnt/hudson_workspace/workspace/jbosstools-3.2.0.Beta1.continuous/sources/birt/plugins/org.jboss.tools.birt.oda/src/org/jboss/tools/birt/oda/impl/ConsoleConfigurationOdaFactory.java (at line 19):[-1,-1]
import org.hibernate.console.ConsoleConfiguration;
^^^^^^^^^^^^^
The import org.hibernate cannot be resolved
/mnt/hudson_workspace/workspace/jbosstools-3.2.0.Beta1.continuous/sources/birt/plugins/org.jboss.tools.birt.oda/src/org/jboss/tools/birt/oda/impl/ConsoleConfigurationOdaFactory.java (at line 20):[-1,-1]
import org.hibernate.console.KnownConfigurations;
^^^^^^^^^^^^^
The import org.hibernate cannot be resolved
http://hudson.qa.jboss.com/hudson/view/DevStudio_Tycho/job/jbosstools-3.2...
This has been broken for 11 builds / 2 days: from Build #122 (Sep 9, 2010 8:45:42 AM) to Build #132 (Sep 10, 2010 6:04:08 PM)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months