You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Thomas Minor (JIRA)" <ve...@apache.org> on 2006/10/12 16:46:36 UTC
[jira] Created: (VELTOOLS-65) Move to the Maven build system.
Move to the Maven build system.
-------------------------------
Key: VELTOOLS-65
URL: http://issues.apache.org/jira/browse/VELTOOLS-65
Project: VelocityTools
Issue Type: New Feature
Components: Build
Affects Versions: 1.3
Reporter: Thomas Minor
Since Velocity 1.5 is moving to maven andVelocity-Tools users will almost certain also use maven
Velocity-Tools should also move to maven as the build system. That way it could be easily included
in maven projects.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
[jira] Closed: (VELTOOLS-65) Move to the Maven build system.
Posted by "Antonio Petrelli (JIRA)" <de...@velocity.apache.org>.
[ https://issues.apache.org/jira/browse/VELTOOLS-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antonio Petrelli closed VELTOOLS-65.
------------------------------------
Resolution: Duplicate
Thanks for letting us know it, it has been superseded by VELOCITYSB-5.
> Move to the Maven build system.
> -------------------------------
>
> Key: VELTOOLS-65
> URL: https://issues.apache.org/jira/browse/VELTOOLS-65
> Project: Velocity Tools
> Issue Type: New Feature
> Components: Build
> Affects Versions: 1.3
> Reporter: Thomas Minor
>
> Since Velocity 1.5 is moving to maven andVelocity-Tools users will almost certain also use maven
> Velocity-Tools should also move to maven as the build system. That way it could be easily included
> in maven projects.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
[jira] Commented: (VELTOOLS-65) Move to the Maven build system.
Posted by "Nathan Bubna (JIRA)" <ve...@apache.org>.
[ http://issues.apache.org/jira/browse/VELTOOLS-65?page=comments#action_12442035 ]
Nathan Bubna commented on VELTOOLS-65:
--------------------------------------
I would at least welcome the contributions toward being able to build both Velocity and VelocityTools with maven2. As Henning said, they won't be the official builds, but having the option to build with Maven2 would be nice.
> Move to the Maven build system.
> -------------------------------
>
> Key: VELTOOLS-65
> URL: http://issues.apache.org/jira/browse/VELTOOLS-65
> Project: VelocityTools
> Issue Type: New Feature
> Components: Build
> Affects Versions: 1.3
> Reporter: Thomas Minor
>
> Since Velocity 1.5 is moving to maven andVelocity-Tools users will almost certain also use maven
> Velocity-Tools should also move to maven as the build system. That way it could be easily included
> in maven projects.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
[jira] Commented: (VELTOOLS-65) Move to the Maven build system.
Posted by "Henning Schmiedehausen (JIRA)" <ve...@apache.org>.
[ http://issues.apache.org/jira/browse/VELTOOLS-65?page=comments#action_12441783 ]
Henning Schmiedehausen commented on VELTOOLS-65:
------------------------------------------------
Just to make one thing clear: Velocity Engine is *NOT* moving to the maven build system anytime soon. All official release builds for now and the foreseeable future will be created by running "ant package" in the build directory. We are currently offering a not really supported maven 1 build for
a maven driven site and we might update to maven 2 exclusively for site building and reports.
But the official code builds will not be done with maven as long as I can -1 it... :-)
> Move to the Maven build system.
> -------------------------------
>
> Key: VELTOOLS-65
> URL: http://issues.apache.org/jira/browse/VELTOOLS-65
> Project: VelocityTools
> Issue Type: New Feature
> Components: Build
> Affects Versions: 1.3
> Reporter: Thomas Minor
>
> Since Velocity 1.5 is moving to maven andVelocity-Tools users will almost certain also use maven
> Velocity-Tools should also move to maven as the build system. That way it could be easily included
> in maven projects.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
[jira] Commented: (VELTOOLS-65) Move to the Maven build system.
Posted by "Henning Schmiedehausen (JIRA)" <ve...@apache.org>.
[ http://issues.apache.org/jira/browse/VELTOOLS-65?page=comments#action_12442062 ]
Henning Schmiedehausen commented on VELTOOLS-65:
------------------------------------------------
Thomas, you are right, I should elaborate on that. I'm also a part of the Turbine team, the project that Maven sprang from. My basic issue here is (as most people know that ever had to endure one of my rants about it) that a maven based build is IMHO neither stable nor repeatable. The ant build is and it is important to me to be able to have a stable, hassle-free build.
Uploading the binaries and sources to a maven archive automatically is really a plus and getting patches here would be greatly appriated. I know that you can drive the deployment side of maven using ant integration but haven't looked into it.
As I said, I'm willing to accept patches to engine for building with maven 2, Natan does the same for velocity-tools, however until maven has been proven to amend on these problems, ant will be first-class citizen for building.
> Move to the Maven build system.
> -------------------------------
>
> Key: VELTOOLS-65
> URL: http://issues.apache.org/jira/browse/VELTOOLS-65
> Project: VelocityTools
> Issue Type: New Feature
> Components: Build
> Affects Versions: 1.3
> Reporter: Thomas Minor
>
> Since Velocity 1.5 is moving to maven andVelocity-Tools users will almost certain also use maven
> Velocity-Tools should also move to maven as the build system. That way it could be easily included
> in maven projects.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
[jira] Commented: (VELTOOLS-65) Move to the Maven build system.
Posted by "Stevo Slavic (JIRA)" <de...@velocity.apache.org>.
[ https://issues.apache.org/jira/browse/VELTOOLS-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926749#action_12926749 ]
Stevo Slavic commented on VELTOOLS-65:
--------------------------------------
Looking at the [current trunk|http://svn.apache.org/repos/asf/velocity/tools/trunk/] (2.1.0-SNAPSHOT, r1023103), move to Apache Maven as build tool is complete, no traces of Apache Ant build.xml files. Only build instructions in [README.txt|http://svn.apache.org/viewvc/velocity/tools/trunk/README.txt?revision=998298&view=markup] seem to be outdated.
> Move to the Maven build system.
> -------------------------------
>
> Key: VELTOOLS-65
> URL: https://issues.apache.org/jira/browse/VELTOOLS-65
> Project: Velocity Tools
> Issue Type: New Feature
> Components: Build
> Affects Versions: 1.3
> Reporter: Thomas Minor
>
> Since Velocity 1.5 is moving to maven andVelocity-Tools users will almost certain also use maven
> Velocity-Tools should also move to maven as the build system. That way it could be easily included
> in maven projects.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
[jira] Commented: (VELTOOLS-65) Move to the Maven build system.
Posted by "Henning Schmiedehausen (JIRA)" <ve...@apache.org>.
[ http://issues.apache.org/jira/browse/VELTOOLS-65?page=comments#action_12442066 ]
Henning Schmiedehausen commented on VELTOOLS-65:
------------------------------------------------
I openend VELOCITY-466 to look into this. Thanks.
> Move to the Maven build system.
> -------------------------------
>
> Key: VELTOOLS-65
> URL: http://issues.apache.org/jira/browse/VELTOOLS-65
> Project: VelocityTools
> Issue Type: New Feature
> Components: Build
> Affects Versions: 1.3
> Reporter: Thomas Minor
>
> Since Velocity 1.5 is moving to maven andVelocity-Tools users will almost certain also use maven
> Velocity-Tools should also move to maven as the build system. That way it could be easily included
> in maven projects.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
[jira] Commented: (VELTOOLS-65) Move to the Maven build system.
Posted by "Thomas Minor (JIRA)" <ve...@apache.org>.
[ http://issues.apache.org/jira/browse/VELTOOLS-65?page=comments#action_12441946 ]
Thomas Minor commented on VELTOOLS-65:
--------------------------------------
Hmm,
you made you position clear, yet I miss an at least small explanation for it.
Would it be possible to provide both build mechanisms? I'd like to contribute here.
I could think of the standard official builds made via the ant build but also providing the
binaries for a maven2 repo. This way a smomth migration is possible.
> Move to the Maven build system.
> -------------------------------
>
> Key: VELTOOLS-65
> URL: http://issues.apache.org/jira/browse/VELTOOLS-65
> Project: VelocityTools
> Issue Type: New Feature
> Components: Build
> Affects Versions: 1.3
> Reporter: Thomas Minor
>
> Since Velocity 1.5 is moving to maven andVelocity-Tools users will almost certain also use maven
> Velocity-Tools should also move to maven as the build system. That way it could be easily included
> in maven projects.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org