ant elder wrote:
On Wed, Mar 2, 2011 at 2:28 PM, Simon Laws <simonsl...@googlemail.com> wrote:
On Tue, Mar 1, 2011 at 4:12 PM, ant elder <ant.el...@gmail.com> wrote:
On Wed, Feb 16, 2011 at 10:04 AM, Simon Nash <n...@apache.org> wrote:
ant elder wrote:
On Fri, Feb 11, 2011 at 11:57 AM, Simon Nash <n...@apache.org> wrote:
ant elder wrote:
On Fri, Feb 11, 2011 at 10:17 AM, ant elder <ant.el...@gmail.com> wrote:
On Fri, Feb 11, 2011 at 9:24 AM, Simon Nash <n...@apache.org> wrote:
Actually I would wonder what is the point of using maven to generate
an ant script that does exactly the same as the maven build.

In 1.x the ant scripts were provided as an alternative to maven that
use local artifacts from the binary distro instead of depending on
remote repositories.
I meant to add, if working offline using local artifacts is
useful/important then i wonder if that should also be possible with
the Maven builds in the binary distribution. It might be nice if both
the Ant and Maven builds could both work offline using the
distribution artifacts, which would probably mean having the jars in
the hierarchical directory structure that maven uses and having the
Tuscany standalone runtimes work with that. At least that would then
have the jars in a fairly common and understandable structure.

 ...ant


From this I presume you mean having these jars under the Tuscany
installation directory rather than in the user's local maven repo.

This seems like a good idea as it's first step to creating a more
embeddable Tuscany runtime installation.

 Simon

Does anyone know how to do that? It sounds like something someone else
must have wanted to do before, i guess with the assmbly plugin you
must be able to find the local repo and include that in a
distribution?

  ...ant


I think the main problem comes when the user wants to use maven to load
jars from some place on the file system other than the local maven repo.
I spent a bit of time a few months ago looking for a way to do that,
but I didn't find one.

 Simon


I've now spent a bit of time trying to do this too without much
success with any automated way. You'd think you should be able to use
the assembly plugin and copy files from somewhere like
${maven.repo.local} but it doesn't seem to work. Does anyone have any
other ideas ?

  ...ant

What was the process you were hoping to follow Ant? It sounds like:

1/ build the Tuscany source to popular .m2/respository
2/ create a distribution which packages .m2/resposityr maintaining the
same structure
3/ install the distribution with the packages respository intact
4/ run mvn but point it at the repository installed from the distribution

is that close?


Yep.

There is also a way using the <repository> element in the assembly
descriptor 
http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html#class_repository,
but that doesn't seem to include any plugins.

   ...ant


A repository that was used to build Tuscany would contain many other things
needed to build Tuscany that aren't part of Tuscany itself.  I presume these
would be removed before we make the distribution.

  Simon

Reply via email to