[osmosis-dev] May I provide Maven builds for Osmosis ?

[Brett Henderson]

On Thu, Nov 26, 2009 at 4:07 AM, Hakan Tandogan <hakan at gurkensalat.com>wrote:

> I have already added a pom.xml to the source tree and asked the guys over
> at sonatype.org to host the osmosis artifacts.
>
> Further progress may depend on the availability of postgis artifacts in
> maven.
>

Cool.


>
> > The svn:externals bit might make your life easier as well, because it
> > would let you build a more maven like directory hierarchy.  Once you get
> > something working, I'm happy to take a look at re-structuring the
> > current tree if it makes sense.
>
> Well, for the moment, I configured the maven pom to use your estabilished
> directory structure. After getting things going, I might come up with a
> restructuring proposal.
>

Okay.


>
> > One thing I should mention though.  Are you just using osmosis as a
> > library?  If so, it's pretty straightforward to configure ivy to publish
> > into a maven repository.  Currently I don't do any publishing because I
>
> Is it? I have to brush up my ivy knowledge, for the last three years, I
> have mostly used maven for java projects...
>

Um, at least I assume it is.  It's easy to read from a maven repository
(osmosis uses the maven public repo), but I've never tried to publish to
one.


>
> > don't have any inter-project dependencies, but it's not terribly
> difficult
> > to add.  It's up to you though.
>
> My main problem is that I live behind a proxy that requires HTTP-Auth.
> Maybe it is possible to convince ivy about the authentication, but I'd
> rather avoid having to put my proxy password in any config files.
>
> For maven, we already have a proxying repository, so the build tools don't
> need to know about my "secret" password...
>

Again, you could possibly configure ivy to point to the proxying repo.  But
no biggy.

Cheers,
Brett
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/osmosis-dev/attachments/20091126/a6fc5c5a/attachment.html>