[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gump-commits
Subject:    svn commit: r890224 - /gump/metadata/project/commons-proper.xml
From:       bodewig () apache ! org
Date:       2009-12-14 8:40:43
Message-ID: 20091214084043.C173123888DC () eris ! apache ! org
[Download RAW message or body]

Author: bodewig
Date: Mon Dec 14 08:40:43 2009
New Revision: 890224

URL: http://svn.apache.org/viewvc?rev=890224&view=rev
Log:
after the groupId has changed, commons-lang3 can build as early as it wants to \
without getting confused with commons-lang-2.x

Modified:
    gump/metadata/project/commons-proper.xml

Modified: gump/metadata/project/commons-proper.xml
URL: http://svn.apache.org/viewvc/gump/metadata/project/commons-proper.xml?rev=890224&r1=890223&r2=890224&view=diff
 ==============================================================================
--- gump/metadata/project/commons-proper.xml (original)
+++ gump/metadata/project/commons-proper.xml Mon Dec 14 08:40:43 2009
@@ -594,20 +594,6 @@
     <package>org.apache.commons.lang3</package>
     <description>utilities for the classes that are in java.lang's \
hierarchy</description>  <mvn basedir="lang" goal="package" \
                separateLocalRepository="true"/>
-
-    <!-- these are mvn built projects that can't or won't adapt to
-         changes in trunk.
-
-         For now, take the easy way out and make sure they are built
-         before commons-lang.  Each of these projects must use a
-         separate local repo itself (and probably get a bunch of
-         dependencies stripped away)
-    -->
-    <option project="commons-configuration"/>
-    <!-- depends on commons-configuration -->
-    <option project="db-torque-generator"/>
-    <option project="db-torque-runtime"/>
-
     <jar name="lang/target/commons-lang-3.0-SNAPSHOT.jar" id="commons-lang"/>
 
     <nag to="dev@commons.apache.org" from="Gump &lt;issues@commons.apache.org&gt;"/>


[prev in list] [next in list] [prev in thread] [next in thread]