On Sat, Jun 29, 2013 at 1:47 PM, Charles Oliver Nutter
<head...@headius.com>wrote:
> Ok, I've incorporated the changes. However for the moment I've left
> openssl and readline in their own ext submodules. What do you think of
> this?
>
not sure yet, might give some problems when we want to build everything
together in one go. but if they are really dependency problems to
jruby-core then we find a solution then ;) actually I like it better
separated.
it is time to look how we clue those pieces together also keeping
jruby-core and jruby-stdlib and jruby-complete in mind.
if you look at typical maven setup of project produces several maven
artifacts then it would look something like
.
├── jruby-complete
│ └── pom.xml
├── jruby-core
│ └── pom.xml
├── jruby-dev
│ ├── pom.xml
│ └── src
├── jruby-stdlib
│ └── pom.xml
├── openssl
│ ├── pom.xml
│ └── src
├── pom.xml
└── readline
├── pom.xml
└── src
the base pom.xml is the aggregator which is used to build all in one go and
to deploy/release everything. and the main thing would take place in
./jruby-dev
old pom.xml from jruby was such an aggregator so in the ./maven/pom.xml or
./docs/pom.xml
that would be one way to go just do it the maven way ;)
the other way to go would be to use our current pom.xml and make packaging
'pom' out of it and add the modules section in it. that is already a bit
"cheating" maven and I expect more such little cheats to get it working
that way.
maybe a mixture of of both is possible too:
.
├── jruby-complete
│ └── pom.xml
├── jruby-core
│ └── pom.xml
├── jruby-dev
│ └── pom.xml
├── jruby-stdlib
│ └── pom.xml
├── ext/openssl
│ ├── pom.xml
│ └── src
├── pom.xml
├── src
└── ext/readline
├── pom.xml
└── src
keep the sources and all in basedir and just move the current pom.xml to
jruby-dev. with some profiles it is possible to keep
$ mvn
just builds the jar for development ! it feels like a nice middle path for
me ;) shall I go for that one ?
- christian
