Er hrm, I'm not sure why this sent again, but ignore it. Question already
answered, thanks!
Matt
On May 30, 2014 at 4:39 PM Matt Whiteman wrote:
> Hi,
>
>
>
> This has probably been answered before, but I haven't been able to find the
> answer and I'm hoping someone knows.
>
>
>
> I'm writing se
Hi,
This has probably been answered before, but I haven't been able to find the
answer and I'm hoping someone knows.
I'm writing several apps that talk to a Microsoft SQL database, so I'm using
the Hibernate dependency. Since Microsoft doesn't make the sqljdbc4 jar
available on Maven, I've
> so that I can do everything right. What I had been trying to do in the
> meantime
> is having it set up
> so that when we set up a new development station, the user can simply clone
> the
> Github repo that
> has these dependency projects and just do 'mvn install' on each one, then
> build
Ar
The install-file is the way to go and it will be successful as soon as your
work on your machine.
If you want to distributed setup, then you must upload the JAR to a
repository manager or install it on a shared maven repository and use that
remote maven repository in your POM files
Jeff
On Sat,
I understand but you can't achieve this using a project to represent a
pre-existing jar. Your attempt won't work. The "install-file" command is
the correct solution; that is how you get it into your local repo without
downloading it from a remote repo.
On May 30, 2014 4:36 PM, "Matt Whiteman"
wrot
Hi Curtis,
I'll take a look at that, thanks! Ideally, I'll eventually be able to have an
internal Maven repository
so that I can do everything right. What I had been trying to do in the meantime
is having it set up
so that when we set up a new development station, the user can simply clone the
Git
I don't think you should make a project for your sql jar. My guess is when
you build+install that, you're creating an empty and useless jar file and
overwriting the good one you already placed in your local repo. The
mvn:install:install-file thing works and is what I would expect as the
answer.
C
Hi Matt,
Have you seen this article?
http://developer-blog.cloudbees.com/2013/03/playing-trade-offs-with-maven.html
If you cannot deploy the Microsoft JARs to your own internal Maven
repository, then you could try the non-maven-jar-plugin approach. It is
strongly recommended over the "basedir rep
Hi,
This has probably been answered before, but I haven't been able to find the
answer and I'm hoping someone knows.
I'm writing several apps that talk to a Microsoft SQL database, so I'm using
the Hibernate dependency. Since Microsoft doesn't make the sqljdbc4 jar
available on Maven, I've
