I can rename jar in my development env, not a isssue.
Problem is,
We want build scripts in such way so that we can use same build scripts on
dev as well as on production.
and for this purpose I wants to give dependancy of jar in the same way as
they are reffered in production.
and because of th
I know, the material is the same (it maybe should be in the m2 faq
too :)
ie, the answer in m1 is "you can but you shouldn't and here's how to
workaround". In m2, it's "you can't, and here's how to work around".
On 03/07/2007, at 12:34 PM, Ralph Goers wrote:
Brett Porter wrote:
http://
Brett Porter wrote:
http://maven.apache.org/maven-1.x/faq.html#unversioned-jars
You can name that what you wish in build/deployment/production, they
just need a version in the repository.
Brett, He wants to do this in Maven 2, not Maven 1.
Ralph
--
http://maven.apache.org/maven-1.x/faq.html#unversioned-jars
You can name that what you wish in build/deployment/production, they
just need a version in the repository.
On 03/07/2007, at 6:27 AM, Harish Kachoria wrote:
In maven 1.0 we were using tag to define jar dependancy.
which I thin
In maven 1.0 we were using tag to define jar dependancy. which I think
deprecated.
How ever in my current project I'm trying to integrating Maven 2.0 (Before
that we make jar using javac and used it).
Problems which I have -
- I have many jars which are third party/inbuild libraries and which
Lukas Theussl wrote:
No, it's still supported and not deprecated in Maven 1.1:
http://maven.apache.org/maven-1.x/reference/maven-model/3.0.2/maven.html#class_dependency
-Lukas
It should have been. I can certainly understand why support for this was
removed in version 2.
Ralph
-
No, it's still supported and not deprecated in Maven 1.1:
http://maven.apache.org/maven-1.x/reference/maven-model/3.0.2/maven.html#class_dependency
-Lukas
Brett Porter wrote:
Probably referring to the tag which let you hack the repository
path. It's forbidden in Maven 2 (and was deprecated
Probably referring to the tag which let you hack the repository
path. It's forbidden in Maven 2 (and was deprecated in 1.1 too I think?)
- Brett
On 02/07/2007, at 5:39 PM, Stephane Nicoll wrote:
On 7/2/07, Ralph Goers <[EMAIL PROTECTED]> wrote:
Harish Kachoria wrote:
I'm really curious as
On 7/2/07, Ralph Goers <[EMAIL PROTECTED]> wrote:
Harish Kachoria wrote:
I'm really curious as to how you got that to work in maven 1.0? AFAIK
version numbers have always been required.
+1
Stéphane
Ralph
-
To unsubscribe, e
Harish Kachoria wrote:
Hello All,
I'm trying to integrating Maven in my project.
I was quite comfortable using maven 1.0.
But with Maven 2.0 I have one problem to define dependency of a jar file.
I wants to define dependency without having a version number. how can
I do
that ??
Please sugg
You must declare a version number. You can either define it in a parent
pom using dependencyManagement, or you could try specifying a range of
allowed values. Either way, something must be defined.
-Original Message-
From: Harish Kachoria [mailto:[EMAIL PROTECTED]
Sent: Friday, June 29, 2
11 matches
Mail list logo
