You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "Dr. Michael Lipp" <Mi...@danet.de> on 2005/07/01 15:31:58 UTC
Need proposal for JS2-255 fix
Hi,
I'm very close to really requiring JS2-255 to be fixed now. I think I
have understood enough to try it myself. However, in order to be able to
provide an acceptable patch, I'd like your opinion about what to use as
replacement for "VALUE" in the DB schema. How about "THE_VALUE"?
Regards,
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: [J2] Build Process Summer Time Clean Up
Posted by Ate Douma <at...@douma.nu>.
David Sean Taylor wrote:
> David Le Strat wrote:
>
>> All,
>>
>> I finally got some time to get back to J2. I have a
>> proposal for some summer time J2 build process clean
>> up.
>>
>> Jetspeed2 current build process is a bit confusing. Through the
>> various evolutions of J2 build process,
>> many targets have been accumulated that make it
>> difficult to easily understand the build process flow.
>>
>> h2. Cleaning up the build process
>>
>> Using J2 in its current form requires an in-depth
>> understanding of how J2 build internals operate.
>>
>> As an example, an integrator wanting to get starting
>> with J2 will want to start with the portal web
>> application and customize it from there. It should be
>> made easy for integrators to get started with the web
>> application without requiring an in-depth
>> understanding of the various sequences in the build
>> process.
>>
>> A typical implementation will want to create a project
>> as described below:
>>
>> {noformat}
>> \sample-portal
>> +---\etc Contains the build
>> dependencies definition.
>> +---\portal-webapp Contains the portal web
>> application being built.
>> +---\src Contains the portal
>> initialization source (db scripts, etc).
>> {noformat}
>>
>> Building the portal in this structure should be
>> possible by leveraging the deployed Jetspeed
>> dependencies:
>>
>> * Components: All libraries (jars) required for the
>> runtime operation of the portal engine.
>> * Portlets: All web libraries (wars) required for the
>> runtime operation of the portal engine.
>>
>> Integrator using Jetspeed2 should be able to do so
>> easily and to easily get (through dependencies) the
>> latest versions of the release Jetspeed components
>> (libraries as well as portlets).
>>
>> The current maven-plugin and portal build
>> implementation rely on the source build (target
>> directories) rather than the dependencies for the
>> assembly of the portal engine, making it more
>> difficult to get quickly started and to keep up with
>> enhanced components.
>>
>> h2. Proposed changes
>>
>> The proposed changes below clean up the build process
>> and slightly reorganize some elements to more easily
>> achieve the goals outlined above.
>>
>> The first changes restructure the portal directory as
>> follow.
>> # Remove all non web related dependencies from portal:
>> ## Move the portal java source and java tests to
>> components/portal. This becomes a component that will
>> be released as jetspeed-(version).jar
>
>
> +1 in general, but don't all components follow a naming pattern of
> jetspeed-{COMPONENT_NAME}-{VERSION}.jar?
>
>
>> ## Rename the web application to portal-webapp and the
>> artifact id to jetspeed-portal (to remove conflict
>> with the jetspeed component artifact).
>
>
> Maybe this artifact should be jetspeed-{VERSION}.war
>
>> ## Move the test directory under portal-webapp to
>> components/portal/test as it support the portal
>> components tests.
>
>
> +1
>
>> ## Add org.apache.jetspeed.PortalTestConstants to
>> centralize initialization of JETSPEED_PROPERTIES_PATH
>> and PORTAL_WEBAPP_PATH.
>>
>> Clean up the portal-webapp (previously portal) build
>> and maven-plugin.
>
>
> I think that all build goals should be a part of the plugin.
> Why have both plugin goals and maven.xml goals?
>
> I'd also like to propose moving to Maven-2 as a part of this refactoring.
> I think we should consider project archetypes for quickstarts and
> replacing the current build with a M2 build.
>
> Overview (from my notes at JavaOne):
> * Super-POM: defaults across all projects
> * transitive dependencies
> * dependency scoping
> * dependency management
> * better control over snapshots
> - only check one snapshot per build
> - or check snapshot once per time period (day, hour..)
> * post/pre goals removed
> * build is now based on a lifecycle
> * maven.xml, project.properties deprecated
> * parent projects can be declared, no more ../..
> * plugins configurable, POM based, auto-downloaded
> * Plugin languages supported: Java Beanshell, Marmalade
> * Explicit definiition of multiprojects
> <modules>
> <module>subproject-1</module>
> <module>subproject-2</module>
> ....
> * Project archetypes for quickstarts
>
>> # Clean portal/maven.xml:
>> ## Remove commented calls to targets.
>> # The deploy and undeploy calls in the portal-webapp
>> (previously portal) build process should be using the
>> maven-plugin to do so. Multiple deploy, undeploy,
>> register, unregister behaviors create confusion. Therefore, I propose
>> to perform the following cleanup
>> in the portal-webapp (previously portal):
>> ## Remove pam.template.deploy. This is not used.
>> ## Remove pam.unregister. Depends on
>> pam.template.register which is not being used.
>> ## Remove pam.template.register. This is not used.
>> ## Remove pam.template.undeploy. There is a
>> jetspeed2:undeploy target in the jetspeed plugin.
>> ## Rename pam.register to pam.layoutdeploy. This
>> really deploys the layout portlet and should be
>> consistent with the other deploy targets.
>> ## Rename pam.deploy to pam.demodeploy. This deploys
>> the demo application.
>> ## Rename pam.undeploy to pam.demoundeploy. This
>> undeploys the demo applications.
>> ## Rename pam.rss to pam.rssdeploy for consistency
>> purpose.
>> ## Modify the pam.(portlet)undeploy targets to use the
>> jetspeed maven plugin jetspeed2:undeploy target.
>> ## Remove deployJar and deployClasses. portal-webapp
>> now uses dependencies for the portal component
>> library.
>> ## Remove jar:jar target.
>> ## Clean plugin.jelly: jetspeed2:register and
>> jetspeed2:unregister. Not used.
>>
>
> +1, remove all Jelly, move to M2
>
>> Have portal-webapp depend on the built Portlet
>> dependencies rather that the build target directories.
>> # Modify the maven.xml pam.(portlet)deploy target and
>> the maven-plugin to use the archived portlet war
>> deployed to the repository (maven install).
>>
>
> I like this idea of the portal-webapp, since its great for starting new
> projects where the goal is to customize the portal with your own skins,
> and your own build.
>
>> Let me know if you are alright with the proposed
>> changes and I will go ahead and create an issue as
>> well as implement the changes. I am almost doen. I
>> just need to perform some final testing locally and
>> get everyone's blessing.
>>
> You have my +1, although I propose going a step further and moving to M2
>
I'm +1 on this too (for starters) but like to add some additional ideas.
I looked into M2 for the first time this evening (but not tried it yet)
and I do like it so far.
But, I'm not sure its ready for use yet for J2. At least, the website docs
didn't give me that impression. Maybe in a month or two?
Anyway, I agree with David Sean Taylor that I'd like to see all portal build/deploy/install etc.
goal functionality moved to the plugin *only*.
The way it now duplicates things I don't very much like.
But, I also don't like the way a specific plugin version is so much dependent on a
specific Jetspeed configuration. I currently packs all configuration scripts, dependency
definitions, sql scripts etc. inside the plugin.
In my own integration builds for clients I don't use the plugin but base my portal setup
directly on an repo installed version of the jetspeed war.
For a specific portal, I extract the jetspeed.war in the project build folder, run some ant filters
and/or replace assembly files and remove/overlay some others files (like new decorators and
additional portlet applications etc.
I think we could provide a solution which has the benefits of both solutions and without
the problems I see with the plugin.
The main idea of David Le Strat that we should provide an integration build based on installed
components from the repository I'd like to extend to providing the integration build *configuration*
too as installed (template) component (thus *not* embedded in the plugin).
What if we would build a jetspeed-portal-template-<VERSION>.jar (not .war) which contained
the proposed portal-webapp as well as its dependency (pom) definitions, sql (or schema) scripts,
app server templates (like the different tomcat context files, JBoss/Webspere/BEA configs etc),
and a default build.properties.
Then the plugin could use that template to build a concrete portal,
support (merge) overlay definitions (if any) and *not* be dependent on the concrete jetspeed component
resources itself but derive those from the template and/or from a custom user build.properties.
For our current portal project we then could be a completely empty project except for a project.xml and
a maven.xml executing nothing but the default plugin goals. A nice starter project for integrators!
We can even add an integrators project template goal to the plugin setting up such a project.
Stuff like portal name, context path and app server version can then be setup already for you.
The plugin itself wouldn't need to be build and installed each and every time again. Only when new
features to the plugin are added. It really can have its own release cycle and version then, independent
from Jetspeed.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
RE: MENUS_BRANCH committed
Posted by Scott T Weaver <sc...@binary-designs.net>.
Awesome! Can't wait to play with it!
-Scott
> -----Original Message-----
> From: Randy Watler [mailto:watler@wispertel.net]
> Sent: Tuesday, July 05, 2005 3:38 PM
> To: Jetspeed Developers List
> Subject: MENUS_BRANCH committed
>
> Gang,
>
> As you can see, I have finally committed the work on M4 menus into its
> own SVN branch. While it is not "done", it was important that this
> component and its integration into J2 get more eyes and hands on it.
> Thanks to David for beating me over the head until I got it committed!
>
> While almost all of the supporting functionality is in place, the "last
> mile" of the modification is not complete: the decorators. At the
> moment, all of the decorators are running in compatibility mode and are
> not using the new menu features of the portal-site component. I plan on
> adding menu support to the tigris decorators later today/tonight. I am
> hoping someone can pick up a JSCookMenu implementation while I keep
> messing around under the portal-site covers.
>
> So, you will not see any visible changes, (other than the lack of
> deprecated document set support), if you pull this branch until we get
> down to actual business of revising the decorators. Of course, the page
> selection and page context generation internals have been completely
> refactored... so I feel it is time to ask for help.
>
> Randy
>
> Here is the commit log message:
>
> COMMITTED:
>
> - implemented new portal-site component
> - added design document for portal-site component
> - removed deprecated profiled page context from profiler and page manager
> - stripped request page selection implementation from page manager
> - tightened access to folders in page manager to require view permission
> - expanded page manager support and tests to include PSML menu definitions
> - modified page manager internals to include marshal/unmarshal hooks
> - changed Castor page mananager implementation to use SAX XML processing
> - integrated new portal-site component removing deprecated page mananger
> support in profiler valve
> - ported portal pages site PSML, removing deprecated document sets
>
> TODO:
>
> - convert tigris decorators to use standard menu definitions from portal-
> site component
> - fix visibilty of hidden pages in portal-site profiled page context
> compatibility mode
> - commit HTML version of design document
> - integrate portal-site component into page manager PSML change
> notification to dump internal caches
> - profile new portal-site component and optimize
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
MENUS_BRANCH committed
Posted by Randy Watler <wa...@wispertel.net>.
Gang,
As you can see, I have finally committed the work on M4 menus into its
own SVN branch. While it is not "done", it was important that this
component and its integration into J2 get more eyes and hands on it.
Thanks to David for beating me over the head until I got it committed!
While almost all of the supporting functionality is in place, the "last
mile" of the modification is not complete: the decorators. At the
moment, all of the decorators are running in compatibility mode and are
not using the new menu features of the portal-site component. I plan on
adding menu support to the tigris decorators later today/tonight. I am
hoping someone can pick up a JSCookMenu implementation while I keep
messing around under the portal-site covers.
So, you will not see any visible changes, (other than the lack of
deprecated document set support), if you pull this branch until we get
down to actual business of revising the decorators. Of course, the page
selection and page context generation internals have been completely
refactored... so I feel it is time to ask for help.
Randy
Here is the commit log message:
COMMITTED:
- implemented new portal-site component
- added design document for portal-site component
- removed deprecated profiled page context from profiler and page manager
- stripped request page selection implementation from page manager
- tightened access to folders in page manager to require view permission
- expanded page manager support and tests to include PSML menu definitions
- modified page manager internals to include marshal/unmarshal hooks
- changed Castor page mananager implementation to use SAX XML processing
- integrated new portal-site component removing deprecated page mananger support in profiler valve
- ported portal pages site PSML, removing deprecated document sets
TODO:
- convert tigris decorators to use standard menu definitions from portal-site component
- fix visibilty of hidden pages in portal-site profiled page context compatibility mode
- commit HTML version of design document
- integrate portal-site component into page manager PSML change notification to dump internal caches
- profile new portal-site component and optimize
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
J2 Web Site
Posted by David Le Strat <dl...@yahoo.com>.
All,
The Jetspeed 2 web site was republished last night.
It provides the latest documentation and the ability
to download the documentation for each sub-project in
a PDF format.
Regards,
David Le Strat.
________________________
David Le Strat
Blogging @ http://dlsthoughts.blogspot.com
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
J2 Web Site
Posted by David Le Strat <dl...@yahoo.com>.
All,
The Jetspeed 2 web site was republished last night.
It provides the latest documentation and the ability
to download the documentation for each sub-project in
a PDF format.
Regards,
David Le Strat.
________________________
David Le Strat
Blogging @ http://dlsthoughts.blogspot.com
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: [J2] Regenerating J2's Web Site
Posted by Santiago Gala <sg...@apache.org>.
El mar, 12-07-2005 a las 19:40 -0700, David Le Strat escribió:
> All,
>
> Does anyone know how to update Jetspeed 2's web site?
> I also noticed that Infrastructure has changed the
> authentication mechanism for cvs.apache.org and
> people.apache.org and that it requires an RSA key. Is
> anyone aware of how this works or where to find info
> on this?
After the update of minotaur to BSD 5, it requires SSH protocol version
2, IIRC. You can change your settings locally so that you try/use SSH
v2. Not sure of where can you find more detailed info on this.
Somewhere like your home/.ssh there should be a bunch of configurations
files and other files from ssh.
Regards
Santiago
>
> Regards,
>
> David Le Strat.
>
> ________________________
> David Le Strat
> Blogging @ http://dlsthoughts.blogspot.com
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
--
VP and Chair, Apache Portals (http://portals.apache.org)
Apache Software Foundation
Re: [J2] Regenerating J2's Web Site
Posted by David Le Strat <dl...@yahoo.com>.
This is great. Thanks Ate.
James, I would love to hear your feedback on how to
improve the docs. There is still some more to come
but I hope we have a good start there.
Regards,
David Le Strat.
--- James Liao <ji...@gmail.com> wrote:
> That's great!
> I have been waiting for this update for a few days.
> I just can't wait to read David's new document about
> J2 security.
> Thanks,
> - James Liao
>
> On 7/29/05, Ate Douma <at...@douma.nu> wrote:
> > All,
> >
> > I've updated the Jetspeed-2 website:
> http://portals.apache.org/jetspeed-2
> >
> > Note: it might take a few hours for this update to
> surface ;-)
> >
> > The latest build and getting-started instructions
> are now available online.
> >
> > Regards,
> >
> > Ate
> >
> > David Le Strat wrote:
> > > Thanks Ate.
> > >
> > > --- Ate Douma <at...@douma.nu> wrote:
> > >
> > >
> > >>David Le Strat wrote:
> > >>
> > >>>Ate,
> > >>>
> > >>>Could we document the process for regenerating
> the
> > >>>site somewhere? Mostly the deployment part. I
> > >>
> > >>can't
> > >>
> > >>>even login to cvs.apache.org. It changed
> recently
> > >>
> > >>and
> > >>
> > >>>now requires to have a trust relationship
> > >>
> > >>established.
> > >>
> > >>> Any pointer would be appreciated.
> > >>
> > >>Well, I can still login to people.apache.org
> without
> > >>a problem (I'm using putty).
> > >>Don't have any idea what's wrong on your side.
> > >>
> > >>
> > >>>I added a documentation.xml page under xdocs,
> the
> > >>
> > >>Wiki
> > >>
> > >>>would also be a good place for it.
> > >>
> > >>I've updated this page and described the allSite
> > >>goal and the steps to bring updates online.
> > >>But, it does require you can login to
> > >>people.apache.org of course.
> > >>
> > >>
> > >>>Also, in the documentation.xml, I added
> > >>
> > >>instruction
> > >>
> > >>>for generating PDF versions of the docs. This
> may
> > >>
> > >>be
> > >>
> > >>>something we may want to add.
> > >>
> > >>+1. Don't have time now though to look into it.
> > >>
> > >>
> > >>>Regards,
> > >>>
> > >>>David.
> > >>>
> > >>>--- Ate Douma <at...@gmail.com> wrote:
> > >>>
> > >>>
> > >>>
> > >>>>All,
> > >>>>
> > >>>>I've just committed a new version of the
> allSite
> > >>>>goal.
> > >>>>Please test if it is working as expected
> > >>
> > >>(especially
> > >>
> > >>>>on Linux platform).
> > >>>>
> > >>>>I intend to update the J2 site later today or
> > >>>>tomorrow.
> > >>>>But, because the portals bridges are no longer
> > >>
> > >>part
> > >>
> > >>>>of the site docs,
> > >>>>we will lose those online docs :-(
> > >>>>
> > >>>>For that reason, Santiago and I are currently
> > >>>>investigating if we can
> > >>>>perform the infrastructural subtasks of
> > >>>>http://issues.apache.org/jira/browse/JS2-284
> > >>>>later today, effectively moving the bridges to
> > >>
> > >>their
> > >>
> > >>>>new home.
> > >>>>
> > >>>>Regards,
> > >>>>
> > >>>>Ate
> > >>>>
> > >>>>David Le Strat wrote:
> > >>>>
> > >>>>
> > >>>>>All,
> > >>>>>
> > >>>>>Does anyone know how to update Jetspeed 2's
> web
> > >>>>
> > >>>>site?
> > >>>>
> > >>>>
> > >>>>>I also noticed that Infrastructure has
> changed
> > >>
> > >>the
> > >>
> > >>>>>authentication mechanism for cvs.apache.org
> and
> > >>>>>people.apache.org and that it requires an RSA
> > >>
> > >>key.
> > >>
> > >>>>Is
> > >>>>
> > >>>>
> > >>>>>anyone aware of how this works or where to
> find
> > >>>>
> > >>>>info
> > >>>>
> > >>>>
> > >>>>>on this?
> > >>>>>
> > >>>>>Regards,
> > >>>>>
> > >>>>>David Le Strat.
> > >>>>>
> > >>>>>________________________
> > >>>>>David Le Strat
> > >>>>>Blogging @ http://dlsthoughts.blogspot.com
> > >>>>>
> > >>
> >
>
>>>>__________________________________________________
> > >>>>
> > >>>>>Do You Yahoo!?
> > >>>>>Tired of spam? Yahoo! Mail has the best spam
> > >>>>
> > >>>>protection around
> > >>>>
> > >>>>
> > >>>>>http://mail.yahoo.com
> > >>>>>
> > >>>>>
> > >>>>
> > >
>
---------------------------------------------------------------------
> > >
> > >>>>>To unsubscribe, e-mail:
> > >>>>
> > >>>>jetspeed-dev-unsubscribe@portals.apache.org
> > >>>>
> > >>>>
> > >>>>>For additional commands, e-mail:
> > >>>>
> > >>>>jetspeed-dev-help@portals.apache.org
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >
>
---------------------------------------------------------------------
> > >
> > >>>>To unsubscribe, e-mail:
> > >>>>jetspeed-dev-unsubscribe@portals.apache.org
> > >>>>For additional commands, e-mail:
>
=== message truncated ===
________________________
David Le Strat
Blogging @ http://dlsthoughts.blogspot.com
____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: [J2] Regenerating J2's Web Site
Posted by James Liao <ji...@gmail.com>.
That's great!
I have been waiting for this update for a few days.
I just can't wait to read David's new document about J2 security.
Thanks,
- James Liao
On 7/29/05, Ate Douma <at...@douma.nu> wrote:
> All,
>
> I've updated the Jetspeed-2 website: http://portals.apache.org/jetspeed-2
>
> Note: it might take a few hours for this update to surface ;-)
>
> The latest build and getting-started instructions are now available online.
>
> Regards,
>
> Ate
>
> David Le Strat wrote:
> > Thanks Ate.
> >
> > --- Ate Douma <at...@douma.nu> wrote:
> >
> >
> >>David Le Strat wrote:
> >>
> >>>Ate,
> >>>
> >>>Could we document the process for regenerating the
> >>>site somewhere? Mostly the deployment part. I
> >>
> >>can't
> >>
> >>>even login to cvs.apache.org. It changed recently
> >>
> >>and
> >>
> >>>now requires to have a trust relationship
> >>
> >>established.
> >>
> >>> Any pointer would be appreciated.
> >>
> >>Well, I can still login to people.apache.org without
> >>a problem (I'm using putty).
> >>Don't have any idea what's wrong on your side.
> >>
> >>
> >>>I added a documentation.xml page under xdocs, the
> >>
> >>Wiki
> >>
> >>>would also be a good place for it.
> >>
> >>I've updated this page and described the allSite
> >>goal and the steps to bring updates online.
> >>But, it does require you can login to
> >>people.apache.org of course.
> >>
> >>
> >>>Also, in the documentation.xml, I added
> >>
> >>instruction
> >>
> >>>for generating PDF versions of the docs. This may
> >>
> >>be
> >>
> >>>something we may want to add.
> >>
> >>+1. Don't have time now though to look into it.
> >>
> >>
> >>>Regards,
> >>>
> >>>David.
> >>>
> >>>--- Ate Douma <at...@gmail.com> wrote:
> >>>
> >>>
> >>>
> >>>>All,
> >>>>
> >>>>I've just committed a new version of the allSite
> >>>>goal.
> >>>>Please test if it is working as expected
> >>
> >>(especially
> >>
> >>>>on Linux platform).
> >>>>
> >>>>I intend to update the J2 site later today or
> >>>>tomorrow.
> >>>>But, because the portals bridges are no longer
> >>
> >>part
> >>
> >>>>of the site docs,
> >>>>we will lose those online docs :-(
> >>>>
> >>>>For that reason, Santiago and I are currently
> >>>>investigating if we can
> >>>>perform the infrastructural subtasks of
> >>>>http://issues.apache.org/jira/browse/JS2-284
> >>>>later today, effectively moving the bridges to
> >>
> >>their
> >>
> >>>>new home.
> >>>>
> >>>>Regards,
> >>>>
> >>>>Ate
> >>>>
> >>>>David Le Strat wrote:
> >>>>
> >>>>
> >>>>>All,
> >>>>>
> >>>>>Does anyone know how to update Jetspeed 2's web
> >>>>
> >>>>site?
> >>>>
> >>>>
> >>>>>I also noticed that Infrastructure has changed
> >>
> >>the
> >>
> >>>>>authentication mechanism for cvs.apache.org and
> >>>>>people.apache.org and that it requires an RSA
> >>
> >>key.
> >>
> >>>>Is
> >>>>
> >>>>
> >>>>>anyone aware of how this works or where to find
> >>>>
> >>>>info
> >>>>
> >>>>
> >>>>>on this?
> >>>>>
> >>>>>Regards,
> >>>>>
> >>>>>David Le Strat.
> >>>>>
> >>>>>________________________
> >>>>>David Le Strat
> >>>>>Blogging @ http://dlsthoughts.blogspot.com
> >>>>>
> >>
> >>>>__________________________________________________
> >>>>
> >>>>>Do You Yahoo!?
> >>>>>Tired of spam? Yahoo! Mail has the best spam
> >>>>
> >>>>protection around
> >>>>
> >>>>
> >>>>>http://mail.yahoo.com
> >>>>>
> >>>>>
> >>>>
> > ---------------------------------------------------------------------
> >
> >>>>>To unsubscribe, e-mail:
> >>>>
> >>>>jetspeed-dev-unsubscribe@portals.apache.org
> >>>>
> >>>>
> >>>>>For additional commands, e-mail:
> >>>>
> >>>>jetspeed-dev-help@portals.apache.org
> >>>>
> >>>>
> >>>>
> >>>>
> > ---------------------------------------------------------------------
> >
> >>>>To unsubscribe, e-mail:
> >>>>jetspeed-dev-unsubscribe@portals.apache.org
> >>>>For additional commands, e-mail:
> >>>>jetspeed-dev-help@portals.apache.org
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>>________________________
> >>>David Le Strat
> >>>Blogging @ http://dlsthoughts.blogspot.com
> >>>
> >>>__________________________________________________
> >>>Do You Yahoo!?
> >>>Tired of spam? Yahoo! Mail has the best spam
> >>
> >>protection around
> >>
> >>>http://mail.yahoo.com
> >>>
> >>>
> >>
> > ---------------------------------------------------------------------
> >
> >>>To unsubscribe, e-mail:
> >>
> >>jetspeed-dev-unsubscribe@portals.apache.org
> >>
> >>>For additional commands, e-mail:
> >>
> >>jetspeed-dev-help@portals.apache.org
> >>
> >>>
> >>>
> >>>
> >>>
> >>
> >>
> >>
> > ---------------------------------------------------------------------
> >
> >>To unsubscribe, e-mail:
> >>jetspeed-dev-unsubscribe@portals.apache.org
> >>For additional commands, e-mail:
> >>jetspeed-dev-help@portals.apache.org
> >>
> >>
> >
> >
> >
> > ________________________
> > David Le Strat
> > Blogging @ http://dlsthoughts.blogspot.com
> >
> >
> >
> > ____________________________________________________
> > Start your day with Yahoo! - make it your home page
> > http://www.yahoo.com/r/hs
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> > For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
> >
> >
> >
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: [J2] Regenerating J2's Web Site
Posted by Ate Douma <at...@douma.nu>.
All,
I've updated the Jetspeed-2 website: http://portals.apache.org/jetspeed-2
Note: it might take a few hours for this update to surface ;-)
The latest build and getting-started instructions are now available online.
Regards,
Ate
David Le Strat wrote:
> Thanks Ate.
>
> --- Ate Douma <at...@douma.nu> wrote:
>
>
>>David Le Strat wrote:
>>
>>>Ate,
>>>
>>>Could we document the process for regenerating the
>>>site somewhere? Mostly the deployment part. I
>>
>>can't
>>
>>>even login to cvs.apache.org. It changed recently
>>
>>and
>>
>>>now requires to have a trust relationship
>>
>>established.
>>
>>> Any pointer would be appreciated.
>>
>>Well, I can still login to people.apache.org without
>>a problem (I'm using putty).
>>Don't have any idea what's wrong on your side.
>>
>>
>>>I added a documentation.xml page under xdocs, the
>>
>>Wiki
>>
>>>would also be a good place for it.
>>
>>I've updated this page and described the allSite
>>goal and the steps to bring updates online.
>>But, it does require you can login to
>>people.apache.org of course.
>>
>>
>>>Also, in the documentation.xml, I added
>>
>>instruction
>>
>>>for generating PDF versions of the docs. This may
>>
>>be
>>
>>>something we may want to add.
>>
>>+1. Don't have time now though to look into it.
>>
>>
>>>Regards,
>>>
>>>David.
>>>
>>>--- Ate Douma <at...@gmail.com> wrote:
>>>
>>>
>>>
>>>>All,
>>>>
>>>>I've just committed a new version of the allSite
>>>>goal.
>>>>Please test if it is working as expected
>>
>>(especially
>>
>>>>on Linux platform).
>>>>
>>>>I intend to update the J2 site later today or
>>>>tomorrow.
>>>>But, because the portals bridges are no longer
>>
>>part
>>
>>>>of the site docs,
>>>>we will lose those online docs :-(
>>>>
>>>>For that reason, Santiago and I are currently
>>>>investigating if we can
>>>>perform the infrastructural subtasks of
>>>>http://issues.apache.org/jira/browse/JS2-284
>>>>later today, effectively moving the bridges to
>>
>>their
>>
>>>>new home.
>>>>
>>>>Regards,
>>>>
>>>>Ate
>>>>
>>>>David Le Strat wrote:
>>>>
>>>>
>>>>>All,
>>>>>
>>>>>Does anyone know how to update Jetspeed 2's web
>>>>
>>>>site?
>>>>
>>>>
>>>>>I also noticed that Infrastructure has changed
>>
>>the
>>
>>>>>authentication mechanism for cvs.apache.org and
>>>>>people.apache.org and that it requires an RSA
>>
>>key.
>>
>>>>Is
>>>>
>>>>
>>>>>anyone aware of how this works or where to find
>>>>
>>>>info
>>>>
>>>>
>>>>>on this?
>>>>>
>>>>>Regards,
>>>>>
>>>>>David Le Strat.
>>>>>
>>>>>________________________
>>>>>David Le Strat
>>>>>Blogging @ http://dlsthoughts.blogspot.com
>>>>>
>>
>>>>__________________________________________________
>>>>
>>>>>Do You Yahoo!?
>>>>>Tired of spam? Yahoo! Mail has the best spam
>>>>
>>>>protection around
>>>>
>>>>
>>>>>http://mail.yahoo.com
>>>>>
>>>>>
>>>>
> ---------------------------------------------------------------------
>
>>>>>To unsubscribe, e-mail:
>>>>
>>>>jetspeed-dev-unsubscribe@portals.apache.org
>>>>
>>>>
>>>>>For additional commands, e-mail:
>>>>
>>>>jetspeed-dev-help@portals.apache.org
>>>>
>>>>
>>>>
>>>>
> ---------------------------------------------------------------------
>
>>>>To unsubscribe, e-mail:
>>>>jetspeed-dev-unsubscribe@portals.apache.org
>>>>For additional commands, e-mail:
>>>>jetspeed-dev-help@portals.apache.org
>>>>
>>>>
>>>
>>>
>>>
>>>________________________
>>>David Le Strat
>>>Blogging @ http://dlsthoughts.blogspot.com
>>>
>>>__________________________________________________
>>>Do You Yahoo!?
>>>Tired of spam? Yahoo! Mail has the best spam
>>
>>protection around
>>
>>>http://mail.yahoo.com
>>>
>>>
>>
> ---------------------------------------------------------------------
>
>>>To unsubscribe, e-mail:
>>
>>jetspeed-dev-unsubscribe@portals.apache.org
>>
>>>For additional commands, e-mail:
>>
>>jetspeed-dev-help@portals.apache.org
>>
>>>
>>>
>>>
>>>
>>
>>
>>
> ---------------------------------------------------------------------
>
>>To unsubscribe, e-mail:
>>jetspeed-dev-unsubscribe@portals.apache.org
>>For additional commands, e-mail:
>>jetspeed-dev-help@portals.apache.org
>>
>>
>
>
>
> ________________________
> David Le Strat
> Blogging @ http://dlsthoughts.blogspot.com
>
>
>
> ____________________________________________________
> Start your day with Yahoo! - make it your home page
> http://www.yahoo.com/r/hs
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: [J2] Regenerating J2's Web Site
Posted by Ate Douma <at...@douma.nu>.
All,
I've updated the Jetspeed-2 website: http://portals.apache.org/jetspeed-2
Note: it might take a few hours for this update to surface ;-)
The latest build and getting-started instructions are now available online.
Regards,
Ate
David Le Strat wrote:
> Thanks Ate.
>
> --- Ate Douma <at...@douma.nu> wrote:
>
>
>>David Le Strat wrote:
>>
>>>Ate,
>>>
>>>Could we document the process for regenerating the
>>>site somewhere? Mostly the deployment part. I
>>
>>can't
>>
>>>even login to cvs.apache.org. It changed recently
>>
>>and
>>
>>>now requires to have a trust relationship
>>
>>established.
>>
>>> Any pointer would be appreciated.
>>
>>Well, I can still login to people.apache.org without
>>a problem (I'm using putty).
>>Don't have any idea what's wrong on your side.
>>
>>
>>>I added a documentation.xml page under xdocs, the
>>
>>Wiki
>>
>>>would also be a good place for it.
>>
>>I've updated this page and described the allSite
>>goal and the steps to bring updates online.
>>But, it does require you can login to
>>people.apache.org of course.
>>
>>
>>>Also, in the documentation.xml, I added
>>
>>instruction
>>
>>>for generating PDF versions of the docs. This may
>>
>>be
>>
>>>something we may want to add.
>>
>>+1. Don't have time now though to look into it.
>>
>>
>>>Regards,
>>>
>>>David.
>>>
>>>--- Ate Douma <at...@gmail.com> wrote:
>>>
>>>
>>>
>>>>All,
>>>>
>>>>I've just committed a new version of the allSite
>>>>goal.
>>>>Please test if it is working as expected
>>
>>(especially
>>
>>>>on Linux platform).
>>>>
>>>>I intend to update the J2 site later today or
>>>>tomorrow.
>>>>But, because the portals bridges are no longer
>>
>>part
>>
>>>>of the site docs,
>>>>we will lose those online docs :-(
>>>>
>>>>For that reason, Santiago and I are currently
>>>>investigating if we can
>>>>perform the infrastructural subtasks of
>>>>http://issues.apache.org/jira/browse/JS2-284
>>>>later today, effectively moving the bridges to
>>
>>their
>>
>>>>new home.
>>>>
>>>>Regards,
>>>>
>>>>Ate
>>>>
>>>>David Le Strat wrote:
>>>>
>>>>
>>>>>All,
>>>>>
>>>>>Does anyone know how to update Jetspeed 2's web
>>>>
>>>>site?
>>>>
>>>>
>>>>>I also noticed that Infrastructure has changed
>>
>>the
>>
>>>>>authentication mechanism for cvs.apache.org and
>>>>>people.apache.org and that it requires an RSA
>>
>>key.
>>
>>>>Is
>>>>
>>>>
>>>>>anyone aware of how this works or where to find
>>>>
>>>>info
>>>>
>>>>
>>>>>on this?
>>>>>
>>>>>Regards,
>>>>>
>>>>>David Le Strat.
>>>>>
>>>>>________________________
>>>>>David Le Strat
>>>>>Blogging @ http://dlsthoughts.blogspot.com
>>>>>
>>
>>>>__________________________________________________
>>>>
>>>>>Do You Yahoo!?
>>>>>Tired of spam? Yahoo! Mail has the best spam
>>>>
>>>>protection around
>>>>
>>>>
>>>>>http://mail.yahoo.com
>>>>>
>>>>>
>>>>
> ---------------------------------------------------------------------
>
>>>>>To unsubscribe, e-mail:
>>>>
>>>>jetspeed-dev-unsubscribe@portals.apache.org
>>>>
>>>>
>>>>>For additional commands, e-mail:
>>>>
>>>>jetspeed-dev-help@portals.apache.org
>>>>
>>>>
>>>>
>>>>
> ---------------------------------------------------------------------
>
>>>>To unsubscribe, e-mail:
>>>>jetspeed-dev-unsubscribe@portals.apache.org
>>>>For additional commands, e-mail:
>>>>jetspeed-dev-help@portals.apache.org
>>>>
>>>>
>>>
>>>
>>>
>>>________________________
>>>David Le Strat
>>>Blogging @ http://dlsthoughts.blogspot.com
>>>
>>>__________________________________________________
>>>Do You Yahoo!?
>>>Tired of spam? Yahoo! Mail has the best spam
>>
>>protection around
>>
>>>http://mail.yahoo.com
>>>
>>>
>>
> ---------------------------------------------------------------------
>
>>>To unsubscribe, e-mail:
>>
>>jetspeed-dev-unsubscribe@portals.apache.org
>>
>>>For additional commands, e-mail:
>>
>>jetspeed-dev-help@portals.apache.org
>>
>>>
>>>
>>>
>>>
>>
>>
>>
> ---------------------------------------------------------------------
>
>>To unsubscribe, e-mail:
>>jetspeed-dev-unsubscribe@portals.apache.org
>>For additional commands, e-mail:
>>jetspeed-dev-help@portals.apache.org
>>
>>
>
>
>
> ________________________
> David Le Strat
> Blogging @ http://dlsthoughts.blogspot.com
>
>
>
> ____________________________________________________
> Start your day with Yahoo! - make it your home page
> http://www.yahoo.com/r/hs
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: [J2] Regenerating J2's Web Site
Posted by David Le Strat <dl...@yahoo.com>.
Thanks Ate.
--- Ate Douma <at...@douma.nu> wrote:
> David Le Strat wrote:
> > Ate,
> >
> > Could we document the process for regenerating the
> > site somewhere? Mostly the deployment part. I
> can't
> > even login to cvs.apache.org. It changed recently
> and
> > now requires to have a trust relationship
> established.
> > Any pointer would be appreciated.
> Well, I can still login to people.apache.org without
> a problem (I'm using putty).
> Don't have any idea what's wrong on your side.
>
> >
> > I added a documentation.xml page under xdocs, the
> Wiki
> > would also be a good place for it.
> I've updated this page and described the allSite
> goal and the steps to bring updates online.
> But, it does require you can login to
> people.apache.org of course.
>
> >
> > Also, in the documentation.xml, I added
> instruction
> > for generating PDF versions of the docs. This may
> be
> > something we may want to add.
> +1. Don't have time now though to look into it.
>
> >
> > Regards,
> >
> > David.
> >
> > --- Ate Douma <at...@gmail.com> wrote:
> >
> >
> >>All,
> >>
> >>I've just committed a new version of the allSite
> >>goal.
> >>Please test if it is working as expected
> (especially
> >>on Linux platform).
> >>
> >>I intend to update the J2 site later today or
> >>tomorrow.
> >>But, because the portals bridges are no longer
> part
> >>of the site docs,
> >>we will lose those online docs :-(
> >>
> >>For that reason, Santiago and I are currently
> >>investigating if we can
> >>perform the infrastructural subtasks of
> >>http://issues.apache.org/jira/browse/JS2-284
> >>later today, effectively moving the bridges to
> their
> >>new home.
> >>
> >>Regards,
> >>
> >>Ate
> >>
> >>David Le Strat wrote:
> >>
> >>>All,
> >>>
> >>>Does anyone know how to update Jetspeed 2's web
> >>
> >>site?
> >>
> >>>I also noticed that Infrastructure has changed
> the
> >>>authentication mechanism for cvs.apache.org and
> >>>people.apache.org and that it requires an RSA
> key.
> >>
> >> Is
> >>
> >>>anyone aware of how this works or where to find
> >>
> >>info
> >>
> >>>on this?
> >>>
> >>>Regards,
> >>>
> >>>David Le Strat.
> >>>
> >>>________________________
> >>>David Le Strat
> >>>Blogging @ http://dlsthoughts.blogspot.com
> >>>
>
>>>__________________________________________________
> >>>Do You Yahoo!?
> >>>Tired of spam? Yahoo! Mail has the best spam
> >>
> >>protection around
> >>
> >>>http://mail.yahoo.com
> >>>
> >>>
> >>
> >
>
---------------------------------------------------------------------
> >
> >>>To unsubscribe, e-mail:
> >>
> >>jetspeed-dev-unsubscribe@portals.apache.org
> >>
> >>>For additional commands, e-mail:
> >>
> >>jetspeed-dev-help@portals.apache.org
> >>
> >>>
> >>
> >>
> >>
> >
>
---------------------------------------------------------------------
> >
> >>To unsubscribe, e-mail:
> >>jetspeed-dev-unsubscribe@portals.apache.org
> >>For additional commands, e-mail:
> >>jetspeed-dev-help@portals.apache.org
> >>
> >>
> >
> >
> >
> > ________________________
> > David Le Strat
> > Blogging @ http://dlsthoughts.blogspot.com
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam? Yahoo! Mail has the best spam
> protection around
> > http://mail.yahoo.com
> >
> >
>
---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> jetspeed-dev-unsubscribe@portals.apache.org
> > For additional commands, e-mail:
> jetspeed-dev-help@portals.apache.org
> >
> >
> >
> >
> >
>
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail:
> jetspeed-dev-help@portals.apache.org
>
>
________________________
David Le Strat
Blogging @ http://dlsthoughts.blogspot.com
____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: [J2] Registry Unit Test Potential Bug
Posted by Shinsuke SUGAYA <sh...@yahoo.co.jp>.
David Le Strat wrote:
> All,
>
> I found an interesting problem with the registry. The
> reason I stumbled on that problem is that the test
> failed with OJB 1.0.3. I think we have a bug with the
> current version of OJB.
>
> The registry tests insert WebAppDescriptionImpl as
> follow:
>
> webApp.addDescription(Locale.FRENCH, "Description: Le
> fromage est dans mon pantalon!");
>
> INSERT INTO LOCALIZED_DESCRIPTION
> VALUES(281,181,'org.apache.jetspeed.om.impl.WebAppDescriptionImpl','Description:
> Le fromage est dans mon pantalon!','fr,,')
>
> The description is added in french.
>
> The test validation does:
>
> assertNotNull("Web app did NOT persist its
> description",
> webApp.getDescription(Locale.getDefault()));
>
> This assertion should fail. It should be
> webApp.getDescription(Locale.FRENCH) that returns a
> record. With current version or OJB, it works either
> way: Locale.FRENCH or (Locale.getDefault().
>
> Thoughts?
What locale do you run on test? C or en_US.UTF-8??
Thanks,
shinsuke
> Regards,
>
> David Le Strat.
>
> ________________________
> David Le Strat
> Blogging @ http://dlsthoughts.blogspot.com
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
__________________________________
Save the earth
http://pr.mail.yahoo.co.jp/ondanka/
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: [J2] Registry Unit Test Potential Bug
Posted by Raphaël Luta <ra...@apache.org>.
David Le Strat wrote:
> All,
>
> I found an interesting problem with the registry. The
> reason I stumbled on that problem is that the test
> failed with OJB 1.0.3. I think we have a bug with the
> current version of OJB.
>
> The registry tests insert WebAppDescriptionImpl as
> follow:
>
> webApp.addDescription(Locale.FRENCH, "Description: Le
> fromage est dans mon pantalon!");
>
> INSERT INTO LOCALIZED_DESCRIPTION
> VALUES(281,181,'org.apache.jetspeed.om.impl.WebAppDescriptionImpl','Description:
> Le fromage est dans mon pantalon!','fr,,')
>
> The description is added in french.
>
> The test validation does:
>
> assertNotNull("Web app did NOT persist its
> description",
> webApp.getDescription(Locale.getDefault()));
>
> This assertion should fail. It should be
> webApp.getDescription(Locale.FRENCH) that returns a
> record. With current version or OJB, it works either
> way: Locale.FRENCH or (Locale.getDefault().
>
Make sure to notify the OJB community about this issue.
Brian McCallister told me at ApacheCon that they would diligently
investigate/fix any bugs we could uncover and for which we could create a test case.
--
Raphaël Luta - raphael@apache.org
Apache Portals - Enterprise Portal in Java
http://portals.apache.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[J2] Registry Unit Test Potential Bug
Posted by David Le Strat <dl...@yahoo.com>.
All,
I found an interesting problem with the registry. The
reason I stumbled on that problem is that the test
failed with OJB 1.0.3. I think we have a bug with the
current version of OJB.
The registry tests insert WebAppDescriptionImpl as
follow:
webApp.addDescription(Locale.FRENCH, "Description: Le
fromage est dans mon pantalon!");
INSERT INTO LOCALIZED_DESCRIPTION
VALUES(281,181,'org.apache.jetspeed.om.impl.WebAppDescriptionImpl','Description:
Le fromage est dans mon pantalon!','fr,,')
The description is added in french.
The test validation does:
assertNotNull("Web app did NOT persist its
description",
webApp.getDescription(Locale.getDefault()));
This assertion should fail. It should be
webApp.getDescription(Locale.FRENCH) that returns a
record. With current version or OJB, it works either
way: Locale.FRENCH or (Locale.getDefault().
Thoughts?
Regards,
David Le Strat.
________________________
David Le Strat
Blogging @ http://dlsthoughts.blogspot.com
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: [J2] Regenerating J2's Web Site
Posted by Ate Douma <at...@douma.nu>.
David Le Strat wrote:
> Ate,
>
> Could we document the process for regenerating the
> site somewhere? Mostly the deployment part. I can't
> even login to cvs.apache.org. It changed recently and
> now requires to have a trust relationship established.
> Any pointer would be appreciated.
Well, I can still login to people.apache.org without a problem (I'm using putty).
Don't have any idea what's wrong on your side.
>
> I added a documentation.xml page under xdocs, the Wiki
> would also be a good place for it.
I've updated this page and described the allSite goal and the steps to bring updates online.
But, it does require you can login to people.apache.org of course.
>
> Also, in the documentation.xml, I added instruction
> for generating PDF versions of the docs. This may be
> something we may want to add.
+1. Don't have time now though to look into it.
>
> Regards,
>
> David.
>
> --- Ate Douma <at...@gmail.com> wrote:
>
>
>>All,
>>
>>I've just committed a new version of the allSite
>>goal.
>>Please test if it is working as expected (especially
>>on Linux platform).
>>
>>I intend to update the J2 site later today or
>>tomorrow.
>>But, because the portals bridges are no longer part
>>of the site docs,
>>we will lose those online docs :-(
>>
>>For that reason, Santiago and I are currently
>>investigating if we can
>>perform the infrastructural subtasks of
>>http://issues.apache.org/jira/browse/JS2-284
>>later today, effectively moving the bridges to their
>>new home.
>>
>>Regards,
>>
>>Ate
>>
>>David Le Strat wrote:
>>
>>>All,
>>>
>>>Does anyone know how to update Jetspeed 2's web
>>
>>site?
>>
>>>I also noticed that Infrastructure has changed the
>>>authentication mechanism for cvs.apache.org and
>>>people.apache.org and that it requires an RSA key.
>>
>> Is
>>
>>>anyone aware of how this works or where to find
>>
>>info
>>
>>>on this?
>>>
>>>Regards,
>>>
>>>David Le Strat.
>>>
>>>________________________
>>>David Le Strat
>>>Blogging @ http://dlsthoughts.blogspot.com
>>>
>>>__________________________________________________
>>>Do You Yahoo!?
>>>Tired of spam? Yahoo! Mail has the best spam
>>
>>protection around
>>
>>>http://mail.yahoo.com
>>>
>>>
>>
> ---------------------------------------------------------------------
>
>>>To unsubscribe, e-mail:
>>
>>jetspeed-dev-unsubscribe@portals.apache.org
>>
>>>For additional commands, e-mail:
>>
>>jetspeed-dev-help@portals.apache.org
>>
>>>
>>
>>
>>
> ---------------------------------------------------------------------
>
>>To unsubscribe, e-mail:
>>jetspeed-dev-unsubscribe@portals.apache.org
>>For additional commands, e-mail:
>>jetspeed-dev-help@portals.apache.org
>>
>>
>
>
>
> ________________________
> David Le Strat
> Blogging @ http://dlsthoughts.blogspot.com
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: [J2] Regenerating J2's Web Site
Posted by David Le Strat <dl...@yahoo.com>.
Ate,
Could we document the process for regenerating the
site somewhere? Mostly the deployment part. I can't
even login to cvs.apache.org. It changed recently and
now requires to have a trust relationship established.
Any pointer would be appreciated.
I added a documentation.xml page under xdocs, the Wiki
would also be a good place for it.
Also, in the documentation.xml, I added instruction
for generating PDF versions of the docs. This may be
something we may want to add.
Regards,
David.
--- Ate Douma <at...@gmail.com> wrote:
> All,
>
> I've just committed a new version of the allSite
> goal.
> Please test if it is working as expected (especially
> on Linux platform).
>
> I intend to update the J2 site later today or
> tomorrow.
> But, because the portals bridges are no longer part
> of the site docs,
> we will lose those online docs :-(
>
> For that reason, Santiago and I are currently
> investigating if we can
> perform the infrastructural subtasks of
> http://issues.apache.org/jira/browse/JS2-284
> later today, effectively moving the bridges to their
> new home.
>
> Regards,
>
> Ate
>
> David Le Strat wrote:
> > All,
> >
> > Does anyone know how to update Jetspeed 2's web
> site?
> > I also noticed that Infrastructure has changed the
> > authentication mechanism for cvs.apache.org and
> > people.apache.org and that it requires an RSA key.
> Is
> > anyone aware of how this works or where to find
> info
> > on this?
> >
> > Regards,
> >
> > David Le Strat.
> >
> > ________________________
> > David Le Strat
> > Blogging @ http://dlsthoughts.blogspot.com
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam? Yahoo! Mail has the best spam
> protection around
> > http://mail.yahoo.com
> >
> >
>
---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> jetspeed-dev-unsubscribe@portals.apache.org
> > For additional commands, e-mail:
> jetspeed-dev-help@portals.apache.org
> >
> >
>
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail:
> jetspeed-dev-help@portals.apache.org
>
>
________________________
David Le Strat
Blogging @ http://dlsthoughts.blogspot.com
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: [J2] Regenerating J2's Web Site
Posted by Ate Douma <at...@gmail.com>.
All,
I've just committed a new version of the allSite goal.
Please test if it is working as expected (especially on Linux platform).
I intend to update the J2 site later today or tomorrow.
But, because the portals bridges are no longer part of the site docs,
we will lose those online docs :-(
For that reason, Santiago and I are currently investigating if we can
perform the infrastructural subtasks of http://issues.apache.org/jira/browse/JS2-284
later today, effectively moving the bridges to their new home.
Regards,
Ate
David Le Strat wrote:
> All,
>
> Does anyone know how to update Jetspeed 2's web site?
> I also noticed that Infrastructure has changed the
> authentication mechanism for cvs.apache.org and
> people.apache.org and that it requires an RSA key. Is
> anyone aware of how this works or where to find info
> on this?
>
> Regards,
>
> David Le Strat.
>
> ________________________
> David Le Strat
> Blogging @ http://dlsthoughts.blogspot.com
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[J2] Regenerating J2's Web Site
Posted by David Le Strat <dl...@yahoo.com>.
All,
Does anyone know how to update Jetspeed 2's web site?
I also noticed that Infrastructure has changed the
authentication mechanism for cvs.apache.org and
people.apache.org and that it requires an RSA key. Is
anyone aware of how this works or where to find info
on this?
Regards,
David Le Strat.
________________________
David Le Strat
Blogging @ http://dlsthoughts.blogspot.com
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
RE: SVN Problems (was RE: [J2] Last Night Commit - Build Still Broken - Persistence Dependency Issue)
Posted by Scott T Weaver <sc...@binary-designs.net>.
I don't really think it has to do with size of commits, though I know I
should commit smaller ones, but sometimes that can be difficult depending on
the scale of the refactoring. I often get checksum corruption that not even
clean up can fix which requires doing a fresh checkout.
> -----Original Message-----
> From: David Sean Taylor [mailto:david@bluesunrise.com]
> Sent: Thursday, July 14, 2005 11:55 AM
> To: Jetspeed Developers List
> Subject: Re: SVN Problems (was RE: [J2] Last Night Commit - Build Still
> Broken - Persistence Dependency Issue)
>
> Scott T Weaver wrote:
> > So I'm not the only one suffering that is actually a relief (I feel like
> > less of an idiot now). Yeah, I am checking out fresh as we speak :(
> >
> > Can anyone help David and me by giving us a little direction on how to
> > better resolve our SVN problems? I can only speak for myself but every
> time
> > I have sync with SVN I spend at least an hour trying to figure out what
> went
> > wrong. And it is not only the Eclipse plugin, TortoiseSVN and the CL
> > interface are just as crappy in terms of breaking my workspace.
> >
> My experience with SVN is that its perceptually slower than CVS, no
> doubt. I really miss the snappiness of CVS + Eclipse.
>
> Did have a SVN problem yesterday, a directory was locked locally. I typed
>
> svn cleanup
>
> and then seemed to do the trick.
>
> Other than that, I haven't experienced any problems recently.
> Generally, I follow XP practices, and commit often and in small
> increments. Perhaps due to my cautious practices, Ive been insulated
> from the problems that you have experienced with SVN. I am by no means
> recommending that you follow my practices. Im just trying to communicate
> my experiences to help out.
>
> One other factor may be proxy servers, as I do not have one here.
>
> I wonder how other teams at Apache and Codehaus are doing with SVN....
>
>
> --
> David Sean Taylor
> Bluesunrise Software
> david@bluesunrise.com
> [office] +01 707 773-4646
> [mobile] +01 707 529 9194
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: SVN Problems (was RE: [J2] Last Night Commit - Build Still Broken
- Persistence Dependency Issue)
Posted by David Sean Taylor <da...@bluesunrise.com>.
Scott T Weaver wrote:
> So I'm not the only one suffering that is actually a relief (I feel like
> less of an idiot now). Yeah, I am checking out fresh as we speak :(
>
> Can anyone help David and me by giving us a little direction on how to
> better resolve our SVN problems? I can only speak for myself but every time
> I have sync with SVN I spend at least an hour trying to figure out what went
> wrong. And it is not only the Eclipse plugin, TortoiseSVN and the CL
> interface are just as crappy in terms of breaking my workspace.
>
My experience with SVN is that its perceptually slower than CVS, no
doubt. I really miss the snappiness of CVS + Eclipse.
Did have a SVN problem yesterday, a directory was locked locally. I typed
svn cleanup
and then seemed to do the trick.
Other than that, I haven't experienced any problems recently.
Generally, I follow XP practices, and commit often and in small
increments. Perhaps due to my cautious practices, Ive been insulated
from the problems that you have experienced with SVN. I am by no means
recommending that you follow my practices. Im just trying to communicate
my experiences to help out.
One other factor may be proxy servers, as I do not have one here.
I wonder how other teams at Apache and Codehaus are doing with SVN....
--
David Sean Taylor
Bluesunrise Software
david@bluesunrise.com
[office] +01 707 773-4646
[mobile] +01 707 529 9194
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
SVN Problems (was RE: [J2] Last Night Commit - Build Still Broken - Persistence Dependency Issue)
Posted by Scott T Weaver <sc...@binary-designs.net>.
So I'm not the only one suffering that is actually a relief (I feel like
less of an idiot now). Yeah, I am checking out fresh as we speak :(
Can anyone help David and me by giving us a little direction on how to
better resolve our SVN problems? I can only speak for myself but every time
I have sync with SVN I spend at least an hour trying to figure out what went
wrong. And it is not only the Eclipse plugin, TortoiseSVN and the CL
interface are just as crappy in terms of breaking my workspace.
Regards,
Scott
> -----Original Message-----
> From: David Le Strat [mailto:dlestrat@yahoo.com]
> Sent: Thursday, July 14, 2005 10:26 AM
> To: Jetspeed Developers List
> Subject: RE: [J2] Last Night Commit - Build Still Broken - Persistence
> Dependency Issue
>
> Thank you Scott, I have had issues with SVN as well.
> I ended up getting a fresh check out...
>
> Regards,
>
> David.
>
> --- Scott T Weaver
> <sc...@binary-designs.net> wrote:
>
> > Well I'm sorry I caused so much trouble :( My SVN
> > is so hosed right now I
> > can't even update. I am really at my wits end with
> > it. When/if I get your
> > changes down I will try to fix any remaining issues.
> >
> > Regards,
> > Scott
> >
> > > -----Original Message-----
> > > From: David Le Strat [mailto:dlestrat@yahoo.com]
> > > Sent: Thursday, July 14, 2005 10:16 AM
> > > To: Jetspeed Developers List
> > > Subject: RE: [J2] Last Night Commit - Build Still
> > Broken - Persistence
> > > Dependency Issue
> > >
> > > Scott,
> > >
> > > I had quite a few issues.
> > >
> > > 1. The plugin was broken, it could not resolve
> > some of
> > > the dependencies versions. See
> > > maven-plugin/maven.xml.
> > > 2. The initMavenPlugin target was broken,
> > something to
> > > do with initializing with webapp and without it.
> > > deploy-plugin-withoutwebapp had an invalid
> > reference
> > > to copyPortalWebapp.
> > > 3. The j2:genapp.portal target was broken. The
> > > template project.xml did not have the correct
> > > dependencies and the plugin did not have the
> > needed
> > > properties.
> > > 4. Some of the dependencies for portal-site, gems
> > did
> > > not resolve porperly.
> > > 5. The persistence component was removed, but
> > > dependencies were still being references.
> > >
> > > When I cleaned up my repo, cache and
> > > portal-webapp/target this morning, to do a test
> > with
> > > everything clean and deployed the jetspeed app
> > without
> > > jetspeed-persistence (as expected). I got an
> > issue
> > > with assembly when starting the engine as
> > mentionned
> > > in my previous email.
> > >
> > > Regards,
> > >
> > > David Le Strat.
> > >
> > > --- Scott T Weaver
> > > <sc...@binary-designs.net> wrote:
> > >
> > > > David,
> > > >
> > > > Can you tell me exactly which parts of the build
> > > > were broke? I had it
> > > > running just fine yesterday before I committed.
> > I
> > > > would like to know
> > > > exactly what I broke. There is a good chance I
> > > > forgot something yesterday
> > > > due to my sheer frustration with SVN.
> > > >
> > > > Regards,
> > > > -Scott
> > > >
> > > > > -----Original Message-----
> > > > > From: David Le Strat
> > [mailto:dlestrat@yahoo.com]
> > > > > Sent: Thursday, July 14, 2005 9:57 AM
> > > > > To: jetspeed-dev@portals.apache.org;
> > > > jetspeed-user@portals.apache.org
> > > > > Subject: [J2] Last Night Commit - Build Still
> > > > Broken - Persistence
> > > > > Dependency Issue
> > > > >
> > > > > All,
> > > > >
> > > > > I decided to be thourough and do some more
> > testing
> > > > > this morning after spending quite a bit of
> > time
> > > > fixing
> > > > > the build last night. I cleaned all my old
> > deps,
> > > > my
> > > > > plugin cache, etc. The good news is that it
> > > > builds
> > > > > and all build functionality seems to be
> > working.
> > > > One
> > > > > caveat is that you now need jetspeed.version
> > in
> > > > > {user.home}/build.properties. I updated
> > > > >
> > > >
> > >
> >
> http://www.geocities.com/dlestrat/etc/j2/buildChangeDocs.pdf
> > > > > and have a blog entry on how to get started
> > with
> > > > the
> > > > > build on http://dlsthoughts.blogspot.com.
> > > > >
> > > > > The bad news is that the dependency on
> > > > > jetspeed-persistence had to be removed, the
> > > > component
> > > > > was deleted. When deploying to Tomcat, some
> > > > Spring
> > > > > dependencies are not resolved correctly.
> > Please
> > > > find
> > > > > enclosed the logs.
> > > > >
> > > > > Regards,
> > > > >
> > > > > David Le Strat.
> > > > >
> > > > > ________________________
> > > > > David Le Strat
> > > > > Blogging @ http://dlsthoughts.blogspot.com
> > > > >
> > > > >
> > __________________________________________________
> > > > > Do You Yahoo!?
> > > > > Tired of spam? Yahoo! Mail has the best spam
> > > > protection around
> > > > > http://mail.yahoo.com
> > > >
> > > >
> > > >
> > >
> >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail:
> > > > jetspeed-dev-unsubscribe@portals.apache.org
> > > > For additional commands, e-mail:
> > > > jetspeed-dev-help@portals.apache.org
> > > >
> > > >
> > >
> > >
> > > ________________________
> > > David Le Strat
> > > Blogging @ http://dlsthoughts.blogspot.com
> > >
> > >
> > >
> > >
> > ____________________________________________________
> > > Start your day with Yahoo! - make it your home
> > page
> > > http://www.yahoo.com/r/hs
> > >
> > >
> > >
> >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> > jetspeed-dev-unsubscribe@portals.apache.org
> > > For additional commands, e-mail:
> > jetspeed-dev-help@portals.apache.org
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> > jetspeed-dev-unsubscribe@portals.apache.org
> > For additional commands, e-mail:
> > jetspeed-dev-help@portals.apache.org
> >
> >
>
>
> ________________________
> David Le Strat
> Blogging @ http://dlsthoughts.blogspot.com
>
>
>
> ____________________________________________________
> Start your day with Yahoo! - make it your home page
> http://www.yahoo.com/r/hs
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
RE: [J2] Last Night Commit - Build Still Broken - Persistence Dependency Issue
Posted by David Le Strat <dl...@yahoo.com>.
Thank you Scott, I have had issues with SVN as well.
I ended up getting a fresh check out...
Regards,
David.
--- Scott T Weaver
<sc...@binary-designs.net> wrote:
> Well I'm sorry I caused so much trouble :( My SVN
> is so hosed right now I
> can't even update. I am really at my wits end with
> it. When/if I get your
> changes down I will try to fix any remaining issues.
>
> Regards,
> Scott
>
> > -----Original Message-----
> > From: David Le Strat [mailto:dlestrat@yahoo.com]
> > Sent: Thursday, July 14, 2005 10:16 AM
> > To: Jetspeed Developers List
> > Subject: RE: [J2] Last Night Commit - Build Still
> Broken - Persistence
> > Dependency Issue
> >
> > Scott,
> >
> > I had quite a few issues.
> >
> > 1. The plugin was broken, it could not resolve
> some of
> > the dependencies versions. See
> > maven-plugin/maven.xml.
> > 2. The initMavenPlugin target was broken,
> something to
> > do with initializing with webapp and without it.
> > deploy-plugin-withoutwebapp had an invalid
> reference
> > to copyPortalWebapp.
> > 3. The j2:genapp.portal target was broken. The
> > template project.xml did not have the correct
> > dependencies and the plugin did not have the
> needed
> > properties.
> > 4. Some of the dependencies for portal-site, gems
> did
> > not resolve porperly.
> > 5. The persistence component was removed, but
> > dependencies were still being references.
> >
> > When I cleaned up my repo, cache and
> > portal-webapp/target this morning, to do a test
> with
> > everything clean and deployed the jetspeed app
> without
> > jetspeed-persistence (as expected). I got an
> issue
> > with assembly when starting the engine as
> mentionned
> > in my previous email.
> >
> > Regards,
> >
> > David Le Strat.
> >
> > --- Scott T Weaver
> > <sc...@binary-designs.net> wrote:
> >
> > > David,
> > >
> > > Can you tell me exactly which parts of the build
> > > were broke? I had it
> > > running just fine yesterday before I committed.
> I
> > > would like to know
> > > exactly what I broke. There is a good chance I
> > > forgot something yesterday
> > > due to my sheer frustration with SVN.
> > >
> > > Regards,
> > > -Scott
> > >
> > > > -----Original Message-----
> > > > From: David Le Strat
> [mailto:dlestrat@yahoo.com]
> > > > Sent: Thursday, July 14, 2005 9:57 AM
> > > > To: jetspeed-dev@portals.apache.org;
> > > jetspeed-user@portals.apache.org
> > > > Subject: [J2] Last Night Commit - Build Still
> > > Broken - Persistence
> > > > Dependency Issue
> > > >
> > > > All,
> > > >
> > > > I decided to be thourough and do some more
> testing
> > > > this morning after spending quite a bit of
> time
> > > fixing
> > > > the build last night. I cleaned all my old
> deps,
> > > my
> > > > plugin cache, etc. The good news is that it
> > > builds
> > > > and all build functionality seems to be
> working.
> > > One
> > > > caveat is that you now need jetspeed.version
> in
> > > > {user.home}/build.properties. I updated
> > > >
> > >
> >
>
http://www.geocities.com/dlestrat/etc/j2/buildChangeDocs.pdf
> > > > and have a blog entry on how to get started
> with
> > > the
> > > > build on http://dlsthoughts.blogspot.com.
> > > >
> > > > The bad news is that the dependency on
> > > > jetspeed-persistence had to be removed, the
> > > component
> > > > was deleted. When deploying to Tomcat, some
> > > Spring
> > > > dependencies are not resolved correctly.
> Please
> > > find
> > > > enclosed the logs.
> > > >
> > > > Regards,
> > > >
> > > > David Le Strat.
> > > >
> > > > ________________________
> > > > David Le Strat
> > > > Blogging @ http://dlsthoughts.blogspot.com
> > > >
> > > >
> __________________________________________________
> > > > Do You Yahoo!?
> > > > Tired of spam? Yahoo! Mail has the best spam
> > > protection around
> > > > http://mail.yahoo.com
> > >
> > >
> > >
> >
>
---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> > > jetspeed-dev-unsubscribe@portals.apache.org
> > > For additional commands, e-mail:
> > > jetspeed-dev-help@portals.apache.org
> > >
> > >
> >
> >
> > ________________________
> > David Le Strat
> > Blogging @ http://dlsthoughts.blogspot.com
> >
> >
> >
> >
> ____________________________________________________
> > Start your day with Yahoo! - make it your home
> page
> > http://www.yahoo.com/r/hs
> >
> >
> >
>
---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> jetspeed-dev-unsubscribe@portals.apache.org
> > For additional commands, e-mail:
> jetspeed-dev-help@portals.apache.org
>
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail:
> jetspeed-dev-help@portals.apache.org
>
>
________________________
David Le Strat
Blogging @ http://dlsthoughts.blogspot.com
____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
RE: [J2] Last Night Commit - Build Still Broken - Persistence Dependency Issue
Posted by Scott T Weaver <sc...@binary-designs.net>.
Well I'm sorry I caused so much trouble :( My SVN is so hosed right now I
can't even update. I am really at my wits end with it. When/if I get your
changes down I will try to fix any remaining issues.
Regards,
Scott
> -----Original Message-----
> From: David Le Strat [mailto:dlestrat@yahoo.com]
> Sent: Thursday, July 14, 2005 10:16 AM
> To: Jetspeed Developers List
> Subject: RE: [J2] Last Night Commit - Build Still Broken - Persistence
> Dependency Issue
>
> Scott,
>
> I had quite a few issues.
>
> 1. The plugin was broken, it could not resolve some of
> the dependencies versions. See
> maven-plugin/maven.xml.
> 2. The initMavenPlugin target was broken, something to
> do with initializing with webapp and without it.
> deploy-plugin-withoutwebapp had an invalid reference
> to copyPortalWebapp.
> 3. The j2:genapp.portal target was broken. The
> template project.xml did not have the correct
> dependencies and the plugin did not have the needed
> properties.
> 4. Some of the dependencies for portal-site, gems did
> not resolve porperly.
> 5. The persistence component was removed, but
> dependencies were still being references.
>
> When I cleaned up my repo, cache and
> portal-webapp/target this morning, to do a test with
> everything clean and deployed the jetspeed app without
> jetspeed-persistence (as expected). I got an issue
> with assembly when starting the engine as mentionned
> in my previous email.
>
> Regards,
>
> David Le Strat.
>
> --- Scott T Weaver
> <sc...@binary-designs.net> wrote:
>
> > David,
> >
> > Can you tell me exactly which parts of the build
> > were broke? I had it
> > running just fine yesterday before I committed. I
> > would like to know
> > exactly what I broke. There is a good chance I
> > forgot something yesterday
> > due to my sheer frustration with SVN.
> >
> > Regards,
> > -Scott
> >
> > > -----Original Message-----
> > > From: David Le Strat [mailto:dlestrat@yahoo.com]
> > > Sent: Thursday, July 14, 2005 9:57 AM
> > > To: jetspeed-dev@portals.apache.org;
> > jetspeed-user@portals.apache.org
> > > Subject: [J2] Last Night Commit - Build Still
> > Broken - Persistence
> > > Dependency Issue
> > >
> > > All,
> > >
> > > I decided to be thourough and do some more testing
> > > this morning after spending quite a bit of time
> > fixing
> > > the build last night. I cleaned all my old deps,
> > my
> > > plugin cache, etc. The good news is that it
> > builds
> > > and all build functionality seems to be working.
> > One
> > > caveat is that you now need jetspeed.version in
> > > {user.home}/build.properties. I updated
> > >
> >
> http://www.geocities.com/dlestrat/etc/j2/buildChangeDocs.pdf
> > > and have a blog entry on how to get started with
> > the
> > > build on http://dlsthoughts.blogspot.com.
> > >
> > > The bad news is that the dependency on
> > > jetspeed-persistence had to be removed, the
> > component
> > > was deleted. When deploying to Tomcat, some
> > Spring
> > > dependencies are not resolved correctly. Please
> > find
> > > enclosed the logs.
> > >
> > > Regards,
> > >
> > > David Le Strat.
> > >
> > > ________________________
> > > David Le Strat
> > > Blogging @ http://dlsthoughts.blogspot.com
> > >
> > > __________________________________________________
> > > Do You Yahoo!?
> > > Tired of spam? Yahoo! Mail has the best spam
> > protection around
> > > http://mail.yahoo.com
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> > jetspeed-dev-unsubscribe@portals.apache.org
> > For additional commands, e-mail:
> > jetspeed-dev-help@portals.apache.org
> >
> >
>
>
> ________________________
> David Le Strat
> Blogging @ http://dlsthoughts.blogspot.com
>
>
>
> ____________________________________________________
> Start your day with Yahoo! - make it your home page
> http://www.yahoo.com/r/hs
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
RE: [J2] Last Night Commit - Build Still Broken - Persistence Dependency Issue
Posted by David Le Strat <dl...@yahoo.com>.
Scott,
I had quite a few issues.
1. The plugin was broken, it could not resolve some of
the dependencies versions. See
maven-plugin/maven.xml.
2. The initMavenPlugin target was broken, something to
do with initializing with webapp and without it.
deploy-plugin-withoutwebapp had an invalid reference
to copyPortalWebapp.
3. The j2:genapp.portal target was broken. The
template project.xml did not have the correct
dependencies and the plugin did not have the needed
properties.
4. Some of the dependencies for portal-site, gems did
not resolve porperly.
5. The persistence component was removed, but
dependencies were still being references.
When I cleaned up my repo, cache and
portal-webapp/target this morning, to do a test with
everything clean and deployed the jetspeed app without
jetspeed-persistence (as expected). I got an issue
with assembly when starting the engine as mentionned
in my previous email.
Regards,
David Le Strat.
--- Scott T Weaver
<sc...@binary-designs.net> wrote:
> David,
>
> Can you tell me exactly which parts of the build
> were broke? I had it
> running just fine yesterday before I committed. I
> would like to know
> exactly what I broke. There is a good chance I
> forgot something yesterday
> due to my sheer frustration with SVN.
>
> Regards,
> -Scott
>
> > -----Original Message-----
> > From: David Le Strat [mailto:dlestrat@yahoo.com]
> > Sent: Thursday, July 14, 2005 9:57 AM
> > To: jetspeed-dev@portals.apache.org;
> jetspeed-user@portals.apache.org
> > Subject: [J2] Last Night Commit - Build Still
> Broken - Persistence
> > Dependency Issue
> >
> > All,
> >
> > I decided to be thourough and do some more testing
> > this morning after spending quite a bit of time
> fixing
> > the build last night. I cleaned all my old deps,
> my
> > plugin cache, etc. The good news is that it
> builds
> > and all build functionality seems to be working.
> One
> > caveat is that you now need jetspeed.version in
> > {user.home}/build.properties. I updated
> >
>
http://www.geocities.com/dlestrat/etc/j2/buildChangeDocs.pdf
> > and have a blog entry on how to get started with
> the
> > build on http://dlsthoughts.blogspot.com.
> >
> > The bad news is that the dependency on
> > jetspeed-persistence had to be removed, the
> component
> > was deleted. When deploying to Tomcat, some
> Spring
> > dependencies are not resolved correctly. Please
> find
> > enclosed the logs.
> >
> > Regards,
> >
> > David Le Strat.
> >
> > ________________________
> > David Le Strat
> > Blogging @ http://dlsthoughts.blogspot.com
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam? Yahoo! Mail has the best spam
> protection around
> > http://mail.yahoo.com
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail:
> jetspeed-dev-help@portals.apache.org
>
>
________________________
David Le Strat
Blogging @ http://dlsthoughts.blogspot.com
____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
RE: [J2] Last Night Commit - Build Still Broken - Persistence Dependency Issue
Posted by Scott T Weaver <sc...@binary-designs.net>.
David,
Can you tell me exactly which parts of the build were broke? I had it
running just fine yesterday before I committed. I would like to know
exactly what I broke. There is a good chance I forgot something yesterday
due to my sheer frustration with SVN.
Regards,
-Scott
> -----Original Message-----
> From: David Le Strat [mailto:dlestrat@yahoo.com]
> Sent: Thursday, July 14, 2005 9:57 AM
> To: jetspeed-dev@portals.apache.org; jetspeed-user@portals.apache.org
> Subject: [J2] Last Night Commit - Build Still Broken - Persistence
> Dependency Issue
>
> All,
>
> I decided to be thourough and do some more testing
> this morning after spending quite a bit of time fixing
> the build last night. I cleaned all my old deps, my
> plugin cache, etc. The good news is that it builds
> and all build functionality seems to be working. One
> caveat is that you now need jetspeed.version in
> {user.home}/build.properties. I updated
> http://www.geocities.com/dlestrat/etc/j2/buildChangeDocs.pdf
> and have a blog entry on how to get started with the
> build on http://dlsthoughts.blogspot.com.
>
> The bad news is that the dependency on
> jetspeed-persistence had to be removed, the component
> was deleted. When deploying to Tomcat, some Spring
> dependencies are not resolved correctly. Please find
> enclosed the logs.
>
> Regards,
>
> David Le Strat.
>
> ________________________
> David Le Strat
> Blogging @ http://dlsthoughts.blogspot.com
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[J2] Last Night Commit - Build Still Broken - Persistence Dependency Issue
Posted by David Le Strat <dl...@yahoo.com>.
All,
I decided to be thourough and do some more testing
this morning after spending quite a bit of time fixing
the build last night. I cleaned all my old deps, my
plugin cache, etc. The good news is that it builds
and all build functionality seems to be working. One
caveat is that you now need jetspeed.version in
{user.home}/build.properties. I updated
http://www.geocities.com/dlestrat/etc/j2/buildChangeDocs.pdf
and have a blog entry on how to get started with the
build on http://dlsthoughts.blogspot.com.
The bad news is that the dependency on
jetspeed-persistence had to be removed, the component
was deleted. When deploying to Tomcat, some Spring
dependencies are not resolved correctly. Please find
enclosed the logs.
Regards,
David Le Strat.
________________________
David Le Strat
Blogging @ http://dlsthoughts.blogspot.com
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
RE: [J2] Build Process Changes - Version 2.0-M4-SNAPSHOT and above.
Posted by Scott T Weaver <sc...@binary-designs.net>.
David,
I just did that and it works fine. When you run intitMavenPlugin, it writes
that version into plugin.properties which be used as a default if the user
doesn't override in their own build.properties. I will commit the change
now.
Regards,
-Scott
> -----Original Message-----
> From: David Sean Taylor [mailto:david@bluesunrise.com]
> Sent: Thursday, July 14, 2005 3:15 PM
> To: Jetspeed Users List
> Subject: Re: [J2] Build Process Changes - Version 2.0-M4-SNAPSHOT and
> above.
>
> Scott T Weaver wrote:
> > Why do we require the jetspeed.version to be manually set in
> > build.properties? Can't we just put the default version in
> > project.properties and allow users to override it in there
> build.properties
> > if need be?
> >
> I agree.
> Think the reason is because the plugin cant pick it up from the root
> jetspeed directory. Perhaps it could be added to the project.properties
> under the plugin...
>
>
> --
> David Sean Taylor
> Bluesunrise Software
> david@bluesunrise.com
> [office] +01 707 773-4646
> [mobile] +01 707 529 9194
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: [J2] Build Process Changes - Version 2.0-M4-SNAPSHOT and above.
Posted by David Sean Taylor <da...@bluesunrise.com>.
Scott T Weaver wrote:
> Why do we require the jetspeed.version to be manually set in
> build.properties? Can't we just put the default version in
> project.properties and allow users to override it in there build.properties
> if need be?
>
I agree.
Think the reason is because the plugin cant pick it up from the root
jetspeed directory. Perhaps it could be added to the project.properties
under the plugin...
--
David Sean Taylor
Bluesunrise Software
david@bluesunrise.com
[office] +01 707 773-4646
[mobile] +01 707 529 9194
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
RE: [J2] Build Process Changes - Version 2.0-M4-SNAPSHOT and above.
Posted by Scott T Weaver <sc...@binary-designs.net>.
Why do we require the jetspeed.version to be manually set in
build.properties? Can't we just put the default version in
project.properties and allow users to override it in there build.properties
if need be?
Regards,
Scott
> -----Original Message-----
> From: David Le Strat [mailto:dlestrat@yahoo.com]
> Sent: Thursday, July 14, 2005 2:27 PM
> To: Jetspeed Users List
> Subject: RE: [J2] Build Process Changes - Version 2.0-M4-SNAPSHOT and
> above.
>
> No changes were made to the security schema that I am
> aware of.
>
> David.
>
> --- Scott T Weaver
> <sc...@binary-designs.net> wrote:
>
> > Hi Frank,
> >
> > That would be great! AFAIK, the security schema has
> > changed at all since m2
> > (someone correct me if I'm wrong). With your
> > permission I would like to
> > commit your changes into Jetspeed.
> >
> > Regard,
> > Scott
> >
> > > -----Original Message-----
> > > From: Frank Villarreal
> > [mailto:f_villarreal@tetco.com]
> > > Sent: Thursday, July 14, 2005 1:39 PM
> > > To: Jetspeed Users List
> > > Subject: RE: [J2] Build Process Changes - Version
> > 2.0-M4-SNAPSHOT and
> > > above.
> > >
> > > Scott,
> > >
> > > I use MSSQL2000 and modified the resulting sql
> > scripts that maven
> > > generates.
> > > Unfortunately, I don't understand Maven too well
> > so I didn't mess with it
> > > other than commenting out the sql regeneration
> > goal. One more thing, I
> > > use
> > > Jetspeed2-m2, so my scripts are most likely
> > out-of-date if the schema has
> > > been modified in any way. Would you like me to
> > email them to you?
> > >
> > > - Frank
> > >
> > > > -----Original Message-----
> > > > From: Scott T Weaver
> > [mailto:scotts-jetspeed-list@binary-designs.net]
> > > > Sent: Thursday, July 14, 2005 11:16 AM
> > > > To: 'Jetspeed Users List'
> > > > Subject: RE: [J2] Build Process Changes -
> > Version 2.0-M4-SNAPSHOT and
> > > > above.
> > > >
> > > >
> > > > Have we found a solution to fix the MSSQL db for
> > Jetspeed 2 other than
> > > > commenting (and effectively breaking) certain
> > pieces of the security
> > > > schema??? Unfortunately, I know nothing about
> > MSSQL but am
> > > > forced to deploy
> > > > to it in my production environment.
> > > >
> > > > Regards,
> > > > Scott
> > > >
> > > > > -----Original Message-----
> > > > > From: David Le Strat
> > [mailto:dlestrat@yahoo.com]
> > > > > Sent: Wednesday, July 13, 2005 5:32 PM
> > > > > To: Jetspeed Users List
> > > > > Subject: RE: [J2] Build Process Changes -
> > Version 2.0-M4-SNAPSHOT and
> > > > > above.
> > > > >
> > > > > Scott,
> > > > >
> > > > > copyDb is not need anymore as I relocated the
> > sql and
> > > > > schema directories to the
> > > > > maven-plugin/plugin-resources.
> > > > >
> > > > > David.
> > > > >
> > > > > --- Scott T Weaver
> > > > > <sc...@binary-designs.net>
> > wrote:
> > > > >
> > > > > > David,
> > > > > >
> > > > > > I am can't seem to find where the dbCopy
> > goal,
> > > > > > referenced from
> > > > > > maven-plugin/maven.xml, is defined. I had
> > to
> > > > > > comment it out to get
> > > > > > everything to run.
> > > > > >
> > > > > > Thanks,
> > > > > > Scott
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: David Le Strat
> > [mailto:dlestrat@yahoo.com]
> > > > > > > Sent: Tuesday, July 12, 2005 10:36 PM
> > > > > > > To: jetspeed-dev@portals.apache.org;
> > > > > > jetspeed-user@portals.apache.org
> > > > > > > Subject: [J2] Build Process Changes -
> > Version
> > > > > > 2.0-M4-SNAPSHOT and above.
> > > > > > >
> > > > > > > All,
> > > > > > >
> > > > > > > Step 2 of Jetspeed's build process clean
> > up has
> > > > > > been
> > > > > > > committed. As a result, a few things have
> > changed
> > > > > > when
> > > > > > > build the latest Jetspeed (2.0-M4-SNAPSHOT
> > and
> > > > > > above).
> > > > > > > A summary of the changes made can be
> > found in <a
> > > > > > >
> > href="http://issues.apache.org/jira/browse/JS2-
> > > > > > > 304?page=comments#action_12315646">Apache
> > > > > > > Jetspeed Jira</a>. Also detailed <a
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> href="http://www.geocities.com/dlestrat/etc/j2/buildChangeDocs.pdf">build
> > > > > > > changes documentation</a> is temporary
> > available
> > > > > > on my
> > > > > > > web site in PDF format until the Jetspeed
> > web site
> > > > > > > gets regenerated.
> > > > > > >
> > > > > > > Then new steps to get started are changed
> > as
> > > > > > follow:
> > > > > > >
> > > > > > > If you are build off of Jetspeed 2 source
> > code for
> > > > > > the
> > > > > > > first time:
> > > > > > > <pre>
> > > > > > > cd ${jetspeed-2-home}
> > > > > > > maven initMavenPlugin allClean allBuild
> > > > > > > </pre>
> > > > > > > If the Jetspeed 2 maven plugin is
> > installed, then
> > > > > > to
> > > > > > > build the portal and all its components
> > run:
> > > > > > > <pre>
> > > > > > > cd ${jetspeed-2-home}
> > > > > > > maven allClean allBuild
> > > > > > > </pre>
> > > > > > > If you are using the Hypersonic SQL
> > database,
> > > > > > start
> > > > > > > the production Hypersonic database by
> > typing
> > > > > > > <pre>
> > > > > > > maven j2:start.production.server
> > > > > > > </pre>
> > > > > > > Then run quickStart (in seperate
> > window/terminal
> > > > > > > session):
> > > > > > > <pre>
> > > > > > > cd ${jetspeed-2-home}
> > > > > > > maven j2:quickStart
> > > > > > > </pre>
> > > > > > > This will recreate the DB to deploy into.
> > WARNING
> > > > > > This
> > > > > > > will drop all the tables and data in the
> > > > > > production
> > > > > > > database.
> > > > > > >
> > > > > > > 3. Start up Tomcat. With a browser, go to:
> > > > > > > http://localhost:8080/jetspeed
> > > > > > >
> > > > > > > If you are creating a new Portal
> > Application
> > > > > > without
> > > > > > > the Jetspeed source:
> > > > > > >
> > > > > > > In order to get started with a new portal
> > > > > > application
> > > > > > > that will include a developer's specific
> > portal
> > > > > > > customization, Jetspeed 2 provides as part
> > of its
> > > > > > > Maven Plugin a goal that can get you
> > started with
> > > > > > your
> > > > > > > project. To do so:
> > > > > > >
> > > > > > > 1. Make sure that the following properties
> > are set
> > > > > > in
> > > > > > > your your ${USER_HOME}/build.properties
> > file:
> >
> === message truncated ===
>
>
> ________________________
> David Le Strat
> Blogging @ http://dlsthoughts.blogspot.com
>
>
>
> ____________________________________________________
> Start your day with Yahoo! - make it your home page
> http://www.yahoo.com/r/hs
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
RE: [J2] Build Process Changes - Version 2.0-M4-SNAPSHOT and above.
Posted by David Le Strat <dl...@yahoo.com>.
No changes were made to the security schema that I am
aware of.
David.
--- Scott T Weaver
<sc...@binary-designs.net> wrote:
> Hi Frank,
>
> That would be great! AFAIK, the security schema has
> changed at all since m2
> (someone correct me if I'm wrong). With your
> permission I would like to
> commit your changes into Jetspeed.
>
> Regard,
> Scott
>
> > -----Original Message-----
> > From: Frank Villarreal
> [mailto:f_villarreal@tetco.com]
> > Sent: Thursday, July 14, 2005 1:39 PM
> > To: Jetspeed Users List
> > Subject: RE: [J2] Build Process Changes - Version
> 2.0-M4-SNAPSHOT and
> > above.
> >
> > Scott,
> >
> > I use MSSQL2000 and modified the resulting sql
> scripts that maven
> > generates.
> > Unfortunately, I don't understand Maven too well
> so I didn't mess with it
> > other than commenting out the sql regeneration
> goal. One more thing, I
> > use
> > Jetspeed2-m2, so my scripts are most likely
> out-of-date if the schema has
> > been modified in any way. Would you like me to
> email them to you?
> >
> > - Frank
> >
> > > -----Original Message-----
> > > From: Scott T Weaver
> [mailto:scotts-jetspeed-list@binary-designs.net]
> > > Sent: Thursday, July 14, 2005 11:16 AM
> > > To: 'Jetspeed Users List'
> > > Subject: RE: [J2] Build Process Changes -
> Version 2.0-M4-SNAPSHOT and
> > > above.
> > >
> > >
> > > Have we found a solution to fix the MSSQL db for
> Jetspeed 2 other than
> > > commenting (and effectively breaking) certain
> pieces of the security
> > > schema??? Unfortunately, I know nothing about
> MSSQL but am
> > > forced to deploy
> > > to it in my production environment.
> > >
> > > Regards,
> > > Scott
> > >
> > > > -----Original Message-----
> > > > From: David Le Strat
> [mailto:dlestrat@yahoo.com]
> > > > Sent: Wednesday, July 13, 2005 5:32 PM
> > > > To: Jetspeed Users List
> > > > Subject: RE: [J2] Build Process Changes -
> Version 2.0-M4-SNAPSHOT and
> > > > above.
> > > >
> > > > Scott,
> > > >
> > > > copyDb is not need anymore as I relocated the
> sql and
> > > > schema directories to the
> > > > maven-plugin/plugin-resources.
> > > >
> > > > David.
> > > >
> > > > --- Scott T Weaver
> > > > <sc...@binary-designs.net>
> wrote:
> > > >
> > > > > David,
> > > > >
> > > > > I am can't seem to find where the dbCopy
> goal,
> > > > > referenced from
> > > > > maven-plugin/maven.xml, is defined. I had
> to
> > > > > comment it out to get
> > > > > everything to run.
> > > > >
> > > > > Thanks,
> > > > > Scott
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: David Le Strat
> [mailto:dlestrat@yahoo.com]
> > > > > > Sent: Tuesday, July 12, 2005 10:36 PM
> > > > > > To: jetspeed-dev@portals.apache.org;
> > > > > jetspeed-user@portals.apache.org
> > > > > > Subject: [J2] Build Process Changes -
> Version
> > > > > 2.0-M4-SNAPSHOT and above.
> > > > > >
> > > > > > All,
> > > > > >
> > > > > > Step 2 of Jetspeed's build process clean
> up has
> > > > > been
> > > > > > committed. As a result, a few things have
> changed
> > > > > when
> > > > > > build the latest Jetspeed (2.0-M4-SNAPSHOT
> and
> > > > > above).
> > > > > > A summary of the changes made can be
> found in <a
> > > > > >
> href="http://issues.apache.org/jira/browse/JS2-
> > > > > > 304?page=comments#action_12315646">Apache
> > > > > > Jetspeed Jira</a>. Also detailed <a
> > > > > >
> > > > >
> > > >
> > >
> >
>
href="http://www.geocities.com/dlestrat/etc/j2/buildChangeDocs.pdf">build
> > > > > > changes documentation</a> is temporary
> available
> > > > > on my
> > > > > > web site in PDF format until the Jetspeed
> web site
> > > > > > gets regenerated.
> > > > > >
> > > > > > Then new steps to get started are changed
> as
> > > > > follow:
> > > > > >
> > > > > > If you are build off of Jetspeed 2 source
> code for
> > > > > the
> > > > > > first time:
> > > > > > <pre>
> > > > > > cd ${jetspeed-2-home}
> > > > > > maven initMavenPlugin allClean allBuild
> > > > > > </pre>
> > > > > > If the Jetspeed 2 maven plugin is
> installed, then
> > > > > to
> > > > > > build the portal and all its components
> run:
> > > > > > <pre>
> > > > > > cd ${jetspeed-2-home}
> > > > > > maven allClean allBuild
> > > > > > </pre>
> > > > > > If you are using the Hypersonic SQL
> database,
> > > > > start
> > > > > > the production Hypersonic database by
> typing
> > > > > > <pre>
> > > > > > maven j2:start.production.server
> > > > > > </pre>
> > > > > > Then run quickStart (in seperate
> window/terminal
> > > > > > session):
> > > > > > <pre>
> > > > > > cd ${jetspeed-2-home}
> > > > > > maven j2:quickStart
> > > > > > </pre>
> > > > > > This will recreate the DB to deploy into.
> WARNING
> > > > > This
> > > > > > will drop all the tables and data in the
> > > > > production
> > > > > > database.
> > > > > >
> > > > > > 3. Start up Tomcat. With a browser, go to:
> > > > > > http://localhost:8080/jetspeed
> > > > > >
> > > > > > If you are creating a new Portal
> Application
> > > > > without
> > > > > > the Jetspeed source:
> > > > > >
> > > > > > In order to get started with a new portal
> > > > > application
> > > > > > that will include a developer's specific
> portal
> > > > > > customization, Jetspeed 2 provides as part
> of its
> > > > > > Maven Plugin a goal that can get you
> started with
> > > > > your
> > > > > > project. To do so:
> > > > > >
> > > > > > 1. Make sure that the following properties
> are set
> > > > > in
> > > > > > your your ${USER_HOME}/build.properties
> file:
>
=== message truncated ===
________________________
David Le Strat
Blogging @ http://dlsthoughts.blogspot.com
____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
RE: [J2] Build Process Changes - Version 2.0-M4-SNAPSHOT and above.
Posted by Scott T Weaver <sc...@binary-designs.net>.
Hi Frank,
That would be great! AFAIK, the security schema has changed at all since m2
(someone correct me if I'm wrong). With your permission I would like to
commit your changes into Jetspeed.
Regard,
Scott
> -----Original Message-----
> From: Frank Villarreal [mailto:f_villarreal@tetco.com]
> Sent: Thursday, July 14, 2005 1:39 PM
> To: Jetspeed Users List
> Subject: RE: [J2] Build Process Changes - Version 2.0-M4-SNAPSHOT and
> above.
>
> Scott,
>
> I use MSSQL2000 and modified the resulting sql scripts that maven
> generates.
> Unfortunately, I don't understand Maven too well so I didn't mess with it
> other than commenting out the sql regeneration goal. One more thing, I
> use
> Jetspeed2-m2, so my scripts are most likely out-of-date if the schema has
> been modified in any way. Would you like me to email them to you?
>
> - Frank
>
> > -----Original Message-----
> > From: Scott T Weaver [mailto:scotts-jetspeed-list@binary-designs.net]
> > Sent: Thursday, July 14, 2005 11:16 AM
> > To: 'Jetspeed Users List'
> > Subject: RE: [J2] Build Process Changes - Version 2.0-M4-SNAPSHOT and
> > above.
> >
> >
> > Have we found a solution to fix the MSSQL db for Jetspeed 2 other than
> > commenting (and effectively breaking) certain pieces of the security
> > schema??? Unfortunately, I know nothing about MSSQL but am
> > forced to deploy
> > to it in my production environment.
> >
> > Regards,
> > Scott
> >
> > > -----Original Message-----
> > > From: David Le Strat [mailto:dlestrat@yahoo.com]
> > > Sent: Wednesday, July 13, 2005 5:32 PM
> > > To: Jetspeed Users List
> > > Subject: RE: [J2] Build Process Changes - Version 2.0-M4-SNAPSHOT and
> > > above.
> > >
> > > Scott,
> > >
> > > copyDb is not need anymore as I relocated the sql and
> > > schema directories to the
> > > maven-plugin/plugin-resources.
> > >
> > > David.
> > >
> > > --- Scott T Weaver
> > > <sc...@binary-designs.net> wrote:
> > >
> > > > David,
> > > >
> > > > I am can't seem to find where the dbCopy goal,
> > > > referenced from
> > > > maven-plugin/maven.xml, is defined. I had to
> > > > comment it out to get
> > > > everything to run.
> > > >
> > > > Thanks,
> > > > Scott
> > > >
> > > > > -----Original Message-----
> > > > > From: David Le Strat [mailto:dlestrat@yahoo.com]
> > > > > Sent: Tuesday, July 12, 2005 10:36 PM
> > > > > To: jetspeed-dev@portals.apache.org;
> > > > jetspeed-user@portals.apache.org
> > > > > Subject: [J2] Build Process Changes - Version
> > > > 2.0-M4-SNAPSHOT and above.
> > > > >
> > > > > All,
> > > > >
> > > > > Step 2 of Jetspeed's build process clean up has
> > > > been
> > > > > committed. As a result, a few things have changed
> > > > when
> > > > > build the latest Jetspeed (2.0-M4-SNAPSHOT and
> > > > above).
> > > > > A summary of the changes made can be found in <a
> > > > > href="http://issues.apache.org/jira/browse/JS2-
> > > > > 304?page=comments#action_12315646">Apache
> > > > > Jetspeed Jira</a>. Also detailed <a
> > > > >
> > > >
> > >
> >
> href="http://www.geocities.com/dlestrat/etc/j2/buildChangeDocs.pdf">build
> > > > > changes documentation</a> is temporary available
> > > > on my
> > > > > web site in PDF format until the Jetspeed web site
> > > > > gets regenerated.
> > > > >
> > > > > Then new steps to get started are changed as
> > > > follow:
> > > > >
> > > > > If you are build off of Jetspeed 2 source code for
> > > > the
> > > > > first time:
> > > > > <pre>
> > > > > cd ${jetspeed-2-home}
> > > > > maven initMavenPlugin allClean allBuild
> > > > > </pre>
> > > > > If the Jetspeed 2 maven plugin is installed, then
> > > > to
> > > > > build the portal and all its components run:
> > > > > <pre>
> > > > > cd ${jetspeed-2-home}
> > > > > maven allClean allBuild
> > > > > </pre>
> > > > > If you are using the Hypersonic SQL database,
> > > > start
> > > > > the production Hypersonic database by typing
> > > > > <pre>
> > > > > maven j2:start.production.server
> > > > > </pre>
> > > > > Then run quickStart (in seperate window/terminal
> > > > > session):
> > > > > <pre>
> > > > > cd ${jetspeed-2-home}
> > > > > maven j2:quickStart
> > > > > </pre>
> > > > > This will recreate the DB to deploy into. WARNING
> > > > This
> > > > > will drop all the tables and data in the
> > > > production
> > > > > database.
> > > > >
> > > > > 3. Start up Tomcat. With a browser, go to:
> > > > > http://localhost:8080/jetspeed
> > > > >
> > > > > If you are creating a new Portal Application
> > > > without
> > > > > the Jetspeed source:
> > > > >
> > > > > In order to get started with a new portal
> > > > application
> > > > > that will include a developer's specific portal
> > > > > customization, Jetspeed 2 provides as part of its
> > > > > Maven Plugin a goal that can get you started with
> > > > your
> > > > > project. To do so:
> > > > >
> > > > > 1. Make sure that the following properties are set
> > > > in
> > > > > your your ${USER_HOME}/build.properties file:
> > > > >
> > > > > - org.apache.jetspeed.portal.name: e.g.
> > > > testportal.
> > > > > The name of your new portal application. This will
> > > > > also be used as the artifactId for your project in
> > > > the
> > > > > maven repository.
> > > > > - org.apache.jetspeed.genapp.home: e.g.
> > > > > C:/tools/workspace/testportal. The location where
> > > > your
> > > > > new portal application should be created.
> > > > > - org.apache.jetspeed.genapp.groupId: e.g.
> > > > testportal.
> > > > > The maven pom group id indicates the group
> > > > location
> > > > > for your project in the maven repository.
> > > > > - org.apache.jetspeed.genapp.name: e.g. My Test
> > > > > Portal. A friendly name for your new portal.
> > > > > - org.apache.jetspeed.genapp.currentVersion: e.g.
> > > > 1.0.
> > > > > The current version for your new portal
> > > > application.
> > > > >
> > > > > 2. Once the above properties are set, make sure
> > > > that
> > > > > the Jetspeed 2 Maven Plugin is installed on your
> > > > local
> > > > > machine. You can install the Jetspeed 2 Maven
> > > > Plugin
> > > > > as follow:
> > > > > <pre>
> > > > > maven -DartifactId=maven-jetspeed2-plugin
> > > > > -DgroupId=jetspeed2
> > > > > -Dversion=2.0-M4-SNAPSHOT plugin:download
> > > > > </pre>
> > > > > where
> > > > >
> > > > > - artifactId: The name of the Jetspeed2 plugin
> > > > > artifact deployed to the maven repository.
> > > > > - groupId: The name of the group where the
> > > > Jetspeed2
> > > > > plugin is deployed in the maven repository.
> > > > > - version: The version that you want to use. For
> > > > this
> > > > > functionality, the version should be
> > > > 2.0-M4-SNAPSHOT
> > > > > or above.
> > > > >
> > > > > 3. Run the Jetspeed2 plugin target for generating
> > > > a
> > > > > new portal application:
> > > > > <pre>
> > > > > maven j2:genapp.portal
> > > > > </pre>
> > > > > 4. Go to the directory where you just created your
> > > > new
> > > > > portal application and execute:
> > > > > <pre>
> > > > > maven j2:portal.install
> > > > > maven j2:quickStart
> > > > > </pre>
> > > > > That's it, you are ready to get started with your
> > > > new
> > > > > portal application.
> > > > >
> > > > > Regards,
> > > > >
> > > > > David Le Strat.
> > > > >
> > > > > ________________________
> > > > > David Le Strat
> > > > > Blogging @ http://dlsthoughts.blogspot.com
> > > > >
> > > > > __________________________________________________
> > > > > Do You Yahoo!?
> > > > > Tired of spam? Yahoo! Mail has the best spam
> > > > protection around
> > > > > http://mail.yahoo.com
> > > > >
> > > > >
> > > >
> > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail:
> > > > jetspeed-user-unsubscribe@portals.apache.org
> > > > > For additional commands, e-mail:
> > > > jetspeed-user-help@portals.apache.org
> > > >
> > > >
> > > >
> > > >
> > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail:
> > > > jetspeed-user-unsubscribe@portals.apache.org
> > > > For additional commands, e-mail:
> > > > jetspeed-user-help@portals.apache.org
> > > >
> > > >
> > >
> > >
> > > ________________________
> > > David Le Strat
> > > Blogging @ http://dlsthoughts.blogspot.com
> > >
> > > __________________________________________________
> > > Do You Yahoo!?
> > > Tired of spam? Yahoo! Mail has the best spam protection around
> > > http://mail.yahoo.com
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> > > For additional commands, e-mail: jetspeed-user-help@portals.apache.org
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> > For additional commands, e-mail: jetspeed-user-help@portals.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
RE: [J2] Build Process Changes - Version 2.0-M4-SNAPSHOT and above.
Posted by Frank Villarreal <f_...@tetco.com>.
Scott,
I use MSSQL2000 and modified the resulting sql scripts that maven generates.
Unfortunately, I don't understand Maven too well so I didn't mess with it
other than commenting out the sql regeneration goal. One more thing, I use
Jetspeed2-m2, so my scripts are most likely out-of-date if the schema has
been modified in any way. Would you like me to email them to you?
- Frank
> -----Original Message-----
> From: Scott T Weaver [mailto:scotts-jetspeed-list@binary-designs.net]
> Sent: Thursday, July 14, 2005 11:16 AM
> To: 'Jetspeed Users List'
> Subject: RE: [J2] Build Process Changes - Version 2.0-M4-SNAPSHOT and
> above.
>
>
> Have we found a solution to fix the MSSQL db for Jetspeed 2 other than
> commenting (and effectively breaking) certain pieces of the security
> schema??? Unfortunately, I know nothing about MSSQL but am
> forced to deploy
> to it in my production environment.
>
> Regards,
> Scott
>
> > -----Original Message-----
> > From: David Le Strat [mailto:dlestrat@yahoo.com]
> > Sent: Wednesday, July 13, 2005 5:32 PM
> > To: Jetspeed Users List
> > Subject: RE: [J2] Build Process Changes - Version 2.0-M4-SNAPSHOT and
> > above.
> >
> > Scott,
> >
> > copyDb is not need anymore as I relocated the sql and
> > schema directories to the
> > maven-plugin/plugin-resources.
> >
> > David.
> >
> > --- Scott T Weaver
> > <sc...@binary-designs.net> wrote:
> >
> > > David,
> > >
> > > I am can't seem to find where the dbCopy goal,
> > > referenced from
> > > maven-plugin/maven.xml, is defined. I had to
> > > comment it out to get
> > > everything to run.
> > >
> > > Thanks,
> > > Scott
> > >
> > > > -----Original Message-----
> > > > From: David Le Strat [mailto:dlestrat@yahoo.com]
> > > > Sent: Tuesday, July 12, 2005 10:36 PM
> > > > To: jetspeed-dev@portals.apache.org;
> > > jetspeed-user@portals.apache.org
> > > > Subject: [J2] Build Process Changes - Version
> > > 2.0-M4-SNAPSHOT and above.
> > > >
> > > > All,
> > > >
> > > > Step 2 of Jetspeed's build process clean up has
> > > been
> > > > committed. As a result, a few things have changed
> > > when
> > > > build the latest Jetspeed (2.0-M4-SNAPSHOT and
> > > above).
> > > > A summary of the changes made can be found in <a
> > > > href="http://issues.apache.org/jira/browse/JS2-
> > > > 304?page=comments#action_12315646">Apache
> > > > Jetspeed Jira</a>. Also detailed <a
> > > >
> > >
> >
> href="http://www.geocities.com/dlestrat/etc/j2/buildChangeDocs.pdf">build
> > > > changes documentation</a> is temporary available
> > > on my
> > > > web site in PDF format until the Jetspeed web site
> > > > gets regenerated.
> > > >
> > > > Then new steps to get started are changed as
> > > follow:
> > > >
> > > > If you are build off of Jetspeed 2 source code for
> > > the
> > > > first time:
> > > > <pre>
> > > > cd ${jetspeed-2-home}
> > > > maven initMavenPlugin allClean allBuild
> > > > </pre>
> > > > If the Jetspeed 2 maven plugin is installed, then
> > > to
> > > > build the portal and all its components run:
> > > > <pre>
> > > > cd ${jetspeed-2-home}
> > > > maven allClean allBuild
> > > > </pre>
> > > > If you are using the Hypersonic SQL database,
> > > start
> > > > the production Hypersonic database by typing
> > > > <pre>
> > > > maven j2:start.production.server
> > > > </pre>
> > > > Then run quickStart (in seperate window/terminal
> > > > session):
> > > > <pre>
> > > > cd ${jetspeed-2-home}
> > > > maven j2:quickStart
> > > > </pre>
> > > > This will recreate the DB to deploy into. WARNING
> > > This
> > > > will drop all the tables and data in the
> > > production
> > > > database.
> > > >
> > > > 3. Start up Tomcat. With a browser, go to:
> > > > http://localhost:8080/jetspeed
> > > >
> > > > If you are creating a new Portal Application
> > > without
> > > > the Jetspeed source:
> > > >
> > > > In order to get started with a new portal
> > > application
> > > > that will include a developer's specific portal
> > > > customization, Jetspeed 2 provides as part of its
> > > > Maven Plugin a goal that can get you started with
> > > your
> > > > project. To do so:
> > > >
> > > > 1. Make sure that the following properties are set
> > > in
> > > > your your ${USER_HOME}/build.properties file:
> > > >
> > > > - org.apache.jetspeed.portal.name: e.g.
> > > testportal.
> > > > The name of your new portal application. This will
> > > > also be used as the artifactId for your project in
> > > the
> > > > maven repository.
> > > > - org.apache.jetspeed.genapp.home: e.g.
> > > > C:/tools/workspace/testportal. The location where
> > > your
> > > > new portal application should be created.
> > > > - org.apache.jetspeed.genapp.groupId: e.g.
> > > testportal.
> > > > The maven pom group id indicates the group
> > > location
> > > > for your project in the maven repository.
> > > > - org.apache.jetspeed.genapp.name: e.g. My Test
> > > > Portal. A friendly name for your new portal.
> > > > - org.apache.jetspeed.genapp.currentVersion: e.g.
> > > 1.0.
> > > > The current version for your new portal
> > > application.
> > > >
> > > > 2. Once the above properties are set, make sure
> > > that
> > > > the Jetspeed 2 Maven Plugin is installed on your
> > > local
> > > > machine. You can install the Jetspeed 2 Maven
> > > Plugin
> > > > as follow:
> > > > <pre>
> > > > maven -DartifactId=maven-jetspeed2-plugin
> > > > -DgroupId=jetspeed2
> > > > -Dversion=2.0-M4-SNAPSHOT plugin:download
> > > > </pre>
> > > > where
> > > >
> > > > - artifactId: The name of the Jetspeed2 plugin
> > > > artifact deployed to the maven repository.
> > > > - groupId: The name of the group where the
> > > Jetspeed2
> > > > plugin is deployed in the maven repository.
> > > > - version: The version that you want to use. For
> > > this
> > > > functionality, the version should be
> > > 2.0-M4-SNAPSHOT
> > > > or above.
> > > >
> > > > 3. Run the Jetspeed2 plugin target for generating
> > > a
> > > > new portal application:
> > > > <pre>
> > > > maven j2:genapp.portal
> > > > </pre>
> > > > 4. Go to the directory where you just created your
> > > new
> > > > portal application and execute:
> > > > <pre>
> > > > maven j2:portal.install
> > > > maven j2:quickStart
> > > > </pre>
> > > > That's it, you are ready to get started with your
> > > new
> > > > portal application.
> > > >
> > > > Regards,
> > > >
> > > > David Le Strat.
> > > >
> > > > ________________________
> > > > David Le Strat
> > > > Blogging @ http://dlsthoughts.blogspot.com
> > > >
> > > > __________________________________________________
> > > > Do You Yahoo!?
> > > > Tired of spam? Yahoo! Mail has the best spam
> > > protection around
> > > > http://mail.yahoo.com
> > > >
> > > >
> > >
> > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail:
> > > jetspeed-user-unsubscribe@portals.apache.org
> > > > For additional commands, e-mail:
> > > jetspeed-user-help@portals.apache.org
> > >
> > >
> > >
> > >
> > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> > > jetspeed-user-unsubscribe@portals.apache.org
> > > For additional commands, e-mail:
> > > jetspeed-user-help@portals.apache.org
> > >
> > >
> >
> >
> > ________________________
> > David Le Strat
> > Blogging @ http://dlsthoughts.blogspot.com
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam? Yahoo! Mail has the best spam protection around
> > http://mail.yahoo.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> > For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
RE: [J2] Build Process Changes - Version 2.0-M4-SNAPSHOT and above.
Posted by Scott T Weaver <sc...@binary-designs.net>.
Have we found a solution to fix the MSSQL db for Jetspeed 2 other than
commenting (and effectively breaking) certain pieces of the security
schema??? Unfortunately, I know nothing about MSSQL but am forced to deploy
to it in my production environment.
Regards,
Scott
> -----Original Message-----
> From: David Le Strat [mailto:dlestrat@yahoo.com]
> Sent: Wednesday, July 13, 2005 5:32 PM
> To: Jetspeed Users List
> Subject: RE: [J2] Build Process Changes - Version 2.0-M4-SNAPSHOT and
> above.
>
> Scott,
>
> copyDb is not need anymore as I relocated the sql and
> schema directories to the
> maven-plugin/plugin-resources.
>
> David.
>
> --- Scott T Weaver
> <sc...@binary-designs.net> wrote:
>
> > David,
> >
> > I am can't seem to find where the dbCopy goal,
> > referenced from
> > maven-plugin/maven.xml, is defined. I had to
> > comment it out to get
> > everything to run.
> >
> > Thanks,
> > Scott
> >
> > > -----Original Message-----
> > > From: David Le Strat [mailto:dlestrat@yahoo.com]
> > > Sent: Tuesday, July 12, 2005 10:36 PM
> > > To: jetspeed-dev@portals.apache.org;
> > jetspeed-user@portals.apache.org
> > > Subject: [J2] Build Process Changes - Version
> > 2.0-M4-SNAPSHOT and above.
> > >
> > > All,
> > >
> > > Step 2 of Jetspeed's build process clean up has
> > been
> > > committed. As a result, a few things have changed
> > when
> > > build the latest Jetspeed (2.0-M4-SNAPSHOT and
> > above).
> > > A summary of the changes made can be found in <a
> > > href="http://issues.apache.org/jira/browse/JS2-
> > > 304?page=comments#action_12315646">Apache
> > > Jetspeed Jira</a>. Also detailed <a
> > >
> >
> href="http://www.geocities.com/dlestrat/etc/j2/buildChangeDocs.pdf">build
> > > changes documentation</a> is temporary available
> > on my
> > > web site in PDF format until the Jetspeed web site
> > > gets regenerated.
> > >
> > > Then new steps to get started are changed as
> > follow:
> > >
> > > If you are build off of Jetspeed 2 source code for
> > the
> > > first time:
> > > <pre>
> > > cd ${jetspeed-2-home}
> > > maven initMavenPlugin allClean allBuild
> > > </pre>
> > > If the Jetspeed 2 maven plugin is installed, then
> > to
> > > build the portal and all its components run:
> > > <pre>
> > > cd ${jetspeed-2-home}
> > > maven allClean allBuild
> > > </pre>
> > > If you are using the Hypersonic SQL database,
> > start
> > > the production Hypersonic database by typing
> > > <pre>
> > > maven j2:start.production.server
> > > </pre>
> > > Then run quickStart (in seperate window/terminal
> > > session):
> > > <pre>
> > > cd ${jetspeed-2-home}
> > > maven j2:quickStart
> > > </pre>
> > > This will recreate the DB to deploy into. WARNING
> > This
> > > will drop all the tables and data in the
> > production
> > > database.
> > >
> > > 3. Start up Tomcat. With a browser, go to:
> > > http://localhost:8080/jetspeed
> > >
> > > If you are creating a new Portal Application
> > without
> > > the Jetspeed source:
> > >
> > > In order to get started with a new portal
> > application
> > > that will include a developer's specific portal
> > > customization, Jetspeed 2 provides as part of its
> > > Maven Plugin a goal that can get you started with
> > your
> > > project. To do so:
> > >
> > > 1. Make sure that the following properties are set
> > in
> > > your your ${USER_HOME}/build.properties file:
> > >
> > > - org.apache.jetspeed.portal.name: e.g.
> > testportal.
> > > The name of your new portal application. This will
> > > also be used as the artifactId for your project in
> > the
> > > maven repository.
> > > - org.apache.jetspeed.genapp.home: e.g.
> > > C:/tools/workspace/testportal. The location where
> > your
> > > new portal application should be created.
> > > - org.apache.jetspeed.genapp.groupId: e.g.
> > testportal.
> > > The maven pom group id indicates the group
> > location
> > > for your project in the maven repository.
> > > - org.apache.jetspeed.genapp.name: e.g. My Test
> > > Portal. A friendly name for your new portal.
> > > - org.apache.jetspeed.genapp.currentVersion: e.g.
> > 1.0.
> > > The current version for your new portal
> > application.
> > >
> > > 2. Once the above properties are set, make sure
> > that
> > > the Jetspeed 2 Maven Plugin is installed on your
> > local
> > > machine. You can install the Jetspeed 2 Maven
> > Plugin
> > > as follow:
> > > <pre>
> > > maven -DartifactId=maven-jetspeed2-plugin
> > > -DgroupId=jetspeed2
> > > -Dversion=2.0-M4-SNAPSHOT plugin:download
> > > </pre>
> > > where
> > >
> > > - artifactId: The name of the Jetspeed2 plugin
> > > artifact deployed to the maven repository.
> > > - groupId: The name of the group where the
> > Jetspeed2
> > > plugin is deployed in the maven repository.
> > > - version: The version that you want to use. For
> > this
> > > functionality, the version should be
> > 2.0-M4-SNAPSHOT
> > > or above.
> > >
> > > 3. Run the Jetspeed2 plugin target for generating
> > a
> > > new portal application:
> > > <pre>
> > > maven j2:genapp.portal
> > > </pre>
> > > 4. Go to the directory where you just created your
> > new
> > > portal application and execute:
> > > <pre>
> > > maven j2:portal.install
> > > maven j2:quickStart
> > > </pre>
> > > That's it, you are ready to get started with your
> > new
> > > portal application.
> > >
> > > Regards,
> > >
> > > David Le Strat.
> > >
> > > ________________________
> > > David Le Strat
> > > Blogging @ http://dlsthoughts.blogspot.com
> > >
> > > __________________________________________________
> > > Do You Yahoo!?
> > > Tired of spam? Yahoo! Mail has the best spam
> > protection around
> > > http://mail.yahoo.com
> > >
> > >
> >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> > jetspeed-user-unsubscribe@portals.apache.org
> > > For additional commands, e-mail:
> > jetspeed-user-help@portals.apache.org
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> > jetspeed-user-unsubscribe@portals.apache.org
> > For additional commands, e-mail:
> > jetspeed-user-help@portals.apache.org
> >
> >
>
>
> ________________________
> David Le Strat
> Blogging @ http://dlsthoughts.blogspot.com
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
RE: [J2] Build Process Changes - Version 2.0-M4-SNAPSHOT and above.
Posted by David Le Strat <dl...@yahoo.com>.
Scott,
copyDb is not need anymore as I relocated the sql and
schema directories to the
maven-plugin/plugin-resources.
David.
--- Scott T Weaver
<sc...@binary-designs.net> wrote:
> David,
>
> I am can't seem to find where the dbCopy goal,
> referenced from
> maven-plugin/maven.xml, is defined. I had to
> comment it out to get
> everything to run.
>
> Thanks,
> Scott
>
> > -----Original Message-----
> > From: David Le Strat [mailto:dlestrat@yahoo.com]
> > Sent: Tuesday, July 12, 2005 10:36 PM
> > To: jetspeed-dev@portals.apache.org;
> jetspeed-user@portals.apache.org
> > Subject: [J2] Build Process Changes - Version
> 2.0-M4-SNAPSHOT and above.
> >
> > All,
> >
> > Step 2 of Jetspeed's build process clean up has
> been
> > committed. As a result, a few things have changed
> when
> > build the latest Jetspeed (2.0-M4-SNAPSHOT and
> above).
> > A summary of the changes made can be found in <a
> > href="http://issues.apache.org/jira/browse/JS2-
> > 304?page=comments#action_12315646">Apache
> > Jetspeed Jira</a>. Also detailed <a
> >
>
href="http://www.geocities.com/dlestrat/etc/j2/buildChangeDocs.pdf">build
> > changes documentation</a> is temporary available
> on my
> > web site in PDF format until the Jetspeed web site
> > gets regenerated.
> >
> > Then new steps to get started are changed as
> follow:
> >
> > If you are build off of Jetspeed 2 source code for
> the
> > first time:
> > <pre>
> > cd ${jetspeed-2-home}
> > maven initMavenPlugin allClean allBuild
> > </pre>
> > If the Jetspeed 2 maven plugin is installed, then
> to
> > build the portal and all its components run:
> > <pre>
> > cd ${jetspeed-2-home}
> > maven allClean allBuild
> > </pre>
> > If you are using the Hypersonic SQL database,
> start
> > the production Hypersonic database by typing
> > <pre>
> > maven j2:start.production.server
> > </pre>
> > Then run quickStart (in seperate window/terminal
> > session):
> > <pre>
> > cd ${jetspeed-2-home}
> > maven j2:quickStart
> > </pre>
> > This will recreate the DB to deploy into. WARNING
> This
> > will drop all the tables and data in the
> production
> > database.
> >
> > 3. Start up Tomcat. With a browser, go to:
> > http://localhost:8080/jetspeed
> >
> > If you are creating a new Portal Application
> without
> > the Jetspeed source:
> >
> > In order to get started with a new portal
> application
> > that will include a developer's specific portal
> > customization, Jetspeed 2 provides as part of its
> > Maven Plugin a goal that can get you started with
> your
> > project. To do so:
> >
> > 1. Make sure that the following properties are set
> in
> > your your ${USER_HOME}/build.properties file:
> >
> > - org.apache.jetspeed.portal.name: e.g.
> testportal.
> > The name of your new portal application. This will
> > also be used as the artifactId for your project in
> the
> > maven repository.
> > - org.apache.jetspeed.genapp.home: e.g.
> > C:/tools/workspace/testportal. The location where
> your
> > new portal application should be created.
> > - org.apache.jetspeed.genapp.groupId: e.g.
> testportal.
> > The maven pom group id indicates the group
> location
> > for your project in the maven repository.
> > - org.apache.jetspeed.genapp.name: e.g. My Test
> > Portal. A friendly name for your new portal.
> > - org.apache.jetspeed.genapp.currentVersion: e.g.
> 1.0.
> > The current version for your new portal
> application.
> >
> > 2. Once the above properties are set, make sure
> that
> > the Jetspeed 2 Maven Plugin is installed on your
> local
> > machine. You can install the Jetspeed 2 Maven
> Plugin
> > as follow:
> > <pre>
> > maven -DartifactId=maven-jetspeed2-plugin
> > -DgroupId=jetspeed2
> > -Dversion=2.0-M4-SNAPSHOT plugin:download
> > </pre>
> > where
> >
> > - artifactId: The name of the Jetspeed2 plugin
> > artifact deployed to the maven repository.
> > - groupId: The name of the group where the
> Jetspeed2
> > plugin is deployed in the maven repository.
> > - version: The version that you want to use. For
> this
> > functionality, the version should be
> 2.0-M4-SNAPSHOT
> > or above.
> >
> > 3. Run the Jetspeed2 plugin target for generating
> a
> > new portal application:
> > <pre>
> > maven j2:genapp.portal
> > </pre>
> > 4. Go to the directory where you just created your
> new
> > portal application and execute:
> > <pre>
> > maven j2:portal.install
> > maven j2:quickStart
> > </pre>
> > That's it, you are ready to get started with your
> new
> > portal application.
> >
> > Regards,
> >
> > David Le Strat.
> >
> > ________________________
> > David Le Strat
> > Blogging @ http://dlsthoughts.blogspot.com
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam? Yahoo! Mail has the best spam
> protection around
> > http://mail.yahoo.com
> >
> >
>
---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> jetspeed-user-unsubscribe@portals.apache.org
> > For additional commands, e-mail:
> jetspeed-user-help@portals.apache.org
>
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail:
> jetspeed-user-help@portals.apache.org
>
>
________________________
David Le Strat
Blogging @ http://dlsthoughts.blogspot.com
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
[J2] Last Night Commit - Build Still Broken - Persistence Dependency Issue
Posted by David Le Strat <dl...@yahoo.com>.
All,
I decided to be thourough and do some more testing
this morning after spending quite a bit of time fixing
the build last night. I cleaned all my old deps, my
plugin cache, etc. The good news is that it builds
and all build functionality seems to be working. One
caveat is that you now need jetspeed.version in
{user.home}/build.properties. I updated
http://www.geocities.com/dlestrat/etc/j2/buildChangeDocs.pdf
and have a blog entry on how to get started with the
build on http://dlsthoughts.blogspot.com.
The bad news is that the dependency on
jetspeed-persistence had to be removed, the component
was deleted. When deploying to Tomcat, some Spring
dependencies are not resolved correctly. Please find
enclosed the logs.
Regards,
David Le Strat.
________________________
David Le Strat
Blogging @ http://dlsthoughts.blogspot.com
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
RE: [J2] Build Process Changes - Version 2.0-M4-SNAPSHOT and above.
Posted by Scott T Weaver <sc...@binary-designs.net>.
David,
I am can't seem to find where the dbCopy goal, referenced from
maven-plugin/maven.xml, is defined. I had to comment it out to get
everything to run.
Thanks,
Scott
> -----Original Message-----
> From: David Le Strat [mailto:dlestrat@yahoo.com]
> Sent: Tuesday, July 12, 2005 10:36 PM
> To: jetspeed-dev@portals.apache.org; jetspeed-user@portals.apache.org
> Subject: [J2] Build Process Changes - Version 2.0-M4-SNAPSHOT and above.
>
> All,
>
> Step 2 of Jetspeed's build process clean up has been
> committed. As a result, a few things have changed when
> build the latest Jetspeed (2.0-M4-SNAPSHOT and above).
> A summary of the changes made can be found in <a
> href="http://issues.apache.org/jira/browse/JS2-
> 304?page=comments#action_12315646">Apache
> Jetspeed Jira</a>. Also detailed <a
> href="http://www.geocities.com/dlestrat/etc/j2/buildChangeDocs.pdf">build
> changes documentation</a> is temporary available on my
> web site in PDF format until the Jetspeed web site
> gets regenerated.
>
> Then new steps to get started are changed as follow:
>
> If you are build off of Jetspeed 2 source code for the
> first time:
> <pre>
> cd ${jetspeed-2-home}
> maven initMavenPlugin allClean allBuild
> </pre>
> If the Jetspeed 2 maven plugin is installed, then to
> build the portal and all its components run:
> <pre>
> cd ${jetspeed-2-home}
> maven allClean allBuild
> </pre>
> If you are using the Hypersonic SQL database, start
> the production Hypersonic database by typing
> <pre>
> maven j2:start.production.server
> </pre>
> Then run quickStart (in seperate window/terminal
> session):
> <pre>
> cd ${jetspeed-2-home}
> maven j2:quickStart
> </pre>
> This will recreate the DB to deploy into. WARNING This
> will drop all the tables and data in the production
> database.
>
> 3. Start up Tomcat. With a browser, go to:
> http://localhost:8080/jetspeed
>
> If you are creating a new Portal Application without
> the Jetspeed source:
>
> In order to get started with a new portal application
> that will include a developer's specific portal
> customization, Jetspeed 2 provides as part of its
> Maven Plugin a goal that can get you started with your
> project. To do so:
>
> 1. Make sure that the following properties are set in
> your your ${USER_HOME}/build.properties file:
>
> - org.apache.jetspeed.portal.name: e.g. testportal.
> The name of your new portal application. This will
> also be used as the artifactId for your project in the
> maven repository.
> - org.apache.jetspeed.genapp.home: e.g.
> C:/tools/workspace/testportal. The location where your
> new portal application should be created.
> - org.apache.jetspeed.genapp.groupId: e.g. testportal.
> The maven pom group id indicates the group location
> for your project in the maven repository.
> - org.apache.jetspeed.genapp.name: e.g. My Test
> Portal. A friendly name for your new portal.
> - org.apache.jetspeed.genapp.currentVersion: e.g. 1.0.
> The current version for your new portal application.
>
> 2. Once the above properties are set, make sure that
> the Jetspeed 2 Maven Plugin is installed on your local
> machine. You can install the Jetspeed 2 Maven Plugin
> as follow:
> <pre>
> maven -DartifactId=maven-jetspeed2-plugin
> -DgroupId=jetspeed2
> -Dversion=2.0-M4-SNAPSHOT plugin:download
> </pre>
> where
>
> - artifactId: The name of the Jetspeed2 plugin
> artifact deployed to the maven repository.
> - groupId: The name of the group where the Jetspeed2
> plugin is deployed in the maven repository.
> - version: The version that you want to use. For this
> functionality, the version should be 2.0-M4-SNAPSHOT
> or above.
>
> 3. Run the Jetspeed2 plugin target for generating a
> new portal application:
> <pre>
> maven j2:genapp.portal
> </pre>
> 4. Go to the directory where you just created your new
> portal application and execute:
> <pre>
> maven j2:portal.install
> maven j2:quickStart
> </pre>
> That's it, you are ready to get started with your new
> portal application.
>
> Regards,
>
> David Le Strat.
>
> ________________________
> David Le Strat
> Blogging @ http://dlsthoughts.blogspot.com
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
[J2] Build Process Changes - Version 2.0-M4-SNAPSHOT and above.
Posted by David Le Strat <dl...@yahoo.com>.
All,
Step 2 of Jetspeed's build process clean up has been
committed. As a result, a few things have changed when
build the latest Jetspeed (2.0-M4-SNAPSHOT and above).
A summary of the changes made can be found in <a
href="http://issues.apache.org/jira/browse/JS2-304?page=comments#action_12315646">Apache
Jetspeed Jira</a>. Also detailed <a
href="http://www.geocities.com/dlestrat/etc/j2/buildChangeDocs.pdf">build
changes documentation</a> is temporary available on my
web site in PDF format until the Jetspeed web site
gets regenerated.
Then new steps to get started are changed as follow:
If you are build off of Jetspeed 2 source code for the
first time:
<pre>
cd ${jetspeed-2-home}
maven initMavenPlugin allClean allBuild
</pre>
If the Jetspeed 2 maven plugin is installed, then to
build the portal and all its components run:
<pre>
cd ${jetspeed-2-home}
maven allClean allBuild
</pre>
If you are using the Hypersonic SQL database, start
the production Hypersonic database by typing
<pre>
maven j2:start.production.server
</pre>
Then run quickStart (in seperate window/terminal
session):
<pre>
cd ${jetspeed-2-home}
maven j2:quickStart
</pre>
This will recreate the DB to deploy into. WARNING This
will drop all the tables and data in the production
database.
3. Start up Tomcat. With a browser, go to:
http://localhost:8080/jetspeed
If you are creating a new Portal Application without
the Jetspeed source:
In order to get started with a new portal application
that will include a developer's specific portal
customization, Jetspeed 2 provides as part of its
Maven Plugin a goal that can get you started with your
project. To do so:
1. Make sure that the following properties are set in
your your ${USER_HOME}/build.properties file:
- org.apache.jetspeed.portal.name: e.g. testportal.
The name of your new portal application. This will
also be used as the artifactId for your project in the
maven repository.
- org.apache.jetspeed.genapp.home: e.g.
C:/tools/workspace/testportal. The location where your
new portal application should be created.
- org.apache.jetspeed.genapp.groupId: e.g. testportal.
The maven pom group id indicates the group location
for your project in the maven repository.
- org.apache.jetspeed.genapp.name: e.g. My Test
Portal. A friendly name for your new portal.
- org.apache.jetspeed.genapp.currentVersion: e.g. 1.0.
The current version for your new portal application.
2. Once the above properties are set, make sure that
the Jetspeed 2 Maven Plugin is installed on your local
machine. You can install the Jetspeed 2 Maven Plugin
as follow:
<pre>
maven -DartifactId=maven-jetspeed2-plugin
-DgroupId=jetspeed2
-Dversion=2.0-M4-SNAPSHOT plugin:download
</pre>
where
- artifactId: The name of the Jetspeed2 plugin
artifact deployed to the maven repository.
- groupId: The name of the group where the Jetspeed2
plugin is deployed in the maven repository.
- version: The version that you want to use. For this
functionality, the version should be 2.0-M4-SNAPSHOT
or above.
3. Run the Jetspeed2 plugin target for generating a
new portal application:
<pre>
maven j2:genapp.portal
</pre>
4. Go to the directory where you just created your new
portal application and execute:
<pre>
maven j2:portal.install
maven j2:quickStart
</pre>
That's it, you are ready to get started with your new
portal application.
Regards,
David Le Strat.
________________________
David Le Strat
Blogging @ http://dlsthoughts.blogspot.com
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[J2] Build Process Changes - Version 2.0-M4-SNAPSHOT and above.
Posted by David Le Strat <dl...@yahoo.com>.
All,
Step 2 of Jetspeed's build process clean up has been
committed. As a result, a few things have changed when
build the latest Jetspeed (2.0-M4-SNAPSHOT and above).
A summary of the changes made can be found in <a
href="http://issues.apache.org/jira/browse/JS2-304?page=comments#action_12315646">Apache
Jetspeed Jira</a>. Also detailed <a
href="http://www.geocities.com/dlestrat/etc/j2/buildChangeDocs.pdf">build
changes documentation</a> is temporary available on my
web site in PDF format until the Jetspeed web site
gets regenerated.
Then new steps to get started are changed as follow:
If you are build off of Jetspeed 2 source code for the
first time:
<pre>
cd ${jetspeed-2-home}
maven initMavenPlugin allClean allBuild
</pre>
If the Jetspeed 2 maven plugin is installed, then to
build the portal and all its components run:
<pre>
cd ${jetspeed-2-home}
maven allClean allBuild
</pre>
If you are using the Hypersonic SQL database, start
the production Hypersonic database by typing
<pre>
maven j2:start.production.server
</pre>
Then run quickStart (in seperate window/terminal
session):
<pre>
cd ${jetspeed-2-home}
maven j2:quickStart
</pre>
This will recreate the DB to deploy into. WARNING This
will drop all the tables and data in the production
database.
3. Start up Tomcat. With a browser, go to:
http://localhost:8080/jetspeed
If you are creating a new Portal Application without
the Jetspeed source:
In order to get started with a new portal application
that will include a developer's specific portal
customization, Jetspeed 2 provides as part of its
Maven Plugin a goal that can get you started with your
project. To do so:
1. Make sure that the following properties are set in
your your ${USER_HOME}/build.properties file:
- org.apache.jetspeed.portal.name: e.g. testportal.
The name of your new portal application. This will
also be used as the artifactId for your project in the
maven repository.
- org.apache.jetspeed.genapp.home: e.g.
C:/tools/workspace/testportal. The location where your
new portal application should be created.
- org.apache.jetspeed.genapp.groupId: e.g. testportal.
The maven pom group id indicates the group location
for your project in the maven repository.
- org.apache.jetspeed.genapp.name: e.g. My Test
Portal. A friendly name for your new portal.
- org.apache.jetspeed.genapp.currentVersion: e.g. 1.0.
The current version for your new portal application.
2. Once the above properties are set, make sure that
the Jetspeed 2 Maven Plugin is installed on your local
machine. You can install the Jetspeed 2 Maven Plugin
as follow:
<pre>
maven -DartifactId=maven-jetspeed2-plugin
-DgroupId=jetspeed2
-Dversion=2.0-M4-SNAPSHOT plugin:download
</pre>
where
- artifactId: The name of the Jetspeed2 plugin
artifact deployed to the maven repository.
- groupId: The name of the group where the Jetspeed2
plugin is deployed in the maven repository.
- version: The version that you want to use. For this
functionality, the version should be 2.0-M4-SNAPSHOT
or above.
3. Run the Jetspeed2 plugin target for generating a
new portal application:
<pre>
maven j2:genapp.portal
</pre>
4. Go to the directory where you just created your new
portal application and execute:
<pre>
maven j2:portal.install
maven j2:quickStart
</pre>
That's it, you are ready to get started with your new
portal application.
Regards,
David Le Strat.
________________________
David Le Strat
Blogging @ http://dlsthoughts.blogspot.com
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: [J2] Build Process Clean Up - Step 2
Posted by Eelco Hillenius <ee...@topicus.nl>.
Especially point 2, please do go ahead! :)
Eelco
David Le Strat wrote:
>All,
>
>Does anyone has any objection with me going ahead and
>applying the changes described below?
>
>Regards,
>
>David Le Strat.
>
>--- David Le Strat <dl...@yahoo.com> wrote:
>
>
>
>>All,
>>
>>I have kept on going with the build process clean
>>up,
>>here is my proposal for step 2:
>>
>>Overview of Proposed Changes.
>>
>>As part of step 2 of the build process clean up, I
>>propose to centralize most of the Jetspeed 2 custom
>>goals to the Jetspeed 2 Maven Plugin. The reasons
>>for
>>doing so are multiple:
>>
>>1. Provide better reusability of common build goals.
>>
>>Users creating a new portal application should be
>>able
>>to leverage Jetspeed 2 Maven plugin for common build
>>operations.
>>2. Provide the ability to quickly get started with a
>>portal application. A new target j2:genapp.portal
>>will be created to create a shell portal
>>application.
>>The developer of the new application can reuse the
>>Jetspeed 2 Maven plugin goals for common build
>>operations for quickStart, portlet deployment, etc.
>>3. Prepare for a migration to M2 in the future.
>>With
>>M2, custom goals are encapsulated in plugins,
>>maven.xml is deprecated. By centralizing most of
>>the
>>Jetspeed 2 build goals to the Jetspeed 2 Maven
>>plugin,
>>migration to M2 should be much easier.
>>
>>In addition, I proposed to remove the site directory
>>as it duplicates application documentation.
>>
>>It would also be a good idea to revive the
>>documentation framework discussion, and centralize
>>the
>>
>>documentation location, Raphael had a forrest
>>proposal
>>out there, why not. We could also stick with Maven,
>>but in any case, we should clean things up and
>>improve
>>docs. I remember reading about a Documentation
>>project going on leveraging the WIKI. Could we
>>clarify the approach (xdocs, WIKI, both?)?
>>
>>Finally, as part of this clean up, I have moved a
>>few
>>things around, most notably the /src/sql and
>>/src/schema directories that are now part of
>>maven-plugin/plugin-resources.
>>
>>Please find below a much more detailed description
>>of
>>the clean up proposed. I look forward to your
>>feedback.
>>
>>Regards,
>>
>>David Le Strat.
>>
>>-------------------------
>>
>>Move the following targets from /maven.xml to
>>maven-plugin:
>>
>>- start.production.server now called
>>j2:start.production.server
>>- start.test.server now called j2:start.test.server
>>- db.execute now called j2:db.execute
>>
>>- Moved copy.shared.deps to j2:copy.shared.deps
>>
>>- db.scripts.gen now called j2:db.scripts.gen
>>- db.test.properties now called
>>j2:db.test.properties
>>- db.production.properties now called
>>j2:db.production.properties
>>- db.create.test now called j2:db.create.test
>>- db.create.production now called
>>j2:db.create.production
>>- db.create now called j2:db.create
>>- db.recreate now called j2:db.recreate
>>
>>- db.drop.test now called j2:db.drop.test
>>- db.drop.production now called
>>j2:db.drop.production
>>- db.drop now called j2:db.drop
>>- db.drop2 now called j2:db.drop2
>>- db.drop.oracle now called j2:db.drop.oracle
>>
>>
>>Move the following targets from /portal-webapp to
>>maven-plugin:
>>
>>- catalina:base-shared moved to
>>j2:catalina.base.shared
>>- catalina:shared moved to j2:catalina.shared
>>- Removed db.execute. Duplicated in plugin.
>>- Removed db.test.properties. Duplicated in plugin.
>>- Removed db.production.properties. Duplicated in
>>plugin.
>>- Removed catalina:base-shared. Duplicated in
>>plugin.
>>- Removed catalina:shared. Duplicated in plugin.
>>
>>- Delete portal-webapp/src/sql. Not used.
>>
>>- Moved deploy to maven plugin j2:portal.deploy
>>
>>- Moved fullDeploy to maven plugin j2:fullDeploy
>>- Moved nodbfullDeploy to maven plugin
>>j2:nodbfullDeploy
>>- Moved minDeploy to maven plugin j2:minDeploy
>>- Moved nodbMinDeploy to plugin j2:nodbMinDeploy
>>
>>- Moved pam.* to maven plugin j2:pam.*
>>
>>Clean /maven-plugin maven.xml:
>>
>>- Removed copyDb target. Not need anymore. SQL
>>files
>>were relocated.
>>- Removed db.execute. Duplicated in plugin.
>>- Remove db.create. Duplicated in plugin.
>>
>>Clean all maven.xml
>>
>>- Removed deployJar. Moved to maven plugin
>>j2:jar.deploy
>>- Moved shared deployJar target to maven plugin
>>j2:jar.deploy.shared
>>
>>Update Getting started documentation.
>>
>>- maven initMavenPlugin allClean allBuild is now
>>required instead of maven allClean allBuild if
>>the latest version of the maven plugin is not
>>installed.
>>- I also provide documentation on how to set up the
>>latest version of the plugin without requiring a J2
>>checkout.
>>
>>Documentation Changes.
>>
>>- Deleted site. Currently duplicate of xdocs.
>>- Updated allSite target to generate multiprojects
>>site. This is not working. Any suggestions on this
>>is appreciated.
>>
>>Creation a new portal application.
>>
>>- j2:genapp.portal Documentation
>>
>>- Add to build.properties in {user.home}:
>> -
>>
>>
>>
>org.apache.jetspeed.genapp.home=C:/tools/workspace/testportal
>
>
>> - org.apache.jetspeed.genapp.groupId=testportal
>> - org.apache.jetspeed.genapp.name=My Test Portal
>> - org.apache.jetspeed.genapp.currentVersion=1.0
>>- Get started with new project: maven
>>j2:genapp.portal
>>
>>________________________
>>David Le Strat
>>Blogging @ http://dlsthoughts.blogspot.com
>>
>>
>>
>>____________________________________________________
>>Sell on Yahoo! Auctions – no fees. Bid on great
>>items.
>>http://auctions.yahoo.com/
>>
>>
>>
>>
>---------------------------------------------------------------------
>
>
>>To unsubscribe, e-mail:
>>jetspeed-dev-unsubscribe@portals.apache.org
>>For additional commands, e-mail:
>>jetspeed-dev-help@portals.apache.org
>>
>>
>>
>>
>
>
>________________________
>David Le Strat
>Blogging @ http://dlsthoughts.blogspot.com
>
>__________________________________________________
>Do You Yahoo!?
>Tired of spam? Yahoo! Mail has the best spam protection around
>http://mail.yahoo.com
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
>For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
RE: [J2] Build Process Clean Up - Step 2
Posted by Scott T Weaver <sc...@binary-designs.net>.
Go for it.
As an FYI, I am currently working on removing ALL locator.ent/.path files
and replacing them instead with project descriptor inheritance instead.
This is a much cleaner approach and is the recommended way of accomplish
sub-project dependencies as opposed to our current approach (which is not
recommended as per the Maven wiki and will not be supported in newer version
of Maven). I hope to have this committed by the end of the day.
-Scott
> -----Original Message-----
> From: David Le Strat [mailto:dlestrat@yahoo.com]
> Sent: Tuesday, July 12, 2005 11:50 AM
> To: Jetspeed Developers List
> Subject: Re: [J2] Build Process Clean Up - Step 2
>
> All,
>
> Does anyone has any objection with me going ahead and
> applying the changes described below?
>
> Regards,
>
> David Le Strat.
>
> --- David Le Strat <dl...@yahoo.com> wrote:
>
> > All,
> >
> > I have kept on going with the build process clean
> > up,
> > here is my proposal for step 2:
> >
> > Overview of Proposed Changes.
> >
> > As part of step 2 of the build process clean up, I
> > propose to centralize most of the Jetspeed 2 custom
> > goals to the Jetspeed 2 Maven Plugin. The reasons
> > for
> > doing so are multiple:
> >
> > 1. Provide better reusability of common build goals.
> >
> > Users creating a new portal application should be
> > able
> > to leverage Jetspeed 2 Maven plugin for common build
> > operations.
> > 2. Provide the ability to quickly get started with a
> > portal application. A new target j2:genapp.portal
> > will be created to create a shell portal
> > application.
> > The developer of the new application can reuse the
> > Jetspeed 2 Maven plugin goals for common build
> > operations for quickStart, portlet deployment, etc.
> > 3. Prepare for a migration to M2 in the future.
> > With
> > M2, custom goals are encapsulated in plugins,
> > maven.xml is deprecated. By centralizing most of
> > the
> > Jetspeed 2 build goals to the Jetspeed 2 Maven
> > plugin,
> > migration to M2 should be much easier.
> >
> > In addition, I proposed to remove the site directory
> > as it duplicates application documentation.
> >
> > It would also be a good idea to revive the
> > documentation framework discussion, and centralize
> > the
> >
> > documentation location, Raphael had a forrest
> > proposal
> > out there, why not. We could also stick with Maven,
> > but in any case, we should clean things up and
> > improve
> > docs. I remember reading about a Documentation
> > project going on leveraging the WIKI. Could we
> > clarify the approach (xdocs, WIKI, both?)?
> >
> > Finally, as part of this clean up, I have moved a
> > few
> > things around, most notably the /src/sql and
> > /src/schema directories that are now part of
> > maven-plugin/plugin-resources.
> >
> > Please find below a much more detailed description
> > of
> > the clean up proposed. I look forward to your
> > feedback.
> >
> > Regards,
> >
> > David Le Strat.
> >
> > -------------------------
> >
> > Move the following targets from /maven.xml to
> > maven-plugin:
> >
> > - start.production.server now called
> > j2:start.production.server
> > - start.test.server now called j2:start.test.server
> > - db.execute now called j2:db.execute
> >
> > - Moved copy.shared.deps to j2:copy.shared.deps
> >
> > - db.scripts.gen now called j2:db.scripts.gen
> > - db.test.properties now called
> > j2:db.test.properties
> > - db.production.properties now called
> > j2:db.production.properties
> > - db.create.test now called j2:db.create.test
> > - db.create.production now called
> > j2:db.create.production
> > - db.create now called j2:db.create
> > - db.recreate now called j2:db.recreate
> >
> > - db.drop.test now called j2:db.drop.test
> > - db.drop.production now called
> > j2:db.drop.production
> > - db.drop now called j2:db.drop
> > - db.drop2 now called j2:db.drop2
> > - db.drop.oracle now called j2:db.drop.oracle
> >
> >
> > Move the following targets from /portal-webapp to
> > maven-plugin:
> >
> > - catalina:base-shared moved to
> > j2:catalina.base.shared
> > - catalina:shared moved to j2:catalina.shared
> > - Removed db.execute. Duplicated in plugin.
> > - Removed db.test.properties. Duplicated in plugin.
> > - Removed db.production.properties. Duplicated in
> > plugin.
> > - Removed catalina:base-shared. Duplicated in
> > plugin.
> > - Removed catalina:shared. Duplicated in plugin.
> >
> > - Delete portal-webapp/src/sql. Not used.
> >
> > - Moved deploy to maven plugin j2:portal.deploy
> >
> > - Moved fullDeploy to maven plugin j2:fullDeploy
> > - Moved nodbfullDeploy to maven plugin
> > j2:nodbfullDeploy
> > - Moved minDeploy to maven plugin j2:minDeploy
> > - Moved nodbMinDeploy to plugin j2:nodbMinDeploy
> >
> > - Moved pam.* to maven plugin j2:pam.*
> >
> > Clean /maven-plugin maven.xml:
> >
> > - Removed copyDb target. Not need anymore. SQL
> > files
> > were relocated.
> > - Removed db.execute. Duplicated in plugin.
> > - Remove db.create. Duplicated in plugin.
> >
> > Clean all maven.xml
> >
> > - Removed deployJar. Moved to maven plugin
> > j2:jar.deploy
> > - Moved shared deployJar target to maven plugin
> > j2:jar.deploy.shared
> >
> > Update Getting started documentation.
> >
> > - maven initMavenPlugin allClean allBuild is now
> > required instead of maven allClean allBuild if
> > the latest version of the maven plugin is not
> > installed.
> > - I also provide documentation on how to set up the
> > latest version of the plugin without requiring a J2
> > checkout.
> >
> > Documentation Changes.
> >
> > - Deleted site. Currently duplicate of xdocs.
> > - Updated allSite target to generate multiprojects
> > site. This is not working. Any suggestions on this
> > is appreciated.
> >
> > Creation a new portal application.
> >
> > - j2:genapp.portal Documentation
> >
> > - Add to build.properties in {user.home}:
> > -
> >
> org.apache.jetspeed.genapp.home=C:/tools/workspace/testportal
> > - org.apache.jetspeed.genapp.groupId=testportal
> > - org.apache.jetspeed.genapp.name=My Test Portal
> > - org.apache.jetspeed.genapp.currentVersion=1.0
> > - Get started with new project: maven
> > j2:genapp.portal
> >
> > ________________________
> > David Le Strat
> > Blogging @ http://dlsthoughts.blogspot.com
> >
> >
> >
> > ____________________________________________________
> > Sell on Yahoo! Auctions - no fees. Bid on great
> > items.
> > http://auctions.yahoo.com/
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> > jetspeed-dev-unsubscribe@portals.apache.org
> > For additional commands, e-mail:
> > jetspeed-dev-help@portals.apache.org
> >
> >
>
>
> ________________________
> David Le Strat
> Blogging @ http://dlsthoughts.blogspot.com
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: [J2] Build Process Clean Up - Step 2
Posted by David Le Strat <dl...@yahoo.com>.
All,
Does anyone has any objection with me going ahead and
applying the changes described below?
Regards,
David Le Strat.
--- David Le Strat <dl...@yahoo.com> wrote:
> All,
>
> I have kept on going with the build process clean
> up,
> here is my proposal for step 2:
>
> Overview of Proposed Changes.
>
> As part of step 2 of the build process clean up, I
> propose to centralize most of the Jetspeed 2 custom
> goals to the Jetspeed 2 Maven Plugin. The reasons
> for
> doing so are multiple:
>
> 1. Provide better reusability of common build goals.
>
> Users creating a new portal application should be
> able
> to leverage Jetspeed 2 Maven plugin for common build
> operations.
> 2. Provide the ability to quickly get started with a
> portal application. A new target j2:genapp.portal
> will be created to create a shell portal
> application.
> The developer of the new application can reuse the
> Jetspeed 2 Maven plugin goals for common build
> operations for quickStart, portlet deployment, etc.
> 3. Prepare for a migration to M2 in the future.
> With
> M2, custom goals are encapsulated in plugins,
> maven.xml is deprecated. By centralizing most of
> the
> Jetspeed 2 build goals to the Jetspeed 2 Maven
> plugin,
> migration to M2 should be much easier.
>
> In addition, I proposed to remove the site directory
> as it duplicates application documentation.
>
> It would also be a good idea to revive the
> documentation framework discussion, and centralize
> the
>
> documentation location, Raphael had a forrest
> proposal
> out there, why not. We could also stick with Maven,
> but in any case, we should clean things up and
> improve
> docs. I remember reading about a Documentation
> project going on leveraging the WIKI. Could we
> clarify the approach (xdocs, WIKI, both?)?
>
> Finally, as part of this clean up, I have moved a
> few
> things around, most notably the /src/sql and
> /src/schema directories that are now part of
> maven-plugin/plugin-resources.
>
> Please find below a much more detailed description
> of
> the clean up proposed. I look forward to your
> feedback.
>
> Regards,
>
> David Le Strat.
>
> -------------------------
>
> Move the following targets from /maven.xml to
> maven-plugin:
>
> - start.production.server now called
> j2:start.production.server
> - start.test.server now called j2:start.test.server
> - db.execute now called j2:db.execute
>
> - Moved copy.shared.deps to j2:copy.shared.deps
>
> - db.scripts.gen now called j2:db.scripts.gen
> - db.test.properties now called
> j2:db.test.properties
> - db.production.properties now called
> j2:db.production.properties
> - db.create.test now called j2:db.create.test
> - db.create.production now called
> j2:db.create.production
> - db.create now called j2:db.create
> - db.recreate now called j2:db.recreate
>
> - db.drop.test now called j2:db.drop.test
> - db.drop.production now called
> j2:db.drop.production
> - db.drop now called j2:db.drop
> - db.drop2 now called j2:db.drop2
> - db.drop.oracle now called j2:db.drop.oracle
>
>
> Move the following targets from /portal-webapp to
> maven-plugin:
>
> - catalina:base-shared moved to
> j2:catalina.base.shared
> - catalina:shared moved to j2:catalina.shared
> - Removed db.execute. Duplicated in plugin.
> - Removed db.test.properties. Duplicated in plugin.
> - Removed db.production.properties. Duplicated in
> plugin.
> - Removed catalina:base-shared. Duplicated in
> plugin.
> - Removed catalina:shared. Duplicated in plugin.
>
> - Delete portal-webapp/src/sql. Not used.
>
> - Moved deploy to maven plugin j2:portal.deploy
>
> - Moved fullDeploy to maven plugin j2:fullDeploy
> - Moved nodbfullDeploy to maven plugin
> j2:nodbfullDeploy
> - Moved minDeploy to maven plugin j2:minDeploy
> - Moved nodbMinDeploy to plugin j2:nodbMinDeploy
>
> - Moved pam.* to maven plugin j2:pam.*
>
> Clean /maven-plugin maven.xml:
>
> - Removed copyDb target. Not need anymore. SQL
> files
> were relocated.
> - Removed db.execute. Duplicated in plugin.
> - Remove db.create. Duplicated in plugin.
>
> Clean all maven.xml
>
> - Removed deployJar. Moved to maven plugin
> j2:jar.deploy
> - Moved shared deployJar target to maven plugin
> j2:jar.deploy.shared
>
> Update Getting started documentation.
>
> - maven initMavenPlugin allClean allBuild is now
> required instead of maven allClean allBuild if
> the latest version of the maven plugin is not
> installed.
> - I also provide documentation on how to set up the
> latest version of the plugin without requiring a J2
> checkout.
>
> Documentation Changes.
>
> - Deleted site. Currently duplicate of xdocs.
> - Updated allSite target to generate multiprojects
> site. This is not working. Any suggestions on this
> is appreciated.
>
> Creation a new portal application.
>
> - j2:genapp.portal Documentation
>
> - Add to build.properties in {user.home}:
> -
>
org.apache.jetspeed.genapp.home=C:/tools/workspace/testportal
> - org.apache.jetspeed.genapp.groupId=testportal
> - org.apache.jetspeed.genapp.name=My Test Portal
> - org.apache.jetspeed.genapp.currentVersion=1.0
> - Get started with new project: maven
> j2:genapp.portal
>
> ________________________
> David Le Strat
> Blogging @ http://dlsthoughts.blogspot.com
>
>
>
> ____________________________________________________
> Sell on Yahoo! Auctions no fees. Bid on great
> items.
> http://auctions.yahoo.com/
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail:
> jetspeed-dev-help@portals.apache.org
>
>
________________________
David Le Strat
Blogging @ http://dlsthoughts.blogspot.com
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[J2] Build Process Clean Up - Step 2
Posted by David Le Strat <dl...@yahoo.com>.
All,
I have kept on going with the build process clean up,
here is my proposal for step 2:
Overview of Proposed Changes.
As part of step 2 of the build process clean up, I
propose to centralize most of the Jetspeed 2 custom
goals to the Jetspeed 2 Maven Plugin. The reasons for
doing so are multiple:
1. Provide better reusability of common build goals.
Users creating a new portal application should be able
to leverage Jetspeed 2 Maven plugin for common build
operations.
2. Provide the ability to quickly get started with a
portal application. A new target j2:genapp.portal
will be created to create a shell portal application.
The developer of the new application can reuse the
Jetspeed 2 Maven plugin goals for common build
operations for quickStart, portlet deployment, etc.
3. Prepare for a migration to M2 in the future. With
M2, custom goals are encapsulated in plugins,
maven.xml is deprecated. By centralizing most of the
Jetspeed 2 build goals to the Jetspeed 2 Maven plugin,
migration to M2 should be much easier.
In addition, I proposed to remove the site directory
as it duplicates application documentation.
It would also be a good idea to revive the
documentation framework discussion, and centralize the
documentation location, Raphael had a forrest proposal
out there, why not. We could also stick with Maven,
but in any case, we should clean things up and improve
docs. I remember reading about a Documentation
project going on leveraging the WIKI. Could we
clarify the approach (xdocs, WIKI, both?)?
Finally, as part of this clean up, I have moved a few
things around, most notably the /src/sql and
/src/schema directories that are now part of
maven-plugin/plugin-resources.
Please find below a much more detailed description of
the clean up proposed. I look forward to your
feedback.
Regards,
David Le Strat.
-------------------------
Move the following targets from /maven.xml to
maven-plugin:
- start.production.server now called
j2:start.production.server
- start.test.server now called j2:start.test.server
- db.execute now called j2:db.execute
- Moved copy.shared.deps to j2:copy.shared.deps
- db.scripts.gen now called j2:db.scripts.gen
- db.test.properties now called j2:db.test.properties
- db.production.properties now called
j2:db.production.properties
- db.create.test now called j2:db.create.test
- db.create.production now called
j2:db.create.production
- db.create now called j2:db.create
- db.recreate now called j2:db.recreate
- db.drop.test now called j2:db.drop.test
- db.drop.production now called j2:db.drop.production
- db.drop now called j2:db.drop
- db.drop2 now called j2:db.drop2
- db.drop.oracle now called j2:db.drop.oracle
Move the following targets from /portal-webapp to
maven-plugin:
- catalina:base-shared moved to
j2:catalina.base.shared
- catalina:shared moved to j2:catalina.shared
- Removed db.execute. Duplicated in plugin.
- Removed db.test.properties. Duplicated in plugin.
- Removed db.production.properties. Duplicated in
plugin.
- Removed catalina:base-shared. Duplicated in plugin.
- Removed catalina:shared. Duplicated in plugin.
- Delete portal-webapp/src/sql. Not used.
- Moved deploy to maven plugin j2:portal.deploy
- Moved fullDeploy to maven plugin j2:fullDeploy
- Moved nodbfullDeploy to maven plugin
j2:nodbfullDeploy
- Moved minDeploy to maven plugin j2:minDeploy
- Moved nodbMinDeploy to plugin j2:nodbMinDeploy
- Moved pam.* to maven plugin j2:pam.*
Clean /maven-plugin maven.xml:
- Removed copyDb target. Not need anymore. SQL files
were relocated.
- Removed db.execute. Duplicated in plugin.
- Remove db.create. Duplicated in plugin.
Clean all maven.xml
- Removed deployJar. Moved to maven plugin
j2:jar.deploy
- Moved shared deployJar target to maven plugin
j2:jar.deploy.shared
Update Getting started documentation.
- maven initMavenPlugin allClean allBuild is now
required instead of maven allClean allBuild if
the latest version of the maven plugin is not
installed.
- I also provide documentation on how to set up the
latest version of the plugin without requiring a J2
checkout.
Documentation Changes.
- Deleted site. Currently duplicate of xdocs.
- Updated allSite target to generate multiprojects
site. This is not working. Any suggestions on this
is appreciated.
Creation a new portal application.
- j2:genapp.portal Documentation
- Add to build.properties in {user.home}:
-
org.apache.jetspeed.genapp.home=C:/tools/workspace/testportal
- org.apache.jetspeed.genapp.groupId=testportal
- org.apache.jetspeed.genapp.name=My Test Portal
- org.apache.jetspeed.genapp.currentVersion=1.0
- Get started with new project: maven j2:genapp.portal
________________________
David Le Strat
Blogging @ http://dlsthoughts.blogspot.com
____________________________________________________
Sell on Yahoo! Auctions no fees. Bid on great items.
http://auctions.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
RE: [J2] Build Process Summer Time Clean Up
Posted by Scott T Weaver <sc...@binary-designs.net>.
+1 all the way. Both the build and the plug-in (my fault) are way out of
hand. I also took a look at M2 the other week and I really do like the idea
of developing plugins in Java or BeanShell as opposed to coding in XML,
which IMOHO, was a bad idea to begin with.
p.s.
David, how is the Jetspeed Eclipse plugin coming along? I recently spent a
week writing a plugin to do web page conversions from .asp/.shtml to
Velocity, so it is fresh in my mind if you need any help.
Regards,
Scott T Weaver
> -----Original Message-----
> From: David Sean Taylor [mailto:david@bluesunrise.com]
> Sent: Monday, July 04, 2005 7:32 PM
> To: Jetspeed Developers List
> Subject: Re: [J2] Build Process Summer Time Clean Up
>
> David Le Strat wrote:
> > All,
> >
> > I finally got some time to get back to J2. I have a
> > proposal for some summer time J2 build process clean
> > up.
> >
> > Jetspeed2 current build process is a bit confusing.
> > Through the various evolutions of J2 build process,
> > many targets have been accumulated that make it
> > difficult to easily understand the build process flow.
> >
> > h2. Cleaning up the build process
> >
> > Using J2 in its current form requires an in-depth
> > understanding of how J2 build internals operate.
> >
> > As an example, an integrator wanting to get starting
> > with J2 will want to start with the portal web
> > application and customize it from there. It should be
> > made easy for integrators to get started with the web
> > application without requiring an in-depth
> > understanding of the various sequences in the build
> > process.
> >
> > A typical implementation will want to create a project
> > as described below:
> >
> > {noformat}
> > \sample-portal
> > +---\etc Contains the build
> > dependencies definition.
> > +---\portal-webapp Contains the portal web
> > application being built.
> > +---\src Contains the portal
> > initialization source (db scripts, etc).
> > {noformat}
> >
> > Building the portal in this structure should be
> > possible by leveraging the deployed Jetspeed
> > dependencies:
> >
> > * Components: All libraries (jars) required for the
> > runtime operation of the portal engine.
> > * Portlets: All web libraries (wars) required for the
> > runtime operation of the portal engine.
> >
> > Integrator using Jetspeed2 should be able to do so
> > easily and to easily get (through dependencies) the
> > latest versions of the release Jetspeed components
> > (libraries as well as portlets).
> >
> > The current maven-plugin and portal build
> > implementation rely on the source build (target
> > directories) rather than the dependencies for the
> > assembly of the portal engine, making it more
> > difficult to get quickly started and to keep up with
> > enhanced components.
> >
> > h2. Proposed changes
> >
> > The proposed changes below clean up the build process
> > and slightly reorganize some elements to more easily
> > achieve the goals outlined above.
> >
> > The first changes restructure the portal directory as
> > follow.
> > # Remove all non web related dependencies from portal:
> > ## Move the portal java source and java tests to
> > components/portal. This becomes a component that will
> > be released as jetspeed-(version).jar
>
> +1 in general, but don't all components follow a naming pattern of
> jetspeed-{COMPONENT_NAME}-{VERSION}.jar?
>
>
> > ## Rename the web application to portal-webapp and the
> > artifact id to jetspeed-portal (to remove conflict
> > with the jetspeed component artifact).
>
> Maybe this artifact should be jetspeed-{VERSION}.war
>
> > ## Move the test directory under portal-webapp to
> > components/portal/test as it support the portal
> > components tests.
>
> +1
>
> > ## Add org.apache.jetspeed.PortalTestConstants to
> > centralize initialization of JETSPEED_PROPERTIES_PATH
> > and PORTAL_WEBAPP_PATH.
> >
> > Clean up the portal-webapp (previously portal) build
> > and maven-plugin.
>
> I think that all build goals should be a part of the plugin.
> Why have both plugin goals and maven.xml goals?
>
> I'd also like to propose moving to Maven-2 as a part of this refactoring.
> I think we should consider project archetypes for quickstarts and
> replacing the current build with a M2 build.
>
> Overview (from my notes at JavaOne):
> * Super-POM: defaults across all projects
> * transitive dependencies
> * dependency scoping
> * dependency management
> * better control over snapshots
> - only check one snapshot per build
> - or check snapshot once per time period (day, hour..)
> * post/pre goals removed
> * build is now based on a lifecycle
> * maven.xml, project.properties deprecated
> * parent projects can be declared, no more ../..
> * plugins configurable, POM based, auto-downloaded
> * Plugin languages supported: Java Beanshell, Marmalade
> * Explicit definiition of multiprojects
> <modules>
> <module>subproject-1</module>
> <module>subproject-2</module>
> ....
> * Project archetypes for quickstarts
>
> > # Clean portal/maven.xml:
> > ## Remove commented calls to targets.
> > # The deploy and undeploy calls in the portal-webapp
> > (previously portal) build process should be using the
> > maven-plugin to do so. Multiple deploy, undeploy,
> > register, unregister behaviors create confusion.
> > Therefore, I propose to perform the following cleanup
> > in the portal-webapp (previously portal):
> > ## Remove pam.template.deploy. This is not used.
> > ## Remove pam.unregister. Depends on
> > pam.template.register which is not being used.
> > ## Remove pam.template.register. This is not used.
> > ## Remove pam.template.undeploy. There is a
> > jetspeed2:undeploy target in the jetspeed plugin.
> > ## Rename pam.register to pam.layoutdeploy. This
> > really deploys the layout portlet and should be
> > consistent with the other deploy targets.
> > ## Rename pam.deploy to pam.demodeploy. This deploys
> > the demo application.
> > ## Rename pam.undeploy to pam.demoundeploy. This
> > undeploys the demo applications.
> > ## Rename pam.rss to pam.rssdeploy for consistency
> > purpose.
> > ## Modify the pam.(portlet)undeploy targets to use the
> > jetspeed maven plugin jetspeed2:undeploy target.
> > ## Remove deployJar and deployClasses. portal-webapp
> > now uses dependencies for the portal component
> > library.
> > ## Remove jar:jar target.
> > ## Clean plugin.jelly: jetspeed2:register and
> > jetspeed2:unregister. Not used.
> >
>
> +1, remove all Jelly, move to M2
>
> > Have portal-webapp depend on the built Portlet
> > dependencies rather that the build target directories.
> > # Modify the maven.xml pam.(portlet)deploy target and
> > the maven-plugin to use the archived portlet war
> > deployed to the repository (maven install).
> >
>
> I like this idea of the portal-webapp, since its great for starting new
> projects where the goal is to customize the portal with your own skins,
> and your own build.
>
> > Let me know if you are alright with the proposed
> > changes and I will go ahead and create an issue as
> > well as implement the changes. I am almost doen. I
> > just need to perform some final testing locally and
> > get everyone's blessing.
> >
> You have my +1, although I propose going a step further and moving to M2
>
> --
> David Sean Taylor
> Bluesunrise Software
> david@bluesunrise.com
> [office] +01 707 773-4646
> [mobile] +01 707 529 9194
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: [J2] Build Process Summer Time Clean Up
Posted by David Le Strat <dl...@yahoo.com>.
See comments below.
--- David Sean Taylor <da...@bluesunrise.com> wrote:
.....
> +1, remove all Jelly, move to M2
> Have portal-webapp depend on the built Portlet
> dependencies rather that the build target
directories.
> # Modify the maven.xml pam.(portlet)deploy target
and
> the maven-plugin to use the archived portlet war
> deployed to the repository (maven install).
>
> I like this idea of the portal-webapp, since its
> great for starting new
> projects where the goal is to customize the portal
> with your own skins,
> and your own build.
>
> You have my +1, although I propose going a step
> further and moving to M2
--> David, we have been using M2 at work, so I
initially started with M2. When trying to upgrade the
plugin to Marmalade, that's where I run into trouble.
There is essentially no Marmalade documentation at
this point. Marmalade plugins are supposed to support
Jelly, but again no documentation. We could move in
that direction but this may take some time. If you
know of any resources on Marmalade, I am willing to
give it a shot. I have written an M2 plugins with
Java and it works quite well, Marmalade does not seem
quite ready yet.
In the meantime, we could make the changes with M1,
centralize the build dependency in the current plugin
and migrate the plugin later to M2.
> What if we would build a
> jetspeed-portal-template-<VERSION>.jar (not
> .war) which contained
> the proposed portal-webapp as well as its dependency
> (pom) definitions,
> sql (or schema) scripts,
> app server templates (like the different tomcat
> context files,
> JBoss/Webspere/BEA configs etc),
> and a default build.properties.
> Then the plugin could use that template to build a
> concrete portal,
> support (merge) overlay definitions (if any) and
> *not* be dependent on
> the concrete jetspeed component
> resources itself but derive those from the template
> and/or from a
> custom user build.properties.
> For our current portal project we then could be a
> completely empty project except for a project.xml
and
> a maven.xml executing nothing but the default plugin
> goals. A nice starter project for integrators!
I like Ate's proposal and will work towards that. I
propose to start the refactoring with M1 and to make
our way towards M2 as it matures.
Regards,
David Le Strat.
________________________
David Le Strat
Blogging @ http://dlsthoughts.blogspot.com
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: [J2] Build Process Summer Time Clean Up
Posted by David Sean Taylor <da...@bluesunrise.com>.
David Le Strat wrote:
> All,
>
> I finally got some time to get back to J2. I have a
> proposal for some summer time J2 build process clean
> up.
>
> Jetspeed2 current build process is a bit confusing.
> Through the various evolutions of J2 build process,
> many targets have been accumulated that make it
> difficult to easily understand the build process flow.
>
> h2. Cleaning up the build process
>
> Using J2 in its current form requires an in-depth
> understanding of how J2 build internals operate.
>
> As an example, an integrator wanting to get starting
> with J2 will want to start with the portal web
> application and customize it from there. It should be
> made easy for integrators to get started with the web
> application without requiring an in-depth
> understanding of the various sequences in the build
> process.
>
> A typical implementation will want to create a project
> as described below:
>
> {noformat}
> \sample-portal
> +---\etc Contains the build
> dependencies definition.
> +---\portal-webapp Contains the portal web
> application being built.
> +---\src Contains the portal
> initialization source (db scripts, etc).
> {noformat}
>
> Building the portal in this structure should be
> possible by leveraging the deployed Jetspeed
> dependencies:
>
> * Components: All libraries (jars) required for the
> runtime operation of the portal engine.
> * Portlets: All web libraries (wars) required for the
> runtime operation of the portal engine.
>
> Integrator using Jetspeed2 should be able to do so
> easily and to easily get (through dependencies) the
> latest versions of the release Jetspeed components
> (libraries as well as portlets).
>
> The current maven-plugin and portal build
> implementation rely on the source build (target
> directories) rather than the dependencies for the
> assembly of the portal engine, making it more
> difficult to get quickly started and to keep up with
> enhanced components.
>
> h2. Proposed changes
>
> The proposed changes below clean up the build process
> and slightly reorganize some elements to more easily
> achieve the goals outlined above.
>
> The first changes restructure the portal directory as
> follow.
> # Remove all non web related dependencies from portal:
> ## Move the portal java source and java tests to
> components/portal. This becomes a component that will
> be released as jetspeed-(version).jar
+1 in general, but don't all components follow a naming pattern of
jetspeed-{COMPONENT_NAME}-{VERSION}.jar?
> ## Rename the web application to portal-webapp and the
> artifact id to jetspeed-portal (to remove conflict
> with the jetspeed component artifact).
Maybe this artifact should be jetspeed-{VERSION}.war
> ## Move the test directory under portal-webapp to
> components/portal/test as it support the portal
> components tests.
+1
> ## Add org.apache.jetspeed.PortalTestConstants to
> centralize initialization of JETSPEED_PROPERTIES_PATH
> and PORTAL_WEBAPP_PATH.
>
> Clean up the portal-webapp (previously portal) build
> and maven-plugin.
I think that all build goals should be a part of the plugin.
Why have both plugin goals and maven.xml goals?
I'd also like to propose moving to Maven-2 as a part of this refactoring.
I think we should consider project archetypes for quickstarts and
replacing the current build with a M2 build.
Overview (from my notes at JavaOne):
* Super-POM: defaults across all projects
* transitive dependencies
* dependency scoping
* dependency management
* better control over snapshots
- only check one snapshot per build
- or check snapshot once per time period (day, hour..)
* post/pre goals removed
* build is now based on a lifecycle
* maven.xml, project.properties deprecated
* parent projects can be declared, no more ../..
* plugins configurable, POM based, auto-downloaded
* Plugin languages supported: Java Beanshell, Marmalade
* Explicit definiition of multiprojects
<modules>
<module>subproject-1</module>
<module>subproject-2</module>
....
* Project archetypes for quickstarts
> # Clean portal/maven.xml:
> ## Remove commented calls to targets.
> # The deploy and undeploy calls in the portal-webapp
> (previously portal) build process should be using the
> maven-plugin to do so. Multiple deploy, undeploy,
> register, unregister behaviors create confusion.
> Therefore, I propose to perform the following cleanup
> in the portal-webapp (previously portal):
> ## Remove pam.template.deploy. This is not used.
> ## Remove pam.unregister. Depends on
> pam.template.register which is not being used.
> ## Remove pam.template.register. This is not used.
> ## Remove pam.template.undeploy. There is a
> jetspeed2:undeploy target in the jetspeed plugin.
> ## Rename pam.register to pam.layoutdeploy. This
> really deploys the layout portlet and should be
> consistent with the other deploy targets.
> ## Rename pam.deploy to pam.demodeploy. This deploys
> the demo application.
> ## Rename pam.undeploy to pam.demoundeploy. This
> undeploys the demo applications.
> ## Rename pam.rss to pam.rssdeploy for consistency
> purpose.
> ## Modify the pam.(portlet)undeploy targets to use the
> jetspeed maven plugin jetspeed2:undeploy target.
> ## Remove deployJar and deployClasses. portal-webapp
> now uses dependencies for the portal component
> library.
> ## Remove jar:jar target.
> ## Clean plugin.jelly: jetspeed2:register and
> jetspeed2:unregister. Not used.
>
+1, remove all Jelly, move to M2
> Have portal-webapp depend on the built Portlet
> dependencies rather that the build target directories.
> # Modify the maven.xml pam.(portlet)deploy target and
> the maven-plugin to use the archived portlet war
> deployed to the repository (maven install).
>
I like this idea of the portal-webapp, since its great for starting new
projects where the goal is to customize the portal with your own skins,
and your own build.
> Let me know if you are alright with the proposed
> changes and I will go ahead and create an issue as
> well as implement the changes. I am almost doen. I
> just need to perform some final testing locally and
> get everyone's blessing.
>
You have my +1, although I propose going a step further and moving to M2
--
David Sean Taylor
Bluesunrise Software
david@bluesunrise.com
[office] +01 707 773-4646
[mobile] +01 707 529 9194
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[J2] Build Process Summer Time Clean Up
Posted by David Le Strat <dl...@yahoo.com>.
All,
I finally got some time to get back to J2. I have a
proposal for some summer time J2 build process clean
up.
Jetspeed2 current build process is a bit confusing.
Through the various evolutions of J2 build process,
many targets have been accumulated that make it
difficult to easily understand the build process flow.
h2. Cleaning up the build process
Using J2 in its current form requires an in-depth
understanding of how J2 build internals operate.
As an example, an integrator wanting to get starting
with J2 will want to start with the portal web
application and customize it from there. It should be
made easy for integrators to get started with the web
application without requiring an in-depth
understanding of the various sequences in the build
process.
A typical implementation will want to create a project
as described below:
{noformat}
\sample-portal
+---\etc Contains the build
dependencies definition.
+---\portal-webapp Contains the portal web
application being built.
+---\src Contains the portal
initialization source (db scripts, etc).
{noformat}
Building the portal in this structure should be
possible by leveraging the deployed Jetspeed
dependencies:
* Components: All libraries (jars) required for the
runtime operation of the portal engine.
* Portlets: All web libraries (wars) required for the
runtime operation of the portal engine.
Integrator using Jetspeed2 should be able to do so
easily and to easily get (through dependencies) the
latest versions of the release Jetspeed components
(libraries as well as portlets).
The current maven-plugin and portal build
implementation rely on the source build (target
directories) rather than the dependencies for the
assembly of the portal engine, making it more
difficult to get quickly started and to keep up with
enhanced components.
h2. Proposed changes
The proposed changes below clean up the build process
and slightly reorganize some elements to more easily
achieve the goals outlined above.
The first changes restructure the portal directory as
follow.
# Remove all non web related dependencies from portal:
## Move the portal java source and java tests to
components/portal. This becomes a component that will
be released as jetspeed-(version).jar
## Rename the web application to portal-webapp and the
artifact id to jetspeed-portal (to remove conflict
with the jetspeed component artifact).
## Move the test directory under portal-webapp to
components/portal/test as it support the portal
components tests.
## Add org.apache.jetspeed.PortalTestConstants to
centralize initialization of JETSPEED_PROPERTIES_PATH
and PORTAL_WEBAPP_PATH.
Clean up the portal-webapp (previously portal) build
and maven-plugin.
# Clean portal/maven.xml:
## Remove commented calls to targets.
# The deploy and undeploy calls in the portal-webapp
(previously portal) build process should be using the
maven-plugin to do so. Multiple deploy, undeploy,
register, unregister behaviors create confusion.
Therefore, I propose to perform the following cleanup
in the portal-webapp (previously portal):
## Remove pam.template.deploy. This is not used.
## Remove pam.unregister. Depends on
pam.template.register which is not being used.
## Remove pam.template.register. This is not used.
## Remove pam.template.undeploy. There is a
jetspeed2:undeploy target in the jetspeed plugin.
## Rename pam.register to pam.layoutdeploy. This
really deploys the layout portlet and should be
consistent with the other deploy targets.
## Rename pam.deploy to pam.demodeploy. This deploys
the demo application.
## Rename pam.undeploy to pam.demoundeploy. This
undeploys the demo applications.
## Rename pam.rss to pam.rssdeploy for consistency
purpose.
## Modify the pam.(portlet)undeploy targets to use the
jetspeed maven plugin jetspeed2:undeploy target.
## Remove deployJar and deployClasses. portal-webapp
now uses dependencies for the portal component
library.
## Remove jar:jar target.
## Clean plugin.jelly: jetspeed2:register and
jetspeed2:unregister. Not used.
Have portal-webapp depend on the built Portlet
dependencies rather that the build target directories.
# Modify the maven.xml pam.(portlet)deploy target and
the maven-plugin to use the archived portlet war
deployed to the repository (maven install).
Let me know if you are alright with the proposed
changes and I will go ahead and create an issue as
well as implement the changes. I am almost doen. I
just need to perform some final testing locally and
get everyone's blessing.
Regards.
________________________
David Le Strat
Blogging @ http://dlsthoughts.blogspot.com
____________________________________________________
Yahoo! Sports
Rekindle the Rivalries. Sign up for Fantasy Football
http://football.fantasysports.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: Need proposal for JS2-255 fix
Posted by David Sean Taylor <da...@bluesunrise.com>.
Dr. Michael Lipp wrote:
> Hi,
>
> I'm very close to really requiring JS2-255 to be fixed now. I think I
> have understood enough to try it myself. However, in order to be able to
> provide an acceptable patch, I'd like your opinion about what to use as
> replacement for "VALUE" in the DB schema. How about "THE_VALUE"?
>
To summarize, the following tables require modification:
FRAGMENT_PARAMETER
RULE_CRITERION
PA_METADATA_FIELDS
PD_METADATA_FIELDS
PREFERENCE_VALUE
SECURITY_CREDENTIAL
This modification is only required by MySQL MAX DB?
The whole name/value pair terminology is so widely used that Im not even
finding a good synonym for 'value'. Not too happy about "THE_VALUE" but
Im just not coming up with anything else except maybe attribute value or
parameter value, which could be abbreviated to AVALUE, not much better IMO
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org