Hi Wouter;
and first off, thanks for your thoughts on that.
Am Fri, 4 Feb 2011 10:21:29 +0100
schrieb Wouter van Reeven <wouter_at_van.reeven.nl>:
> You are trying to do things I haven't tried yet, so I canot help you
> here.
No problem. :) Seems this is something nobody has really tried by now,
at least using glassfish... I am still looking into it. :)
> However, I tried something that sounds similar. I have succesfully
> setup some projects to build and deploy JBI/CASA applications. Those
> are applications that can be deployed on OpenESB/GlassFish ESB. All
> the necessary classes and jars are nowhere to be found on the web.
I thought so. :( As a matter of fact, I found a couple of artifacts
that "resemble" the ones I was looking for (gf-client. ...) here
http://download.java.net/maven/glassfish/ ,
which left me ending up with downloading literally half the internet in
(transitive) dependencies, yet it didn't work. One guy in some of the
java.net forums (or was it a glassfish issue?) pointed out to please use
http://download.java.net/maven/2/
since the other repo is "glassfish implementation", but, in there, the
required artifacts simply aren't around.
> So I dug into the NetBeans ant scripts to figure out which jars are
> needed and installed them into our local Maven repository and told
> Nexus to make them available. I simply took the ones that ship with
> NetBeans :-)
Well...yes. I was thinking about the same solution, as well. But in the
end, we're unsure to eventually make the application we are about to
build publicly available under an open source license, so I so far
hesitate relying upon locally installed artifacts and would like to
rather have them available in a public repository.
> NetBeans also does a lot of checking, xml generation and other stuff
> to build the jars that will be deployed and it uses ant for that. So I
> included the maven antrun plugin in my poms and used that to copy the
> NetBeans behaviour.
Ooooooooooooh yeah, this is a d*** crude way, but I also ended up doing
things just like that way too often by now. :) And yet, I think the
best way for "our" use case would to seamlessly have glassfish play
with the "usual" way of doing such things in maven, especially as far
as the EJB client is concerned:
http://maven.apache.org/plugins/maven-ejb-plugin/examples/generating-ejb-client.html
> Using this approach we have succesfully been building and deploying
> our projects from Hudson to GlassFish ESB version 2. If you need some
> help with this, or have specific questions, you'll know where to find
> me.
Okay, I surely will, thanks a bunch again for your support. :) Again
(for the rest on this list, mainly), I'd really volunteer to write a
short article on how these things have to be done to work, as soon as I
figure out how to do so myself... :)
Cheers & all the best,
Kristian
--
Dipl.-Ing.(BA) Kristian Rink * Software- und Systemingenieur
planConnect GmbH * Könneritzstr. 33 * 01067 Dresden
fon: 0351 215 203 71 * cell: 0176 2447 2771 * mail: rink_at_planconnect.de
Amtsgericht Dresden HRB: 20 015 * St.-Nr. FA DD I 201 / 116 / 05360
Geschäftsführer: Stefan Voß, Karl Stierstorfer