ApacheCon is now less than a month away!
Dear Apache Enthusiast, ApacheCon Sevilla is now less than a month out, and we need your help getting the word out. Please tell your colleagues, your friends, and members of related technical communities, about this event. Rates go up November 3rd, so register today! ApacheCon, and Apache Big Data, are the official gatherings of the Apache Software Foundation, and one of the best places in the world to meet other members of your project community, gain deeper knowledge about your favorite Apache projects, learn about the ASF. Your project doesn't live in a vacuum - it's part of a larger family of projects that have a shared set of values, as well as a shared governance model. And many of our project have an overlap in developers, in communities, and in subject matter, making ApacheCon a great place for cross-pollination of ideas and of communities. Some highlights of these events will be: * Many of our board members and project chairs will be present * The lightning talks are a great place to hear, and give, short presentations about what you and other members of the community are working on * The key signing gets you linked into the web of trust, and better able to verify our software releases * Evening receptions and parties where you can meet community members in a less formal setting * The State of the Feather, where you can learn what the ASF has done in the last year, and what's coming next year * BarCampApache, an informal unconference-style event, is another venue for discussing your projects at the ASF We have a great schedule lined up, covering the wide range of ASF projects, including: * CI and CD at Scale: Scaling Jenkins with Docker and Apache Mesos - Carlos Sanchez * Inner sourcing 101 - Jim Jagielski * Java Memory Leaks in Modular Environments - Mark Thomas ApacheCon/Apache Big Data will be held in Sevilla, Spain, at the Melia Sevilla, November 14th through 18th. You can find out more at http://apachecon.com/ Other ways to stay up to date with ApacheCon are: * Follow us on Twitter at @apachecon * Join us on IRC, at #apachecon on the Freenode IRC network * Join the apachecon-discuss mailing list by sending email to apachecon-discuss-subscr...@apache.org * Or contact me directly at rbo...@apache.org with questions, comments, or to volunteer to help See you in Sevilla! -- Rich Bowen: VP, Conferences rbo...@apache.org http://apachecon.com/ @apachecon - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to filter dependency:tree
Hi, Elliot Huntington wrote: > Hi, > > I work for a company that produces hundreds of artifacts which depend on > each other. I'm trying to use `dependency:tree` to create a graph (with > graphviz) to better understand the relationships of these artifacts. The > problem I'm running into is that the graph is so large it is almost > useless. I would like to filter the results such that only dependencies > from my companies base group id are included in the graph. [snip] maybe you should have a look first at this: https://github.com/batmat/overview-maven-plugin Cheers, Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to filter dependency:tree
Hi, I work for a company that produces hundreds of artifacts which depend on each other. I'm trying to use `dependency:tree` to create a graph (with graphviz) to better understand the relationships of these artifacts. The problem I'm running into is that the graph is so large it is almost useless. I would like to filter the results such that only dependencies from my companies base group id are included in the graph. Assume that all artifacts produced by our company contain the base group id of `com.foo.bar.*`. Here is what I am trying: mvn dependency:tree -DexcludeScope=test -DexcludeTransitive=true -DexcludeGroupIds=* -DincludeGroupIds=com.foo.bar.* -DappendOutput=true -DoutputType=dot -DoutputFile=dependency-graph.gv Using this command I would expect the results to only include explicitly declared dependencies in pom.xml whose group id matches the `com.foo.bar.*` group id. But instead the graph still contains other dependencies such as `org.mockito:mockit-core:jar:1.9.5:test`. In fact, all the dependencies included in the graph are `test` scoped. How can I use the maven-dependency-plugin to generate a graph of a project's first level, explicitly declared, dependencies, filtered to only include dependencies whose group id matches some regular expression? I asked this question on StackOverflow if you would like to answer there instead. http://stackoverflow.com/questions/40137300/graph-project-dependencies-including-only-company-artifacts
Re: Comparing specifying repositories in pom vs. settings.xml?
Our experience is that the not-central repos aren't reliable over the medium term. So, if we can't get it to go to central, we copy it into our own copy of Nexus. This is, of course, not a helpful strategy for anything that has to be maintained 'out in the open'. On Wed, Oct 19, 2016 at 11:16 AM, KARR, DAVID wrote: >> -Original Message- >> From: Mark H. Wood [mailto:mw...@iupui.edu] >> Sent: Wednesday, October 19, 2016 5:55 AM >> To: users@maven.apache.org >> Subject: Re: Comparing specifying repositories in pom vs. settings.xml? >> >> OK, I'm going to learn a lot from this thread. >> >> On Tue, Oct 18, 2016 at 06:57:42AM -0700, Robert Patrick wrote: >> > But in a large corporate environment, the centralized repository >> manager can house hundreds/thousands of repositories so unless you want >> to virtualize the entire set of repositories (which tends to make the >> repository manager slower), you still need to specify the repositories >> to search, right? >> >> We have a local Nexus instance, and besides a mirror of Central and a >> couple of others, there are just two non-mirror repositories: >> local-snapshots and local-releases. Why would you have more than these? > > Our "Nexus instance" maintains artifacts for a very large number of projects, > most of which are managed by different teams that prefer, and often require > (by NDA, et cetera), to keep their artifacts separate from the artifacts from > other projects. It's not unusual for some people to work on different sets > of projects, requiring different sets of repositories. > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Comparing specifying repositories in pom vs. settings.xml?
> -Original Message- > From: Mark H. Wood [mailto:mw...@iupui.edu] > Sent: Wednesday, October 19, 2016 5:55 AM > To: users@maven.apache.org > Subject: Re: Comparing specifying repositories in pom vs. settings.xml? > > OK, I'm going to learn a lot from this thread. > > On Tue, Oct 18, 2016 at 06:57:42AM -0700, Robert Patrick wrote: > > But in a large corporate environment, the centralized repository > manager can house hundreds/thousands of repositories so unless you want > to virtualize the entire set of repositories (which tends to make the > repository manager slower), you still need to specify the repositories > to search, right? > > We have a local Nexus instance, and besides a mirror of Central and a > couple of others, there are just two non-mirror repositories: > local-snapshots and local-releases. Why would you have more than these? Our "Nexus instance" maintains artifacts for a very large number of projects, most of which are managed by different teams that prefer, and often require (by NDA, et cetera), to keep their artifacts separate from the artifacts from other projects. It's not unusual for some people to work on different sets of projects, requiring different sets of repositories. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven build broken with jdk1.8
Hi: Good morning. You are right. I forgot to clean and install a common build. After I did that using jdk1.8, the errors for snapshot went away. Now, the apache FOP is upset. These are software errors nothing to do with maven at all. I need to refactor all the org.apache.xmlgraphics usages for using the latest version FOP2.1 ... Thanks for listening to me and helping me narrow down the error and replying to my message, Gopal -- View this message in context: http://maven.40175.n5.nabble.com/maven-build-broken-with-jdk1-8-tp5883777p5883917.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Comparing specifying repositories in pom vs. settings.xml?
OK, I'm going to learn a lot from this thread. On Tue, Oct 18, 2016 at 06:57:42AM -0700, Robert Patrick wrote: > But in a large corporate environment, the centralized repository manager can > house hundreds/thousands of repositories so unless you want to virtualize the > entire set of repositories (which tends to make the repository manager > slower), you still need to specify the repositories to search, right? We have a local Nexus instance, and besides a mirror of Central and a couple of others, there are just two non-mirror repositories: local-snapshots and local-releases. Why would you have more than these? -- Mark H. Wood Lead Technology Analyst University Library Indiana University - Purdue University Indianapolis 755 W. Michigan Street Indianapolis, IN 46202 317-274-0749 www.ulib.iupui.edu signature.asc Description: PGP signature