El mar, 27-09-2005 a las 16:32 +0800, James Liao escribió: > Hi, > Now the problem comes to myfaces-1.1.0.jar. > I did find a directory like " > http://www.ibiblio.org/maven/myfaces/jars/myfaces-1.1.0/";, but there is not > myfaces-1.1.0.jar. > > The SVN head remain broken. >
Sorry a lot. I have mixed changes (for updating pluto dependency to 1.0.1 when they finally release it) and I missed some commits. This got complicated by the fact that the id in pluto changes from pluto to org.apache.pluto (as recommended), so I should not do this change until the end. I'm building from a clean repositoy and committing the changed project.xml files to ensure this is fixed. The global thing I'm doing is finishing the restructuring of portals bridges. To this aim: - applications/struts-demo will move to somewhere in portals-bridges/struts/ - applications/jpetstore will move to somewhere in the struts bridge too, as a separate war - applications/jsf-demo and applications/jsf-demo-myfaces will be joined into a single jar (little difference between those two) and moved to portals-bridges/jsf/ - applications/perl will move to portals-bridges/perl - applications/php will move to portals/bridges/php After this I will propose a formal (not SNAPSHOT) release in bridges that will make more stable dependencies for J2-2.0-M4, as the demos will be imported as built wars, and decoupled from the portal itself. security, pam and palm will remain in jetspeed, as they are the administration portlets. David suggested to put together pam and palm. This will leave only the gems applications and demo.war remaining, for further restructuring and clean up preparing the M4 (and then 2.0) release. Other missing (implicit) dependency that we should aim to break is that the .psml pages are referencing those demos. For this I think we need a way for a portlet war to specify a pages area, and for the deployment tool to "mount" this pages area in a specific place in the sitemap for the portal. The idea here is that, if a portal does *not* contain the faces demos, no broken faces page will appear. Ditto for php, perl, python, struts, jpetstore, whatever. Ideas on specifying or implementing this? This makes sense because all demos are, in principle, runnable in any JSR-168 portal (most of the just depend on generic bridges stuff and the respective framework/bridge). It will bring the additional benefit of reducing the build time in J2 a lot (6 less projects to build, and stable dependency points means less wait in online builds) We were discussing yesterday too that a very interesting possibility for documentation is that the demo wars carry html documentation (via xdoc in their build) *both* for the bridges site and inside the war, so that people looking around knows what is going on in the different demos. I'm still figuring out the concrete places to put the builds in portals-bridges, and how to add them to the main jetspeed build. I'm no maven expert (I actually hate a lot of things it does, and never voted to use it, in fact my vote was, back then, contingent to keep a working ant build, which never happened), but someone needs to do this un-sexy tasks if we want to have a reasonable environment for programmers to build/modify jetspeed. I also added variables to keep a global log4j.version and log4j.include (it was missing in some directories), and the same for struts.(version| include) and commons.logging.(version|include), so that it is easier to keep track of versions. I bumped the release of jsf due to a classloading bug there that was causing problems, then I discovered that 1.1.0 has changed the names of the artifacts, and it has also a similar problem which requires using the separate parts (-api, -impl and tomahawk.jar) instead of the global myfaces-all-1.1.0.jar. Solving this is causing some (hopefully transient) trouble. What do you (all) think? > -James Liao > > On 9/27/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > Author: sgala > > Date: Tue Sep 27 00:47:14 2005 > > New Revision: 291845 > > > > URL: http://svn.apache.org/viewcvs?rev=291845&view=rev > > Log: > > fix name change in myfaces, from myfaces-jsf-api to myfaces-api > > > > Modified: > > portals/jetspeed-2/trunk/applications/jsf-demo-myfaces/project.xml > > portals/jetspeed-2/trunk/applications/jsf-demo/project.xml > > > > Modified: > > portals/jetspeed-2/trunk/applications/jsf-demo-myfaces/project.xml > > URL: > > http://svn.apache.org/viewcvs/portals/jetspeed-2/trunk/applications/jsf-demo-myfaces/project.xml?rev=291845&r1=291844&r2=291845&view=diff > > > > ============================================================================== > > --- portals/jetspeed-2/trunk/applications/jsf-demo-myfaces/project.xml > > (original) > > +++ portals/jetspeed-2/trunk/applications/jsf-demo-myfaces/project.xml Tue > > Sep 27 00:47:14 2005 > > @@ -99,7 +99,7 @@ > > </properties> > > </dependency> > > <dependency> > > - <id>myfaces:myfaces-jsf-api</id> > > + <id>myfaces:myfaces-api</id> > > <version>${myfaces.version}</version> > > <properties> > > <war.bundle>true</war.bundle> > > > > Modified: portals/jetspeed-2/trunk/applications/jsf-demo/project.xml > > URL: > > http://svn.apache.org/viewcvs/portals/jetspeed-2/trunk/applications/jsf-demo/project.xml?rev=291845&r1=291844&r2=291845&view=diff > > > > ============================================================================== > > --- portals/jetspeed-2/trunk/applications/jsf-demo/project.xml (original) > > +++ portals/jetspeed-2/trunk/applications/jsf-demo/project.xml Tue Sep 27 > > 00:47:14 2005 > > @@ -91,7 +91,7 @@ > > </dependency> > > > > <dependency> > > - <id>myfaces:myfaces-jsf-api</id> > > + <id>myfaces:myfaces-api</id> > > <version>${myfaces.version}</version> > > <properties> > > <war.bundle>true</war.bundle> > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > -- VP and Chair, Apache Portals (http://portals.apache.org) Apache Software Foundation
signature.asc
Description: This is a digitally signed message part
