Hide Forgot
Date of First Response: 2008-12-17 11:43:54 project_key: JBEPP Assigning to myself for now.
Contacted Chris O' Brien as he does the packaging for EAP.
Viliam, This has priority and if you get overwhelmed, I will take care of some of other tasks that I have assigned to you. Please start on it once you are done with selenium builds which I think you are very close. Currently, for JBoss Portal 2.7 release process can be summarized as: 1. svn checkout portal code 2. svn checkout portal docs 3. build portal and docs 4. unzip JBoss AS 5. copy portal stuff to AS for bundled distro 5. copy portal docs 6. zip it and actual commands are: $ mkdir release $ cd release release $ svn export https://svn.jboss.org/repos/portal/tags/JBoss_Portal_2_7_0 project release $ svn export https://svn.jboss.org/repos/portal/docs/tags/JBoss_Portal_2_7_0 docs release $ svn export https://svn.jboss.org/repos/portal/examples/tags/JBoss_Portal_2_7_0_BETA1 examples release $ unzip jboss-4.2.3.GA.zip release $ cd docs release/docs $ mvn package release/docs $ cd ../project/build release/project/build $ sh build.sh release/project/build $ export JBOSS_HOME=$PWD/../../jboss-4.2.3.GA release/project/build $ ant -f distrib.xml Please try this out and see what you get in projects/build/output. These are the output of above steps. Now this needs to be modified for EPP. So, please leave distrib.xml as it is and create a new one (epp-release.xml) taking it as a baseline. What new script should do is: 1. Read different version name (Portal, EAP, location of EAP.zip) from a properties file so that all one needs to do is update this file for a new release. 2. Build JBoss Portal source 3. Copy jboss-portal.sar to default configuration 4. Copy jboss-portal-ha.sar to production and all configuration 5. Build portal docs and copy them to doc folders in EAP 6. Produce one zip out of it. Ultimately, the output if EAP + Portal = EPP. I understand you have many questions so please feel free to ask.
You may be able to steal some ideas from https://svn.corp.jboss.com/repos/soa/trunk/build-tools/build.xml and https://svn.corp.jboss.com/repos/soa/trunk/build-tools/dependencies.properties
There are two eap zips, one with security (jboss-eap-4.3.0.GA_CP03.zip) and one without security(jboss-eap-noauth-4.3.0.GA_CP03.zip). Please create a portal zip wiht each eap zip. We will be using noauth version for testing. Please also create a source zip of portal as well similar to how it's being done in distrib.xml. I will let you know about the doc parts soon.
- Please add portal-hsql-ds.xml to every server configuration. - EAP has seam stuff as well. We need to have that. We may have to modify jboss-log4j.xml to reduce some logging and I will let you know more on that.
When I unzip epp, currently it explodes to jboss-eap-4.3. This should be jboss-epp-4.3 instead.
Please add setup directory which contains DB descriptors for several databases. I believe when you build portal, it's in core/output/setup.
I tested your latest script. It is not using portal-hsql-ds.xml from portal source. This should not be dependent on value in properties file.
portal-hsaql-ds.xml is now hardcoded. i have run the script and tried to run servers in all configurations. it looked fine to me. the question which remains is the position of seam folder within the bundle zip, no the contents of bundle zip are like this: jboss-epp-4.3.GA/ seam/
in distro.xml there are two patches applied : run.conf patch and log4j patch... should i apply them too?
Yes to both. We would need to apply more patches to log4j like increasing the log level for hibernate etc otherwise there is too much logging.
We also need to apply them in various distrib and also patch run.bat to increase permgen space on windows machine.
I justed tested the script. When I unzip the zip, I am not seeing the same directory structure that I see when I unzip EAP zip. Please make sure they EPP zip explodes similar to that of EAP.
Link: Added: This issue depends JBEPP-26
Attaching patch to be applied to all run.conf i.e in default, all and production configuration.
Attachment: Added: run.conf.diff
Remember that there is a server/production/run.conf. :-)
Attachment: Added: run.bat.diff
Attaching jboss-log4j.xml to be used in EPP. Instead of applying it as patch, please simply replace one in EAP with this one but only in production configuration.
Attachment: Added: jboss-log4j.xml
patch for copyright.txt
Attachment: Added: copyright.txt.patch
The structure looks good now.
We need to add source code for modules to src zip as well. Please add following in properties file and use them in script to add it to src zip. common_module_source_url test_module_source_url cms_module_source_url portlet_module_source_url identity_module_source_url
Here are the URLs to try (you can see which tag to use by looking into build-thirdparty.xml) common: http://anonsvn.jboss.org/repos/portal/modules/common/tags/JBP_COMMON_1_2_2/ test:http://anonsvn.jboss.org/repos/portal/modules/test/tags/JBP_TEST_1_0_3/ cms: http://anonsvn.jboss.org/repos/portal/modules/cms/tags/JBP_CMS_1_2_1/ portlet:http://anonsvn.jboss.org/repos/portal/modules/portlet/tags/JBP_PORTLET_2_0_4/ identity:http://anonsvn.jboss.org/repos/portal/modules/identity/tags/JBP_IDENTITY_1_0_5/ I missed web module in my previous comment web:http://anonsvn.jboss.org/repos/portal/modules/web/tags/JBP_WEB_1_2_2/
Currenly, when I explode src zip, it explodes into the current directory. It should create a directory called jboss-epp-4.3-src and explode contents over there.
We need to include source portlet bridge as well. In properties file: portlet_bridge_source_url= You can use http://anonsvn.jboss.org/repos/portletbridge/tags/1.0.0.B5/ to test.
Some complication.:-) We need to include Seam Feature Pack with EPP. I have copied the zip at /home/pjha in qa lab since you don't have access to CSP. This zip nees to be exploded and its content should overwrite that of EAP zip. The seam folder from EAP needs to be removed. In properties file add: seam.featurepack.archive.url=
Oops...Seam feature pack is at /home/pjha/jboss-eap-fp-4.3.0.CP03-FP01.zip
Please add setup directory from core/output/resources/setup as well. Setup directory has sample database descriptor. jboss-epp-4.3 --jboss-as --seam (or seamfp or no seam at all) - Let's wait for this --setup
Another request, we need to pull examples from: https://svn.jboss.org/repos/portal/examples/tags/JBoss_Portal_2_7_1/ to: jboss-epp-4.3/jboss-as/docs/portal also put the 'samples' directory as we find in jboss-portal-bundle in: jboss-epp-4.3/jboss-as/docs/portal/samples thanks !