Ok, it seems to works. Engine and tools do compile.
Some questions remaining:
Webapps usually gather all their dependencies in WEB-INF/lib. Is there
any easy way to ask maven to copy somewhere all needed jars, or at least
give their location in maven cache? Otherwise, this should also be
2010/9/9 Nathan Bubna nbu...@gmail.com:
On Thu, Sep 9, 2010 at 12:27 AM, Antonio Petrelli
antonio.petre...@gmail.com wrote:
2010/9/8 Nathan Bubna nbu...@gmail.com:
2) Merge sandboxed Engine project(s) into the 2.x branch of Engine
3) Copy trunks of current projects into maintenance branches
2010/9/10 Claude Brisson cla...@renegat.net:
Webapps usually gather all their dependencies in WEB-INF/lib. Is there any
easy way to ask maven to copy somewhere all needed jars, or at least give
their location in maven cache? Otherwise, this should also be documented.
Yep, simple use the
2010/9/10 Antonio Petrelli antonio.petre...@gmail.com:
In the tools subprojects, we had very handy start.showcase.webapp and
stop.showcase.webapp that would start/stop the showcase webapp using Jetty
on the configured port. Is there any way to do it using maven?
mvn cargo:start
to start the
By the way, in which config file can one change the version number of a
dependancy?
pom.xml, obviously. It's everything there.
Ok, but what if I want to replace one dependancy with a custom build of
my own? Let's say, for instance: I modify something in the engine and
before
2010/9/10 Claude Brisson cla...@renegat.net:
By the way, in which config file can one change the version number of a
dependancy?
pom.xml, obviously. It's everything there.
Ok, but what if I want to replace one dependancy with a custom build of my
own? Let's say, for instance: I modify
Thanks. I guess we shouldn't wait too long for the migration, otherwise
the merge will quickly become a nightmare...
Claude
On 10/09/2010 13:32, Antonio Petrelli wrote:
2010/9/10 Claude Brissoncla...@renegat.net:
By the way, in which config file can one change the version number
2010/9/10 Claude Brisson cla...@renegat.net:
Thanks. I guess we shouldn't wait too long for the migration, otherwise the
merge will quickly become a nightmare...
I agree but I wish that the merge process is clear for everyone (me
included :-D ).
Antonio
On Fri, Sep 10, 2010 at 3:18 AM, Antonio Petrelli
antonio.petre...@gmail.com wrote:
2010/9/9 Nathan Bubna nbu...@gmail.com:
On Thu, Sep 9, 2010 at 12:27 AM, Antonio Petrelli
antonio.petre...@gmail.com wrote:
2010/9/8 Nathan Bubna nbu...@gmail.com:
2) Merge sandboxed Engine project(s) into the
All Velocity projects, with the exclusion of DBF, have been mavenized.
You can see the result of this process in the Subversion sandbox:
http://svn.apache.org/repos/asf/velocity/sandbox/maven-reorg/
The promotion process will be:
1. Merge recent changes in the official codebase in the sandboxed
+1 (with minor correction)
On Fri, Sep 10, 2010 at 12:01 PM, Antonio Petrelli
antonio.petre...@gmail.com wrote:
All Velocity projects, with the exclusion of DBF, have been mavenized.
You can see the result of this process in the Subversion sandbox:
+1 (non binding) with the correction of Nathan :-)
Antonio
2010/9/10 Antonio Petrelli antonio.petre...@gmail.com:
All Velocity projects, with the exclusion of DBF, have been mavenized.
You can see the result of this process in the Subversion sandbox:
+1 (ditto)
Claude
On 10/09/2010 21:14, Antonio Petrelli wrote:
+1 (non binding) with the correction of Nathan :-)
Antonio
2010/9/10 Antonio Petrelliantonio.petre...@gmail.com:
All Velocity projects, with the exclusion of DBF, have been mavenized.
You can see the result of this process
On 09/10/2010 09:01 PM, Antonio Petrelli wrote:
All Velocity projects, with the exclusion of DBF, have been mavenized.
You can see the result of this process in the Subversion sandbox:
http://svn.apache.org/repos/asf/velocity/sandbox/maven-reorg/
The promotion process will be:
1. Merge recent
14 matches
Mail list logo
