Hi Henrique,
On 19/04/2008, at 6:52 AM, Henrique Prange wrote:
It is not recommended that you store your jars in SVN. So, there is
no simple way to do what you want with Maven.
Recommended or not - I simply cannot go another route. The project
needs to be self-contained which requires another developer to check
it out via svn without any further hassles. Similarly a build server
needs to be able to svn up && build...
Putting it in my local repository seems kind of pointless as it's not
in subversion and the project will fail to build elsewhere. It also
seems to assume that the repo is publicly available (or at least on
vpn).
This seems more like a philosophical limitation, if I can put it that
way :-)
i.e., it seems to me that there's nothing technically difficult for
maven to support this:
<dependency>
<systemPath>...</systemPath>
</dependency>
i.e., where artifactId, groupId, and version are optional if the
systemPath is supplied - seeing as it's kind of redundant when
systemPath is supplied as far as I can see.
But you can create a repository to share your own libraries (Maven
can generate the pom.xml for you). Take a look at [1] and [2].
[1]http://maven.apache.org/guides/introduction/introduction-to-repositories.html
[2]http://maven.apache.org/guides/mini/guide-3rd-party-jars-
remote.html
Thanks for those links. I had already seen the first and a variation
on the 2nd... perhaps I can create a local repo for that framework
with the localRepositoryPath etc options
http://maven.apache.org/plugins/maven-install-plugin/install-file-mojo.html
Seems like it's a bit over the top - but if it works then that's Good
Enough For Now(tm).
Cheers from your WO friend, ;)
:-)
Henrique
Lachlan Deck wrote:
Hi there,
I'm quite new to maven, but I would have thought this question
would have been included on the FAQ page for maven - but it's not.
I've googled around but mustn't be putting in the right search
phrase or something... as obviously I've not found the answer :-)
The simple question is how do I define dependencies on libs/*.jar
for one of my projects where I have jars from a 3rd party (a
payment gateway) in the project's lib folder. These libs live in
svn with the project - not in a repo (and don't have a version or a
pom of their own - they're just libs).
i.e., they obviously need to be on the classpath + packaged with
the final jar?
I'm sure it's something simple... thanks in advance.
with regards,
--
Lachlan Deck
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
with regards,
--
Lachlan Deck
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]