Re: Lets start moving to m2

[John Sisson]

If we do move things around in trunk, will it make merging changes made 
in the 1.1 branch more difficult?  If so, how important is it to move 
things now and would there be a better time to do it, e.g. when 1.1.1 is 
released?

John
Jason Dillon wrote:
FYI, another reason to drop the old m1 files are aggressively get the 
m2 build working are that we can move some stuff around, w/o working 
about breaking m1... for example, we should follow the m2 standard 
module layout:

    
http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html 


That, and pending some resolution about how the car/plan bits work, we 
may want to group module together like:

axis/
     pom.xml
     geronimo-axis/
         pom.xml
     geronimo-asix-plan/
         pom.xml

It will take a little while to move stuff around, and it would suck to 
have to support the m1 build during that time.

--jason


On Jun 27, 2006, at 2:55 PM, Matt Hogstrom wrote:

I'll retract my earlier comment.  Sounds like trunk is broken either 
way.   Damn the torpedoes as they say.  +1 to to M2 and +1 to fixing 
the itests.

Jason Dillon wrote:
This is basically the same clean process I use, and I agree with the 
statement about the actual failure changing quite often.
:-(
IMO it is also really sucky that we have to force tests to skip by 
default to get things built... or in this case closer to being built.
--jason
On Jun 27, 2006, at 1:41 PM, Bill Dudney wrote:
Hi Jacek,

this code base;

svn co https://svn.apache.org/repos/asf/geronimo/trunk geronimo

remove repository;

rm -rf ~/.maven

deep clean;

cd geronimo
find . -name target -type d | xargs rm -rf

build;

maven -Dmaven.test.skip=true new

fail;

....
+----------------------------------------
| geronimo and geronimo-plugins Geronimo :: Scripts
| Memory: 39M/73M
+----------------------------------------
DEPRECATED: the default goal should be specified in the <build> 
section of project.xml instead of maven.xml

build:end:

build:start:

multiproject:install-callback:
    [echo] Running jar:install for Geronimo :: Scripts
Tag library requested that is not present: 'geronimo:deploy' in 
plugin: 'null'
java:prepare-filesystem:
    [mkdir] Created dir: 
/Users/bdudney/Development/geronimo/modules/scripts/target/classes

java:compile:
    [echo] Compiling to 
/Users/bdudney/Development/geronimo/modules/scripts/target/classes
    [echo] No java source files to compile.

java:jar-resources:
Copying 14 files to 
/Users/bdudney/Development/geronimo/modules/scripts/target/classes

test:prepare-filesystem:
    [mkdir] Created dir: 
/Users/bdudney/Development/geronimo/modules/scripts/target/test-classes 

    [mkdir] Created dir: 
/Users/bdudney/Development/geronimo/modules/scripts/target/test-reports 


test:test-resources:

test:compile:
    [echo] No test source files to compile.

test:test:
    [echo] No tests to run.
Running post goal: test:test
    [touch] Creating 
/Users/bdudney/Development/geronimo/modules/scripts/target/test-reports/tstamp 


jar:jar:
    [jar] Building jar: 
/Users/bdudney/Development/geronimo/modules/scripts/target/geronimo-scripts-1.2-SNAPSHOT.jar 


jar:install:
    [echo] Installing...
Uploading to geronimo/jars/geronimo-scripts-1.2-SNAPSHOT.jar:
.................... (44K)
Uploading to geronimo/poms/geronimo-scripts-1.2-SNAPSHOT.pom:
.................... (9K)

+----------------------------------------
| geronimo and geronimo-plugins Geronimo :: Session
| Memory: 43M/73M
+----------------------------------------
DEPRECATED: the default goal should be specified in the <build> 
section of project.xml instead of maven.xml

build:end:

Attempting to download backport-util-concurrent-.jar.
WARNING: Failed to download backport-util-concurrent-.jar.

BUILD FAILED
File...... /Users/bdudney/Development/geronimo/maven.xml
Element... maven:reactor
Line...... 43
Column.... 115
The build cannot continue because of the following unsatisfied 
dependency:

backport-util-concurrent-.jar

Total time   : 22 minutes 30 seconds
Finished at  : Tuesday, June 27, 2006 2:10:30 PM MDT

This is not the only failure that I have received but just the one 
I could reproduce today. The actual failure seems to change quite 
often. The failures seem to come in spurts for a couple of weeks it 
won't build, other times it will build for a week or so then stop 
building.

Thanks!


Bill Dudney
MyFaces - http://myfaces.apache.org
Cayenne - http://incubator.apache.org/projects/cayenne.html



On Jun 27, 2006, at 1:40 PM, Jacek Laskowski wrote:

On 6/27/06, Bill Dudney <[EMAIL PROTECTED]> wrote:
FWIW

I am not able to get a clean build with either m1 or m2 either.

What? I can't be. What error(s) do you encounter? I've just done 
it on
a clean machine and it worked like a charm. The m2 build is another
story, but it's not been announced official yet.

Bill Dudney

Jacek

--Jacek Laskowski
http://www.laskowski.net.pl