Hello Alexander!
When I modified the build generation script to make it possible to update
Java Web Start without downloading all jar files but only those that were
actually changed, I chose the maven repository layout for the jar files. A
few months back, someone complained that there were no pom-files and I fixed
that then.
This means that we already have a repository in place where all jar files
are available with simple pom-files and the release script adds all jars
that belong to a release to that repository.
I hope, but I am not sure, that this can be useful if we should take the
step to use Maven in the builds.
After some struggling with the nightly build and the old tools used there, I
thought that moving to maven would be a good thing but I am also concerned
that it will be a lot of work without any user benefit and I don't know
enough about maven.
/Linus
On Mon, Apr 19, 2010 at 2:12 PM, Alexander Lepekhine <[email protected]>wrote:
> Recently I became the adherent of maven - the project building tool which
> substitutes ant. Maven uses declarative project description and greatly
> facilitate project dependency management. Has it sense to move argouml
> itself and modules projects under maven?
> The single problem I see is to have a repository where we shall store our
> artifacts. If somebody (Linus?) provides us with the repository I can do
> this job.
>
> ------------------------------------------------------
>
> http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2589165
>
> To unsubscribe from this discussion, e-mail: [
> [email protected]].
> To be allowed to post to the list contact the mailing list moderator,
> email: [[email protected]]
>
------------------------------------------------------
http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2589349
To unsubscribe from this discussion, e-mail:
[[email protected]].
To be allowed to post to the list contact the mailing list moderator, email:
[[email protected]]
