Maven 2.1.0 builtin support

When and how will Maven 2.1.0 builtin runner support be added? Probably it should be possible to select 2.0.x vs 2.1 (and probably soon 3.x?).

3 comments
Comment actions Permalink

Hello Yann,

As soon as I download it and run our intergration tests.
I think this going to happen today. If everything goes well Maven 2.1.0 will
be bundled into the next 4.1 EAP.

You can select any Maven installation by setting M2_HOME on the agent machine.
(our tests cover all maven versions starting from 2.0.4). The runner first
looks into the path provided in the settings page, then M2_HOME. The bundled
installation is of the lowest priority.

So you can easily try 2.1.0 right now with the current TeamCity installation.

When and how will Maven 2.1.0 builtin runner support be added?
Probably it should be possible to select 2.0.x vs 2.1 (and probably
soon 3.x?).

---
Original message URL:
http://www.jetbrains.net/devnet/message/5234144#5234144

--
Sergey Anchipolevsky
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

Hello Sergey,

thanks for your quick response.

I understand the current selection possibilites, unfortunately it requires installing all needed Maven version(s) manually on every agent + setting env vars. I suppose the possibility to have multiple versions of Maven runner, choosable in runner configuration, is not high priority and I can live with that.

Regards,
Yann

0
Comment actions Permalink

I see what you mean, Yann.
But usually such selection is appropriate for significantly different versions
like say Maven 1.x and Maven 2.x since they have different data format, much
different functionality and so on.
As far as I know, Maven 2.1.x is going to be compatible with poms created
for 2.0.x. So if backward compatibility issues occur it will hardly ever
be so critical and ubiquitous to make bundling multiple ditributives of the
same product be sensible enough. Anyway such an issue would be a bug in 2.1.x
and most likely would be fixed soon after it's introduction. We continuously
monitor new releases and (if they stable enough) bundle them into our TeamCity
releases as soon as possible.

I can't tell how we will support Maven 3.x -- it will depend on its difference
comparing to 2.x. Maybe as a separate runner, or an option in the existing
runner. As well as I can't tell whether we will bundle only Maven 3.x or
both. It will depend on its usefulness and practicability.

Hello Sergey,

thanks for your quick response.

I understand the current selection possibilites, unfortunately it
requires installing all needed Maven version(s) manually on every
agent + setting env vars. I suppose the possibility to have multiple
versions of Maven runner, choosable in runner configuration, is not
high priority and I can live wi

th that.

Regards,
Yann
---
Original message URL:
http://www.jetbrains.net/devnet/message/5234159#5234159

--
Sergey Anchipolevsky
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0

Please sign in to leave a comment.