build cleanup etc

[David Jencks <da...@yahoo.com>]

The openejb2 build is kind of a mess and after removing o/a/maven  
from my local repo it won't build for me any more.  Jdillon has done  
a great job putting a lot of the configuration info for a successful  
consistent build into geronimo's genesis.  One way we could avoid  
duplicating a lot of that work would be to use that as the openejb2  
parent.

Also:

- is anything useful in m2?

- can we remove the m1 build crud?

- I did NOT convert the package name in itests.  What's going on with  
these?  I think we at least would want to move the sample apps into  
real m2 projects separate from the itest runs.  It looks like someone  
may have put something identical or similar into g. testsuite.   
Having more than one copy seems like a really bad idea.  Anyone know  
what's going on?

- there are still a lot of non-m2-structure directories all over the  
place.

Thoughts about any of these?

thanks
david jencks

Re: build cleanup etc

[Jacek Laskowski <ja...@laskowski.net.pl>]

On 9/30/06, David Jencks <da...@yahoo.com> wrote:
> The openejb2 build is kind of a mess and after removing o/a/maven
> from my local repo it won't build for me any more.

It builds fine for me. What am I doing wrong to recreate your screnario?

jlaskowski@dev /cygdrive/c/oss/openejb2
$ uname -a
CYGWIN_NT-5.1 dev 1.5.21(0.156/4/2) 2006-07-30 14:21 i686 Cygwin

jlaskowski@dev /cygdrive/c/oss/openejb2
$ grep localRepository "$USERPROFILE"/.m2/settings.xml
  <localRepository>C:\.m2</localRepository>

jlaskowski@dev /cygdrive/c/oss/openejb2
$ rm -rf c\:/.m2/org/apache/maven

jlaskowski@dev /cygdrive/c/oss/openejb2
$ svn up && mvn clean install
...
At revision 451599.
...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] ------------------------------------------------------------------------
[INFO] OpenEJB ............................................... SUCCESS
[4:22:08.594s]
[INFO] OpenEJB :: Modules .................................... SUCCESS [0.047s]
[INFO] OpenEJB :: Core ....................................... SUCCESS
[2:16.859s]
[INFO] OpenEJB :: PK Generation :: Builder ................... SUCCESS [21.438s]
[INFO] OpenEJB :: Builder .................................... SUCCESS
[1:50.140s]
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 266 minutes 38 seconds
[INFO] Finished at: Sat Sep 30 15:41:06 CEST 2006
[INFO] Final Memory: 36M/254M
[INFO] ------------------------------------------------------------------------

>  Jdillon has done
> a great job putting a lot of the configuration info for a successful
> consistent build into geronimo's genesis.  One way we could avoid
> duplicating a lot of that work would be to use that as the openejb2
> parent.

+1

There's one thing I'd like to note before we go this way. We've
already inherited some information from org.apache.apache pom:

<parent>
    <groupId>org.apache</groupId>
    <artifactId>apache</artifactId>
    <version>3</version>
</parent>

It's because we're in incubation and lots of useful information is
included in it. Does M2 support multiple inheritance?

> - is anything useful in m2?

Hmm, why do you ask about it? Everybody loves M2 ;-)

> - can we remove the m1 build crud?

+1000000

> - I did NOT convert the package name in itests.  What's going on with
> these?  I think we at least would want to move the sample apps into
> real m2 projects separate from the itest runs.  It looks like someone
> may have put something identical or similar into g. testsuite.
> Having more than one copy seems like a really bad idea.  Anyone know
> what's going on?

Prasad would surely shed some light on it.

> - there are still a lot of non-m2-structure directories all over the
> place.

I'd convert them to m2-compliant structure. I don't want to tread on
your toes and took the liberty of leaving it to you. If you think
otherwise, please let me know and I'll be glad to help with this
matters.

The more I work on these organisational tasks, the better I understand
the layout and how it all works. I'd really like to start implementing
support for @Stateless beans, but since I has not been familiar with
the overall layout and code itself I kept falling short. That's why I
hope it'll change after we've entered incubation.

Jacek

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