It's a widely-used tool which goes out to various internet sites and downloads the software necessary to support things.
The first picture in the tutorial you linked to contains the XML file which Maven would use. I suppose that since the tutorial didn't specifically say to do anything with that, you're justified in ignoring it completely and claiming that you followed the tutorial "to the letter".
I would suggest finding a different tutorial. Learning Maven just so that you can complete this step is, I think, far too much of a diversion.
I need to make sure we all know what we're actually talking about here.
When you say "use a Connection Pool", we normally expect that means that you're going to be working with a multi-user system such as a webserver where your actual application will be a Connection Pool client.
But the code sample is what I'd expect to see if you were trying to implement a Connection Pool [bserver.[/b] Which would generally be built as a JAR ibrary to be either plugged into a framework that supports Connection Pools or as part of a stand-alone Pool Client application (which isn't often done).
To be a Connection Pool client as a web application, you don't need any Apache code. You just need the javax.sql.DataSource interface which is part of the J2EE and JEE implementations and a way to locate that DataSource implementation, which is usually via a JNDI lookup. The Connection Pool itself is a plug-in component to the webapp server, and generally one will already have been bundled as part of the webapp server.
If you actually are attempting to define a wholly new Connection Pool librarty we'd need to know more about what it was expected to do that none of the ready-made Connection Pool implementations don't do.
"privilege" comes from the Latin words for "private" and "law" (legal) and dates to feudal times. To "claim privilege" meant that you were above the laws that applied to the common people.
Stephan van Hulst wrote:I agree that it looks like a poor tutorial, but on the other hand I also believe Maven should be standard knowledge for any Java programmer who is at the level of using connection pools.
IF Yosuf Ibrahim doesn't have to rush to finish this task, now is as good a time as any to learn Maven.
I suppose that's right too. When I installed a connection pool (in March 2019) I chose c3p0, which didn't have any external dependencies and which documented what jar files needed to go in your classpath. So I didn't need Maven, which was fortunate because I've never used it. But when I upgraded my version of Apache POI (in March 2020) there were a lot of external dependencies which I had to track down the hard way, and knowing Maven would have been useful then.
(In other words: you can see my bias regarding Maven.)
I will suppress my every urge. But not this shameless plug: