What do you think: Integrate IDEA global libraries with Maven Repositories

I do not have any experience with Maven (still using tmuch trusted Ant) but
I was wondering if it would be a useful to allow definition of IDEA global
libraries as a reference to a Maven repository.

Few reasons:
- When using TeamCity with Maven we would need this repository anyway
- Provide common libraries for all team members
- Save time on library definition
- Auto cache locally on first use
- Keep libraries up to date in one place


3 comments
Comment actions Permalink

I use Maven + Idea here all the day. And since I use Maven I no longer requre global libraries or something else. I simply create a new Maven project, define the dependencies and then let Maven create a Idea project for me:


Then just open the created project and all is done...

0
Comment actions Permalink

There is really no reason to do this. In any Maven project you end up creating a corporate inhouse Maven repository to store third party jars not available in Maven repositories - this is also done since Maven repositories tend to be kind of slow.

Kind regards
Georges

0
Comment actions Permalink

Georges,

That's fine, I assumed it. But why configure both Maven and IDEA? We have
many small to mid size projects we develop and then maintain. It is a royal
headache to maintain IDEA libraries so you can develop and Ant scripts so
you can build and deploy. We have ant include file which defines all
libraries by version we use and I assume we will have to do it in Maven. But
why can't IDEA take advantage of these definitions. Not to say that I have
several people in my team and I have to make sure they keep their libraries
up to date. I, muself is also getting tired of checking for libraries
updates. I wish I had something like RSS for libraries so I can be notified
when anew version is available and offered to download it to my repository.
And then when I start IDEA Idea would recognize a new version and offer to
import it as an update to an existing library (for minor updates) or a new
library (major update)

Thank you

Alex





"Georges" <no_reply@jetbrains.com> wrote in message
news:29272451.1169804682852.JavaMail.itn@is.intellij.net...

There is really no reason to do this. In any Maven project you end up
creating a corporate inhouse Maven repository to store third party jars
not available in Maven repositories - this is also done since Maven
repositories tend to be kind of slow.

>

Kind regards
Georges



0

Please sign in to leave a comment.