Using install:install-file or deploy:deploy-file will enable you to
install your "legacy" named jars into the repository format by
passing metadata on the command line.
Though jars may not have the version in their name they still have
metadata or a release number associated with them where this
information will be available.
Andy
On 3 Jul 2007, at 20:56, Harish Kachoria wrote:
I understand.. But the bad thing is backward compatiablty.
Maven 1.0 support tag by which we can avoid version number. and
Maven 2.0
not.
and renaming of legacy jar is not a good idea. Because they are
provided by
third party. and because Maven don't like the name of jar, so
rename the jar
Maven designer should consider the fact that Many of Legacy jars do
not have
version numbers. and Mangement always afraid to touch such jars.
even if it
is a small change.
I think I have to convince for renaming jar on development env.
Wayne Fay wrote:
Your only option (if you want to continue using Maven) is to starting
using versions.
Even if you use scope=system you still need to set a version in the
node. And system scope is just a bad idea in the first
place, generally.
Wayne
On 7/3/07, Harish Kachoria wrote:
OK it works from me.. I created remote repo on my local machine.
and maven downloded the jars stored them in the way he likes.
still I have one problem, my libraries does not have any version
number.
and
version number is mandatory for maven 2.0. ( tag had been removed in
maven 2.0)
so now I have two solution -
- rename all jar with some fake version(may be 1.0) and then
convince
management for this. which I know won't happen
- forget maven. which I don't prefer. (this was my idea to use
maven in
this
project)
so can you find any other solution.
Carlos Sanchez-4 wrote:
you can't change the local repository layout, it's a cache for
maven
and it shouldn't matter how it's stored
you can change the remote repositories layout, so just create a
remote
repo for your projects in whatever style you want, although not a
great idea
On 7/3/07, Harish Kachoria wrote:
It would be better if I can explain my problem then you can
suggest me
some
solution
Currently I have one project which has around 30+sub projects
(Which I
can
say modules)
Each sub project has its own ear which contains 1 war module
and 1 ejb
module.
There are some common libraries also which are shared accros the
projects.
In development env we copy this library at local location and
use them
from
JBuilder.
In production env, many ears are deployed (this project as well as
other
projects) and all common libraries are in server lib folder.
now I want to build one sub project using maven. and I need to
refer
all
common libraries just for compilations (as we never include common
library
in EAR)
To use maven I need to define dependancy and needs to copy common
library
in
repo.
I wants to copy all jars in one folder of repo and trying to
use it
but
with
Maven 2.0 it seems to be not possible.
If you have any alternate way then please let me know
--
View this message in context:
http://www.nabble.com/how-to-configure-Default-Repository-Layout-
for-local-repository-tf4018468s177.html#a11417704
Sent from the Maven - Users mailing list archive at Nabble.com.
------------------------------------------------------------------
---
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
-------------------------------------------------------------------
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/how-to-configure-Default-Repository-Layout-
for-local-repository-tf4018468s177.html#a11418660
Sent from the Maven - Users mailing list archive at Nabble.com.
--------------------------------------------------------------------
-
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]
:arguing::arguing::arguing::arguing::arguing::arguing::arguing:
--
View this message in context: http://www.nabble.com/how-to-
configure-Default-Repository-Layout-for-local-repository-
tf4018468s177.html#a11419527
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
