Re: Tomahawk compatibility table
On Feb 1, 2008 1:01 PM, Barbalace, Richard <[EMAIL PROTECTED]> wrote: > Testing whether two related > projects are compatible should be a basic part of the release process. It is > simple QA. IMO It's a bit much to ask a release manager to cross check against every other release. It takes a *lot* of work to get a release out the door. However, this is an excellent place for a company who is using MyFaces in their products to contribute back to the community. If you already have a QA department and are set up to handle a test matrix like this, what about donating an afternoon of work every month or so and reporting the results? -- Wendy
Re: [build tools] Problem with repository to release archetypes 1.0.0
On Jan 27, 2008 9:38 PM, Leonardo Uribe <[EMAIL PROTECTED]> wrote: > I have copied the artifacts to release archetypes 1.0.0 on > http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/myfaces/buildtools/ > but again like with myfaces 1.2.2 the artifacts are not updated How long ago was it? I think it syncs every 4 or 6 hours. I'm seeing a modification date of Jan 28th at 4:10 which is only a couple of hours ago. > Could anyone help me sending this to [EMAIL PROTECTED], so they > can help me with this please? I'll send a note in the morning, if it's still not there. (BTW, you can write to repository@, someone will moderate it through if you're not subscribed (which you're welcome to do if you want).) -- Wendy
Re: [VOTE] release for myfaces build tools archetypes 1.0.0
On Jan 27, 2008 12:18 PM, Wendy Smoak <[EMAIL PROTECTED]> wrote: > Okay, but the idea here is to make it easy for other people to test, > so they'll vote. :) Here are my notes from testing: http://wiki.wsmoak.net/cgi-bin/wiki.pl?MyFacesArchetypes -- Wendy
Re: [VOTE] release for myfaces build tools archetypes 1.0.0
On Jan 27, 2008 11:44 AM, Leonardo Uribe <[EMAIL PROTECTED]> wrote: > Yes, the number of this release is 1.0.0 > > This example comes from my tests for this on my local machine Okay, but the idea here is to make it easy for other people to test, so they'll vote. :) +1 from me, all the archetypes work, the resulting projects build, and the three webapps worked for me in Tomcat 6.0. I spot-checked for .asc signature files (but did not verify them) and checked that LICENSE/NOTICE were in one of the archetype jars. Some thoughts: * make 'mvn jetty:run' work for a project generated from an archetype * change the groupid to org.apache.myfaces.archetypes? * should we arrange it so that LICENSE/NOTICE is in the generated project? Nice job! It's good to finally see these get released. -- Wendy
Re: [VOTE] release for myfaces build tools archetypes 1.0.0
On Jan 26, 2008 9:47 AM, Leonardo Uribe <[EMAIL PROTECTED]> wrote: > One example of how to use this archetypes is this: > > mvn archetype:create -DarchetypeGroupId=org.apache.myfaces.buildtools > -DarchetypeArtifactId=myfaces-archetype-helloworld > -DarchetypeVersion=1.0.1 -DgroupId=org.apache.myfaces.test > -DartifactId=myfaces-helloworld I got this one to work with the following: mvn archetype:create -DarchetypeGroupId=org.apache.myfaces.buildtools \ -DarchetypeArtifactId=myfaces-archetype-helloworld \ -DarchetypeVersion=1.0.0 -DgroupId=com.example \ -DartifactId=myfaces-helloworld \ -DremoteRepositories=http://people.apache.org/~lu4242/m2-archetypes-100 (It had the wrong version number (this is a vote for 1.0.0, correct?) and needs -DremoteRepositories until the archetypes are in the central repo.) Looks good so far, the resulting war worked fine in Tomcat 6.0.14. (I'd like to see 'mvn jetty:run' work in a future release, if that's possible.) I'll vote in a little while after I check the others. -- Wendy
Re: Related Task for release Myfaces 1.2.2
On Jan 27, 2008 10:37 AM, Leonardo Uribe <[EMAIL PROTECTED]> wrote: > Does anyone knows how to update this pages > > http://myfaces.apache.org/download.html > and > http://myfaces.apache.org This should be documented on the wiki, (if not please add it!) The source for the top-level site is here: https://svn.apache.org/repos/asf/myfaces/site/trunk 'mvn site' or 'mvn site:run' to see it locally, then 'mvn site-deploy' will build and deploy the website. (Or 'mvn site:deploy if you've already built it locally.) -- Wendy
Re: [Build tools] Snapshots not working
On Jan 26, 2008 4:23 PM, Leonardo Uribe <[EMAIL PROTECTED]> wrote: > checking the snapshots: > > > http://people.apache.org/repo/m2-snapshot-repository/org/apache/myfaces/buildtools/ > > Only myfaces-plugin-parent is deployed > > All buildtools is necessary to update because myfaces 1.2.3-SNAPSHOT > should depend of > buildtools 1.0.0-SNAPSHOT > > Could anyone know how to fix this? 'mvn deploy' :) I started to do it, but it's not clear exactly what artifacts you want deployed, and when I looked at maven/build-tools/pom.xml I had a few concerns. It should have a parent-- either myfaces-master or directly up to the Apache master pom, if that makes sense. The id for the snapshots repo should be "apache.snapshots" (so I don't have to add yet another element to settings.xml) and the url should be people.apache.org, not minotaur. (Actually the snapshots repo in distribution management section should be inherited, it's the same for everything.) -- Wendy
Re: [Tobago] Introduction of Dojo
On Jan 26, 2008 11:30 AM, Volker Weber <[EMAIL PROTECTED]> wrote: > How can i make maven-war-plugin put the dojo.zip into WEB-INF/lib? > > i tryed > > > org.dojotoolkit > dojo-release > 1.0.1 > zip > runtime > > > and installed it to local repository, but it ended not in the war. Try removing the scope element. (Though I'm not sure whether a zip in WEB-INF/lib is going to work...) -- Wendy
Re: [Tobago] Introduction of Dojo
On Jan 26, 2008 10:00 AM, Volker Weber <[EMAIL PROTECTED]> wrote: > I'm going to try out if we can use the zipped dojo as a dependency, > even if its not in a maven repos, instead of shipping it unpacked in > the theme jar. As long as the license permits, we should be able to get it uploaded. I'm surprised it's not there already! If we're not making any changes to the source, it would be much better to pull it in and unpack it than to have the whole thing in our svn repo. (Even if we do have changes, we could overlay them after unpacking.) -- Wendy
Re: [VOTE] release for myfaces build tools archetypes 1.0.0
On Jan 25, 2008 3:52 PM, Leonardo Uribe <[EMAIL PROTECTED]> wrote: > Someone with time to check this? I think you might get more interest if you explain what an archetype is, and give some sample commands for how to try them out. If I'm not mistaken, this will be the first release for them. >From the title it's not clear if these are "tools" (just jars that get used during the build) or really Maven archetypes (which I think is the case, but again not everyone knows what that is.) Is 1.2.2 in the central repo yet? That will make it easier to test these out. HTH, -- Wendy
Re: [MyFaces 1.2.2] so... why is there no 1.2.1 (was: Re: svn commit: r613971 - /myfaces/core/branches/1_2_2prepare/)
On Jan 21, 2008 1:18 PM, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > the next logical step would be a 1.2.1, IMO. > we would confuse the people much more in just providing a 1.2.2 now, IMO. > I am pretty sure, that a 1.2.2 will even confuse our community a bit. So how > to > manage not confusing others? Like vendors, that plan to provide support for > MyFaces ? I really think it is not a good a idea to release a 1.2.2 after > 1.2.0. I don't agree. Tomcat skips versions occasionally with no ill effects, and so does Struts. (Occasionally someone asks "what happened to x.x.x on the mailing list" but that's all.) -- Wendy
Re: [Vote] MyFaces site design
On Jan 8, 2008 2:32 PM, Matt Cooper <[EMAIL PROTECTED]> wrote: > One minor change for all of the designs is the name of "Apache" in "Apache > Software Foundation". I'm not sure it is supposed to be capitalized as > "APACHE" so that'd be the only change I'd recommend. Actually... it's supposed to be "The Apache Software Foundation". We're very attached to our "The". :) -- Wendy
Re: partial set of core-1.2.1 artifacts published on 22 dec
On Jan 6, 2008 8:55 AM, Wendy Smoak <[EMAIL PROTECTED]> wrote: > I edited the maven-metadata.xml files to say "1.2.0" instead > of "1.2.1" just now, and posted to [EMAIL PROTECTED] asking for the 1.2.1 > files to be removed from central. That was fast. :) Carlos removed the 1.2.1 directories from the central repo, and I expect the metadata will sync in a few hours when the next automated process runs. Back on the subject of renaming tags... what if we continue tagging with the real version number, but if the vote does *not* pass, go back and rename the tag with -RC to indicate it was never released? Adding a README file in the root of the tag might also work... Which reminds me, I started a STATUS file a while ago trying to keep track of all the branches and versions around here, but I don't think it's been kept up. -- Wendy
Re: partial set of core-1.2.1 artifacts published on 22 dec
On Jan 6, 2008 4:46 AM, simon <[EMAIL PROTECTED]> wrote: > But the problem is that the files published are only a *partial* release > (myfaces-project and myfaces-impl, but not myfaces-build or > myfaces-api). All the artifacts need to go out together to form a valid > release AFAIK. I'm not sure what effect this will have on users, but it > doesn't seem like a good idea to leave them there.. > > The fact that they were released too early is a mistake. The fact that > only a partial release happened is due to bad file permissions on the > myfaces-build directory, making it unwritable except for the owner. I've > emailed the current owner of that dir asking for g+w to be added. Agreed. I just wasn't comfortable asking root to remove the files, (since the vote *did* pass) and suggested waiting for the file owner. > The bad dirs have now been removed from people.apache.org. However the > maven release process actually *overwrites* the metadata files in the > parent dir, and we have no copies of the old files AFAIK. So if we do > get the bad dirs removed from repo1.maven.org and mirrors, does this fix > the problem or will the bad metadata files still stuff users up? Bad metadata for a released jar artifact (as opposed to a snapshot or a plugin) isn't going to cause too much of a problem. If someone is trying to use version ranges, it might. But if you declare a dependency on a specific version, Maven just constructs the url and grabs the file, without checking the metadata. Maven isn't overwriting the metadata, we are. :) But only because the tool that properly merges a new release into an existing repository (updating the metadata rather than overwriting it) hasn't emerged from the sandbox yet. It's maven-stage-plugin, and it's already being used for Maven project releases. So the MyFaces metadata has been technically wrong for a long time, though it's usually just missing old releases, rather than mentioning one that does not exist as it does now. Or, did. I edited the maven-metadata.xml files to say "1.2.0" instead of "1.2.1" just now, and posted to [EMAIL PROTECTED] asking for the 1.2.1 files to be removed from central. > I guess the other solution is to just do nothing until the *real* 1.2.1 > release goes out, overwriting the bad files. I believe that is expected > to happen in the next week or so. But I feel a little uncomfortable > about that, and at the least we would need to notify the user list. IMO there should not be a "real" 1.2.1 release now -- we should move on to 1.2.2 to avoid confusion in case anyone has downloaded these bad jars. In general I'm not opposed to a "do-over" if the RM quickly deletes a tag and tries again, but the longer a set of files has been available, the greater chance of having to deal with "well, _which_ 1.2.1 jars do you have?" type support questions. -- Wendy
Re: svn commit: r609231 - /myfaces/core/trunk/impl/pom.xml
On Jan 5, 2008 3:54 PM, simon <[EMAIL PROTECTED]> wrote: > > On Sat, 2008-01-05 at 22:36 +, [EMAIL PROTECTED] wrote: > > Author: wsmoak > > Date: Sat Jan 5 14:36:31 2008 > >
Re: partial set of core-1.2.1 artifacts published on 22 dec
On Jan 5, 2008 10:06 AM, simon <[EMAIL PROTECTED]> wrote: > Leonard has been struggling with Maven (and I know how he feels). Just > some misunderstanding I expect. > > Unfortunately the files that are in the sync directory on > people.apache.org are owned by lu4242 (leonard) and have only read > permissions for group. So no-one but Leonard or root can remove them. Best wait for him then? As far as I can tell, it did get enough votes: http://www.nabble.com/-VOTE--release-for-MyFaces-1.2.1-td14440257.html At the end, Matthias mentions that it didn't pass the TCK. I don't think that invalidates a PMC vote to release, though we are under some restrictions about calling it an official JSF implementation. (I"m not clear on the details here.) Thoughts? -- Wendy > > BTW, this permissions problem appears to be common to many of the dirs > (files owned by the deployer with only read for group); I guess the > deploy instructions need to be updated to include how to set fileperms > correctly. > > > > > > I also see that there is a tag for 1.2.1 in svn: > > > http://svn.apache.org/repos/asf/myfaces/core/tags/1_2_1/ > > > > > > This seems like a bad idea as there is no 1.2.1 release in existence. If > > > a tag is needed for the release-candidate, then the dir name should have > > > "RC" in it, and be renamed to the final 1_2_1 name after publication of > > > the release candidate as an actual release. Does the > > > maven-release-plugin allow this? > > > > It's not a problem for there to be a tag and staged artifacts that > > never passed a vote. They just shouldn't be available for download as > > an official release. > > I think it *is* bad for there to be a directory in subversion that > really looks like a tag for an official release, although the release > has not happened. > > Someone else mentioned that the maven-release-plugin does prompt for the > tagname to create. So in the myfaces situation, the release manager > really should add "-rc" on the end of the proposed name, as there can be > a couple of weeks between the rc being built and it passing the TCK. > Actually, I would think that it would be better for the release plugin > to add -rc by default. > > Regards, > > Simon > >
Re: partial set of core-1.2.1 artifacts published on 22 dec
On Jan 5, 2008 10:06 AM, simon <[EMAIL PROTECTED]> wrote: > I think it *is* bad for there to be a directory in subversion that > really looks like a tag for an official release, although the release > has not happened. A Subversion tag != a release. Only a vote makes a release. There are plenty of tags around the ASF svn repo that never turned into releases. For example, compare http://svn.apache.org/repos/asf/tomcat/tc6.0.x/tags/ with http://archive.apache.org/dist/tomcat/tomcat-6/ . The way it's set up now, we stage and vote on the actual bits that will be released, including the tag. Of course it's up to the release manager how to handle it, but I'm not in favor of adding a required manual step (renaming a tag) to the release process. -- Wendy
Re: Continuum server
On Jan 5, 2008 9:26 AM, simon <[EMAIL PROTECTED]> wrote: > I'm trying to reach the myfaces continuum server at > http://myfaces.zones.apache.org:8080/continuum > but getting no response (nothing appears to be listening on 8080). > > This url is functional: > http://myfaces.zones.apache.org/ > > Does anyone know what might be happening? Sounds like httpd is running, but not Continuum. This page has my notes, I don't know what's happened to it since then... http://wiki.apache.org/myfaces/Continuum_Build There's a shared Continuum instance at http://vmbuild.apache.org/continuum/groupSummary.action also. -- Wendy
Re: partial set of core-1.2.1 artifacts published on 22 dec
On Jan 4, 2008 12:31 PM, simon <[EMAIL PROTECTED]> wrote: > Matt has pointed out on the user list that the official maven repo has > some artifacts from core-1.2.1, dated 22 dec. > > http://repo1.maven.org/maven2/org/apache/myfaces/core/myfaces-core-project/ > http://repo1.maven.org/maven2/org/apache/myfaces/core/myfaces-impl/ > > There are core-project and myfaces-impl from 1.2.1, but no myfaces-api. > > I guess these were accidentally published, and that they should be > removed from the mirrors ASAP. Anyone know how this can be done? I'd delete them from the m2-ibiblio-rsync-repository, and then write to [EMAIL PROTECTED] stating that they were not officially released and requesting that they be removed from central. Carlos or Jason will probably have to get involved. Any idea how it happened? > I also see that there is a tag for 1.2.1 in svn: > http://svn.apache.org/repos/asf/myfaces/core/tags/1_2_1/ > > This seems like a bad idea as there is no 1.2.1 release in existence. If > a tag is needed for the release-candidate, then the dir name should have > "RC" in it, and be renamed to the final 1_2_1 name after publication of > the release candidate as an actual release. Does the > maven-release-plugin allow this? It's not a problem for there to be a tag and staged artifacts that never passed a vote. They just shouldn't be available for download as an official release. -- Wendy
Re: myfaces master pom
On Jan 1, 2008 10:13 AM, simon <[EMAIL PROTECTED]> wrote: > Hi, > > We appear to have two "master" pom files: > 1: http://svn.apache.org/repos/asf/myfaces/maven/trunk/master-pom/ > 2: http://svn.apache.org/repos/asf/myfaces/myfaces-master-pom/trunk/ There was some discussion about the master pom in this thread... http://www.nabble.com/-proposal--New-MyFaces-Master-POM-td13444387.html -- Wendy
Re: [Tobago] apt-plugin JDK tools.jar dependency
On Dec 27, 2007 3:26 PM, Evan Worley <[EMAIL PROTECTED]> wrote: > Hello all, > > Below is a thread that originated on the maven developers list. It seems > that the maven-apt-plugin could use some more infrastructure around > resolving the dependency on the JDK's tools.jar. Here is the original > thread, any thoughts would be great. Struts 2 is also using this plugin... if it's not JSF-specific, does it make sense to take it over to the Codehaus Mojo project where it would be easier to collaborate on? Brett pointed out that there is another apt plugin over there in the sandbox; I'm not sure if they're related. -- Wendy
Re: site restructure
On Dec 15, 2007 1:13 PM, Simon Kitching <[EMAIL PROTECTED]> wrote: > Note that AFAIK there is no way for a menu on the left navbar to have a > "submenu". There's an example of sub-menus on the Continuum site. Is this what you want? http://maven.apache.org/continuum/documentation/1_1/administrator_guides/security/ldap.html Here's the site.xml for it. It looks like you just keep nesting elements, and each menu can either be collapsed, or not. http://svn.apache.org/repos/asf/maven/continuum/trunk/continuum-site/src/site/site.xml -- Wendy
Re: Java version compatibility (was Re: svn commit: r605927 - /myfaces/tomahawk/trunk/core/src/main/java/org/apache/myfaces/dateformat/SimpleDateFormatter.java)
On 12/20/07, Simon Kitching <[EMAIL PROTECTED]> wrote: > Mike Kienenberger <[EMAIL PROTECTED]> schrieb: > > Can't you do something like this to force the rt.jar to be 1.4? > > > > http://java.sun.com/j2se/1.5.0/docs/tooldocs/windows/javac.html > > > > % javac -target 1.4 -bootclasspath jdk1.4.2/lib/classes.zip -extdirs > > "" OldCode.java > > Yep. However that cannot be put into the pom because the location of the > jdk1.4 will be different on everyone's machine - if they have it installed at > all. > > And because it isn't automatic, most people won't bother to set it up. I'm > not sure I would... Continuum 1.1 has the ability to execute builds using a specific JDK, build tool version and/or environment variables in a kind of "Build Environment". (It's currently called a "Build Profile" which is horribly confusing, since it's completely different from the element in the pom. I'm working on getting it renamed. :) ) -- Wendy
Re: [site] preferred doc format for website
On Dec 15, 2007 7:29 AM, Simon Kitching <[EMAIL PROTECTED]> wrote: > I'm experimenting with some changes to the myfaces site. > > I see that there are some files in maven APT format, and some in XDOC. Which > is the preferred format for files? > > In particular, I'd like to split docs into versions that explicitly talk > about either JSF11 or JSF12. Which format should I write the new files in? > > Personally, I'm currently neutral. XML can be a pain sometimes, and is less > readable in raw form. However xdoc is a standard while APT is > maven-specific. AFAIK, both formats initially came from somewhere else and have been modified slightly in Maven land. Probably neither of them would work in their original homes now. Either format is fine with me-- he who does the work gets to choose. :) If I were to write something it would be in APT because I prefer the simpler syntax. -- Wendy
Re: [proposal] New MyFaces Master-POM
On 10/27/07, Manfred Geiler <[EMAIL PROTECTED]> wrote: > Wendy, I think this repo info in our myfaces master is redundant: > > apache.snapshots > http://people.apache.org/repo/m2-snapshot-repository > > > since it is already defined in the asf master: +1 > BUT. I wonder why there is no "true" in it. Is > "true" the default anyway? Could not find anything in the maven docs. True is the default for both snapshots and releases, so you only need to turn "off" the one you do not want. -- Wendy
Re: [proposal] New MyFaces Master-POM
On 10/27/07, Manfred Geiler <[EMAIL PROTECTED]> wrote: > rev 412444 07.06.2006 18:13:29 grantsmith > "MYFACES-1325: Mods to pom.mxl for correct continuum reporting" > > Well... Remove it and see what breaks. :) He who complains should write better commit messages! > So, the master does not really depend on the build-tools artifact - at > least not the maven way. It catches the latest stuff from svn > directly. Now, what about having those two files directly in the new > master root: > /repos/asf/myfaces/myfaces-master-pom/pom.xml > /repos/asf/myfaces/myfaces-master-pom/myfaces-checks.xml > /repos/asf/myfaces/myfaces-master-pom/myfaces-header.txt > > Or is there a better way than to depend on an online (http: !) ressource? The checkstyle config does not belong to the master pom. IMO, build-tools is a better place for it. I think what happened is that we started to establish a build-tools jar, then decided it was too much of a pain to have to version and release it, and went for the http:// urls. The jar is the "correct" way to do it, but I don't consider it all that importantt to be able to faithfully reproduce the exact website with the checkstyle reports for prior releases. -- Wendy
Re: Wrong link
On 10/26/07, Martin Marinschek <[EMAIL PROTECTED]> wrote: > Hi Wendy, > > is this ok? That looks fine... what I'm not entirely sure of is whether that feature has made it into a release yet! -- Wendy
Re: [proposal] New MyFaces Master-POM
On 10/27/07, Manfred Geiler <[EMAIL PROTECTED]> wrote: > Proposal for a MyFaces maven master pom refactoring. > > The current maven master pom for MyFaces has some flaws: > > 1. Not used by all MyFaces (sub)projects. > Currently Tobago has no parent pom and Trinidad uses > org.apache:apache:4 directly. This is not a flaw in the master pom, but rather in those sub-projects. :) > 2. Located in the "maven" folder (i.e. > org.apache.myfaces.maven:maven-project artifact). > The MyFaces maven project is currently a mixture of maven related > stuff. Having the master(!) located within this sub project is a bad > idea. Where it lives on the filesystem, and where it sits in the pom hierarchy are separate matters. It can stay in a "maven" directory, but inherit directly from the ASF master pom (which it does). I think the easiest thing here is to get rid of the 'maven-project' pom altogether. Each thing in the "maven" directory (rename it if you want...) is a separate item either extending from the myfaces-master pom or (in the case of the myfaces-master pom itself) from the ASF parent pom. They do not (collectively) need a parent pom listing them as modules. I don't care if you want to make the master pom separate with its own trunk/branches/tags, but it doesn't seem necessary. > The master pom should be it's own project, depending only on the > org.apache:apache master pom and ALL other MyFaces projects should > derive from it. +1 > 3. Version numbering. > I propose "8" as the first number after the pom move/refactoring. +1 > 4. There is stuff in the myfaces master that is NOT common (or even > unused?) to all myfaces projects and should not be there IMHO. These > are: > 4a. Wagon extension. Who needs this? > >org.apache.maven.wagon >wagon-ssh-external >1.0-alpha-5 > What does the commit log say when it was added? Someone must have needed it... > 4b. Myfaces build tools as extension. Who needs this? > > org.apache.myfaces.maven > build-tools > 1.0.7-SNAPSHOT > It probably has the checkstyle rules in it... and yes, it would be nice to agree on a set of rules across the project. -- Wendy
Re: svn commit: r588624 - /myfaces/site/trunk/pom.xml
As mentioned on the other thread, please change this back to the actual location of the code in svn. The project-info-reports-plugin can be configured to use a different url for the source-repository.html page. -Wendy On 10/26/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Author: mmarinschek > Date: Fri Oct 26 05:26:50 2007 > New Revision: 588624 > > URL: http://svn.apache.org/viewvc?rev=588624&view=rev > Log: > changed myfaces/site/trunk to myfaces/current > > Modified: > myfaces/site/trunk/pom.xml > > Modified: myfaces/site/trunk/pom.xml > URL: > http://svn.apache.org/viewvc/myfaces/site/trunk/pom.xml?rev=588624&r1=588623&r2=588624&view=diff > == > --- myfaces/site/trunk/pom.xml (original) > +++ myfaces/site/trunk/pom.xml Fri Oct 26 05:26:50 2007 > @@ -33,8 +33,8 @@ > > > > - > scm:svn:http://svn.apache.org/repos/asf/myfaces/site/trunk > - > scm:svn:https://svn.apache.org/repos/asf/myfaces/site/trunk > + > scm:svn:http://svn.apache.org/repos/asf/myfaces/current > + > scm:svn:https://svn.apache.org/repos/asf/myfaces/current > http://svn.apache.org/viewcvs.cgi/myfaces/current > > > > >
Re: Wrong link
On 10/26/07, Martin Marinschek <[EMAIL PROTECTED]> wrote: > While working on the PB, I realized the following: > > http://myfaces.apache.org/source-repository.html > > the links further down point to the wrong source-directory. I think > this is as the pom of the site module sets this... I just changed the > entries in this pom, but in the end, probably the settings of the > master-pom should be used directly. WDYT? The scm connection and developerConnection should be the real location of that module in svn. (So please put it back, or Continuum and other things that use the scm url won't work.) I added some optional parameters to the project-info-reports-plugin scm report a while back, so you can configure the plugin to use a different url for the web page. See: http://maven.apache.org/plugins/maven-project-info-reports-plugin/scm-mojo.html Thanks, -- Wendy
Re: Nightly-Builds
On 10/21/07, Bernd Bohmann <[EMAIL PROTECTED]> wrote: > Tobago is still using the zone. Just added the myfaces nighlty build to > the zone again. The continuum server is running on port 8080 and the > admin account has the same password as suggested by wendy on the pmc list. Each person should sign up for an account and get someone to make him an administrator. Then we can unlock each other when passwords are forgotten. :) -- Wendy
Re: [Announce] Release of Apache MyFaces Orchestra 1.0
On 10/12/07, Dan Tran <[EMAIL PROTECTED]> wrote: > when do we expect to see orchestra-core-1.0 at repo1.maven.org/maven2 ? > > dont see it there yet!! I pinged the repository list to ask someone to check on the sync. -- Wendy
Re: svn commit: r582644 - in /myfaces/orchestra/trunk: core/pom.xml maven/pom.xml
This should be 'people.apache.org' (not minotaur). -Wendy On 10/7/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Author: imario > Date: Sun Oct 7 09:38:00 2007 > New Revision: 582644 > > URL: http://svn.apache.org/viewvc?rev=582644&view=rev > Log: > backport pom changes from 1.0 tag > > Modified: > myfaces/orchestra/trunk/core/pom.xml > myfaces/orchestra/trunk/maven/pom.xml > > Modified: myfaces/orchestra/trunk/core/pom.xml > URL: > http://svn.apache.org/viewvc/myfaces/orchestra/trunk/core/pom.xml?rev=582644&r1=582643&r2=582644&view=diff > == > --- myfaces/orchestra/trunk/core/pom.xml (original) > +++ myfaces/orchestra/trunk/core/pom.xml Sun Oct 7 09:38:00 2007 > @@ -186,6 +186,14 @@ > > > > + > + > + apache-site > + Apache Website > + > scpexe://minotaur.apache.org/www/myfaces.apache.org/orchestra/myfaces-orchestra-core > + > + > + > > > > @@ -372,4 +380,4 @@ > > > > - > \ No newline at end of file > + > > Modified: myfaces/orchestra/trunk/maven/pom.xml > URL: > http://svn.apache.org/viewvc/myfaces/orchestra/trunk/maven/pom.xml?rev=582644&r1=582643&r2=582644&view=diff > == > --- myfaces/orchestra/trunk/maven/pom.xml (original) > +++ myfaces/orchestra/trunk/maven/pom.xml Sun Oct 7 09:38:00 2007 > @@ -116,7 +116,7 @@ > > apache-site > Apache Website > - > scpexe://minotaur.apache.org/www/myfaces.apache.org/orchestra > + > scpexe://minotaur.apache.org/www/myfaces.apache.org/orchestra/myfaces-orchestra-maven > > > > @@ -213,4 +213,4 @@ > > 2.0.7 > > > - > \ No newline at end of file > + > > >
Re: GuiceFaces
On 10/2/07, Dennis Byrne <[EMAIL PROTECTED]> wrote: > I've thrown together a couple of different ways of getting MyFaces to use > Guice (similar to > org.springframework.web.jsf.DelegatingVariableResolver ). > I would like a place to commit this but some of this code (a custom > ELResolver) depends on JSP 2.1 . Taking this code along the > sandbox->tomahawk route will obviously interfere w/ the dependencies that > are already in those pom files. Thoughts on the following? Create a myfaces/sandbox/guicefaces directory at the very top of the repo so it's separate from everything else? -- Wendy
Re: Continuum
On 9/18/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > there was a continuum server (port 8081) on our zone, currently down. > The vmbuild, I can't deploy stuff, does only build... > > What is the current plan, do we want to move all our projects to > Brett's vmbuild ? Yes please. We have a group of volunteers to maintain vmbuild, and the zone machine is low on resources; infra would prefer we didn't run applications on it. I've never been comfortable with the way we publish from the zone to people.a.o. We'll probably need to turn it around and run something on people.a.o that pulls content over from vmbuild. -- Wendy
Re: svn commit: r573765 - in /myfaces/trinidad-maven/trunk: ./ maven-faces-plugin/ maven-i18n-plugin/ maven-javacc-plugin/ maven-javascript-plugin/ maven-jdev-plugin/ maven-tagdoc-plugin/ maven-xrts-p
On 9/8/07, Wendy Smoak <[EMAIL PROTECTED]> wrote: > On 9/7/07, Adam Winer <[EMAIL PROTECTED]> wrote: > > > @Matthias, can you take care of the Continuum fix? > > Done. ... and I deleted them from Continuum on the MyFaces zone. We need to get the rest of the MyFaces builds moved over so we can shut that one down. -- Wendy
Re: [TRINIDAD] Maven Plugin version: 1.0.3 or 1.2.3
On 9/8/07, Adam Winer <[EMAIL PROTECTED]> wrote: > I've moved the Trinidad Maven Plugins to their own sub-repository. > The codebase is really the 1.2 codeline. > > The question is, should the version number of the next release be: > - 1.0.3 > - 1.2.3 > - Something else? I thought it was odd that the version number went backwards when the code was moved, which presents the opportunity for duplicate version numbers at some future time. I don't think the version number needs to be tied to the JSF spec level, just pick a number and advance versions based on the changes and whatever rules you use, such as major.minor.patch. -- Wendy
Re: svn commit: r573765 - in /myfaces/trinidad-maven/trunk: ./ maven-faces-plugin/ maven-i18n-plugin/ maven-javacc-plugin/ maven-javascript-plugin/ maven-jdev-plugin/ maven-tagdoc-plugin/ maven-xrts-p
On 9/7/07, Adam Winer <[EMAIL PROTECTED]> wrote: > @Matthias, can you take care of the Continuum fix? Done. -- Wendy
Re: svn commit: r573765 - in /myfaces/trinidad-maven/trunk: ./ maven-faces-plugin/ maven-i18n-plugin/ maven-javacc-plugin/ maven-javascript-plugin/ maven-jdev-plugin/ maven-tagdoc-plugin/ maven-xrts-p
On 9/7/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Author: awiner > Date: Fri Sep 7 17:47:54 2007 > New Revision: 573765 > > URL: http://svn.apache.org/viewvc?rev=573765&view=rev > Log: > Update version number and SCM info These need to be deleted and re-added in Continuum, it's trying to 'svn up' the old location. http://vmbuild.apache.org/continuum/groupSummary.action Why did the version number go backwards? -- Wendy
Re: [Trinidad] maven problem
On 9/1/07, Andrew Robinson <[EMAIL PROTECTED]> wrote: > Sorry never mind, it is a bug with the plugin: > > http://mojo.codehaus.org/findbugs-maven-plugin/usage.html Not sure that's a bug... did you try increasing the heap size? Some things just take more than the default. > Anyone know if it is possible to suppress these reports when staging > locally without changing the pom? http://mojo.codehaus.org/findbugs-maven-plugin/findbugs-mojo.html Not sure if it works at the command line or only in the pom, but you can try: -Dfindbugs.skip=true -- Wendy
[jira] Commented: (MYFACES-1664) JSR-301 Implementation
[ https://issues.apache.org/jira/browse/MYFACES-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524286 ] Wendy Smoak commented on MYFACES-1664: -- Scott, can you please supply a md5 checksum for the zip file? It's one of the things needed on the IP clearance form. > JSR-301 Implementation > -- > > Key: MYFACES-1664 > URL: https://issues.apache.org/jira/browse/MYFACES-1664 > Project: MyFaces Core > Issue Type: New Feature > Components: Portlet_Support >Affects Versions: 1.2.0-SNAPSHOT > Environment: JSR-168, JSF 1.2 >Reporter: Scott O'Bryan > Attachments: jsf-portlet-bridge.zip > > > MyFaces 1.2 does not currently have a JSR-301 subproject. Work should begin > on JSR-301 as bridge support for the MyFaces 1.2 branch. Trinidad is > currently dependant on this project for bridge support and other Renderkits > may wish to use this standards based bridge as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [PORTAL] Liscencing (was: [PORTAL] JSR-301 Portlet Bridge uploaded)
On 9/1/07, Martin Marinschek <[EMAIL PROTECTED]> wrote: > Should we ask on [EMAIL PROTECTED] if there is someone who wants to support > us? Shouldn't be too complicated, right? As soon as I get a link / the > document, I'll ask there. (Not following this one closely, but) follow the instructions here: http://incubator.apache.org/ip-clearance/index.html Commit the IP clearance form, update the index page, post to [EMAIL PROTECTED] and wait three days... it's not a vote there, just lazy consensus. -- Wendy
Re: svn commit: r567449 - in /myfaces/orchestra/trunk: core/src/main/resources/META-INF/LICENSE.txt core15/src/main/resources/META-INF/LICENSE.txt examples/src/main/resources/META-INF/LICENSE.txt
On 8/19/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Author: imario > Date: Sun Aug 19 11:17:41 2007 > New Revision: 567449 > > URL: http://svn.apache.org/viewvc?view=rev&rev=567449 > Log: > added license file The remote resources plugin can do this for you. It also generates the notice file based on the declared dependencies. -- Wendy
Re: [commits] efastl commits on weekend
On 7/19/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: Very strange... I just got a bunch of "old" commit messages, from you. Likely they were stuck in moderation and someone let them through... -- Wendy
Re: Continuum server down?
On 7/15/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: Should we ask him now ? Or, have you already pinged Brett ? Brett, please add MyFaces to the list for vmbuild. -- Wendy
Re: Continuum server down?
On 7/12/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: down again? should we move to Brett's vmbuild machine ? +1 Much more efficient to help maintain that one, than to do it all ourselves. -- Wendy
Re: Continuum server down?
On 7/4/07, Bernd Bohmann <[EMAIL PROTECTED]> wrote: Restarted again. And it stays running? It didn't for me. Maybe we should try the alpha-2 version? I uploaded and unpacked alpha-2, so it's there if you'd like to edit the scripts and switch over. I *think* the database schema is compatible between alpha-1 and alpha-2 so it should just work, but... -- Wendy
Re: Continuum server down?
On 6/28/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: Can somebody grant me admin rights ? Done. -- Wendy
Re: Continuum server down?
Who fixed Continuum? Thanks! And please update the wiki with whatever magic you performed... http://wiki.apache.org/myfaces/Continuum_Build -- Wendy
Re: Continuum server down?
It's down again and this time it's complaining about the database and doesn't want to re-start. I suspect running a Java database out of memory is not a good thing... I won't have time to work on it until the weekend, so if anyone else wants to jump in, feel free. Upgrading to 1.1-alpha-2 would be good. -- Wendy
Re: Any guidelines for new contributions?
On 6/17/07, Andrew Robinson <[EMAIL PROTECTED]> wrote: Okay, I tried the "mvn clean site:site site:deploy" from in the sandbox/core directory, and although it said it succeeded, the site doesn't show the changes. How long ago? The site syncs to the live server hourly at most, possibly longer. -- Wendy
Re: Any guidelines for new contributions?
On 6/17/07, Andrew Robinson <[EMAIL PROTECTED]> wrote: I committed my changes to the sandbox (component in one commit and then the site documentation in apt format in another commit), and the page is not updated on the site. Still getting a 404 error around 8 hours after the commit: http://myfaces.apache.org/sandbox/limitRendered.html Any ideas? It doesn't look like the sandbox site gets published by Continuum: http://myfaces.zones.apache.org:8081/continuum/groupSummary.action -- Wendy
Re: [Build] Trinidad
On 6/14/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: On 6/14/07, Wendy Smoak <[EMAIL PROTECTED]> wrote: > > the assembly tries download that stuff, that the same build was > > building 10 secs before > > :-) > > > > any idea? > > What versions of Maven and the assembly plugin? Sounds vaguely > familiar but I can't find an issue in a quick search. I can live with > 'mvn install' just building all the modules for now... 2.2-beta-1. Is there any *template* I can look at? And what version of Maven? I think it's this, fixed in 2.0.6: http://jira.codehaus.org/browse/MNG-2434 -- Wendy
Re: [continuum] BUILD FAILURE: Apache MyFaces Trinidad Build
On 6/14/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: Is this maven weirdness ? Depends. It's complaining that it can't find some snapshots, and the fact that it's only listing the central repo makes me think that a repository/pluginRepository definition for the snapshot repo is missing. I haven't looked at the build though. -- Wendy
Re: [Build] Trinidad
On 6/14/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > > Maven builds should > > Just Work. I was smiling already yesterday on this, and now my guess is reality. I said they *should* not that they *do* just yet. We're working on it. ;) the assembly tries download that stuff, that the same build was building 10 secs before :-) any idea? What versions of Maven and the assembly plugin? Sounds vaguely familiar but I can't find an issue in a quick search. I can live with 'mvn install' just building all the modules for now... -- Wendy
Re: [Build] Trinidad
On 6/13/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: ok, perhaps I introduce an "assembly" profile so that :prepare does the prepartion on all *important* artifacts. an optional profile like CORE could be introduced to just create build, api and impl I'd like to see a new person be able to check out the project, type 'mvn install', and build *everything* including the release assemblies. (They need to be 'assembly:attached' for this to work.) Needing to know secrets like what profiles to activate reminds me of the old Ant builds where you had to know what targets to execute, because every project did it a different way. Maven builds should Just Work. -- Wendy
Re: [Build] Trinidad
On 6/13/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: currently (in trunk) you run mvn install and get "all" (build, api, impl, demo) I'd like to change that. The default (mvn install) should create only build, api and impl to get all (above + examples (blank and demo)) mvn install -Pall-modules ... With that, we also will only deploy build, api, and impl to a maven repo. blank and demo will be only available via website download. The default build should create everything, so that 'mvn release:prepare' and 'mvn release:perform' increments all the version numbers, tags and deploys everything. If you don't want to sync the examples to the central Maven repo, delete that section of the staging repository before you copy/merge it over to the rsynced ASF repo. If you want a faster build, break the modules up into profiles that are activated on the absence of a property, for example !noapps. Then the profile is active _unless_ you specify -Dnoapps=xxx. -- Wendy
Re: Continuum server down?
On 6/12/07, Manfred Geiler <[EMAIL PROTECTED]> wrote: seems like it is up again... I just restarted it and added a note to the wiki. -- Wendy
Re: Checksum error on JSF RI artifacts on continuum server.
On 5/31/07, Paul Spencer <[EMAIL PROTECTED]> wrote: When I build Tomahawk locally, I do not see the errors. In addition I do not have javax.servlet.jsp:jsp-api:jar:1.2.0 in my local repository. I am wondering if the RI artifacts are corrupt/outdated for some strange reason. Based on the following, it appears the artifacts should not be used. Thus leading be to believe the RI artifacts on the continuum server are bad. What do you want me to do? If you want something deleted from mrmaven's local repo, give the groupId/artifactId. -- Wendy
Re: Checksum error on JSF RI artifacts on continuum server.
On 5/31/07, Paul Spencer <[EMAIL PROTECTED]> wrote: I am trying to add a build of Tomahawk against the RI, but there are Checksum errors on JSF RI artifacts on continuum server see[1]. What is the best way to resolve this? I believe the goal dependency:purge-local-repository will remove the artifacts, but it seems extreme since it will remove ALL dependencies. It looks to me like the build failure is due to a missing dependency, not bad checksums. Those are just warnings and are ignored. Or are you saying that javax.servlet.jsp:jsp-api:jar:1.2.0 is available in a public repo and Maven is refusing to download it? -- Wendy
Re: Continuum server down?
On 5/31/07, Paul Spencer <[EMAIL PROTECTED]> wrote: The Continuum server is not responding. Is it down? Looks like the JVM was hung again. Last time it was an odd Jetty OOME that I haven't had time to track down. Probably needs some settings adjusted. I restarted it using the scripts in ~mrmaven on the zone. There's a Continuum page on the wiki, if you do anything interesting, leave a note there. -- Wendy
Re: Branching tomahawk 2.0
On 5/28/07, Bruno Aranda <[EMAIL PROTECTED]> wrote: I would like to create a branch for tomahawk to start playing with the autogeneration of tomahawk components. So this is meant to be the branch for the future Tomahawk 2.0, that will work with jsf 1.2+. Any objections? Let's not choose a version number just yet... do branch and experiment, but call it jsf12_compat or something. Then when it comes time to merge into or replace the trunk, we can decide what version it is. -- Wendy
Re: svn commit: r542015 - /myfaces/core/branches/jsf12/pom.xml
On 5/27/07, Bruno Aranda <[EMAIL PROTECTED]> wrote: And how can we do that? It is only needed to build the myfaces-api and myfaces-impl artifacts and not for anything else... Try... ... * http://maven.apache.org/ref/2.0.6/maven-model/maven.html : Another option is to make it a dependency of a particular plugin, if that's appropriate. I don't know what's in this jar. -- Wendy
Re: svn commit: r542015 - /myfaces/core/branches/jsf12/pom.xml
I wonder if it should be a build extension instead of a dependency. -- Wendy On 5/27/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Author: baranda Date: Sun May 27 11:26:54 2007 New Revision: 542015 URL: http://svn.apache.org/viewvc?view=rev&rev=542015 Log: Fixes MYFAECS-1648 (myfaces-build should have scope "provided" as it is only needed on build time) Modified: myfaces/core/branches/jsf12/pom.xml Modified: myfaces/core/branches/jsf12/pom.xml URL: http://svn.apache.org/viewvc/myfaces/core/branches/jsf12/pom.xml?view=diff&rev=542015&r1=542014&r2=542015 == --- myfaces/core/branches/jsf12/pom.xml (original) +++ myfaces/core/branches/jsf12/pom.xml Sun May 27 11:26:54 2007 @@ -116,6 +116,7 @@ org.apache.myfaces.core myfaces-build 1.2.0-SNAPSHOT +provided org.apache.myfaces.core
Re: Starting over with Continuum on the MyFaces zone
On 5/13/07, Wendy Smoak <[EMAIL PROTECTED]> wrote: Continuum 1.1-alpha-1 is running here: http://myfaces.zones.apache.org:8081/continuum I have some time tomorrow afternoon/evening (GMT -7) to help if anything remains to be done to get the Continuum instance back where it was before the upgrade incident. Please let me know if there's something you'd like me to look at. Paul, thanks for your feedback in the Continuum JIRA! I was also able to point somone in the #continuum irc channel at our instance as a running example for a presentation he was making. -- Wendy
Re: What is nightly builds ?
On 5/22/07, Bernd Bohmann <[EMAIL PROTECTED]> wrote: I try to enable the nightly build for myfaces at the last weekend. I discovered one problem the nigthly build contains different svn urls for myfaces core, shared and tomahawk. I can't use the the same scheme as the tobago nightly. Now I try the old system for the myfaces nightly. The new Project Id of the nightly build is 166. I assume this means a script outside of Continuum. Can you please add some notes to the wiki so we know how to fix it next time? http://wiki.apache.org/myfaces/Continuum_Build Thanks, -- Wendy
Re: [PROPOSAL] Create a notifications mailing list
On 5/13/07, Wendy Smoak <[EMAIL PROTECTED]> wrote: I'd like to create [EMAIL PROTECTED] for automated messages from Continuum. The list has been requested: https://issues.apache.org/jira/browse/INFRA-1248 -- Wendy
Re: MyFaces PMC += Gabrielle Crawford
On 5/18/07, Gabrielle Crawford <[EMAIL PROTECTED]> wrote: duh, I should probably know this, but which site? Ah, it's a trick. :) Assuming you have the "current' svn external checked out [1] then edit maven/master-pom/pom.xml and add yourself or edit your information. That information gets used to generate the team list on the website: http://myfaces.apache.org/team-list.html And, welcome! [1] svn co https://svn.apache.org/repos/asf/myfaces/current myfaces -- Wendy
Re: Adding MyFaces site to continuum
On 5/16/07, Adam Winer <[EMAIL PROTECTED]> wrote:
Anyone see issues with my adding:
http://svn.apache.org/repos/asf/myfaces/site/trunk/pom.xml
... as a nightly "mvn deploy-site" on the continuum server?
Nope, have fun. :)
Paul, MYFACES-1631 might be solved by adding ${version} in the site
deployment url.
--
Wendy
Re: svn commit: r538387 [1/13] - in /myfaces/trinidad/trunk: plugins/maven-xrts-plugin/src/main/java/org/apache/myfaces/trinidadbuild/plugin/xrts/ trinidad/ trinidad/trinidad-api/src/main/java-templat
Were the changes to the xml files intentional? I don't see anything relevant in the commit message. On 5/15/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Author: awiner Date: Tue May 15 16:42:41 2007 New Revision: 538387 URL: http://svn.apache.org/viewvc?view=rev&rev=538387 Log: TRINIDAD-16: Resolve issues reported by FindBugs - Use the latest version of FindBugs to analyze the Trinidad codebase and fix reported problems. Most were stylistic, but a few genuine bugs were detected. Changes included: - Consistently use valueOf() instead of new Integer/Character/Short/Long/etc. - Avoid unnecessary toString() and new String() calls - A few synchronization issues, none especially significant - Make inner classes static were possible - Make constants static were this was missing - Make clones of arrays (mostly) consistently - Avoid String instance equality - Fix some incorrect null pointer checks - Fix some object equals() implementations Modified: myfaces/trinidad/trunk/plugins/maven-xrts-plugin/src/main/java/org/apache/myfaces/trinidadbuild/plugin/xrts/ListRTSWriter.java myfaces/trinidad/trunk/trinidad/pom.xml myfaces/trinidad/trunk/trinidad/trinidad-api/src/main/java-templates/org/apache/myfaces/trinidad/component/UIXIteratorTemplate.java myfaces/trinidad/trunk/trinidad/trinidad-api/src/main/java-templates/org/apache/myfaces/trinidad/component/UIXTableTemplate.java myfaces/trinidad/trunk/trinidad/trinidad-api/src/main/java-templates/org/apache/myfaces/trinidad/component/UIXTreeTableTemplate.java myfaces/trinidad/trunk/trinidad/trinidad-api/src/main/java/org/apache/myfaces/trinidad/bean/PropertyKey.java myfaces/trinidad/trunk/trinidad/trinidad-api/src/main/java/org/apache/myfaces/trinidad/bean/util/PropertyHashMap.java myfaces/trinidad/trunk/trinidad/trinidad-api/src/main/java/org/apache/myfaces/trinidad/bean/util/StateUtils.java myfaces/trinidad/trunk/trinidad/trinidad-api/src/main/java/org/apache/myfaces/trinidad/bean/util/ValueMap.java myfaces/trinidad/trunk/trinidad/trinidad-api/src/main/java/org/apache/myfaces/trinidad/change/ChangeComponentProxy.java myfaces/trinidad/trunk/trinidad/trinidad-api/src/main/java/org/apache/myfaces/trinidad/change/ReorderChildrenComponentChange.java myfaces/trinidad/trunk/trinidad/trinidad-api/src/main/java/org/apache/myfaces/trinidad/component/StampState.java myfaces/trinidad/trunk/trinidad/trinidad-api/src/main/java/org/apache/myfaces/trinidad/component/UIXCollection.java myfaces/trinidad/trunk/trinidad/trinidad-api/src/main/java/org/apache/myfaces/trinidad/component/UIXComponentBase.java myfaces/trinidad/trunk/trinidad/trinidad-api/src/main/java/org/apache/myfaces/trinidad/component/ValueMap.java myfaces/trinidad/trunk/trinidad/trinidad-api/src/main/java/org/apache/myfaces/trinidad/convert/ColorConverter.java myfaces/trinidad/trunk/trinidad/trinidad-api/src/main/java/org/apache/myfaces/trinidad/convert/DateTimeConverter.java myfaces/trinidad/trunk/trinidad/trinidad-api/src/main/java/org/apache/myfaces/trinidad/convert/NumberConverter.java myfaces/trinidad/trunk/trinidad/trinidad-api/src/main/java/org/apache/myfaces/trinidad/event/ChartDrillDownEvent.java myfaces/trinidad/trunk/trinidad/trinidad-api/src/main/java/org/apache/myfaces/trinidad/logging/TrinidadLogRecord.java myfaces/trinidad/trunk/trinidad/trinidad-api/src/main/java/org/apache/myfaces/trinidad/model/PathHelper.java myfaces/trinidad/trunk/trinidad/trinidad-api/src/main/java/org/apache/myfaces/trinidad/model/RowKeySetImpl.java myfaces/trinidad/trunk/trinidad/trinidad-api/src/main/java/org/apache/myfaces/trinidad/model/RowKeySetTreeImpl.java myfaces/trinidad/trunk/trinidad/trinidad-api/src/main/java/org/apache/myfaces/trinidad/model/XMLMenuModel.java myfaces/trinidad/trunk/trinidad/trinidad-api/src/main/java/org/apache/myfaces/trinidad/resource/AggregatingResourceLoader.java myfaces/trinidad/trunk/trinidad/trinidad-api/src/main/java/org/apache/myfaces/trinidad/resource/StringContentResourceLoader.java myfaces/trinidad/trunk/trinidad/trinidad-api/src/main/java/org/apache/myfaces/trinidad/validator/ByteLengthValidator.java myfaces/trinidad/trunk/trinidad/trinidad-api/src/main/java/org/apache/myfaces/trinidad/validator/DoubleRangeValidator.java myfaces/trinidad/trunk/trinidad/trinidad-api/src/main/java/org/apache/myfaces/trinidad/validator/LengthValidator.java myfaces/trinidad/trunk/trinidad/trinidad-api/src/main/java/org/apache/myfaces/trinidad/validator/LongRangeValidator.java myfaces/trinidad/trunk/trinidad/trinidad-api/src/main/java/org/apache/myfaces/trinidad/validator/RegExpValidator.java myfaces/trinidad/trunk/trinidad/trinidad-api/src/main/java/org/apache/myfaces/trinidad/webapp/ResourceServlet.java myfaces/trinidad/trunk/trinidad/trinidad-api/src/main/java/org/apache/myfaces/trinidad/webapp/UIXComponentTag.java myfaces/trinidad/tr
Re: Where is Tomahawk on the new Continuum server?
On 5/15/07, Paul Spencer <[EMAIL PROTECTED]> wrote: It appears that Tomahawk has not been added to the new Continuum server. I added it last night and there were a bunch of notifications. If it's not visible as a guest (when you're not logged in) then the guest user needs to have the 'project user' role for that project group. I've given admin rights to the committers who have registered so far, and anyone who has admin rights can edit roles. Thanks, -- Wendy
Re: [PROPOSAL] Create a notifications mailing list
On 5/15/07, Manfred Geiler <[EMAIL PROTECTED]> wrote: currently there are 91 subscribers to the commits list (4 of them with digest option). don't know if there is a way to do a mass subscribe. There is. I'll request that infrastructure seed the notifications list with the current list of subscribers to the commits list. Existing subscribers will notice a change in the 'to' address and may need to adjust mail filters. I'll moderate it, and need one more volunteer. No one except Continuum should be writing to it directly, so moderation messages can largely be ignored. The reply-to on both the commits and notifications lists should be set to the dev list. -- Wendy
Re: [Trinidad] Deploying site?
On 5/14/07, Adam Winer <[EMAIL PROTECTED]> wrote: How can we start deploying our site to http://myfaces.apache.org/trinidad/index.html ? Any special magic? Set distributionManagement/site/url to the right place, then 'mvn site-deploy' should work. I added the trinidad and trinidadbuild poms to Continuum. For the module with the top-level of the Trinidad site, try adding a build definition of 'clean site-deploy' and remove the '--non-recursive' bit. There's already a nightly schedule, so choose that, and it should re-deploy the site if anything has changed. -- Wendy
Re: [PROPOSAL] Create a notifications mailing list
On 5/14/07, Mario Ivankovits <[EMAIL PROTECTED]> wrote: Hi! > I am -0 on placing Continuum messages on a different mailing list > because I like seeing the commit message(s) followed by a Continuum > success/failure message. The Continuum message is a nice confirmation > that the commit(s) did or did not break the build. Email clients can > be configured to filter messages if the user prefers to not see the > Continuum message or see the message in a different folder. The > converse can also be said, filtering commit and Continuum messages > into the same folder. Yep, these are my thoughts too. When Continuum is running stable I really prefer its messages showing up after the commit. Even a newbie developer should see that every commit triggers an (nearly) immediate action. In the end every developer should subscribe to the continuum notification list too ... so no need to split them. Somehow, I feel the need to restate my case. :) People who want to see commits and notifications right next to each other should absolutely have that option. And you will, just filter both lists into the same folder (or give them the same tag.) And active developers should certainly be watching both commits and notifications. Howver, _how_ you watch them should be up to you -- the Atom feed on the official archives is a great resource, as are Nabble forums. Separate streams of information can be combined and consumed in whatever way makes sense for you, personally. Also _whether_ you watch both of them should be up to the reader. Not everyone who reads the commits list is a developer. One of the reasons I argue for descriptive commit messages is that I learn a great deal from reading code and understanding what the change was meant to do. I do this for projects I'm only a casual user of. At that level, notifications are just noise -- soon enough, I'll see the next commit with the correction and another explanation. So, carry on... -- Wendy
Re: Starting over with Continuum on the MyFaces zone
On 5/13/07, Wendy Smoak <[EMAIL PROTECTED]> wrote: For the Tobago site, what about an additional build definition in the existing group? You can have multiple build definitions per project group, each on a different schedule. ...or, an additional build definition on an individual project, say the top-level Apache Tobago, without the --non-recursive bit. :) -- Wendy
Re: Starting over with Continuum on the MyFaces zone
For the Tobago site, what about an additional build definition in the existing group? You can have multiple build definitions per project group, each on a different schedule. HTH, -- Wendy
Re: Starting over with Continuum on the MyFaces zone
On 5/13/07, Bernd Bohmann <[EMAIL PROTECTED]> wrote: can you add my account bommel to the administrator group, please. Done, for you (and for Bruno also). -- Wendy
[PROPOSAL] Create a notifications mailing list
I'd like to create [EMAIL PROTECTED] for automated messages from Continuum. I feel that more people are interested in watching commits than notifications. Particularly in the case of new contributors who may start as users, then watch the dev list, then perhaps want to (just) review commits. Continuum notifications may just be noise at this point. Also, having separate lists gives each person control over the incoming info. For example, you might want to receive commits in email, but watch the notifications on an RSS feed. Thoughts? Thanks, Wendy
Starting over with Continuum on the MyFaces zone
I decided to upgrade Continuum on the zone to 1.1-alpha-1 this morning... and forgot that this version unpacks to 'continuum' rather than 'continuum-1.1-alpha-1'. There's a symlink continuum -> continuum-1.0.3-SNAPSHOT, so that overwrote the old version that was running on port 8080. Oops. So, let's start fresh! Continuum 1.1-alpha-1 is running here: http://myfaces.zones.apache.org:8081/continuum It's installed at /local/continuum-1.1-alpha-1 (renamed this time...) The data lives in /local/continuum-data (will make upgrades easier) Committers are invited to register for an account here: http://myfaces.zones.apache.org:8081/continuum/security/register.action Use your @apache.org userid and email address, (or the email address in your .forward,) and I'll make you an administrator. If you know your way around Continuum 1.0 things should seem familiar. The biggest change is the addition of project groups, so that the front page summarizes all groups, and you can click one to see the list of modules. The default build definition is 'clean install' so you'll probaly want to change it to 'clean deploy' at the group level. So far, I've added Core 1.1, Core 1.2, and Tobago to the new instance. (BTW, if you want access to the zone itself, write to [EMAIL PROTECTED] and one of the PMC members will send you the information.) -- Wendy
Re: [Trinidad] non-"sandbox" commits should have JIRA issues
On 5/12/07, Adam Winer <[EMAIL PROTECTED]> wrote:
All that said, I absolutely should have referred
some checkins last week to
http://issues.apache.org/jira/browse/ADFFACES-135
Mea culpa!
You can fix the commit log message after the fact:
svn propedit --revprop -r12345 svn:log
('svn help propedit' for more info.)
--
Wendy
Re: Moving tobago developer into master pom
On 5/4/07, Volker Weber <[EMAIL PROTECTED]> wrote: you mean the "[Tobago] get rid of gentlement agreement" thread? I never saw a official result, nor a official anouncement of voting them in, as for me and Bernd. And, because i was not in the PMC at this time, i don't know if there was a PMC vote as for other committers as i suggest in the "Tobago and MyFaces" thread http://www.nabble.com/Tobago-and-MyFaces-tf2262739.html#a6851332 I'm sorry this is still being dragged out. :( I don't think I was on the the PMC then either and would have to check the archives, but my intent last fall was to get rid of that "agreement". I thought it was taken care of. If we need to vote, then let's vote on the private list. I'd also like to see the myfaces-tobago group removed from the svn auth file. (It's redundant in any case-- all of the people listed are also in the myfaces group.) Let's also make sure the trinidad committers are not getting a separate svn auth group. A MyFaces committer is a MyFaces committer, if we trust you with part of the code or documentation, we trust you with all of it. :) -- Wendy
Re: Moving tobago developer into master pom
On 5/4/07, Volker Weber <[EMAIL PROTECTED]> wrote: the other Tobago committer are afaik still not voted in as myfaces committer. They have only access by "Gentleman agreement". Bernd and me are separatly voted in by the PMC. I think this is needed for the others (idus, pleff, hennes and lofwyr) also. We did that already. :) http://www.nabble.com/Tobago-and-MyFaces-t2262739.html http://www.nabble.com/-Tobago--get-rid-of-gentlement-agreement-%28was-Re%3A-Tobago-and-MyFaces%29-t2264526.html -- Wendy
Re: svn commit: r525759 - /myfaces/tobago/trunk/theme/standard/src/main/resources/org/apache/myfaces/tobago/renderkit/html/standard/standard/script/tobago.js
On 4/5/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Author: bommel Date: Thu Apr 5 01:40:46 2007 New Revision: 525759 URL: http://svn.apache.org/viewvc?view=rev&rev=525759 Log: (TOBAGO-333) While we're picking on this commit... :) Please include a description of the change in addition to the issue number. It's great that JIRA will link up to commits, but the scm log comments tend to outlive issue trackers. Thanks! -- Wendy
Re: publishing 1.2.0 snapshots to m2 snapshot repo
On 4/19/07, Mathias Brökelmann <[EMAIL PROTECTED]> wrote: I fixed the continuum setup. The problem where some orphan lock files of the embedded derby database: rm /local/continuum-1.1-SNAPSHOT/data/continuum/database/*.lck and restarted continuum. Thanks! Can someone please update the troubleshooting section of the wiki with this info? http://wiki.apache.org/myfaces/Continuum_Build -- Wendy
Re: publishing 1.2.0 snapshots to m2 snapshot repo
On 4/19/07, Paul McMahan <[EMAIL PROTECTED]> wrote: Looks like the 1.2.0 snapshot was last published to the snapshot repo on 11-Apr-2007.Are the 1.2.0 snapshots no longer being published automatically? No. There's some discussion in the list archives. Apparently no one can log into the zone, and the Continuum nightly builds are failing. One of these days someone will have time to coordinate with infrastructure to reboot it or figure out how to regain access. Solaris is not my native language, unfortunately. Meanwhile any committer should have permission to 'mvn deploy' updated snapshots. -- Wendy
Re: Need a MyFaces Product & Environment matrix.
On 4/18/07, Paul Spencer <[EMAIL PROTECTED]> wrote: Users looking at MyFaces Products do not have one place that lists the products and their supported environments. Below is a example of what I would expect. ... I suspect this need to be on the MyFaces site. Well... then... add it. :) Seriously, we're a 'commit then review' project, and documentation is unlikely to be controversial. If you think it needs to be done but don't have time right now, open a JIRA issue and maybe someone else will pick it up. -- Wendy
Re: svn externals
On 4/17/07, Dennis Byrne <[EMAIL PROTECTED]> wrote: I think I've asked Sean this before but I can't remember his response. What was the verdict on why we don't use svn externals very much? Didn't this have something to do with losing history? I don't know what Sean's reason is, but my objection to them has to do with tagging. Externals definitions are not updated when you tag (which is just a copy) so unless you're careful to update them, you can end up with pieces of a "tag" still pointing at trunk. Much as I dislike the complicated "shared" setup, it's better than using externals. -- Wendy
Re: FYI: How to clean the maven repository when testing release candidates
On 4/11/07, Paul Spencer <[EMAIL PROTECTED]> wrote:
Since it appears their will be a 2nd release canidate for Tomahawk 1.1.5, I
thought
the following command to cleanup the local maven repository might be useful.
mvn dependency:purge-local-repository -Dverbose=true -DreResolve=false
-DresolutionFuzziness=version
Notes:
reResolve=false - Do not download the artifact in this maven
session after deleting it.
resolutionFuzziness=version - Delete all files associated with the
artifact's version.
There's another issue... the staging repo seems to have more than one
thing in it:
http://people.apache.org/builds/myfaces/m2-staging-repository/org/apache/myfaces/
The intent is to stage releases separately so it's easy to move them
over to the rsynced repo after the vote. Not a huge deal in this case
since it's everything under the 'tomahawk' directory.
With the current configuration, the procedure should be to move the
directory after deploying the staged release.
Another option is to change to
include ${version}, so it will land in the right place by default.
(My preference, Antonio over at Tiles thought it up, but I haven't
gotten around to changing it here yet.)
--
Wendy
Re: continuum down?
On 3/29/07, Manfred Geiler <[EMAIL PROTECTED]> wrote: "Doesn't work for ssh" What does that mean? mrmaven is a unix user. why can't I login with that user? I attempted both login as mrmaven and su to mrmaven. No success. My intention was to run the start_continuum-1.1.sh script as mrmaven. I can't log in as mrmaven either-- it says the password is invalid, but I don't remember anyone saying it was changed. I thought the myfaces zone is our private zone and we have our own continuum instance running there. So why can't we simply start it? I have no idea -- I can't get to either Continuum instance with a web browser, and I can't log in to see what's wrong. If no one else can get into the box, we'll have to ask the infrastructure team for help. -- Wendy
Re: continuum down?
On 3/29/07, Mike Kienenberger <[EMAIL PROTECTED]> wrote: Apparently not my fault: [ERROR] BUILD ERROR [INFO] [INFO] Error during page generation Embedded error: Error rendering Maven report: Unable to find configuration file location. Unable to find location 'config/myfaces-checks.xml' as URL, File or Resource. In the Orchestra site thread, Mario had a patch for this that uses the full url to the Checkstyle config file in svn. -- Wendy
Re: continuum down?
On 3/28/07, Manfred Geiler <[EMAIL PROTECTED]> wrote: Hi Wendy! Hi all! What happened to continuum? Is it down? Just tried to login as mrmaven. No success. Has the password changed? (Can someone please send me the password) What steps are necessary to bring it up again? Is it as simple as running the start_continuum-1.1.sh script? Both of the Continuum instances seem to be down, and the password I remember doesn't work for ssh. The Continuum instructions (such as they are) are here: * http://wiki.apache.org/myfaces/Continuum_Build Once it comes back up, register for an account using your ASF id, and I'll make you a system administrator. (If register for an account doesn't work, let me know and I'll just add you.) -- Wendy
Re: Ochestra Site
On 3/28/07, Mario Ivankovits <[EMAIL PROTECTED]> wrote: I still do not know how to build the whole MyFaces Web-Site ... Without anyone volunteering - or at least give some pointers/logins/scripts I have no chance to move on. :-( The whole site? Or just Orchestra? Maven docs: http://maven.apache.org/guides/mini/guide-site.html If you got the Orchestra site to build (with "mvn site"?) then try "mvn site-deploy" to publish it. First, check where it will be published to. Look at the output of "mvn help:effective-pom" for the section. To change it, add that section to one of the Orchestra poms and fix the url. (I assume you want it to land at http://myfaces.apache.org/orchestra.) I don't see anything on the MyFaces wiki, but these two Struts pages have info on configuring Maven and publishing websites. http://wiki.apache.org/struts/StrutsMaintenanceWebsite http://wiki.apache.org/struts/StrutsMaintenanceMaven This page has a section for publishing the MyFaces site, but it's old. Cn you please update it? http://wiki.apache.org/myfaces/Building_With_Maven Once it works, we can have Continuum (on the zone) publish the site along with snapshots. -- Wendy
Re: [continuum] BUILD FAILURE: API
On 3/24/07, Dennis Byrne <[EMAIL PROTECTED]> wrote: Has the password changed or does the user just no longer exist? Maybe I can kill the dir - which machine is this on? It was just me forgetting the password. I removed core/api/impl from the old continuum on port 8080, but I still don't know why it just started complaining about a checkstyle config file. -- Wendy
Re: [continuum] BUILD FAILURE: API
On 3/24/07, Wendy Smoak <[EMAIL PROTECTED]> wrote: It was already there, and building fine. I changed the build definition to deploy, etc. http://myfaces.zones.apache.org:8081/continuum/projectGroupSummary.action?projectGroupId=6 I spoke too soon... it was working, but now it's doing the same thing in both Continuum instances. :( -- Wendy
Re: [continuum] BUILD FAILURE: API
On 3/24/07, Wendy Smoak <[EMAIL PROTECTED]> wrote: I vote we move it over to the (newer) Continuum instance on port 8081 and see if it works there. It was already there, and building fine. I changed the build definition to deploy, etc. http://myfaces.zones.apache.org:8081/continuum/projectGroupSummary.action?projectGroupId=6 However, I can't seem to log into the old Continuum on port 8080 to delete the core/api/impl projects. Can someone else try it? Or we can just see what else needs to be moved over and turn that one off. -- Wendy
Re: [continuum] BUILD FAILURE: API
On 3/24/07, Dennis Byrne <[EMAIL PROTECTED]> wrote: Can anyone help with this? It looks like velocity errors are being generated from a checkstyle report. I vote we move it over to the (newer) Continuum instance on port 8081 and see if it works there. Any committer is welcome to a Continuum account... just ask. :) -- Wendy
Re: [status] tomahawk 1.1.5 release
On 3/22/07, Manfred Geiler <[EMAIL PROTECTED]> wrote: I will change the assembly configurations of myfaces core and myfaces tomahawk accordingly. There's more to it than that. To change the jar file names, the artifactIds would need to be changed, and we should think about relocating the old releases in the Maven repo [1]. I would suggest making this change on trunk for 1.1.6 so we have more time to test it. [1] http://maven.apache.org/guides/mini/guide-relocation.html -- Wendy
Re: source-repository page confusing
On 3/7/07, David Jencks <[EMAIL PROTECTED]> wrote: Could someone who knows where parts of the project actually are please update http://myfaces.apache.org/source-repository.html ? I don't think any of the links on that page except to svn documentation have any relationship with what a developer would expect from their descriptions. i'm hoping that the current code base is actually located at https:// svn.apache.org/repos/asf/myfaces/core/trunk/ The page is auto-generated based on the contents of pom.xml for the site module. It could be overridden by adding src/site/apt/source-repository.apt with the desired content, which (since this page is at the top level of the site) should list all of the sub projects. It could just link to the generated source-repository pages for the sub-projects, to avoid duplicating information. Feel free to open a JIRA issue for this so it doesn't get overlooked here on the list. If you'd like to contribute a patch that would be even better. -- Wendy
Re: Has the Tomahawk 1.1.5 release process started?
On 3/5/07, Paul Spencer <[EMAIL PROTECTED]> wrote: Any change in the timetable? Has a release manager been set? Are you volunteering? :) I know everyone has other commitments, but I am just trying to make sure this release is not forgotten about :) It's unlikely anyone has forgotten about it. As you note, everyone is busy, and it will happen as soon as someone has time. That someone could be any one (or more) of the committers. I've offered before to help anyone who wants the learn the release process. I don't have time to take it on alone right now, but I will make time to help anyone who wants to learn. -- Wendy
Re: Tomahawk 1.1.5 branch created to eartly?
On 3/5/07, Wendy Smoak <[EMAIL PROTECTED]> wrote: Not necessarily. There was no 1.1.6-SNAPSHOT in JIRA to choose when closing the issue. I added one and edited the issue. Now it's up to the releae manager whether to merge that change to the branch. Hold on... the trunk *is* at 1.1.5-SNAPSHOT: http://svn.apache.org/repos/asf/myfaces/tomahawk/trunk/pom.xml And so is the branch: http://svn.apache.org/repos/asf/myfaces/tomahawk/branches/1_1_5/pom.xml ) That's not allowed. :) What to do depends on how soon someone has plans to do the Tomahawk 1.1.5 release. Either we 1. update trunk to 1.1.6-SNAPSHOT or 2. delete the branch and re-copy it at some later point -- Wendy
