[jboss-svn-commits] JBL Code SVN: r35965 - labs/jbossesb/workspace/johan.kumps.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Sun Nov 14 13:59:26 EST 2010
Author: johan.kumps
Date: 2010-11-14 13:59:25 -0500 (Sun, 14 Nov 2010)
New Revision: 35965
Removed:
labs/jbossesb/workspace/johan.kumps/Contributors.txt
labs/jbossesb/workspace/johan.kumps/Copyright.txt
labs/jbossesb/workspace/johan.kumps/Developer.txt
labs/jbossesb/workspace/johan.kumps/IDE/
labs/jbossesb/workspace/johan.kumps/JBossEULA.txt
labs/jbossesb/workspace/johan.kumps/Readme.txt
labs/jbossesb/workspace/johan.kumps/antlib/
labs/jbossesb/workspace/johan.kumps/findbugs/
labs/jbossesb/workspace/johan.kumps/integration-build.xml
labs/jbossesb/workspace/johan.kumps/product/
labs/jbossesb/workspace/johan.kumps/qa/
labs/jbossesb/workspace/johan.kumps/testlib/
Log:
Deleted: labs/jbossesb/workspace/johan.kumps/Contributors.txt
===================================================================
--- labs/jbossesb/workspace/johan.kumps/Contributors.txt 2010-11-14 07:50:01 UTC (rev 35964)
+++ labs/jbossesb/workspace/johan.kumps/Contributors.txt 2010-11-14 18:59:25 UTC (rev 35965)
@@ -1,35 +0,0 @@
-JBossESB is truly a community development. The following people have helped to make JBossESB.
-
-Adams, Derek
-Azizullah, Faisal
-Bevenius, Daniel
-Brum, Daniel
-Burke, Bill
-Cao, Sebastic
-Conner, Kevin
-Cunningham, Thomas
-Debnath, Mugdho
-DeGroff, Dave
-DiMaggio, Len
-Dunkin, Dave
-Fennelly, Tom
-Georges, Bruno
-Gilbert, John
-Kelly, Martin
-Keswani, Mohit
-Kumps, Johan
-Kunz, Dominik
-Larsen, Kenneth
-Lenhart, Jason
-Lietolahti, Jarkko
-Little, Mark
-Marchant, Dan
-Naidoo, Surendra
-Peuss, Thomas
-Sahu, Mihir
-Schifman, Esteban
-Sheridan, Rex
-Singh, Arvinder
-Stam, Kurt
-Sutter, Burr
-Ward, David
Deleted: labs/jbossesb/workspace/johan.kumps/Copyright.txt
===================================================================
--- labs/jbossesb/workspace/johan.kumps/Copyright.txt 2010-11-14 07:50:01 UTC (rev 35964)
+++ labs/jbossesb/workspace/johan.kumps/Copyright.txt 2010-11-14 18:59:25 UTC (rev 35965)
@@ -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/johan.kumps/Developer.txt
===================================================================
--- labs/jbossesb/workspace/johan.kumps/Developer.txt 2010-11-14 07:50:01 UTC (rev 35964)
+++ labs/jbossesb/workspace/johan.kumps/Developer.txt 2010-11-14 18:59:25 UTC (rev 35965)
@@ -1,135 +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_ROOT -> should point to directory *above* product
-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.
-
-DO NOT reformat code that is checked out from the repository. In the JBossESB 4.x codebase there
-is no mandatory style guide (we will fix this in the ESB 5 effort). If you change the format of
-code for no other reason than to make it easier to read, it makes it harder for others to determine
-what changes have occurred. Such changes may be backed out as a result.
-
-If adding tests then they should either be called:
-
-*UnitTest - unit tests
-*FuncTest - functional tests
-*IntegrationTest - integration tests
-
-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.jboss.org/repos/labs/labs/jbossesb/workspace/yourName
- 2) svn copy https://svn.jboss.org/repos/labs/labs/jbossesb/trunk https://svn.jboss.org/repos/labs/labs/jbossesb/workspace/yourName/branchName
- 3) svn co https://svn.jboss.org/repos/labs/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.jboss.org/repos/labs/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.jboss.org/repos/labs/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.jboss.org/repos/labs/labs/jbossesb/workspace/yourName
- 2) svn delete https://svn.jboss.org/repos/labs/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/johan.kumps/JBossEULA.txt
===================================================================
--- labs/jbossesb/workspace/johan.kumps/JBossEULA.txt 2010-11-14 07:50:01 UTC (rev 35964)
+++ labs/jbossesb/workspace/johan.kumps/JBossEULA.txt 2010-11-14 18:59:25 UTC (rev 35965)
@@ -1,127 +0,0 @@
-END USER LICENSE AGREEMENT
-JBOSS(r) ENTERPRISE MIDDLEWARE(TM)
-
-This end user license agreement ("EULA") governs the use of the various
-software modules that collectively comprise the JBoss Enterprise Middleware
-and any related updates, source code, appearance, structure and organization
-(the "Programs"), regardless of the delivery mechanism.
-
-1. License Grant. Subject to the following terms, Red Hat, Inc. ("Red Hat")
-grants to you ("User") a license to the Programs pursuant to the GNU Lesser
-General Public License v. 2.1 except for the following Programs: (a) JBoss
-Portal Forums and JBoss Transactions, 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 User wishes to obtain a commercial license for
-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
-www.opensource.org/licenses/alphabetical. The Programs are comprised of
-hundreds of software components. With the exception of certain image files
-identified in Section 2 below, the license agreement for each software
-component is located in the software component's source code and permits User
-to run, copy, modify, and redistribute (subject to certain obligations in some
-cases) the software component, in both source code and binary code forms. This
-agreement does not limit User's rights under, or grant User rights that
-supersede, the license terms of any particular component.
-
-2. Intellectual Property Rights. The Programs and each of their components are
-owned by Red Hat and others and are protected under copyright law and under
-other laws as applicable. Title to the Programs 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 Program trademarks, and the "Shadowman" logo are registered
-trademarks of Red Hat and its affiliates in the U.S. and other countries. This
-EULA does not permit User to distribute the Programs using Red Hat's
-trademarks, regardless of whether they have been modified. User should read
-the information found at http://www.redhat.com/about/corporate/trademark/
-before distributing a copy of the Programs. User may make a commercial
-redistribution of the Programs only if (a) a separate agreement with Red Hat
-authorizing such commercial redistribution is executed or other written
-permission is granted by Red Hat or (b) User must replace all Red Hat
-trademarks as well as the logos identified at
-http://www.jboss.com/company/logos. Merely deleting the files containing the
-Red Hat trademarks and logos may corrupt the Programs.
-
-3. Limited Warranty. Except as specifically stated in this Section 3, a
-separate agreement with Red Hat, or a license for a particular component, to
-the maximum extent permitted under applicable law, the Programs 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 Programs and the components are 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 User. Red Hat does not warrant that the functions
-contained in the Programs will meet User's requirements or that the operation
-of the Programs will be entirely error free, appear precisely as described in
-the accompanying documentation, or comply with regulatory requirements. This
-warranty extends only to the party that purchases services pertaining to the
-Programs from Red Hat or a Red Hat authorized distributor.
-
-4. Limitation of Remedies and Liability. To the maximum extent permitted by
-applicable law, User's exclusive remedy under this EULA is to return any
-defective media within 30 days of delivery along with a copy of User's payment
-receipt and Red Hat, at its option, will replace it or refund the money paid
-by User for the media. To the maximum extent permitted under applicable law,
-neither Red Hat, any Red Hat authorized distributor, nor the licensor of any
-component provided to User under this EULA will be liable to User for any
-incidental or consequential damages, including lost profits or lost savings
-arising out of the use or inability to use the Programs or any component, even
-if Red Hat, such authorized distributor, or licensor has been advised of the
-possibility of such damages. In no event shall Red Hat's liability, an
-authorized distributor's liability or the liability of the licensor of a
-component provided to User under this EULA exceed the amount that User paid to
-Red Hat under this EULA during the twelve months preceding the action.
-
-5. Export Control. As required by the laws of the United States and other
-countries, User represents and warrants that it: (a) understands that the
-Programs and their components 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, North Korea, Sudan and Syria, subject
-to change as posted by the United States government); (c) will not export,
-re-export, or transfer the Programs to any prohibited destination or entities
-on the U.S. Bureau of Industry and Security Denied Parties List or Entity
-List, or the U.S. Office of Foreign Assets Control list of Specially
-Designated Nationals and Blocked Persons, or any similar lists maintained by
-other countries, without the necessary export license(s) or authorizations(s);
-(d) will not use or transfer the Programs for use in connection with any
-nuclear, chemical or biological weapons, missile technology, or military
-end-uses where prohibited by an applicable arms embargo, unless authorized by
-the relevant government agency individual without the necessary export
-license(s) or authorizations(s) from the U.S. Government; (e) understands and
-agrees that if it is in the United States and exports or transfers the
-Programs to eligible end users, it will, to the extent required by EAR Section
-740.17(e), submit semi-annual reports to the Commerce Department's Bureau of
-Industry and Security, which include the name and address (including country)
-of each transferee; and (f) understands that countries including the United
-States may restrict the import, use, or export of encryption products (which
-may include the Programs and the components) and agrees 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 Programs that are not part of the Programs. These third party
-software programs are not required to run the Programs, are provided as a
-convenience to User, and are subject to their own license terms. The license
-terms either accompany the third party software programs or can be viewed at
-http://www.redhat.com/licenses/thirdparty/eula.html. If User does not agree to
-abide by the applicable license terms for the third party software programs,
-then User may not install them. If User wishes to install the third party
-software programs on more than one system or transfer the programs to another
-party, then User must contact the licensor of the applicable third party
-software 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 New York and
-of the United States, without regard to any conflict of laws provisions. The
-rights and obligations of the parties to this EULA shall not be governed by
-the United Nations Convention on the International Sale of Goods.
-
-Copyright (c) 2007 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.
Deleted: labs/jbossesb/workspace/johan.kumps/Readme.txt
===================================================================
--- labs/jbossesb/workspace/johan.kumps/Readme.txt 2010-11-14 07:50:01 UTC (rev 35964)
+++ labs/jbossesb/workspace/johan.kumps/Readme.txt 2010-11-14 18:59:25 UTC (rev 35965)
@@ -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/johan.kumps/integration-build.xml
===================================================================
--- labs/jbossesb/workspace/johan.kumps/integration-build.xml 2010-11-14 07:50:01 UTC (rev 35964)
+++ labs/jbossesb/workspace/johan.kumps/integration-build.xml 2010-11-14 18:59:25 UTC (rev 35965)
@@ -1,21 +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">
- <!--
- If you are adding something here then you are probably
- in the wrong location. This is just a wrapper for the
- product/qa configurations. All changes should be made
- within those build.xml files.
- -->
- <ant dir="product" target="ci-integration"/>
- <ant dir="qa" target="ci-test"/>
- </target>
-
- <target name="clean" description="Clean the distribution">
- <delete file="${clean.jms.dest}"/>
- <!-- Reversed order for clean -->
- <ant dir="qa" target="clean"/>
- <ant dir="product" target="clean"/>
- </target>
-</project>
More information about the jboss-svn-commits
mailing list