Hi,
Could you update the nightly build of tomahawk at
http://cvs.apache.org/builds/myfaces/nightly/ such that we can test the core
snapshot ?
Currently the tomahawk build gives:
08:32:10,309 ERROR [WebXmlParser]
org.apache.myfaces.shared_tomahawk.webapp.webxml.WebXml.init must be called
before!
JBoss classloading fails if myfaces jars installed in tomcat
Key: MYFACES-1163
URL: http://issues.apache.org/jira/browse/MYFACES-1163
Project: MyFaces Core
Type: Bug
Versions: 1.1.2, 1.1.2-SNAPSHOT,
[
http://issues.apache.org/jira/browse/TOMAHAWK-175?page=comments#action_12369216
]
Jurgen Lust commented on TOMAHAWK-175:
--
I'll get to it tonight. Shouldn't be a lot of work i think.
schedule component: select available time slots to create new
These are manual builds from continuum. I'm looking into it.
Sean
On 3/7/06, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Online report :
http://myfaces.zones.apache.org:8080/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/37/buildId/619
Build statistics:
State:
[ http://issues.apache.org/jira/browse/MYFACES-776?page=all ]
updated MYFACES-776:
-
Tree2 state problem when using dynamic trees
Key: MYFACES-776
URL: http://issues.apache.org/jira/browse/MYFACES-776
Hi!
plugin
groupIdorg.apache.myfaces.maven/groupId
artifactIdwagon-maven-plugin/artifactId
-version1.0.1-SNAPSHOT/version
+version1.0.2-SNAPSHOT/version
Is it possible to use a entity references in an pom.xml?
So we can move all the version stuff
tree2 should support expandRoot=true like tree
Key: TOMAHAWK-179
URL: http://issues.apache.org/jira/browse/TOMAHAWK-179
Project: MyFaces Tomahawk
Type: New Feature
Components: Tree2
Reporter: Bill Schneider
Not sure if its possible. I also worry that if its possible we will
eventually get burned like we did with externals. My recommended
solution is to document the release steps for each subproject in the
wiki.
Sean
On 3/7/06, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi!
plugin
[ http://issues.apache.org/jira/browse/MYFACES-334?page=all ]
updated MYFACES-334:
-
aliasbean and alias usage in binding
Key: MYFACES-334
URL: http://issues.apache.org/jira/browse/MYFACES-334
Project:
[ http://issues.apache.org/jira/browse/MYFACES-334?page=all ]
Mario Ivankovits updated MYFACES-334:
-
Resolution: Fixed
aliasbean and alias usage in binding
Key: MYFACES-334
URL:
[ http://issues.apache.org/jira/browse/MYFACES-334?page=all ]
Mario Ivankovits closed MYFACES-334:
aliasbean and alias usage in binding
Key: MYFACES-334
URL:
Dennis mentioned that we are not using JDK 1.3 compile option on the
core branch. Can someone fix this and test? I will do one last build
tonight.
Sean
Hi Sean!
Dennis mentioned that we are not using JDK 1.3 compile option on the
core branch.
Its not only to set the target/source options, but also to
a) set the bootclasspath for the compiler to the jdk1.3 libraries - see:
http://jroller.com/page/scolebourne?entry=compiling_for_older_jdks and
Picklist does not support non-string values
---
Key: TOMAHAWK-181
URL: http://issues.apache.org/jira/browse/TOMAHAWK-181
Project: MyFaces Tomahawk
Type: Bug
Versions: 1.1.2-SNAPSHOT
Reporter: Peter Mahoney
The
Hi *, Hi Simon,
logging again - what do we do with static methods - do we have to get
all of them out?
or should we be calling getLog on every logging attempt?
regards,
Martin
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
[
http://issues.apache.org/jira/browse/TOBAGO-20?page=comments#action_12369297 ]
Udo Schnurpfeil commented on TOBAGO-20:
---
You have to make the next steps. There are 2 possibilities, one for easy setup
and development and one for production:
a)
[ http://issues.apache.org/jira/browse/MYFACES-1092?page=all ]
Martin Marinschek resolved MYFACES-1092:
Fix Version: 1.1.3-SNAPSHOT
Resolution: Fixed
Craig, please check this with the current SVN head.
regards,
Martin
I believe the core is already compiled using:
plugins
plugin
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.3/source
target1.3/target
/configuration
/plugin
/plugins
This plugin is configured in the master pom. I
I've forgotten something:
Put the tag
resource-dirorg/apache/myfaces/tobago/renderkit/resource-dir
in your tobago-config.xml. Instead of
resource-dirtobago/resource-dir
In further versions, this will be unnecessary. The resource-dir will
be automatically resolved by the theme
I noticed that the shared branch pom depends on the maven idea plugin
which is a SNAPSHOT. I hate to keep bringing this up but we cannot
release with a SNAPSHOT dependency. This is why I went to all the
trouble to get a beta release of the XSLT plugin.
What are our options here? Is there an
On 3/7/06, Sean Schofield [EMAIL PROTECTED] wrote:
I noticed that the shared branch pom depends on the maven idea pluginwhich is a SNAPSHOT.I hate to keep bringing this up but we cannotrelease with a SNAPSHOT dependency.This is why I went to all thetrouble to get a beta release of the XSLT plugin.
Can we do another alpha release of the entire shale project? As long
as it compiles I don't see the harm in another alpha with known
issues.
Sean
On 3/7/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 3/7/06, Sean Schofield [EMAIL PROTECTED] wrote:
I noticed that the shared branch pom
Weird, the manifest said jdk 1.4 though.
Dennis Byrne
-Original Message-
From: Sean Schofield [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 7, 2006 03:37 PM
To: 'MyFaces Development'
Subject: Re: Core and JDK 1.3
I believe the core is already compiled using:
plugins
plugin
Since the reorg there seem to be dummy packages, now I run into the
problem, that I can compile without errors, because the dummy source
packages are referenced, but I cannot deploy from eclipse for exactly
the same reason, in the builds the dummy packages are renamed to their
real release
Werner Punz schrieb:
Since the reorg there seem to be dummy packages, now I run into the
problem, that I can compile without errors, because the dummy source
packages are referenced, but I cannot deploy from eclipse for exactly
the same reason, in the builds the dummy packages are renamed to
Hi,
The manifest JVM version is whatever JVM was used to run the jar task,
which obviously *was* the 1.4 jvm.
I expect that the source and target tags just set the -source and
-target options for the compiler. So the compiler used is still the
default one (whatever was used to run maven; 1.4 in
Simon,
Thanks for the explanation. For now it seems we will have to settle
for the limited 1.3 compatability.
Sean
On 3/7/06, Simon Kitching [EMAIL PROTECTED] wrote:
Hi,
The manifest JVM version is whatever JVM was used to run the jar task,
which obviously *was* the 1.4 jvm.
I expect
On Tue, 2006-03-07 at 21:10 +0100, Martin Marinschek wrote:
Hi *, Hi Simon,
logging again - what do we do with static methods - do we have to get
all of them out?
or should we be calling getLog on every logging attempt?
Yep, even static methods must avoid logging via a static logger :-(
new validator - validate comma separated entries by splitting them and
validating individually
--
Key: TOMAHAWK-182
URL: http://issues.apache.org/jira/browse/TOMAHAWK-182
Project:
[ http://issues.apache.org/jira/browse/TOMAHAWK-182?page=all ]
Lance Frohman updated TOMAHAWK-182:
---
new validator - validate comma separated entries by splitting them and
validating individually
[ http://issues.apache.org/jira/browse/TOMAHAWK-182?page=all ]
Lance Frohman updated TOMAHAWK-182:
---
new validator - validate comma separated entries by splitting them and
validating individually
[
http://issues.apache.org/jira/browse/TOMAHAWK-66?page=comments#action_12369355
]
Lance Frohman commented on TOMAHAWK-66:
---
My email address is changed to [EMAIL PROTECTED]
add colspan (and header/footer colspan) attributes to tomahawk extended
[
http://issues.apache.org/jira/browse/TOMAHAWK-99?page=comments#action_12369356
]
Lance Frohman commented on TOMAHAWK-99:
---
My email address is changed to [EMAIL PROTECTED]
add reordering columns ability to tomahawk extended data table
[
http://issues.apache.org/jira/browse/TOMAHAWK-123?page=comments#action_12369357
]
Lance Frohman commented on TOMAHAWK-123:
My email address is changed to [EMAIL PROTECTED]
Add orientation parameter to NewspaperTable
[
http://issues.apache.org/jira/browse/TOMAHAWK-178?page=comments#action_12369358
]
Lance Frohman commented on TOMAHAWK-178:
My email address is changed to [EMAIL PROTECTED]
Change NewspaperTable to be able to use extended column properly
[
http://issues.apache.org/jira/browse/MYFACES-1163?page=comments#action_12369359
]
Stan Silvert commented on MYFACES-1163:
---
The 1.1.2 snapshot craps out in JBoss 4.0.4 RC2 as well, if you try to upgrade
MyFaces. So, I believe I have found the same
[
http://issues.apache.org/jira/browse/TOMAHAWK-175?page=comments#action_12369361
]
Jurgen Lust commented on TOMAHAWK-175:
--
Hmm, I implemented some of it, but there seem to be problems with the latest
svn version of myfaces, so I can't test it yet.
[
http://issues.apache.org/jira/browse/MYFACES-1163?page=comments#action_12369381
]
Stan Silvert commented on MYFACES-1163:
---
I was wrong. What I was seeing was some experimental JBoss code crapping out
because of the MyFaces package name changes.
[
http://issues.apache.org/jira/browse/MYFACES-1163?page=comments#action_12369393
]
Dennis Byrne commented on MYFACES-1163:
---
Related ?
http://issues.apache.org/jira/browse/MYFACES-872
JBoss classloading fails if myfaces jars installed in tomcat
The main problem is, that if you try to build everything from scratch
with mvn eclipse:eclipse in the old project structure that worked, you
also could deploy the sandbox examples directly from eclipse that way.
Now if you do that you run into runtime issues, due to the rename of the
shared
Hi,Sean.
I used Myfaces Core 1.1.2 to test the java.lang.IllegalStateException:
Cannot forward after response has been committed issue,Now found it:
If redirect in Java back form bean,has no problem.
But if using redirect in filter class, the problem is still exist.
I knowned the two test-cases
41 matches
Mail list logo
