aspose file tools*
The moose likes Ant, Maven and Other Build Tools and the fly likes Software Development/Maven/Eclipse Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » Ant, Maven and Other Build Tools
Bookmark "Software Development/Maven/Eclipse" Watch "Software Development/Maven/Eclipse" New topic
Author

Software Development/Maven/Eclipse

t corey
Greenhorn

Joined: Dec 15, 2011
Posts: 2
Hello,

Can some folks give real life stories about how maven is used from start to releasing a product to production? I'm not looking for full details but a high level description of some real policies and procedures used by companies that have Maven.

Thanks.

--tc
t corey
Greenhorn

Joined: Dec 15, 2011
Posts: 2
Hello,

I found a detailed description here, Maven in our development process
Peter Johnson
author
Bartender

Joined: May 14, 2008
Posts: 5845
    
    7

Some points:

* Make sure your IDE has a plugin that supports Maven and use it.

* Set up a remote repository on one of your servers using Nexus or Artifactory. Make sure everyone modifies their settings.xml file to reference that repository.

* If you need to access multiple repositories, configure that within Nexus., not within the pom.xml file.

* Make sure all binary artifact sharing is done via Nexus (discourage use of "file shares" for sharing stuff).

* Place binary artifacts that are not available anywhere else into your Nexus repository (that is what the "thirdparty" repository is for).

* Make sure everyone understands basic Maven terminology, and how Maven works.

* Write some plugins. That is the best way I know of to really learn Maven.

* Make extensive use of Maven's capability to generate project web sites.

* Set up a central source code repository (or repositories), even if using git or mercurial.

* Set up Jenkins to do "official" builds from the central source code repository. Only these builds should update the Nexus repository (that is, only Jenkins should run "mvn deploy", developers should never run that, they should do at most "mvn install"). When setting up Jenkins, NEVER set up a developer's machine as a build slave!

As you can see, Maven is only a small, but significant part, of a system that uses multiple programs, each with their own strengths.


JBoss In Action
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Software Development/Maven/Eclipse