Thanks for the reply.
I too primarily use Maven since I think that Maven is awesome. However,
it is not nearly as pervasive as Ant and it is a bit "needy".
It needs access to the Internet, not only to get project dependencies,
but to also get all of Maven plugins, which can be quite a lot. For
those without access to the Internet, this is a problem. Granted, you
can initially build on an Internet-connect machine, then move the local
repository to the disconnected machine. However, the local repository
includes a lot of dependencies for someone who just needs to build the
software but not do development.
My hope was to use Maven to do development of a project on an
Internet-connected machine. Then, when the project is released, I would
also release the project's sources, an ant build.xml file, and all the
project's dependencies. This would be the smallest complete set of
requirements for someone to build the project from source. This set of
requirements would be much less than those required to build the project
using Maven.
Perhaps this is just too much to ask. Thanks again for the reply.
Tim Moloney
Felix Meschberger wrote:
Hi Tim,
I have none, sorry, as I stopped using ant the moment I went maven :-)
Regards
Felix
On 11/8/06, Tim Moloney <[EMAIL PROTECTED]> wrote:
No suggestions or comments?
On Monday, 30 October 2006, Tim Moloney wrote:
> Is it possible for maven-ant-plugin to generate a build.xml file that
> will create a Felix bundle?
>
> Without changing my pom.xml, I ran "mvn ant:ant: to generate a
> build.xml file. Running ant on that build.xml does create a jar file
> that installs and resolves in Felix but it certainly doesn't execute.
>
> Documentation on maven-ant-plugin is a bit slim. It just describes
> the one goal (ant:ant) with its two parameters (localRepository and
> project||).
>
> Perhaps I'm expecting too much from maven-ant-plugin?
>
> Tim Moloney
>
>
