In fact, we don't even support "plain" Maven 2.0. TeamCity uses Maven 2.1 snapshot to run maven builds, because only this version has API which allows us to continuously monitor status of the build.
We can, surely, run Maven 1.0 builds as a simple command, but in this case we don't monitor status of the tests. All you'll get - downloaded artifacts and html reports generated by the build itself. I think such behavior can be obtained by running Simple Command Runner, which is available in Agra EAP
Honestly, Maven 1.0 doesn't have a high priority for us. We just suppose that it will become obsolete in a year or two and we prefer to spend resources to more perspective tools and technologies.
A lot of people moved from Maven 1.0 -> Maven 2.0 for performance and stability reasons. However, a large drawback of migrating to Maven 2.0 is that build customization is much more complex. Now that Maven 1.1 resolves most/all of the issues with Maven 1.1 you might want to seriously reconsider adding support for 1.x...
This is an interesting idea. Would you please add an issue into our tracker (http://www.jetbrains.net/tracker), so other people who might be intersted could vote for it. We would like to collect people's opinion before doing something in this field.
Thank you
A lot of people moved from Maven 1.0 -> Maven 2.0 for performance and stability reasons. However, a large drawback of migrating to Maven 2.0 is that build customization is much more complex. Now that Maven 1.1 resolves most/all of the issues with Maven 1.1 you might want to seriously reconsider adding support for 1.x...
Damian Murphy wrote:
By the moment Maven 1 is not supported.
Regards,
KIR
--
Kirill Maximov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com
"Develop with pleasure!"
Maven 1.x is still used and I think is a good point to support Maven 1.x; and I think is not huge to add it.
There are plans to support Maven 1.x?
Adrian,
In fact, we don't even support "plain" Maven 2.0.
TeamCity uses Maven 2.1 snapshot to run maven builds, because only this version has API which allows us to continuously monitor status of the build.
We can, surely, run Maven 1.0 builds as a simple command, but in this case we don't monitor status of the tests. All you'll get - downloaded artifacts and html reports generated by the build itself.
I think such behavior can be obtained by running Simple Command Runner, which is available in Agra EAP
Honestly, Maven 1.0 doesn't have a high priority for us. We just suppose that it will become obsolete in a year or two and we prefer to spend resources to more perspective tools and technologies.
With kind regards,
KIR
--
Kirill Maximov
JetBrains, Inc.
http://www.jetbrains.com
"Develop with pleasure!"
A lot of people moved from Maven 1.0 -> Maven 2.0 for performance and stability reasons. However, a large drawback of migrating to Maven 2.0 is that build customization is much more complex. Now that Maven 1.1 resolves most/all of the issues with Maven 1.1 you might want to seriously reconsider adding support for 1.x...
Hello,
This is an interesting idea. Would you please add an issue into our tracker
(http://www.jetbrains.net/tracker), so other people who might be intersted
could vote for it. We would like to collect people's opinion before doing
something in this field.
Thank you
--
Sergey Anchipolevsky
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"