[maven] myfaces pom
Hi, the ASF master-pom does contain a _regular_ snapshot repo (linked to the (new) nexus repo), see: https://svn.apache.org/repos/asf/maven/pom/trunk/asf/pom.xml *snip* repository idapache.snapshots/id nameApache Snapshot Repository/name urlhttp://repository.apache.org/snapshots/url releases enabledfalse/enabled /releases /repository *snip* However, it doesn't define the apache.snapshot for plugins. Nor does the myfaces pom. Does one know why? In Trinidad we currently have this setting: pluginRepositories pluginRepository idapache.snapshots/id nameApache Snapshot Repository/name urlhttp://repository.apache.org/snapshots/url releases enabledfalse/enabled /releases /pluginRepository /pluginRepositories IMO it could be centralized: In myfaces-pom or in the ASF pom. Thoughts? -Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
[maven] master pom
Hi, the master pom still contains this section: ciManagement systemcontinuum/system urlhttp://myfaces.zones.apache.org:8080/continuum/url notifiers notifier typemail/type configuration addressnotificati...@myfaces.apache.org/address /configuration /notifier /notifiers /ciManagement Was there any reason for keeping it? (since we are now (mostly) on hudson) -Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
[jira] Commented: (TRINIDAD-1953) Cannot build the trunk on a clean maven repository
[ https://issues.apache.org/jira/browse/TRINIDAD-1953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12928560#action_12928560 ] Matthias Weßendorf commented on TRINIDAD-1953: -- I did a) clean ups of the pom.xml (odd references were in there) b) I am currently changing the Trinidad plugins to be deployed to the hudson (looks like that was missing) -Matthias Cannot build the trunk on a clean maven repository -- Key: TRINIDAD-1953 URL: https://issues.apache.org/jira/browse/TRINIDAD-1953 Project: MyFaces Trinidad Issue Type: Bug Components: Build Affects Versions: 2.0.0.3-core Reporter: Andrew Robinson Assignee: Matthias Weßendorf Priority: Blocker If you do not have a ~/.m2/settings.xml and you do not build the plugins or maven 1.2.x trunk locally, the Trinidad 2 trunk will not build. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.myfaces.trinidadbuild:maven-xrts-plugin Reason: POM 'org.apache.myfaces.trinidadbuild:maven-xrts-plugin' not found in repository: Unable to download the artifact from any repository org.apache.myfaces.trinidadbuild:maven-xrts-plugin:pom:2.0.3-SNAPSHOT from the specified remote repositories: apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), jboss releases (http://repository.jboss.org/maven2/), central (http://repo1.maven.org/maven2), java.net (http://download.java.net/maven/1), maven2-repository.dev.java.net (http://download.java.net/maven/2/) for project org.apache.myfaces.trinidadbuild:maven-xrts-plugin We should ensure that the necessary repositories are in the pom.xml and the plugin snapshots are being correctly deployed to the snapshot repository so that we can build without having to build the plugins or the 1.2.x branch locally. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [maven] master pom
hi, thx - i was going to write the same mail. +1 for changing it. regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2010/11/5 Matthias Wessendorf mat...@apache.org Hi, the master pom still contains this section: ciManagement systemcontinuum/system urlhttp://myfaces.zones.apache.org:8080/continuum/url notifiers notifier typemail/type configuration addressnotificati...@myfaces.apache.org/address /configuration /notifier /notifiers /ciManagement Was there any reason for keeping it? (since we are now (mostly) on hudson) -Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [maven] master pom
Committed revision 1031524. On Fri, Nov 5, 2010 at 12:22 PM, Gerhard gerhard.petra...@gmail.com wrote: hi, thx - i was going to write the same mail. +1 for changing it. regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2010/11/5 Matthias Wessendorf mat...@apache.org Hi, the master pom still contains this section: ciManagement systemcontinuum/system urlhttp://myfaces.zones.apache.org:8080/continuum/url notifiers notifier typemail/type configuration addressnotificati...@myfaces.apache.org/address /configuration /notifier /notifiers /ciManagement Was there any reason for keeping it? (since we are now (mostly) on hudson) -Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
[Trinidad BUILD] Can we update the portlet-bridge version ?
Hi, the TRUNK has this dependency portlet-bridge.version1.0.0-beta/portlet-bridge.version which causes some *problems* when you delete your entire REPO. Why? It's OLD portlet-bridge-master-pom-2 has: a) overridden the repositories section ([1]) b) dependency to myfaces-6 (Trinidad has against 9) in a) there is the WORST ever repo: urlhttps://maven-repository.dev.java.net/nonav/repository/url what's wrong with that REPO? Well it has been removed. and it issues redirects via HTML... Yes, I really don't know why... Hence... for portlet-bridge-master-pom-2 MAVEN had to download myfaces-6, but the repo is gone (g) ... and the maven tool is not a human, so it really can't read this HTML: ... The document has moved a href=http://download.java.net/maven/1/org.apache.myfaces/poms/myfaces-6.pom;here/a. ... So it (maven) ended up downloading a HTML file It took a good amount of time to realize the above dilemma.. Quick fix: manually downloaded myfaces-6. This made the build running, but yes the problem is really the 'relocation' of that mentioned repo. Therefore... we should update the TRINIDAD TRUNK to use a newer version than: portlet-bridge.version (1.0.0-beta). Since the master poms have been touched and updated the bogus (relocated) repo to it's real, new URL. Scott, can you update the version ? -Matthias [1] https://svn.apache.org/repos/asf/myfaces/portlet-bridge/master-pom/tags/portlet-bridge-master-pom-2/pom.xml -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [maven] myfaces pom
We keep that inside of our Trinidad pom b/c that way we don't force all others to go with *snapshots*, of plugins. Trinidad's maven plugins are a separate project, therefore it is needed. Will update the POM with a comment. -M On Fri, Nov 5, 2010 at 9:49 AM, Matthias Wessendorf mat...@apache.org wrote: Hi, the ASF master-pom does contain a _regular_ snapshot repo (linked to the (new) nexus repo), see: https://svn.apache.org/repos/asf/maven/pom/trunk/asf/pom.xml *snip* repository idapache.snapshots/id nameApache Snapshot Repository/name urlhttp://repository.apache.org/snapshots/url releases enabledfalse/enabled /releases /repository *snip* However, it doesn't define the apache.snapshot for plugins. Nor does the myfaces pom. Does one know why? In Trinidad we currently have this setting: pluginRepositories pluginRepository idapache.snapshots/id nameApache Snapshot Repository/name urlhttp://repository.apache.org/snapshots/url releases enabledfalse/enabled /releases /pluginRepository /pluginRepositories IMO it could be centralized: In myfaces-pom or in the ASF pom. Thoughts? -Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: Build failed in Hudson: MyFaces-Trinidad-2.0.x #33
If you are wondering, why this failure is here: http://jira.codehaus.org/browse/MENFORCER-110 (looks like it's fixed in a few days...) .Matthias On Fri, Nov 5, 2010 at 8:42 AM, Apache Hudson Server hud...@hudson.apache.org wrote: See https://hudson.apache.org/hudson/job/MyFaces-Trinidad-2.0.x/33/changes Changes: [matzew] fixing minor typo -- Started by user matzew Building remotely on ubuntu2 Updating https://svn.apache.org/repos/asf/myfaces/trinidad/trunk U trinidad-build/src/main/resources/META-INF/maven-faces-plugin/events/trinidad/AttributeChange.xml U trinidad-build/src/main/resources/META-INF/maven-faces-plugin/components/trinidad/SelectBoolean.xml At revision 1031460 Parsing POMs [trunk] $ /home/hudson/tools/java/latest1.6/bin/java -cp /home/hudson/hudson-slave/maven-agent.jar:/home/hudson/tools/maven/latest/boot/classworlds-1.1.jar hudson.maven.agent.Main /home/hudson/tools/maven/latest /home/hudson/hudson-slave/slave.jar /home/hudson/hudson-slave/maven-interceptor.jar 38068 /home/hudson/hudson-slave/maven2.1-interceptor.jar ===[HUDSON REMOTING CAPACITY]===channel started Executing Maven: -B -f https://hudson.apache.org/hudson/job/MyFaces-Trinidad-2.0.x/ws/trunk/pom.xml install [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Apache MyFaces Trinidad 2.0 [INFO] Apache MyFaces Trinidad Build [INFO] Apache MyFaces Trinidad API [INFO] Apache MyFaces Trinidad Impl [INFO] Apache MyFaces Trinidad Examples [INFO] Apache MyFaces Trinidad Blank Demo [INFO] Apache MyFaces Trinidad Demo [INFO] Apache MyFaces Trinidad Components Showcase [INFO] [INFO] Building Apache MyFaces Trinidad 2.0 [INFO] task-segment: [install] [INFO] [INFO] artifact org.apache.maven.plugins:maven-enforcer-plugin: checking for updates from apache.snapshots [INFO] snapshot org.apache.maven.plugins:maven-enforcer-plugin:1.1-SNAPSHOT: checking for updates from apache.snapshots [INFO] snapshot org.apache.maven.enforcer:enforcer:1.1-SNAPSHOT: checking for updates from apache.snapshots Downloading: http://repository.apache.org/snapshots/org/apache/maven/maven-parent/17/maven-parent-17.pom [INFO] Unable to find resource 'org.apache.maven:maven-parent:pom:17' in repository apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository) Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven-parent/17/maven-parent-17.pom [INFO] Unable to find resource 'org.apache.maven:maven-parent:pom:17' in repository central (http://repo1.maven.org/maven2) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.maven.enforcer:enforcer:pom:1.1-SNAPSHOT Reason: Cannot find parent: org.apache.maven:maven-parent for project: org.apache.maven.enforcer:enforcer:pom:1.1-SNAPSHOT for project org.apache.maven.enforcer:enforcer:pom:1.1-SNAPSHOT [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Fri Nov 05 07:42:13 UTC 2010 [INFO] Final Memory: 5M/61M [INFO] channel stopped -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [jira] Commented: (TRINIDAD-1953) Cannot build the trunk on a clean maven repository
Matthias, Just wanted to say thanks for all the work. Cleaning up the pom is no fun especially when there were complications, but I appreciate the effort. -Andrew 2010/11/5 Matthias Weßendorf (JIRA) dev@myfaces.apache.org [ https://issues.apache.org/jira/browse/TRINIDAD-1953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12928560#action_12928560] Matthias Weßendorf commented on TRINIDAD-1953: -- I did a) clean ups of the pom.xml (odd references were in there) b) I am currently changing the Trinidad plugins to be deployed to the hudson (looks like that was missing) -Matthias Cannot build the trunk on a clean maven repository -- Key: TRINIDAD-1953 URL: https://issues.apache.org/jira/browse/TRINIDAD-1953 Project: MyFaces Trinidad Issue Type: Bug Components: Build Affects Versions: 2.0.0.3-core Reporter: Andrew Robinson Assignee: Matthias Weßendorf Priority: Blocker If you do not have a ~/.m2/settings.xml and you do not build the plugins or maven 1.2.x trunk locally, the Trinidad 2 trunk will not build. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.myfaces.trinidadbuild:maven-xrts-plugin Reason: POM 'org.apache.myfaces.trinidadbuild:maven-xrts-plugin' not found in repository: Unable to download the artifact from any repository org.apache.myfaces.trinidadbuild:maven-xrts-plugin:pom:2.0.3-SNAPSHOT from the specified remote repositories: apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository ), jboss releases (http://repository.jboss.org/maven2/), central (http://repo1.maven.org/maven2), java.net (http://download.java.net/maven/1), maven2-repository.dev.java.net (http://download.java.net/maven/2/) for project org.apache.myfaces.trinidadbuild:maven-xrts-plugin We should ensure that the necessary repositories are in the pom.xml and the plugin snapshots are being correctly deployed to the snapshot repository so that we can build without having to build the plugins or the 1.2.x branch locally. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (TRINIDAD-1953) Cannot build the trunk on a clean maven repository
You are welcome! It was needed, and I am actually happy that's almost working (see my other 'rant' email) :) -Matthias On Fri, Nov 5, 2010 at 4:37 PM, Andrew Robinson andrew.rw.robin...@gmail.com wrote: Matthias, Just wanted to say thanks for all the work. Cleaning up the pom is no fun especially when there were complications, but I appreciate the effort. -Andrew 2010/11/5 Matthias Weßendorf (JIRA) dev@myfaces.apache.org [ https://issues.apache.org/jira/browse/TRINIDAD-1953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12928560#action_12928560 ] Matthias Weßendorf commented on TRINIDAD-1953: -- I did a) clean ups of the pom.xml (odd references were in there) b) I am currently changing the Trinidad plugins to be deployed to the hudson (looks like that was missing) -Matthias Cannot build the trunk on a clean maven repository -- Key: TRINIDAD-1953 URL: https://issues.apache.org/jira/browse/TRINIDAD-1953 Project: MyFaces Trinidad Issue Type: Bug Components: Build Affects Versions: 2.0.0.3-core Reporter: Andrew Robinson Assignee: Matthias Weßendorf Priority: Blocker If you do not have a ~/.m2/settings.xml and you do not build the plugins or maven 1.2.x trunk locally, the Trinidad 2 trunk will not build. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.myfaces.trinidadbuild:maven-xrts-plugin Reason: POM 'org.apache.myfaces.trinidadbuild:maven-xrts-plugin' not found in repository: Unable to download the artifact from any repository org.apache.myfaces.trinidadbuild:maven-xrts-plugin:pom:2.0.3-SNAPSHOT from the specified remote repositories: apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), jboss releases (http://repository.jboss.org/maven2/), central (http://repo1.maven.org/maven2), java.net (http://download.java.net/maven/1), maven2-repository.dev.java.net (http://download.java.net/maven/2/) for project org.apache.myfaces.trinidadbuild:maven-xrts-plugin We should ensure that the necessary repositories are in the pom.xml and the plugin snapshots are being correctly deployed to the snapshot repository so that we can build without having to build the plugins or the 1.2.x branch locally. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
[Portlet Bridge] maven, pom change...
Hi, https://svn.apache.org/repos/asf/myfaces/portlet-bridge/core/trunk/pom.xml can we move that to parent artifactIdportlet-bridge-master-pom/artifactId groupIdorg.apache.myfaces.portlet-bridge/groupId version3/version /parent to version '4' (or even '5-SNAPSHOT') ? -Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [maven] myfaces pom
Hi I think it could be useful to include it on myfaces master pom. After all, on myfaces there exists multiple plugins that should be updated from time to time. regards, Leonardo Uribe 2010/11/5 Matthias Wessendorf mat...@apache.org We keep that inside of our Trinidad pom b/c that way we don't force all others to go with *snapshots*, of plugins. Trinidad's maven plugins are a separate project, therefore it is needed. Will update the POM with a comment. -M On Fri, Nov 5, 2010 at 9:49 AM, Matthias Wessendorf mat...@apache.org wrote: Hi, the ASF master-pom does contain a _regular_ snapshot repo (linked to the (new) nexus repo), see: https://svn.apache.org/repos/asf/maven/pom/trunk/asf/pom.xml *snip* repository idapache.snapshots/id nameApache Snapshot Repository/name urlhttp://repository.apache.org/snapshots/url releases enabledfalse/enabled /releases /repository *snip* However, it doesn't define the apache.snapshot for plugins. Nor does the myfaces pom. Does one know why? In Trinidad we currently have this setting: pluginRepositories pluginRepository idapache.snapshots/id nameApache Snapshot Repository/name urlhttp://repository.apache.org/snapshots/url releases enabledfalse/enabled /releases /pluginRepository /pluginRepositories IMO it could be centralized: In myfaces-pom or in the ASF pom. Thoughts? -Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [maven] myfaces pom
No, I think we don't want every plugin's (all the maven plugins etc) on our trunk build... -M On Fri, Nov 5, 2010 at 5:30 PM, Leonardo Uribe lu4...@gmail.com wrote: Hi I think it could be useful to include it on myfaces master pom. After all, on myfaces there exists multiple plugins that should be updated from time to time. regards, Leonardo Uribe 2010/11/5 Matthias Wessendorf mat...@apache.org We keep that inside of our Trinidad pom b/c that way we don't force all others to go with *snapshots*, of plugins. Trinidad's maven plugins are a separate project, therefore it is needed. Will update the POM with a comment. -M On Fri, Nov 5, 2010 at 9:49 AM, Matthias Wessendorf mat...@apache.org wrote: Hi, the ASF master-pom does contain a _regular_ snapshot repo (linked to the (new) nexus repo), see: https://svn.apache.org/repos/asf/maven/pom/trunk/asf/pom.xml *snip* repository idapache.snapshots/id nameApache Snapshot Repository/name urlhttp://repository.apache.org/snapshots/url releases enabledfalse/enabled /releases /repository *snip* However, it doesn't define the apache.snapshot for plugins. Nor does the myfaces pom. Does one know why? In Trinidad we currently have this setting: pluginRepositories pluginRepository idapache.snapshots/id nameApache Snapshot Repository/name urlhttp://repository.apache.org/snapshots/url releases enabledfalse/enabled /releases /pluginRepository /pluginRepositories IMO it could be centralized: In myfaces-pom or in the ASF pom. Thoughts? -Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [maven] myfaces pom
What I understand is add that entry to myfaces master pom allow to use snapshot versions temporally for maven plugins, but does not force to use it. Some days ago I did a svn checkout of a myfaces project and I notice that myfaces-builder-plugin was not downloaded from internet, but that one was added on hudson, so I had to recompile the plugin locally. 2010/11/5 Matthias Wessendorf mat...@apache.org No, I think we don't want every plugin's (all the maven plugins etc) on our trunk build... -M On Fri, Nov 5, 2010 at 5:30 PM, Leonardo Uribe lu4...@gmail.com wrote: Hi I think it could be useful to include it on myfaces master pom. After all, on myfaces there exists multiple plugins that should be updated from time to time. regards, Leonardo Uribe 2010/11/5 Matthias Wessendorf mat...@apache.org We keep that inside of our Trinidad pom b/c that way we don't force all others to go with *snapshots*, of plugins. Trinidad's maven plugins are a separate project, therefore it is needed. Will update the POM with a comment. -M On Fri, Nov 5, 2010 at 9:49 AM, Matthias Wessendorf mat...@apache.org wrote: Hi, the ASF master-pom does contain a _regular_ snapshot repo (linked to the (new) nexus repo), see: https://svn.apache.org/repos/asf/maven/pom/trunk/asf/pom.xml *snip* repository idapache.snapshots/id nameApache Snapshot Repository/name urlhttp://repository.apache.org/snapshots/url releases enabledfalse/enabled /releases /repository *snip* However, it doesn't define the apache.snapshot for plugins. Nor does the myfaces pom. Does one know why? In Trinidad we currently have this setting: pluginRepositories pluginRepository idapache.snapshots/id nameApache Snapshot Repository/name urlhttp://repository.apache.org/snapshots/url releases enabledfalse/enabled /releases /pluginRepository /pluginRepositories IMO it could be centralized: In myfaces-pom or in the ASF pom. Thoughts? -Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
[jira] Created: (TRINIDAD-1955) panelPageSkinDemo - the skin picker choice is not changing the skin
panelPageSkinDemo - the skin picker choice is not changing the skin
---
Key: TRINIDAD-1955
URL: https://issues.apache.org/jira/browse/TRINIDAD-1955
Project: MyFaces Trinidad
Issue Type: Bug
Components: Skinning
Reporter: Jeanne Waldman
The panelPageSkinDemo.jspx page in the demos directory of the demo project has
a choice menu where you can choose a skin, like purple, and press the Go button
and the skin should change. It isn't changing.
tr:selectOneChoice label=Skin-family: autoSubmit=false
value=#{sessionScope.skinFamily}
tr:selectItem label=simple value=simple/
tr:selectItem label=minimal value=minimal/
tr:selectItem label=purple value=purple/
tr:selectItem label=purpleBigFont value=purpleBigFont/
tr:selectItem label=beach value=beach/
tr:selectItem label=suede value=suede/
tr:selectItem label=locale value=localeDemo/
/tr:selectOneChoice
tr:commandButton text=Go/
In trinidad-config.xml we have:
!-- you can use EL to get the skin. This allows the skin to change between
requests. --
skin-family#{prefs.proxy.skinFamily}/skin-family
In faces-config.xml
managed-bean
managed-bean-nameprefs/managed-bean-name
managed-bean-class
org.apache.myfaces.trinidaddemo.PreferencesProxy
/managed-bean-class
managed-bean-scope
application
/managed-bean-scope
/managed-bean
public Object getProxy()
{
FacesContext context = FacesContext.getCurrentInstance();
String viewId = _getViewId(context);
if (viewId != null)
{
// Certain views have their own preferences
// storage. Figure out which preferences
// we are proxying.
String preferencesExpression = null;
if (viewId.indexOf(/email/) = 0)
preferencesExpression = #{email.preferences};
else if (viewId.indexOf(SkinDemo) = 0)
preferencesExpression = #{sessionScope};
else if (viewId.indexOf(accessibilityProfileDemo) = 0)
preferencesExpression = #{accProfileDemo};
if (preferencesExpression != null)
{
ValueExpression ve =
context.getApplication().getExpressionFactory().createValueExpression(context.getELContext(),
preferencesExpression, Object.class);
return ve.getValue(context.getELContext());
}
}
But every time I get the skin-family from the code, it returns null.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (TRINIDAD-1956) View root caching causes transient property keys to be kept for multiple requests
View root caching causes transient property keys to be kept for multiple requests - Key: TRINIDAD-1956 URL: https://issues.apache.org/jira/browse/TRINIDAD-1956 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions: 2.0.0.3-core, 1.2.15-core Reporter: Andrew Robinson Assignee: Andrew Robinson If org.apache.myfaces.trinidad.CACHE_VIEW_ROOT is set to true, any PropertyKey attributes are kept longer than one request. This may break components that expect the transient attributes only to be used for one request. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
require-bundle header in api bundle
I'm trying to understand why the require-bundle header is in the api bundle. This is a pretty bizarre thing to do in what I've seen of osgi. I took it out and geronimo-tomcat appears to work OK. Maybe because this is because geronimo has a somewhat extended thread context classloader, but maybe not. I saw some vague claims in the comments to MYFACES-2911 that the api classes need to load impl classes, but no details. Could someone point me to the code where this happens? There must be a better way to do this thanks david jencks
Re: [maven] myfaces pom
I think a plugin snapshot repo is not in the asf master pom because using snapshot plugins is not something the maven devs want to encourage. Why does myfaces need a snapshot plugin? I'd recommend putting the plugin repo entry near the use of the plugin so it can be removed easily when the plugin is released. I'd include a comment on why its needed too. thanks david jencks On Nov 5, 2010, at 1:49 AM, Matthias Wessendorf wrote: Hi, the ASF master-pom does contain a _regular_ snapshot repo (linked to the (new) nexus repo), see: https://svn.apache.org/repos/asf/maven/pom/trunk/asf/pom.xml *snip* repository idapache.snapshots/id nameApache Snapshot Repository/name urlhttp://repository.apache.org/snapshots/url releases enabledfalse/enabled /releases /repository *snip* However, it doesn't define the apache.snapshot for plugins. Nor does the myfaces pom. Does one know why? In Trinidad we currently have this setting: pluginRepositories pluginRepository idapache.snapshots/id nameApache Snapshot Repository/name urlhttp://repository.apache.org/snapshots/url releases enabledfalse/enabled /releases /pluginRepository /pluginRepositories IMO it could be centralized: In myfaces-pom or in the ASF pom. Thoughts? -Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [maven] myfaces pom
On Fri, Nov 5, 2010 at 7:03 PM, David Jencks david_jen...@yahoo.com wrote: I think a plugin snapshot repo is not in the asf master pom because using snapshot plugins is not something the maven devs want to encourage. Agreed - said that later on, too Why does myfaces need a snapshot plugin? core (the jsf impl) does not need it. A subproject's trunk (trinidad) is having dependency against some (specialized) maven plugins (trinidad-maven). These plugins are deployed to the nexus repo, hence we have that in our (trinidad) pom.xml First it sound a good idea. No, it's not - There is no need for having that setting in myfaces/asf pom. I'd recommend putting the plugin repo entry near the use of the plugin so it can be removed easily when the plugin is released. I'd include a comment on why its needed too. yep thanks david jencks On Nov 5, 2010, at 1:49 AM, Matthias Wessendorf wrote: Hi, the ASF master-pom does contain a _regular_ snapshot repo (linked to the (new) nexus repo), see: https://svn.apache.org/repos/asf/maven/pom/trunk/asf/pom.xml *snip* repository idapache.snapshots/id nameApache Snapshot Repository/name urlhttp://repository.apache.org/snapshots/url releases enabledfalse/enabled /releases /repository *snip* However, it doesn't define the apache.snapshot for plugins. Nor does the myfaces pom. Does one know why? In Trinidad we currently have this setting: pluginRepositories pluginRepository idapache.snapshots/id nameApache Snapshot Repository/name urlhttp://repository.apache.org/snapshots/url releases enabledfalse/enabled /releases /pluginRepository /pluginRepositories IMO it could be centralized: In myfaces-pom or in the ASF pom. Thoughts? -Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [maven] myfaces pom
Hi Well, in myfaces there are projects that use plugins hosted in myfaces. For example, myfaces-builder-plugin is required to build myfaces-core. In some moments, it appear bugs on core that require some changes on myfaces-builder-plugin, so in those moments we need a plugin snapshot, just while we release the plugin. If maven release plugin check for snapshot plugins usage before release (and do not allow if that's the case), why bother us to change the pom every time a bug like this happens? regards, Leonardo Uribe 2010/11/5 David Jencks david_jen...@yahoo.com I think a plugin snapshot repo is not in the asf master pom because using snapshot plugins is not something the maven devs want to encourage. Why does myfaces need a snapshot plugin? I'd recommend putting the plugin repo entry near the use of the plugin so it can be removed easily when the plugin is released. I'd include a comment on why its needed too. thanks david jencks On Nov 5, 2010, at 1:49 AM, Matthias Wessendorf wrote: Hi, the ASF master-pom does contain a _regular_ snapshot repo (linked to the (new) nexus repo), see: https://svn.apache.org/repos/asf/maven/pom/trunk/asf/pom.xml *snip* repository idapache.snapshots/id nameApache Snapshot Repository/name urlhttp://repository.apache.org/snapshots/url releases enabledfalse/enabled /releases /repository *snip* However, it doesn't define the apache.snapshot for plugins. Nor does the myfaces pom. Does one know why? In Trinidad we currently have this setting: pluginRepositories pluginRepository idapache.snapshots/id nameApache Snapshot Repository/name urlhttp://repository.apache.org/snapshots/url releases enabledfalse/enabled /releases /pluginRepository /pluginRepositories IMO it could be centralized: In myfaces-pom or in the ASF pom. Thoughts? -Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
[jira] Resolved: (TRINIDAD-1956) View root caching causes transient property keys to be kept for multiple requests
[ https://issues.apache.org/jira/browse/TRINIDAD-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Robinson resolved TRINIDAD-1956. --- Resolution: Fixed Fix Version/s: 1.2.15-core 2.0.0.3-core Fix implemented to null out transient property key values when saving the state of a faces bean View root caching causes transient property keys to be kept for multiple requests - Key: TRINIDAD-1956 URL: https://issues.apache.org/jira/browse/TRINIDAD-1956 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions: 2.0.0.3-core, 1.2.15-core Reporter: Andrew Robinson Assignee: Andrew Robinson Fix For: 2.0.0.3-core, 1.2.15-core If org.apache.myfaces.trinidad.CACHE_VIEW_ROOT is set to true, any PropertyKey attributes are kept longer than one request. This may break components that expect the transient attributes only to be used for one request. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[Trinidad] Nightly Builds are back for 1.0.x, 1.2.x and 2.0.x
Hi, today I did some maven/pom clean up and hudson server related work. As part of that the nightly builds for all 'supported' Trinidad versions are back: See here for example: https://repository.apache.org/content/repositories/snapshots/org/apache/myfaces/trinidad/trinidad-api/ Next (as I did a bit of the clean up already) is doing releases for them - most likely end of the month... Greetings, Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
[jira] Resolved: (MYFACES-2944) Make those add*** methods public in WebXml
[ https://issues.apache.org/jira/browse/MYFACES-2944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonardo Uribe resolved MYFACES-2944. - Resolution: Fixed Assignee: Leonardo Uribe (was: Jakob Korherr) Make those add*** methods public in WebXml -- Key: MYFACES-2944 URL: https://issues.apache.org/jira/browse/MYFACES-2944 Project: MyFaces Core Issue Type: Improvement Components: General Affects Versions: 2.0.2 Reporter: Ivan Assignee: Leonardo Uribe Fix For: 2.0.3-SNAPSHOT Attachments: MYFACES-2944-core-2.patch, MYFACES-2944-core.patch, MYFACES-2944-shared-2.patch, MYFACES-2944-shared.patch, MYFACES-2944.patch In the Geronimo integration work, we have an internal structure for the parsed web.xml file, and we hope to use that instance to fill in the org.apache.myfaces.shared.webapp.webxml.WebXml, so that myfaces does not need to parse the web.xml file again, But those add*** method are package scope. Is it possible to make those methods public, I did not see it will break anyting. Thanks -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (MFCOMMONS-20) Add mc:outputClientId component and Facelets EL function
[ https://issues.apache.org/jira/browse/MFCOMMONS-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonardo Uribe resolved MFCOMMONS-20. - Resolution: Fixed Fix Version/s: 1.0.1-SNAPSHOT Add mc:outputClientId component and Facelets EL function Key: MFCOMMONS-20 URL: https://issues.apache.org/jira/browse/MFCOMMONS-20 Project: MyFaces Commons Issue Type: New Feature Components: myfaces-commons-components Affects Versions: 1.0.1-SNAPSHOT Reporter: Leonardo Uribe Assignee: Leonardo Uribe Fix For: 1.0.1-SNAPSHOT Sometimes it is useful when you write javascript to output the clientId of a component. Since this is a very simple component, it could be good to add it directly to myfaces-commons-components. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (MYFACES-2951) [PERF] enhance scanning for #{cc} expressions
[
https://issues.apache.org/jira/browse/MYFACES-2951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe resolved MYFACES-2951.
-
Resolution: Fixed
Fix Version/s: 2.0.3-SNAPSHOT
[PERF] enhance scanning for #{cc} expressions
-
Key: MYFACES-2951
URL: https://issues.apache.org/jira/browse/MYFACES-2951
Project: MyFaces Core
Issue Type: Improvement
Components: JSR-314
Reporter: Leonardo Uribe
Assignee: Leonardo Uribe
Fix For: 2.0.3-SNAPSHOT
Reported by Martin Koci
MK a issue to consider in
MK org.apache.myfaces.view.facelets.tag.TagAttributeImpl:
MK Methods
MK TagAttributeImpl.getMethodExpression and
MK TagAttributeImpl.getValueExpression use
MK CompositeComponentELUtils.isCompositeComponentXYZ methods to detect if
MK current #{} contains cc expression. But consider following: if user
MK migrates from facelets 1.2 to 2.0, this new cc detection slows down
MK build view process. In one my test case VDL.buildView calls
MK CompositeComponentELUtils.isCompositeComponentXYZ approx 3000 times per
MK build view with no match. isCompositeComponentXYZ is not cheap method
MK because it uses Pattern.matches().
MK Are there possibilities to avoid this? For example is possible have some
MK kind of isProcessingCompositeComponent method and skip
MK Pattern.matches() if false? We are in VDL.buildView here and no
MK components are available yet, no use of methods like
MK UIComponent.isCompositeComponent(UIComponent) is possible.
See discussion on dev list:
[core] performance: TagAttributeImpl and composite component EL detection
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (TOBAGO-938) Remove the feature that puts Tobago in debugMode with locale to-ba-go
Remove the feature that puts Tobago in debugMode with locale to-ba-go --- Key: TOBAGO-938 URL: https://issues.apache.org/jira/browse/TOBAGO-938 Project: MyFaces Tobago Issue Type: Task Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil It is better to set this only with application logic, so the application can control the right of it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TOBAGO-938) Remove the feature that puts Tobago in debugMode with locale to-ba-go
[ https://issues.apache.org/jira/browse/TOBAGO-938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Schnurpfeil resolved TOBAGO-938. Resolution: Fixed Remove the feature that puts Tobago in debugMode with locale to-ba-go --- Key: TOBAGO-938 URL: https://issues.apache.org/jira/browse/TOBAGO-938 Project: MyFaces Tobago Issue Type: Task Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil Fix For: 1.5.0-alpha-2, 1.5.0 It is better to set this only with application logic, so the application can control the right of it. It can be done with ClientProperties.setDebugMode(). An example is in the tobago-example-demo app. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (MYFACES-2962) Descriptions of components, attributes, etc. are missing in taglib.xml files generated by MyFaces Builder Plugin
Descriptions of components, attributes, etc. are missing in taglib.xml files generated by MyFaces Builder Plugin Key: MYFACES-2962 URL: https://issues.apache.org/jira/browse/MYFACES-2962 Project: MyFaces Core Issue Type: Improvement Components: build process Affects Versions: 2.0.2 Reporter: Ali Ok Assignee: Ali Ok Descriptions of components, attributes, etc. are missing in taglib.xml files generated by MyFaces Builder Plugin. Those documentations are used in most IDES (AFAIK Eclipse and Intellij). Of course most IDEs cache the documentation for standard Html libraries, but they read the documentation from taglib.xml file for the other libraries. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (MFCOMMONS-21) Update shale-test dependency with myfaces-test
Update shale-test dependency with myfaces-test -- Key: MFCOMMONS-21 URL: https://issues.apache.org/jira/browse/MFCOMMONS-21 Project: MyFaces Commons Issue Type: Improvement Reporter: Leonardo Uribe Assignee: Leonardo Uribe -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (MFCOMMONS-21) Update shale-test dependency with myfaces-test
[ https://issues.apache.org/jira/browse/MFCOMMONS-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonardo Uribe resolved MFCOMMONS-21. - Resolution: Fixed Fix Version/s: 1.0.1-SNAPSHOT Update shale-test dependency with myfaces-test -- Key: MFCOMMONS-21 URL: https://issues.apache.org/jira/browse/MFCOMMONS-21 Project: MyFaces Commons Issue Type: Improvement Reporter: Leonardo Uribe Assignee: Leonardo Uribe Fix For: 1.0.1-SNAPSHOT -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (MYFACES-2963) Set default templates automatically when jsfVersion is 20 or 2.0 with myfaces-builder-plugin
Set default templates automatically when jsfVersion is 20 or 2.0 with myfaces-builder-plugin Key: MYFACES-2963 URL: https://issues.apache.org/jira/browse/MYFACES-2963 Project: MyFaces Core Issue Type: Improvement Components: build process, JSR-314 Reporter: Leonardo Uribe Assignee: Leonardo Uribe Set default templates automatically when jsfVersion is 20 or 2.0 with myfaces-builder-plugin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (MYFACES-2963) Set default templates automatically when jsfVersion is 20 or 2.0 with myfaces-builder-plugin
[ https://issues.apache.org/jira/browse/MYFACES-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonardo Uribe resolved MYFACES-2963. - Resolution: Fixed Fix Version/s: 2.0.3-SNAPSHOT Set default templates automatically when jsfVersion is 20 or 2.0 with myfaces-builder-plugin Key: MYFACES-2963 URL: https://issues.apache.org/jira/browse/MYFACES-2963 Project: MyFaces Core Issue Type: Improvement Components: build process, JSR-314 Reporter: Leonardo Uribe Assignee: Leonardo Uribe Fix For: 2.0.3-SNAPSHOT Set default templates automatically when jsfVersion is 20 or 2.0 with myfaces-builder-plugin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
