ya I think we also need to manage our dependdancy in same way.
But one thing worried me the Version number.
Some of my third party jars do not have version number. and I think I have
to rename them by some version number.
That I can do on development env but for production I need to convince man
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:
>>
&g
> 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
>
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 a
can see all jar of group in one
directory.
Max O Bowsher wrote:
>
> Harish Kachoria wrote:
>> I mean to say, If I wants to use maven then I have to use in this way, I
>> have
>> to maintain version, but for my project maintaing of version is not a
>> problem. and
using Maven1. But I really
> don't know why you care how Maven "internally" handles its own local
> repository.
>
> You can only configure the layout for "legacy" when dealing with
> remote repos ie corporate repo, snapshot repo, etc.
>
> Wayne
>
>
I mean to say, If I wants to use maven then I have to use in this way, I have
to maintain version, but for my project maintaing of version is not a
problem. and Management won't like Idea to have directory for each module.
So if Maven is enough flexible then adoptation in any project becomes ver
y layout"
> you will find all the documentation you could possibly need.
>
> Wayne
>
> On 7/3/07, Harish Kachoria <[EMAIL PROTECTED]> wrote:
>>
>> Thanks Wayne
>>
>> Can you please give me the sytax for this. I tried various systax but it
>>
y to legacy as well with "mvn deploy:deploy-file
> -DrepositoryLayout=legacy".
>
> So if you really believe the M1 layout is better, you can keep using it.
>
> Wayne
>
> On 7/3/07, Harish Kachoria <[EMAIL PROTECTED]> wrote:
>>
>> I can use that comman
Thanks,
But still is there any way in maven 2.0 by which I can put all jar of a
group at one place. (not in different different directory)
I don't like directory structure which is just over burden for maintaince.
As of now we do not have any problems to maintain version of our jars.
But because
I can use that command but presently I have almost more then 30 jar files.
and
First It is bad idea to run same command for all this jar.
Second this structure will create 30 different folder in my repository which
I think a burden to maintain.
I like the maven 1.0 layout in which I can put all m
Default layout of maven 2.0 is a burden for me. as I have many jar with same
group and if I need to use default layour of Maven 2.0 then I need to create
seprate directory for each jar.
So please help me to configure legacy layout for local repository.
I tried to configure it but could not suce
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 suggest me
Best Regards
Haris
13 matches
Mail list logo
