Re: [OGNL] drop old opensymphony build
2011/5/17 Henri Yandell flame...@gmail.com Looks useful to me. Download the ant task. Use this standard file. Execute. Save us maintaining a pointless build.xml. I don't think we need it at all. Don't you think that developers are able to download Maven like they did for Ant? I think that presuming that developers want always to use Ant for their builds is an insult to their intelligence :-D Don't misunderstand me, Ant was a great tool, but now we have to move on, like when most of us moved away from Java 1.4. Antonio
Re: [OGNL] drop old opensymphony build
+1 for dropping the old way of build REgards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ Warszawa JUG conference - Confitura http://confitura.pl/ - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [OGNL] drop old opensymphony build
On 18 May 2011 08:31, Antonio Petrelli antonio.petre...@gmail.com wrote: 2011/5/17 Henri Yandell flame...@gmail.com Looks useful to me. Download the ant task. Use this standard file. Execute. Save us maintaining a pointless build.xml. I don't think we need it at all. Don't you think that developers are able to download Maven like they did for Ant? Maven requires a lot more downloading than just the product. The first time you use Maven for a build, it will download a lot of other stuff, much of which is not (yet) needed. I think that presuming that developers want always to use Ant for their builds is an insult to their intelligence :-D What has intelligence to do with it? This is about providing choice. Don't misunderstand me, Ant was a great tool, but now we have to move on, like when most of us moved away from Java 1.4. Ant still is a great tool. But it has different goals from Maven. - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [OGNL] drop old opensymphony build
2011/5/18 sebb seb...@gmail.com On 18 May 2011 08:31, Antonio Petrelli antonio.petre...@gmail.com wrote: 2011/5/17 Henri Yandell flame...@gmail.com Looks useful to me. Download the ant task. Use this standard file. Execute. Save us maintaining a pointless build.xml. I don't think we need it at all. Don't you think that developers are able to download Maven like they did for Ant? Maven requires a lot more downloading than just the product. The first time you use Maven for a build, it will download a lot of other stuff, much of which is not (yet) needed. I don't want to start a Maven vs Ant war, but we need to choose only one of those. Providing two ways of building a project is not choice, it increases confusion. What is important to OGNL users is the possibility to use it in a Maven, Ant, Whatever build tool. Since Apache is committed to Maven we *should* use Maven. But Ant users can use Ivy. Other build tools are able to use Maven repository. I think that presuming that developers want always to use Ant for their builds is an insult to their intelligence :-D What has intelligence to do with it? This is about providing choice. What I meant is that developers are able to download and install Maven like they did it for Ant. After some minutes of ranting, they will be able to build the project from source, even if we don't provide an Ant build file. Don't misunderstand me, Ant was a great tool, but now we have to move on, like when most of us moved away from Java 1.4. Ant still is a great tool. But it has different goals from Maven. But surely we won't use it as a primary way of building OGNL. What I am trying to say is that it is superfluous to use it even as a secondary way. Adding a plugn for Maven that generates a build file, adds a (minimal) amount of maintenance effort that, IMHO, can be avoided because it does not give a real benefit to final users. Antonio
[OGNL] drop old opensymphony build
Hi all guys, WDYT on dropping old opensymphony ant related build stuff? I think maintaining the maven stuff only is more than enough, or not? I don't think that minor-task worths an Iusse, just discuss about it here. Have a nice day! Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [OGNL] drop old opensymphony build
Generally that it's fine to drop the build and focus on the m2 build, but if someone is willing to step up and support a different build then that is fine too. I think the solution is an Ant task that can parse pom.xml and provide basic build/test support :) Hen On Tue, May 17, 2011 at 6:47 AM, Simone Tripodi simonetrip...@apache.org wrote: Hi all guys, WDYT on dropping old opensymphony ant related build stuff? I think maintaining the maven stuff only is more than enough, or not? I don't think that minor-task worths an Iusse, just discuss about it here. Have a nice day! Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [OGNL] drop old opensymphony build
Henri Yandell wrote: Generally that it's fine to drop the build and focus on the m2 build, but if someone is willing to step up and support a different build then that is fine too. I think the solution is an Ant task that can parse pom.xml and provide basic build/test support :) You mean this: http://maven.apache.org/plugins/maven-ant-plugin/ - Jörg - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [OGNL] drop old opensymphony build
We're using the commons-parent, that has the ant-plugin already set, I'll give a try :) thanks! Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Tue, May 17, 2011 at 5:17 PM, Jörg Schaible joerg.schai...@scalaris.com wrote: Henri Yandell wrote: Generally that it's fine to drop the build and focus on the m2 build, but if someone is willing to step up and support a different build then that is fine too. I think the solution is an Ant task that can parse pom.xml and provide basic build/test support :) You mean this: http://maven.apache.org/plugins/maven-ant-plugin/ - Jörg - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [OGNL] drop old opensymphony build
On Tue, May 17, 2011 at 8:17 AM, Jörg Schaible joerg.schai...@scalaris.com wrote: Henri Yandell wrote: Generally that it's fine to drop the build and focus on the m2 build, but if someone is willing to step up and support a different build then that is fine too. I think the solution is an Ant task that can parse pom.xml and provide basic build/test support :) You mean this: http://maven.apache.org/plugins/maven-ant-plugin/ Not really - I'd mean an Ant task that reads a pom, not a Maven plugin that generates an Ant file. The latter needs Maven (which the user specifically won't have) and is a pain to manage (we have to keep regenerating). Hen - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [OGNL] drop old opensymphony build
Hello, At least for dependency resolution you can use [1]. But is it useful ? /Olivier [1] http://maven.apache.org/ant-tasks/ 2011/5/17 Henri Yandell flame...@gmail.com: On Tue, May 17, 2011 at 8:17 AM, Jörg Schaible joerg.schai...@scalaris.com wrote: Henri Yandell wrote: Generally that it's fine to drop the build and focus on the m2 build, but if someone is willing to step up and support a different build then that is fine too. I think the solution is an Ant task that can parse pom.xml and provide basic build/test support :) You mean this: http://maven.apache.org/plugins/maven-ant-plugin/ Not really - I'd mean an Ant task that reads a pom, not a Maven plugin that generates an Ant file. The latter needs Maven (which the user specifically won't have) and is a pain to manage (we have to keep regenerating). Hen - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [OGNL] drop old opensymphony build
2011/5/17 Simone Tripodi simonetrip...@apache.org WDYT on dropping old opensymphony ant related build stuff? I think maintaining the maven stuff only is more than enough, or not? I don't think that minor-task worths an Iusse, just discuss about it here. Hi Absolutely, kill Ant stuff, we don't need it and we can do anything with Maven plugins. Antonio P.S. Been out for 4 days so sorry for not having read it before.
Re: [OGNL] drop old opensymphony build
Hi Antonio, don't worry and thanks for your feedback!!! Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Tue, May 17, 2011 at 9:00 PM, Antonio Petrelli antonio.petre...@gmail.com wrote: 2011/5/17 Simone Tripodi simonetrip...@apache.org WDYT on dropping old opensymphony ant related build stuff? I think maintaining the maven stuff only is more than enough, or not? I don't think that minor-task worths an Iusse, just discuss about it here. Hi Absolutely, kill Ant stuff, we don't need it and we can do anything with Maven plugins. Antonio P.S. Been out for 4 days so sorry for not having read it before. - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [OGNL] drop old opensymphony build
Henri Yandell wrote: On Tue, May 17, 2011 at 8:17 AM, Jörg Schaible joerg.schai...@scalaris.com wrote: Henri Yandell wrote: Generally that it's fine to drop the build and focus on the m2 build, but if someone is willing to step up and support a different build then that is fine too. I think the solution is an Ant task that can parse pom.xml and provide basic build/test support :) You mean this: http://maven.apache.org/plugins/maven-ant-plugin/ Not really - I'd mean an Ant task that reads a pom, not a Maven plugin that generates an Ant file. The latter needs Maven (which the user specifically won't have) and is a pain to manage (we have to keep regenerating). The idea is that you generate the Ant build and include it in the delivery, so that a user can chose between Ant or Maven on its own. I just have no idea, how well the generated build works. The latter is also possible, but if you call Maven (core) with an Ant task, it does not really help. - Jörg - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [OGNL] drop old opensymphony build
Looks useful to me. Download the ant task. Use this standard file. Execute. Save us maintaining a pointless build.xml. Hen On Tue, May 17, 2011 at 10:07 AM, Olivier Lamy ol...@apache.org wrote: Hello, At least for dependency resolution you can use [1]. But is it useful ? /Olivier [1] http://maven.apache.org/ant-tasks/ 2011/5/17 Henri Yandell flame...@gmail.com: On Tue, May 17, 2011 at 8:17 AM, Jörg Schaible joerg.schai...@scalaris.com wrote: Henri Yandell wrote: Generally that it's fine to drop the build and focus on the m2 build, but if someone is willing to step up and support a different build then that is fine too. I think the solution is an Ant task that can parse pom.xml and provide basic build/test support :) You mean this: http://maven.apache.org/plugins/maven-ant-plugin/ Not really - I'd mean an Ant task that reads a pom, not a Maven plugin that generates an Ant file. The latter needs Maven (which the user specifically won't have) and is a pain to manage (we have to keep regenerating). Hen - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [OGNL] drop old opensymphony build
+1!!! :) http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Tue, May 17, 2011 at 11:36 PM, Henri Yandell flame...@gmail.com wrote: Looks useful to me. Download the ant task. Use this standard file. Execute. Save us maintaining a pointless build.xml. Hen On Tue, May 17, 2011 at 10:07 AM, Olivier Lamy ol...@apache.org wrote: Hello, At least for dependency resolution you can use [1]. But is it useful ? /Olivier [1] http://maven.apache.org/ant-tasks/ 2011/5/17 Henri Yandell flame...@gmail.com: On Tue, May 17, 2011 at 8:17 AM, Jörg Schaible joerg.schai...@scalaris.com wrote: Henri Yandell wrote: Generally that it's fine to drop the build and focus on the m2 build, but if someone is willing to step up and support a different build then that is fine too. I think the solution is an Ant task that can parse pom.xml and provide basic build/test support :) You mean this: http://maven.apache.org/plugins/maven-ant-plugin/ Not really - I'd mean an Ant task that reads a pom, not a Maven plugin that generates an Ant file. The latter needs Maven (which the user specifically won't have) and is a pain to manage (we have to keep regenerating). Hen - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
