[jboss-svn-commits] JBL Code SVN: r26921 - labs/jbossesb/workspace/tfennelly.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Thu Jun 11 05:43:13 EDT 2009
Author: tfennelly
Date: 2009-06-11 05:43:13 -0400 (Thu, 11 Jun 2009)
New Revision: 26921
Removed:
labs/jbossesb/workspace/tfennelly/Contributors.txt
labs/jbossesb/workspace/tfennelly/Copyright.txt
labs/jbossesb/workspace/tfennelly/Developer.txt
labs/jbossesb/workspace/tfennelly/IDE/
labs/jbossesb/workspace/tfennelly/JBossORG-EULA.txt
labs/jbossesb/workspace/tfennelly/Readme.txt
labs/jbossesb/workspace/tfennelly/integration-build.xml
labs/jbossesb/workspace/tfennelly/product/
labs/jbossesb/workspace/tfennelly/qa/
Log:
dead
Deleted: labs/jbossesb/workspace/tfennelly/Contributors.txt
===================================================================
--- labs/jbossesb/workspace/tfennelly/Contributors.txt 2009-06-11 09:02:46 UTC (rev 26920)
+++ labs/jbossesb/workspace/tfennelly/Contributors.txt 2009-06-11 09:43:13 UTC (rev 26921)
@@ -1,31 +0,0 @@
-JBossESB is truly a community development. The following people have helped to make JBossESB.
-
-Mark Little
-Kevin Conner
-Daniel Brum
-Esteban Schifman
-Tom Fennelly
-Kurt Stam
-Johan Kumps
-Arvinder Singh
-Mugdho Debnath
-Mihir Sahu
-Dave Dunkin
-John Gilbert
-Burr Sutter
-Jason Lenhart
-Dave DeGroff
-Bruno Georges
-Sebastic Cao
-Jarkko Lietolahti
-Martin Kelly
-Surendra Naidoo
-Mohit Keswani
-Bill Burke
-Rex Sheridan
-Dan Marchant
-Derek Adams
-Thomas Peuss
-Daniel Bevenius
-Thomas Cunningham
-
Deleted: labs/jbossesb/workspace/tfennelly/Copyright.txt
===================================================================
--- labs/jbossesb/workspace/tfennelly/Copyright.txt 2009-06-11 09:02:46 UTC (rev 26920)
+++ labs/jbossesb/workspace/tfennelly/Copyright.txt 2009-06-11 09:43:13 UTC (rev 26921)
@@ -1,19 +0,0 @@
-/*
- * JBoss, Home of Professional Open Source
- * Copyright 2006, JBoss Inc., and others contributors as indicated
- * by the @authors tag. All rights reserved.
- * See the copyright.txt in the distribution for a
- * full listing of individual contributors.
- * This copyrighted material is made available to anyone wishing to use,
- * modify, copy, or redistribute it subject to the terms and conditions
- * of the GNU Lesser General Public License, v. 2.1.
- * This program is distributed in the hope that it will be useful, but WITHOUT A
- * WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
- * PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details.
- * You should have received a copy of the GNU Lesser General Public License,
- * v.2.1 along with this distribution; if not, write to the Free Software
- * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
- * MA 02110-1301, USA.
- *
- * (C) 2005-2006, 2007,
- */
\ No newline at end of file
Deleted: labs/jbossesb/workspace/tfennelly/Developer.txt
===================================================================
--- labs/jbossesb/workspace/tfennelly/Developer.txt 2009-06-11 09:02:46 UTC (rev 26920)
+++ labs/jbossesb/workspace/tfennelly/Developer.txt 2009-06-11 09:43:13 UTC (rev 26921)
@@ -1,123 +0,0 @@
-Project directory structure
-===========================
-product - contains the JBossESB product codebase, including unit tests.
-qa - contains the QA infrastructure for JBossESB.
-
-IDE
-===
-
-Eclipse:
-The IDE/JBossIDE/ directory contains .project and .classpath files for Eclipse.
-Copy these files to the corresponding directories under the trunk/product directory.
-
-The product/services directory contains several sub-projects that have their own src and test folders.
-Each of these can be created as new projects in eclipse.
-Example of creating a project for jbpm:
-1) Ctrl-N -> "Java Project" -> "Create project from existing source"
-2) Browse to product/services/jbpm and press "ok"
-3) Name the project something like "jbpm_<workspaceName>"
-
-Just repeat the above steps for the projects in the services directory that you want to have included
-in your workspace. The same can also be done for the product directory..
-A good way to keep different branches separate is to use working sets in Eclipse, this is where the
-suffix _workspaceName comes handy.
-
-The projects use the following user variables in Eclipse:
-ESB_HOME -> should point to product/build/jbossesb/lib
-ESB_LIB -> should point to product/lib/ext
-LOG4J -> should point to a log4j.jar
-
-The projects use the following libraries in Eclipse:
-JUnit 4
-
-Development
-===========
-If you have svn commit rights, then try to do your work within the workspace area first, before
-committing it to the trunk. We have a continuous integration build process that runs against the
-trunk whenever it is updated. See 'Subversion Guidelines' for more information.
-
-Please run the following test prior to commiting code against the main trunk:
-# product/build.xml -> target 'test'
-# product/build.xml -> target 'integration' (requires a local ftp server. See product.properties)
-# product/samples/quickstarts/test/build.xml -> target 'test'
-# qa/build.xml -> target 'test'
-
-Coding guidelines
-=================
-NOTE: you must ensure that all source files have the standard JBoss copyright at the start.
-
-Subversion Guidelines
-=====================
-Simple bug fixes may be performed on the trunk, but anything else should
-be done in a personal workspace. The following text will describe how to
-create a personal workspace, how to merge changes from main into your
-workspace, and also how to merge changes from your workspace into the trunk.
-
-
- Creating a personal workspace
- ==============================
- 1) svn mkdir https://svn.labs.jboss.com/labs/jbossesb/workspace/yourName
- 2) svn copy https://svn.labs.jboss.com/labs/jbossesb/trunk https://svn.labs.jboss.com/labs/jbossesb/workspace/yourName/branchName
- 3) svn co https://svn.labs.jboss.com/labs/jbossesb/workspace/yourName/branchName [<some local folder>]
-
- Step 1 is simply creating a directory where we can store as many workspaces as we want.
- Step 2 is making a copy of the main trunk to a folder name of your choice (branchName). This step can be repeated whenever
- you have the need to work on a separate branch, for example if you need to address a bug and do not want to disturb your
- current workspace with the changes.
- Step 3 is just a normal checkout of the workspace just copied.
-
-
- Merging changes from the trunk to your private workspace
- ========================================================
- Change directory to the local working copy of your workspace prior to performing the commands below.
-
- 1) svn merge -r initial_revision:$HEAD https://svn.labs.jboss.com/labs/jbossesb/trunk
- 2) resolve conflicts, run tests...
- 3) svn ci -m 'Merge from main initial_revision:$HEAD'
-
- * initial_revision - is the revision given to your branch by the svn copy command in step 2 of 'Creating a
- personal workspace'. You can use the command 'svn log --stop-on-copy' from within your working
- copy to display this revision number.
- * $HEAD is not a valid value, but specified in this way to indicate that you should use the actual value of
- the revision you want. This can be found by running 'svn update' from within the workspace copy
- of the main trunk. This is important, especially in the commit log message.
-
- Next time you want to update your working branch you can use the log command and grep like this:
- svn log | grep -A 1 -B 3 'Merge from main'
- This will display the list of merges that have been preformed previously. The next merge should use
- the value of the lastest merge's $HEAD value instead of the initial_revison number above.
-
-
- Merging changes from your private workspace to the trunk
- ========================================================
- Change directory to your working copy of the trunk prior to performing the commands below.
-
- 1) svn merge -r last_merge_commit_revision:$HEAD https://svn.labs.jboss.com/labs/jbossesb/workspace/yourName/branchName
- 2) Make sure you run the unit tests in the product directory and also the tests in the qa directory.
- 3) svn commit -m 'Merge from workspace/yourName/branchName last_merge_commit_revision:$HEAD'
-
- * last_merge_commit_revision - If this is the first time you are merging your workspace branch with main
- then this will be the revision given to your branch by the svn copy command in step 2 of 'Creating a
- personal workspace'. You can use the command 'svn log --stop-on-copy' from within your working
- copy to display this revision number.
- If this is not the first time you can run the following command from within your copy of the main trunks
- workspace:
- svn log | grep -A 1 -B 3 'Merge from workspace/yourName/branchName'
- This will give you a list all the merges that you have performed, BUT you should not use the revision numbers
- in this message, but instead the revision number of the commit for the entry, which is specified in the first column
- and the number is prefixed with an 'r', like r17.
-
- * $HEAD is not a valid value, but specified in this way to indicate that you should use the actual value of
- the revision you want. This can be found by running 'svn update' from with the workspace copy
- of the main trunk. This is important especially in the commit log message.
-
- Deleting your workspace
- =======================
- You can delete branches that you have created when they are no longer needed.
- 1) svn list https://svn.labs.jboss.com/labs/jbossesb/workspace/yourName
- 2) svn delete https://svn.labs.jboss.com/labs/jbossesb/workspace/yourName/branchName
-
- Step 1 is simply listing your branches.
-
- The branch is missing from the HEAD revision but can be resurrected.
-
Deleted: labs/jbossesb/workspace/tfennelly/JBossORG-EULA.txt
===================================================================
--- labs/jbossesb/workspace/tfennelly/JBossORG-EULA.txt 2009-06-11 09:02:46 UTC (rev 26920)
+++ labs/jbossesb/workspace/tfennelly/JBossORG-EULA.txt 2009-06-11 09:43:13 UTC (rev 26921)
@@ -1,107 +0,0 @@
-LICENSE AGREEMENT
-JBOSS(r)
-
-This License Agreement governs the use of the Software Packages and any updates to the Software
-Packages, regardless of the delivery mechanism. Each Software Package is a collective work
-under U.S. Copyright Law. Subject to the following terms, Red Hat, Inc. ("Red Hat") grants to
-the user ("Client") a license to the applicable collective work(s) pursuant to the
-GNU Lesser General Public License v. 2.1 except for the following Software Packages:
-(a) JBoss Portal Forums and JBoss Transactions JTS, each of which is licensed pursuant to the
-GNU General Public License v.2;
-
-(b) JBoss Rules, which is licensed pursuant to the Apache License v.2.0;
-
-(c) an optional download for JBoss Cache for the Berkeley DB for Java database, which is licensed under the
-(open source) Sleepycat License (if Client does not wish to use the open source version of this database,
-it may purchase a license from Sleepycat Software);
-
-and (d) the BPEL extension for JBoss jBPM, which is licensed under the Common Public License v.1,
-and, pursuant to the OASIS BPEL4WS standard, requires parties wishing to redistribute to enter various
-royalty-free patent licenses.
-
-Each of the foregoing licenses is available at http://www.opensource.org/licenses/index.php.
-
-1. The Software. "Software Packages" refer to the various software modules that are created and made available
-for distribution by the JBoss.org open source community at http://www.jboss.org. Each of the Software Packages
-may be comprised of hundreds of software components. The end user license agreement for each component is located in
-the component's source code. With the exception of certain image files identified in Section 2 below,
-the license terms for the components permit Client to copy, modify, and redistribute the component,
-in both source code and binary code forms. This agreement does not limit Client's rights under,
-or grant Client rights that supersede, the license terms of any particular component.
-
-2. Intellectual Property Rights. The Software Packages are owned by Red Hat and others and are protected under copyright
-and other laws. Title to the Software Packages and any component, or to any copy, modification, or merged portion shall
-remain with the aforementioned, subject to the applicable license. The "JBoss" trademark, "Red Hat" trademark, the
-individual Software Package trademarks, and the "Shadowman" logo are registered trademarks of Red Hat and its affiliates
-in the U.S. and other countries. This agreement permits Client to distribute unmodified copies of the Software Packages
-using the Red Hat trademarks that Red Hat has inserted in the Software Packages on the condition that Client follows Red Hat's
-trademark guidelines for those trademarks located at http://www.redhat.com/about/corporate/trademark/. Client must abide by
-these trademark guidelines when distributing the Software Packages, regardless of whether the Software Packages have been modified.
-If Client modifies the Software Packages, then Client must replace all Red Hat trademarks and logos identified at
-http://www.jboss.com/company/logos, unless a separate agreement with Red Hat is executed or other permission granted.
-Merely deleting the files containing the Red Hat trademarks may corrupt the Software Packages.
-
-3. Limited Warranty. Except as specifically stated in this Paragraph 3 or a license for a particular
-component, to the maximum extent permitted under applicable law, the Software Packages and the
-components are provided and licensed "as is" without warranty of any kind, expressed or implied,
-including the implied warranties of merchantability, non-infringement or fitness for a particular purpose.
-Red Hat warrants that the media on which Software Packages may be furnished will be free from defects in
-materials and manufacture under normal use for a period of 30 days from the date of delivery to Client.
-Red Hat does not warrant that the functions contained in the Software Packages will meet Client's requirements
-or that the operation of the Software Packages will be entirely error free or appear precisely as described
-in the accompanying documentation. This warranty extends only to the party that purchases the Services
-pertaining to the Software Packages from Red Hat or a Red Hat authorized distributor.
-
-4. Limitation of Remedies and Liability. To the maximum extent permitted by applicable law, the remedies
-described below are accepted by Client as its only remedies. Red Hat's entire liability, and Client's
-exclusive remedies, shall be: If the Software media is defective, Client may return it within 30 days of
-delivery along with a copy of Client's payment receipt and Red Hat, at its option, will replace it or
-refund the money paid by Client for the Software. To the maximum extent permitted by applicable law,
-Red Hat or any Red Hat authorized dealer will not be liable to Client for any incidental or consequential
-damages, including lost profits or lost savings arising out of the use or inability to use the Software,
-even if Red Hat or such dealer has been advised of the possibility of such damages. In no event shall
-Red Hat's liability under this agreement exceed the amount that Client paid to Red Hat under this
-Agreement during the twelve months preceding the action.
-
-5. Export Control. As required by U.S. law, Client represents and warrants that it:
-(a) understands that the Software Packages are subject to export controls under the
-U.S. Commerce Department's Export Administration Regulations ("EAR");
-
-(b) is not located in a prohibited destination country under the EAR or U.S. sanctions regulations
-(currently Cuba, Iran, Iraq, Libya, North Korea, Sudan and Syria);
-
-(c) will not export, re-export, or transfer the Software Packages to any prohibited destination, entity,
-or individual without the necessary export license(s) or authorizations(s) from the U.S. Government;
-
-(d) will not use or transfer the Software Packages for use in any sensitive nuclear, chemical or
-biological weapons, or missile technology end-uses unless authorized by the U.S. Government by
-regulation or specific license;
-
-(e) understands and agrees that if it is in the United States and exports or transfers the Software
-Packages to eligible end users, it will, as required by EAR Section 740.17(e), submit semi-annual
-reports to the Commerce Department's Bureau of Industry & Security (BIS), which include the name and
-address (including country) of each transferee;
-
-and (f) understands that countries other than the United States may restrict the import, use, or
-export of encryption products and that it shall be solely responsible for compliance with any such
-import, use, or export restrictions.
-
-6. Third Party Programs. Red Hat may distribute third party software programs with the Software Packages
-that are not part of the Software Packages and which Client must install separately. These third party
-programs are subject to their own license terms. The license terms either accompany the programs or
-can be viewed at http://www.redhat.com/licenses/. If Client does not agree to abide by the applicable
-license terms for such programs, then Client may not install them. If Client wishes to install the programs
-on more than one system or transfer the programs to another party, then Client must contact the licensor
-of the programs.
-
-7. General. If any provision of this agreement is held to be unenforceable, that shall not affect the
-enforceability of the remaining provisions. This License Agreement shall be governed by the laws of the
-State of North Carolina and of the United States, without regard to any conflict of laws provisions,
-except that the United Nations Convention on the International Sale of Goods shall not apply.
-
-Copyright 2006 Red Hat, Inc. All rights reserved.
-"JBoss" and the JBoss logo are registered trademarks of Red Hat, Inc.
-All other trademarks are the property of their respective owners.
-
- Page 1 of 1 18 October 2006
-
Deleted: labs/jbossesb/workspace/tfennelly/Readme.txt
===================================================================
--- labs/jbossesb/workspace/tfennelly/Readme.txt 2009-06-11 09:02:46 UTC (rev 26920)
+++ labs/jbossesb/workspace/tfennelly/Readme.txt 2009-06-11 09:43:13 UTC (rev 26921)
@@ -1,8 +0,0 @@
-This is the source code repository for JBossESB.
-
-For more information on JBossESB, visit http://labs.jboss.com/portal/jbossesb/?prjlist=false
-
-If you just want to check out the product codebase then check out jbossesb/product. The QA suite (available
-in jbossesb/qa) can be checked out and built separately. This is because QA code will eventually exceed the
-size of the product codebase and may not be needed by all users/developers.
-
Deleted: labs/jbossesb/workspace/tfennelly/integration-build.xml
===================================================================
--- labs/jbossesb/workspace/tfennelly/integration-build.xml 2009-06-11 09:02:46 UTC (rev 26920)
+++ labs/jbossesb/workspace/tfennelly/integration-build.xml 2009-06-11 09:43:13 UTC (rev 26921)
@@ -1,20 +0,0 @@
-<project name="JBESB-QA" default="integration" basedir=".">
- <property name="clean.jms.dest" location="clean.jms"/>
-
- <target name="integration" description="Run Continuous Integration." depends="clean">
- <ant dir="product" target="ci-integration"/>
- <!--
- <ant dir="product/samples/quickstarts/tests" target="qs-test"/>
- -->
- <ant dir="qa" target="ci-test"/>
- </target>
-
- <target name="clean" description="Clean the distribution">
- <delete file="${clean.jms.dest}"/>
- <ant dir="product" target="clean"/>
- <!--
- <ant dir="product/samples/quickstarts/tests" target="qs-clean"/>
- -->
- <ant dir="qa" target="clean"/>
- </target>
-</project>
More information about the jboss-svn-commits
mailing list