when we have all the maven artifacts in place I feel that the biggest step
is done (I might be wrong ;)
currently I use the same build directory structure as ant uses (up to one
or two exceptions). so something like
$ mvn package
$ ant dist
should/will still work.
I personally find it important i
Tom: Maybe you can do some verification that "mvn package ; ant dist"
produces the right artifacts?
I think our best path forward would be to switch over to mvn as soon
as possible and slowly start dropping ant stuff as we confirm it's
working. But getting it in place and using it day today sooner
Charlie and I just talked about this and Charlie will merge this work onto
master and we will debug and fix from there.
My only other issue which might have been covered earlier is how we deal
with snapshots? We frequently update a library in build_lib today with the
intention to release it befor
On Fri, Jun 28, 2013 at 1:16 PM, Thomas E Enebo wrote:
> Charlie and I just talked about this and Charlie will merge this work onto
> master and we will debug and fix from there.
This is done! I made one additional change to use the shade plugin to
produce lib/jruby.jar directly (plus rename ASM
On Fri, Jun 28, 2013 at 7:16 PM, Thomas E Enebo wrote:
> We frequently update a library in build_lib today with the intention to
> release it before our next jruby release.
@Tom I am sure you know this: the usual maven procedure is using snapshots
- assuming that all of you can deploy snapshot
On Fri, Jun 28, 2013 at 7:34 PM, Charles Oliver Nutter
wrote:
> Can we make pom-ng.xml be pom.xml right now, kristian?
yes, go ahead. then I will rebase my repo to jruby master and send pull
requests.
I have to admit that I did switch over to use Mavenfile to do my changes.
just have a look if
yeah I was just not aware that sonatype gives us easy access to snapshots
repo. Knowing this makes me feel better about doing it the maven way.
-Tom
On Fri, Jun 28, 2013 at 1:35 PM, kristian wrote:
>
> On Fri, Jun 28, 2013 at 7:16 PM, Thomas E Enebo wrote:
>
>> We frequently update a library
Ok, updates...
I have done:
* remove all compile-related targets from ant build and shell out to
maven for compile. We still use jar targets in ant build because of
some missing pieces.
We are missing from the mvn build:
* building openssl and readline into their own jars (in stdlib), as in
ant
Oh and it looks like our next goal might be getting snapshot repo set
up, since travis can't find jnr-posix 3.0.1-SNAPSHOT to build. It will
be red until we can get a snapshot repo set up.
- Charlie
On Fri, Jun 28, 2013 at 3:03 PM, Charles Oliver Nutter
wrote:
> Ok, updates...
>
> I have done:
>
On Fri, Jun 28, 2013 at 9:03 PM, Charles Oliver Nutter
wrote:
> * building openssl and readline into their own jars (in stdlib), as in
> ant build. They're done this way so we can upgrade them. Will it be
> easier to do this if we make them their own artifacts? See
> jar-jopenssl and jar-readline
I just pushed a jnr-posix snapshot, and its in the sonatype snapshots
dir. Not sure if/when those get propagated to maven central.
On 29 June 2013 06:06, Charles Oliver Nutter wrote:
> Oh and it looks like our next goal might be getting snapshot repo set
> up, since travis can't find jnr-posix
On Sat, Jun 29, 2013 at 10:21:57AM +1000, Wayne Meissner wrote:
> I just pushed a jnr-posix snapshot, and its in the sonatype snapshots
> dir. Not sure if/when those get propagated to maven central.
This happens because our parent isn't sonatype atm; we might want to go
the consistency way and mov
Let's put the snapshot repo in the pom - the current pom for jruby.jar is not a
pom we are going to deploy to maven central as such.
- christian
Douglas Campos schrieb:
>On Sat, Jun 29, 2013 at 10:21:57AM +1000, Wayne Meissner wrote:
>> I just pushed a jnr-posix snapshot, and its in the sonat
13 matches
Mail list logo
