Re: svn commit: r452927 - /geronimo/server/trunk/pom.xml

2006-10-04 Thread David Jencks


On Oct 4, 2006, at 11:38 AM, Dain Sundstrom wrote:


On Oct 4, 2006, at 11:13 AM, Jason Dillon wrote:

I have been trying to remove the need for all of those  
properties.  I think a few of these are fine... just as long as  
those properties are never used in child modules.  But most people  
copy past the deps, so these properties are bound to leak.


I agree but the alternative is some pretty ugly perl code to find  
the correct version numbers to change.


Another possiblility might be to move the openejb configs into  
openejb so the only use of openejb is in assemblies.  (don't know if  
the webconsole refers to openejb -- if so that part should also move  
to openejb)


david jencks



-dain




Re: svn commit: r452927 - /geronimo/server/trunk/pom.xml

2006-10-04 Thread Jason Dillon
I think maven needs to fix this problem in general... I was thinking  
about suggesting they add dependencyGroups to dependencies, which can  
be used to share config between dependencies:





org.apache.openejb
2.2-incubating-SNAPSHOT


openejb-core


openejb-builder


openejb-pkgen-builder


openejb-yoko


openejb-sunorb






Dunno about the exact syntax, but the general idea is to allow more  
config to be shared between deps.


--jason


On Oct 4, 2006, at 11:38 AM, Dain Sundstrom wrote:


On Oct 4, 2006, at 11:13 AM, Jason Dillon wrote:

I have been trying to remove the need for all of those  
properties.  I think a few of these are fine... just as long as  
those properties are never used in child modules.  But most people  
copy past the deps, so these properties are bound to leak.


I agree but the alternative is some pretty ugly perl code to find  
the correct version numbers to change.


-dain




Re: svn commit: r452927 - /geronimo/server/trunk/pom.xml

2006-10-04 Thread Dain Sundstrom

On Oct 4, 2006, at 11:13 AM, Jason Dillon wrote:

I have been trying to remove the need for all of those properties.   
I think a few of these are fine... just as long as those properties  
are never used in child modules.  But most people copy past the  
deps, so these properties are bound to leak.


I agree but the alternative is some pretty ugly perl code to find the  
correct version numbers to change.


-dain


Re: svn commit: r452927 - /geronimo/server/trunk/pom.xml

2006-10-04 Thread Jason Dillon
I have been trying to remove the need for all of those properties.  I  
think a few of these are fine... just as long as those properties are  
never used in child modules.  But most people copy past the deps, so  
these properties are bound to leak.


--jason


On Oct 4, 2006, at 9:40 AM, [EMAIL PROTECTED] wrote:


Author: dain
Date: Wed Oct  4 09:40:49 2006
New Revision: 452927

URL: http://svn.apache.org/viewvc?view=rev&rev=452927
Log:
Move openejb version number to a single shared property which makes  
automcatically changing it in the weekly build much easier


Modified:
geronimo/server/trunk/pom.xml

Modified: geronimo/server/trunk/pom.xml
URL: http://svn.apache.org/viewvc/geronimo/server/trunk/pom.xml? 
view=diff&rev=452927&r1=452926&r2=452927
== 


--- geronimo/server/trunk/pom.xml (original)
+++ geronimo/server/trunk/pom.xml Wed Oct  4 09:40:49 2006
@@ -46,6 +46,11 @@

 
 
+2.2-incubating-SNAPSHOT
+
+
 10.1.3.1
@@ -585,31 +590,31 @@
 
 org.apache.openejb
 openejb-core
-2.2-incubating-SNAPSHOT
+${openejbVersion}
 

 
 org.apache.openejb
 openejb-builder
-2.2-incubating-SNAPSHOT
+${openejbVersion}
 

 
 org.apache.openejb
 openejb-pkgen-builder
-2.2-incubating-SNAPSHOT
+${openejbVersion}
 

 
 org.apache.openejb
 openejb-yoko
-2.2-incubating-SNAPSHOT
+${openejbVersion}
 

 
 org.apache.openejb
 openejb-sunorb
-2.2-incubating-SNAPSHOT
+${openejbVersion}