You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Zilvinas Vilutis <ci...@gmail.com> on 2011/02/16 17:46:44 UTC
subversion vs maven
Hello Maven Users!
Probably this question was already asked, so if there is an answer
which I could not find - please point me to the right place.
I'm working on an enterprise project where maven integration plays a huge role.
However the project is big as a lot of teams are working on it and it
takes quite some time to build it ( 30-40 minutes ), which I need to
do every morning after an svn update.
So I was thinking - is there any way to configure maven to build only
the projects which were updated by SVN ( e.g. in the script time )?
Most likely there is no direct answer...however, I think that I could
find a way to gather the project names which were updated in the shell
script - then I could pass the list of project names to maven command.
Is there any way to make sure that those and dependent projects would
be built in the right order?
The project structure is:
parent
-- subsystem1
-- s1-project1
-- s1-project2
-- subsystem2
-- s2-project1
-- s2-project2
-- s2-project3
-- subsystem3
-- s3-project1
Thank you for any ideas!
Žilvinas Vilutis
Mobile: (+370) 652 38353
E-mail: cikasfm@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: subversion vs maven
Posted by "Yanko, Curtis" <cu...@uhc.com>.
This is what Build Management Servers can do for you. It could poll each project each morning and only build the ones that have changes.
________________________________
Curt Yanko | Continuous Integration Services | UnitedHealth Group IT
Making IT Happen, one build at a time, 600 times a day
> -----Original Message-----
> From: Zilvinas Vilutis [mailto:cikasfm@gmail.com]
> Sent: Wednesday, February 16, 2011 11:47 AM
> To: users@maven.apache.org
> Subject: subversion vs maven
>
> Hello Maven Users!
>
> Probably this question was already asked, so if there is an
> answer which I could not find - please point me to the right place.
>
>
> I'm working on an enterprise project where maven integration
> plays a huge role.
>
> However the project is big as a lot of teams are working on
> it and it takes quite some time to build it ( 30-40 minutes
> ), which I need to do every morning after an svn update.
>
>
> So I was thinking - is there any way to configure maven to
> build only the projects which were updated by SVN ( e.g. in
> the script time )?
>
>
> Most likely there is no direct answer...however, I think that
> I could find a way to gather the project names which were
> updated in the shell script - then I could pass the list of
> project names to maven command.
> Is there any way to make sure that those and dependent
> projects would be built in the right order?
>
>
> The project structure is:
>
> parent
> -- subsystem1
> -- s1-project1
> -- s1-project2
> -- subsystem2
> -- s2-project1
> -- s2-project2
> -- s2-project3
> -- subsystem3
> -- s3-project1
>
>
> Thank you for any ideas!
>
>
> Žilvinas Vilutis
>
> Mobile: (+370) 652 38353
> E-mail: cikasfm@gmail.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: subversion vs maven
Posted by "a.geo" <aq...@gmail.com>.
You first need analyze the change level in every component, maybe split a
project in more subprojects, so the 'static' code could be managed like a
external library, this is, compile it and upload to Maven Proxy, and the
changeable code only get from subversion.
2011/2/16 Leon Rosenberg <ro...@gmail.com>
> How about hudson?
>
> Hudson can watch for svn changes and trigger builds on commit.
>
> regards
> Leon
>
> On Wed, Feb 16, 2011 at 5:46 PM, Zilvinas Vilutis <ci...@gmail.com>
> wrote:
> > Hello Maven Users!
> >
> > Probably this question was already asked, so if there is an answer
> > which I could not find - please point me to the right place.
> >
> >
> > I'm working on an enterprise project where maven integration plays a huge
> role.
> >
> > However the project is big as a lot of teams are working on it and it
> > takes quite some time to build it ( 30-40 minutes ), which I need to
> > do every morning after an svn update.
> >
> >
> > So I was thinking - is there any way to configure maven to build only
> > the projects which were updated by SVN ( e.g. in the script time )?
> >
> >
> > Most likely there is no direct answer...however, I think that I could
> > find a way to gather the project names which were updated in the shell
> > script - then I could pass the list of project names to maven command.
> > Is there any way to make sure that those and dependent projects would
> > be built in the right order?
> >
> >
> > The project structure is:
> >
> > parent
> > -- subsystem1
> > -- s1-project1
> > -- s1-project2
> > -- subsystem2
> > -- s2-project1
> > -- s2-project2
> > -- s2-project3
> > -- subsystem3
> > -- s3-project1
> >
> >
> > Thank you for any ideas!
> >
> >
> > Žilvinas Vilutis
> >
> > Mobile: (+370) 652 38353
> > E-mail: cikasfm@gmail.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Cesar De la Cruz Rojas
*
-----------------------------------------------------------------------------
*
Sennior Software Engineer
-----------------------------------------------------------------------------
Follow me in Facebook : http://www.facebook.com/aquiles.geo
Twitter http://twitter.com/ageo
Picture blog http://ageo.deviantart.com
AW: subversion vs maven
Posted by "Moser, Christian" <cm...@metrohm.com>.
"..takes quite some time to build it ( 30-40 minutes ), which I need to
do every morning after an svn update."
I'm not sure why do you think that it's necessary to build the whole project locally every morning? After a commit, a maven project should be deployed as SNAPSHOT version into the remote repository.
It would recommend to do an svn update on the project root and calling "mvn -U initialize dependency:sources" on your project parent (s?) or a pom which contains all required dependencies (starter pom?) for the whole project. This call should resolve all newer available snapshot dependencies from the remote repository in no time.
I hope this help,
- Chris
-----Ursprüngliche Nachricht-----
Von: Stadelmann Josef [mailto:josef.stadelmann@axa-winterthur.ch]
Gesendet: Dienstag, 22. Februar 2011 11:03
An: Maven Users List
Betreff: AW: subversion vs maven
I would consider this as either a) "bad dependencies" or b) "bad dependency management"
And I woul NOT and never ever expect that from a modern build system like maven.
Josef
-----Ursprüngliche Nachricht-----
Von: Jeff [mailto:predatorvi@gmail.com]
Gesendet: Mittwoch, 16. Februar 2011 18:28
An: Maven Users List; cikasfm@gmail.com
Betreff: Re: subversion vs maven
Maybe this question will expose my ignorance, but I thought most build
systems only build the things that have changed unless you do a "clean" each
time or are starting from a fresh checkout as opposed to doing an "svn
update" and then running the build.
Being new to Maven myself, there could there be an option in the POM that
might be forcing a full build each time?
I would think that as long as you aren't specifying "clean" in your build
kickoff process or otherwise forcing a full biuld, you should only be
getting the incremental build, no? Am I off in my understanding?
On Wed, Feb 16, 2011 at 10:18 AM, Zilvinas Vilutis <ci...@gmail.com>wrote:
> Yes,
>
> However it does a "full build" which takes ~30-40 minutes. But I want
> to build only specific projects and their dependents.
>
> Regards
>
> Žilvinas Vilutis
>
> Mobile: (+370) 652 38353
> E-mail: cikasfm@gmail.com
>
>
>
> On Wed, Feb 16, 2011 at 9:54 AM, Leon Rosenberg
> <ro...@gmail.com> wrote:
> > How about hudson?
> >
> > Hudson can watch for svn changes and trigger builds on commit.
> >
> > regards
> > Leon
> >
> > On Wed, Feb 16, 2011 at 5:46 PM, Zilvinas Vilutis <ci...@gmail.com>
> wrote:
> >> Hello Maven Users!
> >>
> >> Probably this question was already asked, so if there is an answer
> >> which I could not find - please point me to the right place.
> >>
> >>
> >> I'm working on an enterprise project where maven integration plays a
> huge role.
> >>
> >> However the project is big as a lot of teams are working on it and it
> >> takes quite some time to build it ( 30-40 minutes ), which I need to
> >> do every morning after an svn update.
> >>
> >>
> >> So I was thinking - is there any way to configure maven to build only
> >> the projects which were updated by SVN ( e.g. in the script time )?
> >>
> >>
> >> Most likely there is no direct answer...however, I think that I could
> >> find a way to gather the project names which were updated in the shell
> >> script - then I could pass the list of project names to maven command.
> >> Is there any way to make sure that those and dependent projects would
> >> be built in the right order?
> >>
> >>
> >> The project structure is:
> >>
> >> parent
> >> -- subsystem1
> >> -- s1-project1
> >> -- s1-project2
> >> -- subsystem2
> >> -- s2-project1
> >> -- s2-project2
> >> -- s2-project3
> >> -- subsystem3
> >> -- s3-project1
> >>
> >>
> >> Thank you for any ideas!
> >>
> >>
> >> Žilvinas Vilutis
> >>
> >> Mobile: (+370) 652 38353
> >> E-mail: cikasfm@gmail.com
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Jeff Vincent
predatorvi@gmail.com
See my LinkedIn profile at:
http://www.linkedin.com/in/rjeffreyvincent
AW: subversion vs maven
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
I would consider this as either a) "bad dependencies" or b) "bad dependency management"
And I woul NOT and never ever expect that from a modern build system like maven.
Josef
-----Ursprüngliche Nachricht-----
Von: Jeff [mailto:predatorvi@gmail.com]
Gesendet: Mittwoch, 16. Februar 2011 18:28
An: Maven Users List; cikasfm@gmail.com
Betreff: Re: subversion vs maven
Maybe this question will expose my ignorance, but I thought most build
systems only build the things that have changed unless you do a "clean" each
time or are starting from a fresh checkout as opposed to doing an "svn
update" and then running the build.
Being new to Maven myself, there could there be an option in the POM that
might be forcing a full build each time?
I would think that as long as you aren't specifying "clean" in your build
kickoff process or otherwise forcing a full biuld, you should only be
getting the incremental build, no? Am I off in my understanding?
On Wed, Feb 16, 2011 at 10:18 AM, Zilvinas Vilutis <ci...@gmail.com>wrote:
> Yes,
>
> However it does a "full build" which takes ~30-40 minutes. But I want
> to build only specific projects and their dependents.
>
> Regards
>
> Žilvinas Vilutis
>
> Mobile: (+370) 652 38353
> E-mail: cikasfm@gmail.com
>
>
>
> On Wed, Feb 16, 2011 at 9:54 AM, Leon Rosenberg
> <ro...@gmail.com> wrote:
> > How about hudson?
> >
> > Hudson can watch for svn changes and trigger builds on commit.
> >
> > regards
> > Leon
> >
> > On Wed, Feb 16, 2011 at 5:46 PM, Zilvinas Vilutis <ci...@gmail.com>
> wrote:
> >> Hello Maven Users!
> >>
> >> Probably this question was already asked, so if there is an answer
> >> which I could not find - please point me to the right place.
> >>
> >>
> >> I'm working on an enterprise project where maven integration plays a
> huge role.
> >>
> >> However the project is big as a lot of teams are working on it and it
> >> takes quite some time to build it ( 30-40 minutes ), which I need to
> >> do every morning after an svn update.
> >>
> >>
> >> So I was thinking - is there any way to configure maven to build only
> >> the projects which were updated by SVN ( e.g. in the script time )?
> >>
> >>
> >> Most likely there is no direct answer...however, I think that I could
> >> find a way to gather the project names which were updated in the shell
> >> script - then I could pass the list of project names to maven command.
> >> Is there any way to make sure that those and dependent projects would
> >> be built in the right order?
> >>
> >>
> >> The project structure is:
> >>
> >> parent
> >> -- subsystem1
> >> -- s1-project1
> >> -- s1-project2
> >> -- subsystem2
> >> -- s2-project1
> >> -- s2-project2
> >> -- s2-project3
> >> -- subsystem3
> >> -- s3-project1
> >>
> >>
> >> Thank you for any ideas!
> >>
> >>
> >> Žilvinas Vilutis
> >>
> >> Mobile: (+370) 652 38353
> >> E-mail: cikasfm@gmail.com
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Jeff Vincent
predatorvi@gmail.com
See my LinkedIn profile at:
http://www.linkedin.com/in/rjeffreyvincent
Re: subversion vs maven
Posted by Zilvinas Vilutis <ci...@gmail.com>.
> This sounds like you need to do more svn updates on projects you are working on. My suggestion would be to do that SVN update on those projects, resolve any conflicts, and then run the maven install. This will make your version into the latest in your repository.
That's what I do every morning before starting work, as I've wrote in
the original e-mail. I'm in a different timezone from other teams, so
I don't really need updating more often.
I do SVN update, resolve conflicts & run the full build to make sure
that all dependencies are built, that they compile and that all
changes are added to the webapp ( war ).
However, doing an SVN update does not let me avoid doing the full build :)
I mean, yes when you're working on 2-3 projects at the same time -
then yes, it is easy to update them manually from time to time. But
when during SVN updates you get updates which require updates from
other projects and you don't know which ones - then a "full build" is
required, or at least "full SVN update" and then building all the
updated projects, installing to your local repo and building the app
war.
Yes, it is possible to build them manually, and copy to your app
manually to save time, but it would take like 10-15 minutes to do that
for ~5 projects, instead of that I'm looking for an automated solution
which would do the job in 15 minutes for me, so I could drink coffee
during that time :)
Žilvinas Vilutis
Mobile: (+370) 652 38353
E-mail: cikasfm@gmail.com
On Wed, Feb 16, 2011 at 1:54 PM, Collins, Russell
<rc...@corelogic.com> wrote:
> This sounds like you need to do more svn updates on projects you are working on. My suggestion would be to do that SVN update on those projects, resolve any conflicts, and then run the maven install. This will make your version into the latest in your repository.
>
> It may also help if you checked in your code a little quicker. You might be letting your code get to far out of sync.
>
>
> Russell Collins
> Sr. Software Engineer
> CoreLogic Spatial Solutions
>
> "Do or do not, there is no try." - Yoda
>
> -----Original Message-----
> From: Zilvinas Vilutis [mailto:cikasfm@gmail.com]
> Sent: Wednesday, February 16, 2011 2:41 PM
> To: Maven Users List
> Cc: Thiessen, Todd (Todd)
> Subject: Re: subversion vs maven
>
>> You don't need to do a full build AND you will only be using artifacts in your local repository. Sounds like its exactly what you want.
> Exactly :) When doing it incrementally - that's how it should work
> when building only "changed" projects and their dependents, what the
> original question was
>
>> So when you get in in the morning, issue a mvn -U install on your module,
>> and you will get latest artifacts installed to your local repo (don't have to
>> do a full build). For the rest of the day, do a mvn install to do your module
>> builds and snapshots won't get updated."
> Yeah, this sounds good when working in a dev environment.
>
> However I'm "on my own" in the customers' office where network latency
> is not enough to download the artifacts quickly.
>
> Anyways, in this case - if I changed my code yesterday and did not
> commit it to SVN - then the downloaded snapshot would be newer and
> will be put in my webapp's "war". In most cases - other people are
> updating the same projects as I'm working on so they would almost all
> the time match the right projects to be built. And my projects would
> not get built during the "full-build" - they would already exist in my
> local repo so they would be picked up when building the war.
>
> I guess I will try to make the most use of the maven reactor (
> http://docs.codehaus.org/display/MAVEN/Make+Like+Reactor+Mode ) to use
> the "--project-list" ( for specifying updated projects ) and
> "--also-make-dependents" parameters is exactly what I want.
>
> Thank you all for ideas & help!
>
> Žilvinas Vilutis
>
> Mobile: (+370) 652 38353
> E-mail: cikasfm@gmail.com
>
>
>
> On Wed, Feb 16, 2011 at 1:22 PM, Thiessen, Todd (Todd)
> <tt...@avaya.com> wrote:
>> Ok. You should be able to achieve the same result by configuring your settings.xml file to never update snapshots. That way you have more control. When you want to get latest snapshots, issue mvn -U install.
>>
>> You don't need to do a full build AND you will only be using artifacts in your local repository. Sounds like its exactly what you want.
>>
>> So when you get in in the morning, issue a mvn -U install on your module, and you will get latest artifacts installed to your local repo (don't have to do a full build). For the rest of the day, do a mvn install to do your module builds and snapshots won't get updated.
>>
>> Just a thought. Hope it helps.
>>
>>> -----Original Message-----
>>> From: Zilvinas Vilutis [mailto:cikasfm@gmail.com]
>>> Sent: Wednesday, February 16, 2011 3:12 PM
>>> To: Maven Users List
>>> Cc: Thiessen, Todd (Todd)
>>> Subject: Re: subversion vs maven
>>>
>>> Theoretically - yes
>>> Practically - no
>>>
>>> We were using the approach with CI and snapshots from the repo long
>>> time ago, however in a lot of cases we came to a case where the
>>> project does not compile or work as expected when having different
>>> snapshot versions, or takes just a very long time to at least package
>>> the project you're working on, so in the long term to make it quick,
>>> safe and making sure that all my modified but not committed modules
>>> get into the app from my local, not external repo ( in case they're
>>> "older" ) - we just do the build on our boxes.
>>>
>>> Žilvinas Vilutis
>>>
>>> Mobile: (+370) 652 38353
>>> E-mail: cikasfm@gmail.com
>>>
>>>
>>>
>>> 2011/2/16 Thiessen, Todd (Todd) <tt...@avaya.com>:
>>> > You could control your dependencies by checking out which ever
>>> dependencies you care about and ensure you build those as well.
>>> Normally, you would just want the snapshot versions anyway. There is
>>> also a properity in your settings.xml file to instruct maven to never
>>> check for updates. To get latest snapshot artifacts you would have to
>>> issue a mvn -U.
>>> >
>>> > The whole idea here is that you should only every be compiling and
>>> downloading what you need. Let your CI server do the full builds. You
>>> should rarely have to.
>>> >
>>> >> -----Original Message-----
>>> >> From: Zilvinas Vilutis [mailto:cikasfm@gmail.com]
>>> >> Sent: Wednesday, February 16, 2011 1:52 PM
>>> >> To: Maven Users List
>>> >> Cc: Thiessen, Todd (Todd)
>>> >> Subject: Re: subversion vs maven
>>> >>
>>> >> yes, we could set this up.
>>> >>
>>> >> However there's 2 things:
>>> >> - We're working with "SNAPSHOT" versions most of the time with CI you
>>> >> can hardly control when to use YOUR code versus from the repo in a big
>>> >> projcet
>>> >> - I'm working in a client's office and the network latency between our
>>> >> office and clients office would make it slow
>>> >>
>>> >> I could run a CI / Hundson / whatever other build management server on
>>> >> my laptop...but then it would not be quicker then just the full build
>>> >> :)
>>> >>
>>> >> Žilvinas Vilutis
>>> >>
>>> >> Mobile: (+370) 652 38353
>>> >> E-mail: cikasfm@gmail.com
>>> >>
>>> >>
>>> >>
>>> >> On Wed, Feb 16, 2011 at 11:41 AM, Thiessen, Todd (Todd)
>>> >> <tt...@avaya.com> wrote:
>>> >> > If you have a CI server already building everything, why do you need
>>> to
>>> >> build everything every morning? Can't you just checkout only the one
>>> >> module you need to change and build that?
>>> >> >
>>> >> >> -----Original Message-----
>>> >> >> From: Zilvinas Vilutis [mailto:cikasfm@gmail.com]
>>> >> >> Sent: Wednesday, February 16, 2011 1:37 PM
>>> >> >> To: a.geo
>>> >> >> Cc: Maven Users List; Jeff
>>> >> >> Subject: Re: subversion vs maven
>>> >> >>
>>> >> >> trust me, not so easy :)
>>> >> >>
>>> >> >> our project has like 20 subsystems which all have 5-10 sub-
>>> projects.
>>> >> >>
>>> >> >> Our "core" is extracted into a separate dependency maintained by
>>> >> >> another team, it is also managed by maven ( ~30 subsystems, 10-50
>>> >> >> projects each ).
>>> >> >>
>>> >> >> Yes, daily updates happen on 5-10 projects, that is why I don't
>>> want
>>> >> >> to build the "full" build but only the changed projects and their
>>> >> >> dependents ( web apps ).
>>> >> >>
>>> >> >> Žilvinas Vilutis
>>> >> >>
>>> >> >> Mobile: (+370) 652 38353
>>> >> >> E-mail: cikasfm@gmail.com
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >> On Wed, Feb 16, 2011 at 10:37 AM, a.geo <aq...@gmail.com>
>>> wrote:
>>> >> >> > You mus consider a "core" section, that contain your business
>>> main
>>> >> >> code,
>>> >> >> > usually you don't change it. Around it, is the implementation of
>>> the
>>> >> >> > requirement.
>>> >> >> >
>>> >> >> >
>>> >> >> >
>>> >> >> > 2011/2/16 Jeff <pr...@gmail.com>
>>> >> >> >>
>>> >> >> >> Maybe this question will expose my ignorance, but I thought most
>>> >> build
>>> >> >> >> systems only build the things that have changed unless you do a
>>> >> >> "clean"
>>> >> >> >> each
>>> >> >> >> time or are starting from a fresh checkout as opposed to doing
>>> an
>>> >> "svn
>>> >> >> >> update" and then running the build.
>>> >> >> >>
>>> >> >> >> Being new to Maven myself, there could there be an option in the
>>> >> POM
>>> >> >> that
>>> >> >> >> might be forcing a full build each time?
>>> >> >> >>
>>> >> >> >> I would think that as long as you aren't specifying "clean" in
>>> your
>>> >> >> build
>>> >> >> >> kickoff process or otherwise forcing a full biuld, you should
>>> only
>>> >> be
>>> >> >> >> getting the incremental build, no? Am I off in my
>>> understanding?
>>> >> >> >> On Wed, Feb 16, 2011 at 10:18 AM, Zilvinas Vilutis
>>> >> >> >> <ci...@gmail.com>wrote:
>>> >> >> >>
>>> >> >> >> > Yes,
>>> >> >> >> >
>>> >> >> >> > However it does a "full build" which takes ~30-40 minutes. But
>>> I
>>> >> >> want
>>> >> >> >> > to build only specific projects and their dependents.
>>> >> >> >> >
>>> >> >> >> > Regards
>>> >> >> >> >
>>> >> >> >> > Žilvinas Vilutis
>>> >> >> >> >
>>> >> >> >> > Mobile: (+370) 652 38353
>>> >> >> >> > E-mail: cikasfm@gmail.com
>>> >> >> >> >
>>> >> >> >> >
>>> >> >> >> >
>>> >> >> >> > On Wed, Feb 16, 2011 at 9:54 AM, Leon Rosenberg
>>> >> >> >> > <ro...@gmail.com> wrote:
>>> >> >> >> > > How about hudson?
>>> >> >> >> > >
>>> >> >> >> > > Hudson can watch for svn changes and trigger builds on
>>> commit.
>>> >> >> >> > >
>>> >> >> >> > > regards
>>> >> >> >> > > Leon
>>> >> >> >> > >
>>> >> >> >> > > On Wed, Feb 16, 2011 at 5:46 PM, Zilvinas Vilutis
>>> >> >> <ci...@gmail.com>
>>> >> >> >> > wrote:
>>> >> >> >> > >> Hello Maven Users!
>>> >> >> >> > >>
>>> >> >> >> > >> Probably this question was already asked, so if there is an
>>> >> >> answer
>>> >> >> >> > >> which I could not find - please point me to the right
>>> place.
>>> >> >> >> > >>
>>> >> >> >> > >>
>>> >> >> >> > >> I'm working on an enterprise project where maven
>>> integration
>>> >> >> plays a
>>> >> >> >> > huge role.
>>> >> >> >> > >>
>>> >> >> >> > >> However the project is big as a lot of teams are working on
>>> it
>>> >> >> and it
>>> >> >> >> > >> takes quite some time to build it ( 30-40 minutes ), which
>>> I
>>> >> need
>>> >> >> to
>>> >> >> >> > >> do every morning after an svn update.
>>> >> >> >> > >>
>>> >> >> >> > >>
>>> >> >> >> > >> So I was thinking - is there any way to configure maven to
>>> >> build
>>> >> >> only
>>> >> >> >> > >> the projects which were updated by SVN ( e.g. in the script
>>> >> time
>>> >> >> )?
>>> >> >> >> > >>
>>> >> >> >> > >>
>>> >> >> >> > >> Most likely there is no direct answer...however, I think
>>> that
>>> >> I
>>> >> >> could
>>> >> >> >> > >> find a way to gather the project names which were updated
>>> in
>>> >> the
>>> >> >> >> > >> shell
>>> >> >> >> > >> script - then I could pass the list of project names to
>>> maven
>>> >> >> >> > >> command.
>>> >> >> >> > >> Is there any way to make sure that those and dependent
>>> >> projects
>>> >> >> would
>>> >> >> >> > >> be built in the right order?
>>> >> >> >> > >>
>>> >> >> >> > >>
>>> >> >> >> > >> The project structure is:
>>> >> >> >> > >>
>>> >> >> >> > >> parent
>>> >> >> >> > >> -- subsystem1
>>> >> >> >> > >> -- s1-project1
>>> >> >> >> > >> -- s1-project2
>>> >> >> >> > >> -- subsystem2
>>> >> >> >> > >> -- s2-project1
>>> >> >> >> > >> -- s2-project2
>>> >> >> >> > >> -- s2-project3
>>> >> >> >> > >> -- subsystem3
>>> >> >> >> > >> -- s3-project1
>>> >> >> >> > >>
>>> >> >> >> > >>
>>> >> >> >> > >> Thank you for any ideas!
>>> >> >> >> > >>
>>> >> >> >> > >>
>>> >> >> >> > >> Žilvinas Vilutis
>>> >> >> >> > >>
>>> >> >> >> > >> Mobile: (+370) 652 38353
>>> >> >> >> > >> E-mail: cikasfm@gmail.com
>>> >> >> >> > >>
>>> >> >> >> > >> -----------------------------------------------------------
>>> ---
>>> >> ---
>>> >> >> ----
>>> >> >> >> > >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> >> >> >> > >> For additional commands, e-mail: users-
>>> help@maven.apache.org
>>> >> >> >> > >>
>>> >> >> >> > >>
>>> >> >> >> > >
>>> >> >> >> >
>>> >> >> >> > --------------------------------------------------------------
>>> ---
>>> >> ---
>>> >> >> -
>>> >> >> >> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> >> >> >> > For additional commands, e-mail: users-help@maven.apache.org
>>> >> >> >> >
>>> >> >> >> >
>>> >> >> >>
>>> >> >> >>
>>> >> >> >> --
>>> >> >> >> Jeff Vincent
>>> >> >> >> predatorvi@gmail.com
>>> >> >> >> See my LinkedIn profile at:
>>> >> >> >> http://www.linkedin.com/in/rjeffreyvincent
>>> >> >> >
>>> >> >> >
>>> >> >> >
>>> >> >> > --
>>> >> >> > Cesar De la Cruz Rojas
>>> >> >> > -----------------------------------------------------------------
>>> ---
>>> >> ---
>>> >> >> ------
>>> >> >> > Sennior Software Engineer
>>> >> >> > -----------------------------------------------------------------
>>> ---
>>> >> ---
>>> >> >> ------
>>> >> >> > Follow me in Facebook : http://www.facebook.com/aquiles.geo
>>> >> >> > Twitter http://twitter.com/ageo
>>> >> >> > Picture blog http://ageo.deviantart.com
>>> >> >> >
>>> >> >> >
>>> >> >>
>>> >> >> -------------------------------------------------------------------
>>> --
>>> >> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> >> >> For additional commands, e-mail: users-help@maven.apache.org
>>> >> >
>>> >> >
>>> >
>>> > ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> > For additional commands, e-mail: users-help@maven.apache.org
>>> >
>>> >
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ***************************
> This message may contain confidential or proprietary information intended only
> for the use of the addressee(s) named above or may contain information that is
> legally privileged. If you are not the intended addressee, or the person
> responsible for delivering it to the intended addressee, you are hereby
> notified that reading, disseminating, distributing or copying this message is
> strictly prohibited. If you have received this message by mistake, please
> immediately notify us by replying to the message and delete the original
> message and any copies immediately thereafter.
>
> Thank you.
> ****************************
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: subversion vs maven
Posted by "Collins, Russell" <rc...@corelogic.com>.
This sounds like you need to do more svn updates on projects you are working on. My suggestion would be to do that SVN update on those projects, resolve any conflicts, and then run the maven install. This will make your version into the latest in your repository.
It may also help if you checked in your code a little quicker. You might be letting your code get to far out of sync.
Russell Collins
Sr. Software Engineer
CoreLogic Spatial Solutions
"Do or do not, there is no try." - Yoda
-----Original Message-----
From: Zilvinas Vilutis [mailto:cikasfm@gmail.com]
Sent: Wednesday, February 16, 2011 2:41 PM
To: Maven Users List
Cc: Thiessen, Todd (Todd)
Subject: Re: subversion vs maven
> You don't need to do a full build AND you will only be using artifacts in your local repository. Sounds like its exactly what you want.
Exactly :) When doing it incrementally - that's how it should work
when building only "changed" projects and their dependents, what the
original question was
> So when you get in in the morning, issue a mvn -U install on your module,
> and you will get latest artifacts installed to your local repo (don't have to
> do a full build). For the rest of the day, do a mvn install to do your module
> builds and snapshots won't get updated."
Yeah, this sounds good when working in a dev environment.
However I'm "on my own" in the customers' office where network latency
is not enough to download the artifacts quickly.
Anyways, in this case - if I changed my code yesterday and did not
commit it to SVN - then the downloaded snapshot would be newer and
will be put in my webapp's "war". In most cases - other people are
updating the same projects as I'm working on so they would almost all
the time match the right projects to be built. And my projects would
not get built during the "full-build" - they would already exist in my
local repo so they would be picked up when building the war.
I guess I will try to make the most use of the maven reactor (
http://docs.codehaus.org/display/MAVEN/Make+Like+Reactor+Mode ) to use
the "--project-list" ( for specifying updated projects ) and
"--also-make-dependents" parameters is exactly what I want.
Thank you all for ideas & help!
Žilvinas Vilutis
Mobile: (+370) 652 38353
E-mail: cikasfm@gmail.com
On Wed, Feb 16, 2011 at 1:22 PM, Thiessen, Todd (Todd)
<tt...@avaya.com> wrote:
> Ok. You should be able to achieve the same result by configuring your settings.xml file to never update snapshots. That way you have more control. When you want to get latest snapshots, issue mvn -U install.
>
> You don't need to do a full build AND you will only be using artifacts in your local repository. Sounds like its exactly what you want.
>
> So when you get in in the morning, issue a mvn -U install on your module, and you will get latest artifacts installed to your local repo (don't have to do a full build). For the rest of the day, do a mvn install to do your module builds and snapshots won't get updated.
>
> Just a thought. Hope it helps.
>
>> -----Original Message-----
>> From: Zilvinas Vilutis [mailto:cikasfm@gmail.com]
>> Sent: Wednesday, February 16, 2011 3:12 PM
>> To: Maven Users List
>> Cc: Thiessen, Todd (Todd)
>> Subject: Re: subversion vs maven
>>
>> Theoretically - yes
>> Practically - no
>>
>> We were using the approach with CI and snapshots from the repo long
>> time ago, however in a lot of cases we came to a case where the
>> project does not compile or work as expected when having different
>> snapshot versions, or takes just a very long time to at least package
>> the project you're working on, so in the long term to make it quick,
>> safe and making sure that all my modified but not committed modules
>> get into the app from my local, not external repo ( in case they're
>> "older" ) - we just do the build on our boxes.
>>
>> Žilvinas Vilutis
>>
>> Mobile: (+370) 652 38353
>> E-mail: cikasfm@gmail.com
>>
>>
>>
>> 2011/2/16 Thiessen, Todd (Todd) <tt...@avaya.com>:
>> > You could control your dependencies by checking out which ever
>> dependencies you care about and ensure you build those as well.
>> Normally, you would just want the snapshot versions anyway. There is
>> also a properity in your settings.xml file to instruct maven to never
>> check for updates. To get latest snapshot artifacts you would have to
>> issue a mvn -U.
>> >
>> > The whole idea here is that you should only every be compiling and
>> downloading what you need. Let your CI server do the full builds. You
>> should rarely have to.
>> >
>> >> -----Original Message-----
>> >> From: Zilvinas Vilutis [mailto:cikasfm@gmail.com]
>> >> Sent: Wednesday, February 16, 2011 1:52 PM
>> >> To: Maven Users List
>> >> Cc: Thiessen, Todd (Todd)
>> >> Subject: Re: subversion vs maven
>> >>
>> >> yes, we could set this up.
>> >>
>> >> However there's 2 things:
>> >> - We're working with "SNAPSHOT" versions most of the time with CI you
>> >> can hardly control when to use YOUR code versus from the repo in a big
>> >> projcet
>> >> - I'm working in a client's office and the network latency between our
>> >> office and clients office would make it slow
>> >>
>> >> I could run a CI / Hundson / whatever other build management server on
>> >> my laptop...but then it would not be quicker then just the full build
>> >> :)
>> >>
>> >> Žilvinas Vilutis
>> >>
>> >> Mobile: (+370) 652 38353
>> >> E-mail: cikasfm@gmail.com
>> >>
>> >>
>> >>
>> >> On Wed, Feb 16, 2011 at 11:41 AM, Thiessen, Todd (Todd)
>> >> <tt...@avaya.com> wrote:
>> >> > If you have a CI server already building everything, why do you need
>> to
>> >> build everything every morning? Can't you just checkout only the one
>> >> module you need to change and build that?
>> >> >
>> >> >> -----Original Message-----
>> >> >> From: Zilvinas Vilutis [mailto:cikasfm@gmail.com]
>> >> >> Sent: Wednesday, February 16, 2011 1:37 PM
>> >> >> To: a.geo
>> >> >> Cc: Maven Users List; Jeff
>> >> >> Subject: Re: subversion vs maven
>> >> >>
>> >> >> trust me, not so easy :)
>> >> >>
>> >> >> our project has like 20 subsystems which all have 5-10 sub-
>> projects.
>> >> >>
>> >> >> Our "core" is extracted into a separate dependency maintained by
>> >> >> another team, it is also managed by maven ( ~30 subsystems, 10-50
>> >> >> projects each ).
>> >> >>
>> >> >> Yes, daily updates happen on 5-10 projects, that is why I don't
>> want
>> >> >> to build the "full" build but only the changed projects and their
>> >> >> dependents ( web apps ).
>> >> >>
>> >> >> Žilvinas Vilutis
>> >> >>
>> >> >> Mobile: (+370) 652 38353
>> >> >> E-mail: cikasfm@gmail.com
>> >> >>
>> >> >>
>> >> >>
>> >> >> On Wed, Feb 16, 2011 at 10:37 AM, a.geo <aq...@gmail.com>
>> wrote:
>> >> >> > You mus consider a "core" section, that contain your business
>> main
>> >> >> code,
>> >> >> > usually you don't change it. Around it, is the implementation of
>> the
>> >> >> > requirement.
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > 2011/2/16 Jeff <pr...@gmail.com>
>> >> >> >>
>> >> >> >> Maybe this question will expose my ignorance, but I thought most
>> >> build
>> >> >> >> systems only build the things that have changed unless you do a
>> >> >> "clean"
>> >> >> >> each
>> >> >> >> time or are starting from a fresh checkout as opposed to doing
>> an
>> >> "svn
>> >> >> >> update" and then running the build.
>> >> >> >>
>> >> >> >> Being new to Maven myself, there could there be an option in the
>> >> POM
>> >> >> that
>> >> >> >> might be forcing a full build each time?
>> >> >> >>
>> >> >> >> I would think that as long as you aren't specifying "clean" in
>> your
>> >> >> build
>> >> >> >> kickoff process or otherwise forcing a full biuld, you should
>> only
>> >> be
>> >> >> >> getting the incremental build, no? Am I off in my
>> understanding?
>> >> >> >> On Wed, Feb 16, 2011 at 10:18 AM, Zilvinas Vilutis
>> >> >> >> <ci...@gmail.com>wrote:
>> >> >> >>
>> >> >> >> > Yes,
>> >> >> >> >
>> >> >> >> > However it does a "full build" which takes ~30-40 minutes. But
>> I
>> >> >> want
>> >> >> >> > to build only specific projects and their dependents.
>> >> >> >> >
>> >> >> >> > Regards
>> >> >> >> >
>> >> >> >> > Žilvinas Vilutis
>> >> >> >> >
>> >> >> >> > Mobile: (+370) 652 38353
>> >> >> >> > E-mail: cikasfm@gmail.com
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > On Wed, Feb 16, 2011 at 9:54 AM, Leon Rosenberg
>> >> >> >> > <ro...@gmail.com> wrote:
>> >> >> >> > > How about hudson?
>> >> >> >> > >
>> >> >> >> > > Hudson can watch for svn changes and trigger builds on
>> commit.
>> >> >> >> > >
>> >> >> >> > > regards
>> >> >> >> > > Leon
>> >> >> >> > >
>> >> >> >> > > On Wed, Feb 16, 2011 at 5:46 PM, Zilvinas Vilutis
>> >> >> <ci...@gmail.com>
>> >> >> >> > wrote:
>> >> >> >> > >> Hello Maven Users!
>> >> >> >> > >>
>> >> >> >> > >> Probably this question was already asked, so if there is an
>> >> >> answer
>> >> >> >> > >> which I could not find - please point me to the right
>> place.
>> >> >> >> > >>
>> >> >> >> > >>
>> >> >> >> > >> I'm working on an enterprise project where maven
>> integration
>> >> >> plays a
>> >> >> >> > huge role.
>> >> >> >> > >>
>> >> >> >> > >> However the project is big as a lot of teams are working on
>> it
>> >> >> and it
>> >> >> >> > >> takes quite some time to build it ( 30-40 minutes ), which
>> I
>> >> need
>> >> >> to
>> >> >> >> > >> do every morning after an svn update.
>> >> >> >> > >>
>> >> >> >> > >>
>> >> >> >> > >> So I was thinking - is there any way to configure maven to
>> >> build
>> >> >> only
>> >> >> >> > >> the projects which were updated by SVN ( e.g. in the script
>> >> time
>> >> >> )?
>> >> >> >> > >>
>> >> >> >> > >>
>> >> >> >> > >> Most likely there is no direct answer...however, I think
>> that
>> >> I
>> >> >> could
>> >> >> >> > >> find a way to gather the project names which were updated
>> in
>> >> the
>> >> >> >> > >> shell
>> >> >> >> > >> script - then I could pass the list of project names to
>> maven
>> >> >> >> > >> command.
>> >> >> >> > >> Is there any way to make sure that those and dependent
>> >> projects
>> >> >> would
>> >> >> >> > >> be built in the right order?
>> >> >> >> > >>
>> >> >> >> > >>
>> >> >> >> > >> The project structure is:
>> >> >> >> > >>
>> >> >> >> > >> parent
>> >> >> >> > >> -- subsystem1
>> >> >> >> > >> -- s1-project1
>> >> >> >> > >> -- s1-project2
>> >> >> >> > >> -- subsystem2
>> >> >> >> > >> -- s2-project1
>> >> >> >> > >> -- s2-project2
>> >> >> >> > >> -- s2-project3
>> >> >> >> > >> -- subsystem3
>> >> >> >> > >> -- s3-project1
>> >> >> >> > >>
>> >> >> >> > >>
>> >> >> >> > >> Thank you for any ideas!
>> >> >> >> > >>
>> >> >> >> > >>
>> >> >> >> > >> Žilvinas Vilutis
>> >> >> >> > >>
>> >> >> >> > >> Mobile: (+370) 652 38353
>> >> >> >> > >> E-mail: cikasfm@gmail.com
>> >> >> >> > >>
>> >> >> >> > >> -----------------------------------------------------------
>> ---
>> >> ---
>> >> >> ----
>> >> >> >> > >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> >> >> >> > >> For additional commands, e-mail: users-
>> help@maven.apache.org
>> >> >> >> > >>
>> >> >> >> > >>
>> >> >> >> > >
>> >> >> >> >
>> >> >> >> > --------------------------------------------------------------
>> ---
>> >> ---
>> >> >> -
>> >> >> >> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> >> >> >> > For additional commands, e-mail: users-help@maven.apache.org
>> >> >> >> >
>> >> >> >> >
>> >> >> >>
>> >> >> >>
>> >> >> >> --
>> >> >> >> Jeff Vincent
>> >> >> >> predatorvi@gmail.com
>> >> >> >> See my LinkedIn profile at:
>> >> >> >> http://www.linkedin.com/in/rjeffreyvincent
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > --
>> >> >> > Cesar De la Cruz Rojas
>> >> >> > -----------------------------------------------------------------
>> ---
>> >> ---
>> >> >> ------
>> >> >> > Sennior Software Engineer
>> >> >> > -----------------------------------------------------------------
>> ---
>> >> ---
>> >> >> ------
>> >> >> > Follow me in Facebook : http://www.facebook.com/aquiles.geo
>> >> >> > Twitter http://twitter.com/ageo
>> >> >> > Picture blog http://ageo.deviantart.com
>> >> >> >
>> >> >> >
>> >> >>
>> >> >> -------------------------------------------------------------------
>> --
>> >> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> >> >> For additional commands, e-mail: users-help@maven.apache.org
>> >> >
>> >> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> > For additional commands, e-mail: users-help@maven.apache.org
>> >
>> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
***************************
This message may contain confidential or proprietary information intended only
for the use of the addressee(s) named above or may contain information that is
legally privileged. If you are not the intended addressee, or the person
responsible for delivering it to the intended addressee, you are hereby
notified that reading, disseminating, distributing or copying this message is
strictly prohibited. If you have received this message by mistake, please
immediately notify us by replying to the message and delete the original
message and any copies immediately thereafter.
Thank you.
****************************
Re: subversion vs maven
Posted by Zilvinas Vilutis <ci...@gmail.com>.
> You don't need to do a full build AND you will only be using artifacts in your local repository. Sounds like its exactly what you want.
Exactly :) When doing it incrementally - that's how it should work
when building only "changed" projects and their dependents, what the
original question was
> So when you get in in the morning, issue a mvn -U install on your module,
> and you will get latest artifacts installed to your local repo (don't have to
> do a full build). For the rest of the day, do a mvn install to do your module
> builds and snapshots won't get updated."
Yeah, this sounds good when working in a dev environment.
However I'm "on my own" in the customers' office where network latency
is not enough to download the artifacts quickly.
Anyways, in this case - if I changed my code yesterday and did not
commit it to SVN - then the downloaded snapshot would be newer and
will be put in my webapp's "war". In most cases - other people are
updating the same projects as I'm working on so they would almost all
the time match the right projects to be built. And my projects would
not get built during the "full-build" - they would already exist in my
local repo so they would be picked up when building the war.
I guess I will try to make the most use of the maven reactor (
http://docs.codehaus.org/display/MAVEN/Make+Like+Reactor+Mode ) to use
the "--project-list" ( for specifying updated projects ) and
"--also-make-dependents" parameters is exactly what I want.
Thank you all for ideas & help!
Žilvinas Vilutis
Mobile: (+370) 652 38353
E-mail: cikasfm@gmail.com
On Wed, Feb 16, 2011 at 1:22 PM, Thiessen, Todd (Todd)
<tt...@avaya.com> wrote:
> Ok. You should be able to achieve the same result by configuring your settings.xml file to never update snapshots. That way you have more control. When you want to get latest snapshots, issue mvn -U install.
>
> You don't need to do a full build AND you will only be using artifacts in your local repository. Sounds like its exactly what you want.
>
> So when you get in in the morning, issue a mvn -U install on your module, and you will get latest artifacts installed to your local repo (don't have to do a full build). For the rest of the day, do a mvn install to do your module builds and snapshots won't get updated.
>
> Just a thought. Hope it helps.
>
>> -----Original Message-----
>> From: Zilvinas Vilutis [mailto:cikasfm@gmail.com]
>> Sent: Wednesday, February 16, 2011 3:12 PM
>> To: Maven Users List
>> Cc: Thiessen, Todd (Todd)
>> Subject: Re: subversion vs maven
>>
>> Theoretically - yes
>> Practically - no
>>
>> We were using the approach with CI and snapshots from the repo long
>> time ago, however in a lot of cases we came to a case where the
>> project does not compile or work as expected when having different
>> snapshot versions, or takes just a very long time to at least package
>> the project you're working on, so in the long term to make it quick,
>> safe and making sure that all my modified but not committed modules
>> get into the app from my local, not external repo ( in case they're
>> "older" ) - we just do the build on our boxes.
>>
>> Žilvinas Vilutis
>>
>> Mobile: (+370) 652 38353
>> E-mail: cikasfm@gmail.com
>>
>>
>>
>> 2011/2/16 Thiessen, Todd (Todd) <tt...@avaya.com>:
>> > You could control your dependencies by checking out which ever
>> dependencies you care about and ensure you build those as well.
>> Normally, you would just want the snapshot versions anyway. There is
>> also a properity in your settings.xml file to instruct maven to never
>> check for updates. To get latest snapshot artifacts you would have to
>> issue a mvn -U.
>> >
>> > The whole idea here is that you should only every be compiling and
>> downloading what you need. Let your CI server do the full builds. You
>> should rarely have to.
>> >
>> >> -----Original Message-----
>> >> From: Zilvinas Vilutis [mailto:cikasfm@gmail.com]
>> >> Sent: Wednesday, February 16, 2011 1:52 PM
>> >> To: Maven Users List
>> >> Cc: Thiessen, Todd (Todd)
>> >> Subject: Re: subversion vs maven
>> >>
>> >> yes, we could set this up.
>> >>
>> >> However there's 2 things:
>> >> - We're working with "SNAPSHOT" versions most of the time with CI you
>> >> can hardly control when to use YOUR code versus from the repo in a big
>> >> projcet
>> >> - I'm working in a client's office and the network latency between our
>> >> office and clients office would make it slow
>> >>
>> >> I could run a CI / Hundson / whatever other build management server on
>> >> my laptop...but then it would not be quicker then just the full build
>> >> :)
>> >>
>> >> Žilvinas Vilutis
>> >>
>> >> Mobile: (+370) 652 38353
>> >> E-mail: cikasfm@gmail.com
>> >>
>> >>
>> >>
>> >> On Wed, Feb 16, 2011 at 11:41 AM, Thiessen, Todd (Todd)
>> >> <tt...@avaya.com> wrote:
>> >> > If you have a CI server already building everything, why do you need
>> to
>> >> build everything every morning? Can't you just checkout only the one
>> >> module you need to change and build that?
>> >> >
>> >> >> -----Original Message-----
>> >> >> From: Zilvinas Vilutis [mailto:cikasfm@gmail.com]
>> >> >> Sent: Wednesday, February 16, 2011 1:37 PM
>> >> >> To: a.geo
>> >> >> Cc: Maven Users List; Jeff
>> >> >> Subject: Re: subversion vs maven
>> >> >>
>> >> >> trust me, not so easy :)
>> >> >>
>> >> >> our project has like 20 subsystems which all have 5-10 sub-
>> projects.
>> >> >>
>> >> >> Our "core" is extracted into a separate dependency maintained by
>> >> >> another team, it is also managed by maven ( ~30 subsystems, 10-50
>> >> >> projects each ).
>> >> >>
>> >> >> Yes, daily updates happen on 5-10 projects, that is why I don't
>> want
>> >> >> to build the "full" build but only the changed projects and their
>> >> >> dependents ( web apps ).
>> >> >>
>> >> >> Žilvinas Vilutis
>> >> >>
>> >> >> Mobile: (+370) 652 38353
>> >> >> E-mail: cikasfm@gmail.com
>> >> >>
>> >> >>
>> >> >>
>> >> >> On Wed, Feb 16, 2011 at 10:37 AM, a.geo <aq...@gmail.com>
>> wrote:
>> >> >> > You mus consider a "core" section, that contain your business
>> main
>> >> >> code,
>> >> >> > usually you don't change it. Around it, is the implementation of
>> the
>> >> >> > requirement.
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > 2011/2/16 Jeff <pr...@gmail.com>
>> >> >> >>
>> >> >> >> Maybe this question will expose my ignorance, but I thought most
>> >> build
>> >> >> >> systems only build the things that have changed unless you do a
>> >> >> "clean"
>> >> >> >> each
>> >> >> >> time or are starting from a fresh checkout as opposed to doing
>> an
>> >> "svn
>> >> >> >> update" and then running the build.
>> >> >> >>
>> >> >> >> Being new to Maven myself, there could there be an option in the
>> >> POM
>> >> >> that
>> >> >> >> might be forcing a full build each time?
>> >> >> >>
>> >> >> >> I would think that as long as you aren't specifying "clean" in
>> your
>> >> >> build
>> >> >> >> kickoff process or otherwise forcing a full biuld, you should
>> only
>> >> be
>> >> >> >> getting the incremental build, no? Am I off in my
>> understanding?
>> >> >> >> On Wed, Feb 16, 2011 at 10:18 AM, Zilvinas Vilutis
>> >> >> >> <ci...@gmail.com>wrote:
>> >> >> >>
>> >> >> >> > Yes,
>> >> >> >> >
>> >> >> >> > However it does a "full build" which takes ~30-40 minutes. But
>> I
>> >> >> want
>> >> >> >> > to build only specific projects and their dependents.
>> >> >> >> >
>> >> >> >> > Regards
>> >> >> >> >
>> >> >> >> > Žilvinas Vilutis
>> >> >> >> >
>> >> >> >> > Mobile: (+370) 652 38353
>> >> >> >> > E-mail: cikasfm@gmail.com
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > On Wed, Feb 16, 2011 at 9:54 AM, Leon Rosenberg
>> >> >> >> > <ro...@gmail.com> wrote:
>> >> >> >> > > How about hudson?
>> >> >> >> > >
>> >> >> >> > > Hudson can watch for svn changes and trigger builds on
>> commit.
>> >> >> >> > >
>> >> >> >> > > regards
>> >> >> >> > > Leon
>> >> >> >> > >
>> >> >> >> > > On Wed, Feb 16, 2011 at 5:46 PM, Zilvinas Vilutis
>> >> >> <ci...@gmail.com>
>> >> >> >> > wrote:
>> >> >> >> > >> Hello Maven Users!
>> >> >> >> > >>
>> >> >> >> > >> Probably this question was already asked, so if there is an
>> >> >> answer
>> >> >> >> > >> which I could not find - please point me to the right
>> place.
>> >> >> >> > >>
>> >> >> >> > >>
>> >> >> >> > >> I'm working on an enterprise project where maven
>> integration
>> >> >> plays a
>> >> >> >> > huge role.
>> >> >> >> > >>
>> >> >> >> > >> However the project is big as a lot of teams are working on
>> it
>> >> >> and it
>> >> >> >> > >> takes quite some time to build it ( 30-40 minutes ), which
>> I
>> >> need
>> >> >> to
>> >> >> >> > >> do every morning after an svn update.
>> >> >> >> > >>
>> >> >> >> > >>
>> >> >> >> > >> So I was thinking - is there any way to configure maven to
>> >> build
>> >> >> only
>> >> >> >> > >> the projects which were updated by SVN ( e.g. in the script
>> >> time
>> >> >> )?
>> >> >> >> > >>
>> >> >> >> > >>
>> >> >> >> > >> Most likely there is no direct answer...however, I think
>> that
>> >> I
>> >> >> could
>> >> >> >> > >> find a way to gather the project names which were updated
>> in
>> >> the
>> >> >> >> > >> shell
>> >> >> >> > >> script - then I could pass the list of project names to
>> maven
>> >> >> >> > >> command.
>> >> >> >> > >> Is there any way to make sure that those and dependent
>> >> projects
>> >> >> would
>> >> >> >> > >> be built in the right order?
>> >> >> >> > >>
>> >> >> >> > >>
>> >> >> >> > >> The project structure is:
>> >> >> >> > >>
>> >> >> >> > >> parent
>> >> >> >> > >> -- subsystem1
>> >> >> >> > >> -- s1-project1
>> >> >> >> > >> -- s1-project2
>> >> >> >> > >> -- subsystem2
>> >> >> >> > >> -- s2-project1
>> >> >> >> > >> -- s2-project2
>> >> >> >> > >> -- s2-project3
>> >> >> >> > >> -- subsystem3
>> >> >> >> > >> -- s3-project1
>> >> >> >> > >>
>> >> >> >> > >>
>> >> >> >> > >> Thank you for any ideas!
>> >> >> >> > >>
>> >> >> >> > >>
>> >> >> >> > >> Žilvinas Vilutis
>> >> >> >> > >>
>> >> >> >> > >> Mobile: (+370) 652 38353
>> >> >> >> > >> E-mail: cikasfm@gmail.com
>> >> >> >> > >>
>> >> >> >> > >> -----------------------------------------------------------
>> ---
>> >> ---
>> >> >> ----
>> >> >> >> > >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> >> >> >> > >> For additional commands, e-mail: users-
>> help@maven.apache.org
>> >> >> >> > >>
>> >> >> >> > >>
>> >> >> >> > >
>> >> >> >> >
>> >> >> >> > --------------------------------------------------------------
>> ---
>> >> ---
>> >> >> -
>> >> >> >> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> >> >> >> > For additional commands, e-mail: users-help@maven.apache.org
>> >> >> >> >
>> >> >> >> >
>> >> >> >>
>> >> >> >>
>> >> >> >> --
>> >> >> >> Jeff Vincent
>> >> >> >> predatorvi@gmail.com
>> >> >> >> See my LinkedIn profile at:
>> >> >> >> http://www.linkedin.com/in/rjeffreyvincent
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > --
>> >> >> > Cesar De la Cruz Rojas
>> >> >> > -----------------------------------------------------------------
>> ---
>> >> ---
>> >> >> ------
>> >> >> > Sennior Software Engineer
>> >> >> > -----------------------------------------------------------------
>> ---
>> >> ---
>> >> >> ------
>> >> >> > Follow me in Facebook : http://www.facebook.com/aquiles.geo
>> >> >> > Twitter http://twitter.com/ageo
>> >> >> > Picture blog http://ageo.deviantart.com
>> >> >> >
>> >> >> >
>> >> >>
>> >> >> -------------------------------------------------------------------
>> --
>> >> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> >> >> For additional commands, e-mail: users-help@maven.apache.org
>> >> >
>> >> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> > For additional commands, e-mail: users-help@maven.apache.org
>> >
>> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: subversion vs maven
Posted by "Thiessen, Todd (Todd)" <tt...@avaya.com>.
Ok. You should be able to achieve the same result by configuring your settings.xml file to never update snapshots. That way you have more control. When you want to get latest snapshots, issue mvn -U install.
You don't need to do a full build AND you will only be using artifacts in your local repository. Sounds like its exactly what you want.
So when you get in in the morning, issue a mvn -U install on your module, and you will get latest artifacts installed to your local repo (don't have to do a full build). For the rest of the day, do a mvn install to do your module builds and snapshots won't get updated.
Just a thought. Hope it helps.
> -----Original Message-----
> From: Zilvinas Vilutis [mailto:cikasfm@gmail.com]
> Sent: Wednesday, February 16, 2011 3:12 PM
> To: Maven Users List
> Cc: Thiessen, Todd (Todd)
> Subject: Re: subversion vs maven
>
> Theoretically - yes
> Practically - no
>
> We were using the approach with CI and snapshots from the repo long
> time ago, however in a lot of cases we came to a case where the
> project does not compile or work as expected when having different
> snapshot versions, or takes just a very long time to at least package
> the project you're working on, so in the long term to make it quick,
> safe and making sure that all my modified but not committed modules
> get into the app from my local, not external repo ( in case they're
> "older" ) - we just do the build on our boxes.
>
> Žilvinas Vilutis
>
> Mobile: (+370) 652 38353
> E-mail: cikasfm@gmail.com
>
>
>
> 2011/2/16 Thiessen, Todd (Todd) <tt...@avaya.com>:
> > You could control your dependencies by checking out which ever
> dependencies you care about and ensure you build those as well.
> Normally, you would just want the snapshot versions anyway. There is
> also a properity in your settings.xml file to instruct maven to never
> check for updates. To get latest snapshot artifacts you would have to
> issue a mvn -U.
> >
> > The whole idea here is that you should only every be compiling and
> downloading what you need. Let your CI server do the full builds. You
> should rarely have to.
> >
> >> -----Original Message-----
> >> From: Zilvinas Vilutis [mailto:cikasfm@gmail.com]
> >> Sent: Wednesday, February 16, 2011 1:52 PM
> >> To: Maven Users List
> >> Cc: Thiessen, Todd (Todd)
> >> Subject: Re: subversion vs maven
> >>
> >> yes, we could set this up.
> >>
> >> However there's 2 things:
> >> - We're working with "SNAPSHOT" versions most of the time with CI you
> >> can hardly control when to use YOUR code versus from the repo in a big
> >> projcet
> >> - I'm working in a client's office and the network latency between our
> >> office and clients office would make it slow
> >>
> >> I could run a CI / Hundson / whatever other build management server on
> >> my laptop...but then it would not be quicker then just the full build
> >> :)
> >>
> >> Žilvinas Vilutis
> >>
> >> Mobile: (+370) 652 38353
> >> E-mail: cikasfm@gmail.com
> >>
> >>
> >>
> >> On Wed, Feb 16, 2011 at 11:41 AM, Thiessen, Todd (Todd)
> >> <tt...@avaya.com> wrote:
> >> > If you have a CI server already building everything, why do you need
> to
> >> build everything every morning? Can't you just checkout only the one
> >> module you need to change and build that?
> >> >
> >> >> -----Original Message-----
> >> >> From: Zilvinas Vilutis [mailto:cikasfm@gmail.com]
> >> >> Sent: Wednesday, February 16, 2011 1:37 PM
> >> >> To: a.geo
> >> >> Cc: Maven Users List; Jeff
> >> >> Subject: Re: subversion vs maven
> >> >>
> >> >> trust me, not so easy :)
> >> >>
> >> >> our project has like 20 subsystems which all have 5-10 sub-
> projects.
> >> >>
> >> >> Our "core" is extracted into a separate dependency maintained by
> >> >> another team, it is also managed by maven ( ~30 subsystems, 10-50
> >> >> projects each ).
> >> >>
> >> >> Yes, daily updates happen on 5-10 projects, that is why I don't
> want
> >> >> to build the "full" build but only the changed projects and their
> >> >> dependents ( web apps ).
> >> >>
> >> >> Žilvinas Vilutis
> >> >>
> >> >> Mobile: (+370) 652 38353
> >> >> E-mail: cikasfm@gmail.com
> >> >>
> >> >>
> >> >>
> >> >> On Wed, Feb 16, 2011 at 10:37 AM, a.geo <aq...@gmail.com>
> wrote:
> >> >> > You mus consider a "core" section, that contain your business
> main
> >> >> code,
> >> >> > usually you don't change it. Around it, is the implementation of
> the
> >> >> > requirement.
> >> >> >
> >> >> >
> >> >> >
> >> >> > 2011/2/16 Jeff <pr...@gmail.com>
> >> >> >>
> >> >> >> Maybe this question will expose my ignorance, but I thought most
> >> build
> >> >> >> systems only build the things that have changed unless you do a
> >> >> "clean"
> >> >> >> each
> >> >> >> time or are starting from a fresh checkout as opposed to doing
> an
> >> "svn
> >> >> >> update" and then running the build.
> >> >> >>
> >> >> >> Being new to Maven myself, there could there be an option in the
> >> POM
> >> >> that
> >> >> >> might be forcing a full build each time?
> >> >> >>
> >> >> >> I would think that as long as you aren't specifying "clean" in
> your
> >> >> build
> >> >> >> kickoff process or otherwise forcing a full biuld, you should
> only
> >> be
> >> >> >> getting the incremental build, no? Am I off in my
> understanding?
> >> >> >> On Wed, Feb 16, 2011 at 10:18 AM, Zilvinas Vilutis
> >> >> >> <ci...@gmail.com>wrote:
> >> >> >>
> >> >> >> > Yes,
> >> >> >> >
> >> >> >> > However it does a "full build" which takes ~30-40 minutes. But
> I
> >> >> want
> >> >> >> > to build only specific projects and their dependents.
> >> >> >> >
> >> >> >> > Regards
> >> >> >> >
> >> >> >> > Žilvinas Vilutis
> >> >> >> >
> >> >> >> > Mobile: (+370) 652 38353
> >> >> >> > E-mail: cikasfm@gmail.com
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >> > On Wed, Feb 16, 2011 at 9:54 AM, Leon Rosenberg
> >> >> >> > <ro...@gmail.com> wrote:
> >> >> >> > > How about hudson?
> >> >> >> > >
> >> >> >> > > Hudson can watch for svn changes and trigger builds on
> commit.
> >> >> >> > >
> >> >> >> > > regards
> >> >> >> > > Leon
> >> >> >> > >
> >> >> >> > > On Wed, Feb 16, 2011 at 5:46 PM, Zilvinas Vilutis
> >> >> <ci...@gmail.com>
> >> >> >> > wrote:
> >> >> >> > >> Hello Maven Users!
> >> >> >> > >>
> >> >> >> > >> Probably this question was already asked, so if there is an
> >> >> answer
> >> >> >> > >> which I could not find - please point me to the right
> place.
> >> >> >> > >>
> >> >> >> > >>
> >> >> >> > >> I'm working on an enterprise project where maven
> integration
> >> >> plays a
> >> >> >> > huge role.
> >> >> >> > >>
> >> >> >> > >> However the project is big as a lot of teams are working on
> it
> >> >> and it
> >> >> >> > >> takes quite some time to build it ( 30-40 minutes ), which
> I
> >> need
> >> >> to
> >> >> >> > >> do every morning after an svn update.
> >> >> >> > >>
> >> >> >> > >>
> >> >> >> > >> So I was thinking - is there any way to configure maven to
> >> build
> >> >> only
> >> >> >> > >> the projects which were updated by SVN ( e.g. in the script
> >> time
> >> >> )?
> >> >> >> > >>
> >> >> >> > >>
> >> >> >> > >> Most likely there is no direct answer...however, I think
> that
> >> I
> >> >> could
> >> >> >> > >> find a way to gather the project names which were updated
> in
> >> the
> >> >> >> > >> shell
> >> >> >> > >> script - then I could pass the list of project names to
> maven
> >> >> >> > >> command.
> >> >> >> > >> Is there any way to make sure that those and dependent
> >> projects
> >> >> would
> >> >> >> > >> be built in the right order?
> >> >> >> > >>
> >> >> >> > >>
> >> >> >> > >> The project structure is:
> >> >> >> > >>
> >> >> >> > >> parent
> >> >> >> > >> -- subsystem1
> >> >> >> > >> -- s1-project1
> >> >> >> > >> -- s1-project2
> >> >> >> > >> -- subsystem2
> >> >> >> > >> -- s2-project1
> >> >> >> > >> -- s2-project2
> >> >> >> > >> -- s2-project3
> >> >> >> > >> -- subsystem3
> >> >> >> > >> -- s3-project1
> >> >> >> > >>
> >> >> >> > >>
> >> >> >> > >> Thank you for any ideas!
> >> >> >> > >>
> >> >> >> > >>
> >> >> >> > >> Žilvinas Vilutis
> >> >> >> > >>
> >> >> >> > >> Mobile: (+370) 652 38353
> >> >> >> > >> E-mail: cikasfm@gmail.com
> >> >> >> > >>
> >> >> >> > >> -----------------------------------------------------------
> ---
> >> ---
> >> >> ----
> >> >> >> > >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> >> >> > >> For additional commands, e-mail: users-
> help@maven.apache.org
> >> >> >> > >>
> >> >> >> > >>
> >> >> >> > >
> >> >> >> >
> >> >> >> > --------------------------------------------------------------
> ---
> >> ---
> >> >> -
> >> >> >> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> >> >> > For additional commands, e-mail: users-help@maven.apache.org
> >> >> >> >
> >> >> >> >
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Jeff Vincent
> >> >> >> predatorvi@gmail.com
> >> >> >> See my LinkedIn profile at:
> >> >> >> http://www.linkedin.com/in/rjeffreyvincent
> >> >> >
> >> >> >
> >> >> >
> >> >> > --
> >> >> > Cesar De la Cruz Rojas
> >> >> > -----------------------------------------------------------------
> ---
> >> ---
> >> >> ------
> >> >> > Sennior Software Engineer
> >> >> > -----------------------------------------------------------------
> ---
> >> ---
> >> >> ------
> >> >> > Follow me in Facebook : http://www.facebook.com/aquiles.geo
> >> >> > Twitter http://twitter.com/ageo
> >> >> > Picture blog http://ageo.deviantart.com
> >> >> >
> >> >> >
> >> >>
> >> >> -------------------------------------------------------------------
> --
> >> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> >> For additional commands, e-mail: users-help@maven.apache.org
> >> >
> >> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
Re: subversion vs maven
Posted by Zilvinas Vilutis <ci...@gmail.com>.
Theoretically - yes
Practically - no
We were using the approach with CI and snapshots from the repo long
time ago, however in a lot of cases we came to a case where the
project does not compile or work as expected when having different
snapshot versions, or takes just a very long time to at least package
the project you're working on, so in the long term to make it quick,
safe and making sure that all my modified but not committed modules
get into the app from my local, not external repo ( in case they're
"older" ) - we just do the build on our boxes.
Žilvinas Vilutis
Mobile: (+370) 652 38353
E-mail: cikasfm@gmail.com
2011/2/16 Thiessen, Todd (Todd) <tt...@avaya.com>:
> You could control your dependencies by checking out which ever dependencies you care about and ensure you build those as well. Normally, you would just want the snapshot versions anyway. There is also a properity in your settings.xml file to instruct maven to never check for updates. To get latest snapshot artifacts you would have to issue a mvn -U.
>
> The whole idea here is that you should only every be compiling and downloading what you need. Let your CI server do the full builds. You should rarely have to.
>
>> -----Original Message-----
>> From: Zilvinas Vilutis [mailto:cikasfm@gmail.com]
>> Sent: Wednesday, February 16, 2011 1:52 PM
>> To: Maven Users List
>> Cc: Thiessen, Todd (Todd)
>> Subject: Re: subversion vs maven
>>
>> yes, we could set this up.
>>
>> However there's 2 things:
>> - We're working with "SNAPSHOT" versions most of the time with CI you
>> can hardly control when to use YOUR code versus from the repo in a big
>> projcet
>> - I'm working in a client's office and the network latency between our
>> office and clients office would make it slow
>>
>> I could run a CI / Hundson / whatever other build management server on
>> my laptop...but then it would not be quicker then just the full build
>> :)
>>
>> Žilvinas Vilutis
>>
>> Mobile: (+370) 652 38353
>> E-mail: cikasfm@gmail.com
>>
>>
>>
>> On Wed, Feb 16, 2011 at 11:41 AM, Thiessen, Todd (Todd)
>> <tt...@avaya.com> wrote:
>> > If you have a CI server already building everything, why do you need to
>> build everything every morning? Can't you just checkout only the one
>> module you need to change and build that?
>> >
>> >> -----Original Message-----
>> >> From: Zilvinas Vilutis [mailto:cikasfm@gmail.com]
>> >> Sent: Wednesday, February 16, 2011 1:37 PM
>> >> To: a.geo
>> >> Cc: Maven Users List; Jeff
>> >> Subject: Re: subversion vs maven
>> >>
>> >> trust me, not so easy :)
>> >>
>> >> our project has like 20 subsystems which all have 5-10 sub-projects.
>> >>
>> >> Our "core" is extracted into a separate dependency maintained by
>> >> another team, it is also managed by maven ( ~30 subsystems, 10-50
>> >> projects each ).
>> >>
>> >> Yes, daily updates happen on 5-10 projects, that is why I don't want
>> >> to build the "full" build but only the changed projects and their
>> >> dependents ( web apps ).
>> >>
>> >> Žilvinas Vilutis
>> >>
>> >> Mobile: (+370) 652 38353
>> >> E-mail: cikasfm@gmail.com
>> >>
>> >>
>> >>
>> >> On Wed, Feb 16, 2011 at 10:37 AM, a.geo <aq...@gmail.com> wrote:
>> >> > You mus consider a "core" section, that contain your business main
>> >> code,
>> >> > usually you don't change it. Around it, is the implementation of the
>> >> > requirement.
>> >> >
>> >> >
>> >> >
>> >> > 2011/2/16 Jeff <pr...@gmail.com>
>> >> >>
>> >> >> Maybe this question will expose my ignorance, but I thought most
>> build
>> >> >> systems only build the things that have changed unless you do a
>> >> "clean"
>> >> >> each
>> >> >> time or are starting from a fresh checkout as opposed to doing an
>> "svn
>> >> >> update" and then running the build.
>> >> >>
>> >> >> Being new to Maven myself, there could there be an option in the
>> POM
>> >> that
>> >> >> might be forcing a full build each time?
>> >> >>
>> >> >> I would think that as long as you aren't specifying "clean" in your
>> >> build
>> >> >> kickoff process or otherwise forcing a full biuld, you should only
>> be
>> >> >> getting the incremental build, no? Am I off in my understanding?
>> >> >> On Wed, Feb 16, 2011 at 10:18 AM, Zilvinas Vilutis
>> >> >> <ci...@gmail.com>wrote:
>> >> >>
>> >> >> > Yes,
>> >> >> >
>> >> >> > However it does a "full build" which takes ~30-40 minutes. But I
>> >> want
>> >> >> > to build only specific projects and their dependents.
>> >> >> >
>> >> >> > Regards
>> >> >> >
>> >> >> > Žilvinas Vilutis
>> >> >> >
>> >> >> > Mobile: (+370) 652 38353
>> >> >> > E-mail: cikasfm@gmail.com
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > On Wed, Feb 16, 2011 at 9:54 AM, Leon Rosenberg
>> >> >> > <ro...@gmail.com> wrote:
>> >> >> > > How about hudson?
>> >> >> > >
>> >> >> > > Hudson can watch for svn changes and trigger builds on commit.
>> >> >> > >
>> >> >> > > regards
>> >> >> > > Leon
>> >> >> > >
>> >> >> > > On Wed, Feb 16, 2011 at 5:46 PM, Zilvinas Vilutis
>> >> <ci...@gmail.com>
>> >> >> > wrote:
>> >> >> > >> Hello Maven Users!
>> >> >> > >>
>> >> >> > >> Probably this question was already asked, so if there is an
>> >> answer
>> >> >> > >> which I could not find - please point me to the right place.
>> >> >> > >>
>> >> >> > >>
>> >> >> > >> I'm working on an enterprise project where maven integration
>> >> plays a
>> >> >> > huge role.
>> >> >> > >>
>> >> >> > >> However the project is big as a lot of teams are working on it
>> >> and it
>> >> >> > >> takes quite some time to build it ( 30-40 minutes ), which I
>> need
>> >> to
>> >> >> > >> do every morning after an svn update.
>> >> >> > >>
>> >> >> > >>
>> >> >> > >> So I was thinking - is there any way to configure maven to
>> build
>> >> only
>> >> >> > >> the projects which were updated by SVN ( e.g. in the script
>> time
>> >> )?
>> >> >> > >>
>> >> >> > >>
>> >> >> > >> Most likely there is no direct answer...however, I think that
>> I
>> >> could
>> >> >> > >> find a way to gather the project names which were updated in
>> the
>> >> >> > >> shell
>> >> >> > >> script - then I could pass the list of project names to maven
>> >> >> > >> command.
>> >> >> > >> Is there any way to make sure that those and dependent
>> projects
>> >> would
>> >> >> > >> be built in the right order?
>> >> >> > >>
>> >> >> > >>
>> >> >> > >> The project structure is:
>> >> >> > >>
>> >> >> > >> parent
>> >> >> > >> -- subsystem1
>> >> >> > >> -- s1-project1
>> >> >> > >> -- s1-project2
>> >> >> > >> -- subsystem2
>> >> >> > >> -- s2-project1
>> >> >> > >> -- s2-project2
>> >> >> > >> -- s2-project3
>> >> >> > >> -- subsystem3
>> >> >> > >> -- s3-project1
>> >> >> > >>
>> >> >> > >>
>> >> >> > >> Thank you for any ideas!
>> >> >> > >>
>> >> >> > >>
>> >> >> > >> Žilvinas Vilutis
>> >> >> > >>
>> >> >> > >> Mobile: (+370) 652 38353
>> >> >> > >> E-mail: cikasfm@gmail.com
>> >> >> > >>
>> >> >> > >> --------------------------------------------------------------
>> ---
>> >> ----
>> >> >> > >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> >> >> > >> For additional commands, e-mail: users-help@maven.apache.org
>> >> >> > >>
>> >> >> > >>
>> >> >> > >
>> >> >> >
>> >> >> > -----------------------------------------------------------------
>> ---
>> >> -
>> >> >> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> >> >> > For additional commands, e-mail: users-help@maven.apache.org
>> >> >> >
>> >> >> >
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Jeff Vincent
>> >> >> predatorvi@gmail.com
>> >> >> See my LinkedIn profile at:
>> >> >> http://www.linkedin.com/in/rjeffreyvincent
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Cesar De la Cruz Rojas
>> >> > --------------------------------------------------------------------
>> ---
>> >> ------
>> >> > Sennior Software Engineer
>> >> > --------------------------------------------------------------------
>> ---
>> >> ------
>> >> > Follow me in Facebook : http://www.facebook.com/aquiles.geo
>> >> > Twitter http://twitter.com/ageo
>> >> > Picture blog http://ageo.deviantart.com
>> >> >
>> >> >
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> >> For additional commands, e-mail: users-help@maven.apache.org
>> >
>> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: subversion vs maven
Posted by "Thiessen, Todd (Todd)" <tt...@avaya.com>.
You could control your dependencies by checking out which ever dependencies you care about and ensure you build those as well. Normally, you would just want the snapshot versions anyway. There is also a properity in your settings.xml file to instruct maven to never check for updates. To get latest snapshot artifacts you would have to issue a mvn -U.
The whole idea here is that you should only every be compiling and downloading what you need. Let your CI server do the full builds. You should rarely have to.
> -----Original Message-----
> From: Zilvinas Vilutis [mailto:cikasfm@gmail.com]
> Sent: Wednesday, February 16, 2011 1:52 PM
> To: Maven Users List
> Cc: Thiessen, Todd (Todd)
> Subject: Re: subversion vs maven
>
> yes, we could set this up.
>
> However there's 2 things:
> - We're working with "SNAPSHOT" versions most of the time with CI you
> can hardly control when to use YOUR code versus from the repo in a big
> projcet
> - I'm working in a client's office and the network latency between our
> office and clients office would make it slow
>
> I could run a CI / Hundson / whatever other build management server on
> my laptop...but then it would not be quicker then just the full build
> :)
>
> Žilvinas Vilutis
>
> Mobile: (+370) 652 38353
> E-mail: cikasfm@gmail.com
>
>
>
> On Wed, Feb 16, 2011 at 11:41 AM, Thiessen, Todd (Todd)
> <tt...@avaya.com> wrote:
> > If you have a CI server already building everything, why do you need to
> build everything every morning? Can't you just checkout only the one
> module you need to change and build that?
> >
> >> -----Original Message-----
> >> From: Zilvinas Vilutis [mailto:cikasfm@gmail.com]
> >> Sent: Wednesday, February 16, 2011 1:37 PM
> >> To: a.geo
> >> Cc: Maven Users List; Jeff
> >> Subject: Re: subversion vs maven
> >>
> >> trust me, not so easy :)
> >>
> >> our project has like 20 subsystems which all have 5-10 sub-projects.
> >>
> >> Our "core" is extracted into a separate dependency maintained by
> >> another team, it is also managed by maven ( ~30 subsystems, 10-50
> >> projects each ).
> >>
> >> Yes, daily updates happen on 5-10 projects, that is why I don't want
> >> to build the "full" build but only the changed projects and their
> >> dependents ( web apps ).
> >>
> >> Žilvinas Vilutis
> >>
> >> Mobile: (+370) 652 38353
> >> E-mail: cikasfm@gmail.com
> >>
> >>
> >>
> >> On Wed, Feb 16, 2011 at 10:37 AM, a.geo <aq...@gmail.com> wrote:
> >> > You mus consider a "core" section, that contain your business main
> >> code,
> >> > usually you don't change it. Around it, is the implementation of the
> >> > requirement.
> >> >
> >> >
> >> >
> >> > 2011/2/16 Jeff <pr...@gmail.com>
> >> >>
> >> >> Maybe this question will expose my ignorance, but I thought most
> build
> >> >> systems only build the things that have changed unless you do a
> >> "clean"
> >> >> each
> >> >> time or are starting from a fresh checkout as opposed to doing an
> "svn
> >> >> update" and then running the build.
> >> >>
> >> >> Being new to Maven myself, there could there be an option in the
> POM
> >> that
> >> >> might be forcing a full build each time?
> >> >>
> >> >> I would think that as long as you aren't specifying "clean" in your
> >> build
> >> >> kickoff process or otherwise forcing a full biuld, you should only
> be
> >> >> getting the incremental build, no? Am I off in my understanding?
> >> >> On Wed, Feb 16, 2011 at 10:18 AM, Zilvinas Vilutis
> >> >> <ci...@gmail.com>wrote:
> >> >>
> >> >> > Yes,
> >> >> >
> >> >> > However it does a "full build" which takes ~30-40 minutes. But I
> >> want
> >> >> > to build only specific projects and their dependents.
> >> >> >
> >> >> > Regards
> >> >> >
> >> >> > Žilvinas Vilutis
> >> >> >
> >> >> > Mobile: (+370) 652 38353
> >> >> > E-mail: cikasfm@gmail.com
> >> >> >
> >> >> >
> >> >> >
> >> >> > On Wed, Feb 16, 2011 at 9:54 AM, Leon Rosenberg
> >> >> > <ro...@gmail.com> wrote:
> >> >> > > How about hudson?
> >> >> > >
> >> >> > > Hudson can watch for svn changes and trigger builds on commit.
> >> >> > >
> >> >> > > regards
> >> >> > > Leon
> >> >> > >
> >> >> > > On Wed, Feb 16, 2011 at 5:46 PM, Zilvinas Vilutis
> >> <ci...@gmail.com>
> >> >> > wrote:
> >> >> > >> Hello Maven Users!
> >> >> > >>
> >> >> > >> Probably this question was already asked, so if there is an
> >> answer
> >> >> > >> which I could not find - please point me to the right place.
> >> >> > >>
> >> >> > >>
> >> >> > >> I'm working on an enterprise project where maven integration
> >> plays a
> >> >> > huge role.
> >> >> > >>
> >> >> > >> However the project is big as a lot of teams are working on it
> >> and it
> >> >> > >> takes quite some time to build it ( 30-40 minutes ), which I
> need
> >> to
> >> >> > >> do every morning after an svn update.
> >> >> > >>
> >> >> > >>
> >> >> > >> So I was thinking - is there any way to configure maven to
> build
> >> only
> >> >> > >> the projects which were updated by SVN ( e.g. in the script
> time
> >> )?
> >> >> > >>
> >> >> > >>
> >> >> > >> Most likely there is no direct answer...however, I think that
> I
> >> could
> >> >> > >> find a way to gather the project names which were updated in
> the
> >> >> > >> shell
> >> >> > >> script - then I could pass the list of project names to maven
> >> >> > >> command.
> >> >> > >> Is there any way to make sure that those and dependent
> projects
> >> would
> >> >> > >> be built in the right order?
> >> >> > >>
> >> >> > >>
> >> >> > >> The project structure is:
> >> >> > >>
> >> >> > >> parent
> >> >> > >> -- subsystem1
> >> >> > >> -- s1-project1
> >> >> > >> -- s1-project2
> >> >> > >> -- subsystem2
> >> >> > >> -- s2-project1
> >> >> > >> -- s2-project2
> >> >> > >> -- s2-project3
> >> >> > >> -- subsystem3
> >> >> > >> -- s3-project1
> >> >> > >>
> >> >> > >>
> >> >> > >> Thank you for any ideas!
> >> >> > >>
> >> >> > >>
> >> >> > >> Žilvinas Vilutis
> >> >> > >>
> >> >> > >> Mobile: (+370) 652 38353
> >> >> > >> E-mail: cikasfm@gmail.com
> >> >> > >>
> >> >> > >> --------------------------------------------------------------
> ---
> >> ----
> >> >> > >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> >> > >> For additional commands, e-mail: users-help@maven.apache.org
> >> >> > >>
> >> >> > >>
> >> >> > >
> >> >> >
> >> >> > -----------------------------------------------------------------
> ---
> >> -
> >> >> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> >> > For additional commands, e-mail: users-help@maven.apache.org
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >> --
> >> >> Jeff Vincent
> >> >> predatorvi@gmail.com
> >> >> See my LinkedIn profile at:
> >> >> http://www.linkedin.com/in/rjeffreyvincent
> >> >
> >> >
> >> >
> >> > --
> >> > Cesar De la Cruz Rojas
> >> > --------------------------------------------------------------------
> ---
> >> ------
> >> > Sennior Software Engineer
> >> > --------------------------------------------------------------------
> ---
> >> ------
> >> > Follow me in Facebook : http://www.facebook.com/aquiles.geo
> >> > Twitter http://twitter.com/ageo
> >> > Picture blog http://ageo.deviantart.com
> >> >
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: subversion vs maven
Posted by Zilvinas Vilutis <ci...@gmail.com>.
yes, we could set this up.
However there's 2 things:
- We're working with "SNAPSHOT" versions most of the time with CI you
can hardly control when to use YOUR code versus from the repo in a big
projcet
- I'm working in a client's office and the network latency between our
office and clients office would make it slow
I could run a CI / Hundson / whatever other build management server on
my laptop...but then it would not be quicker then just the full build
:)
Žilvinas Vilutis
Mobile: (+370) 652 38353
E-mail: cikasfm@gmail.com
On Wed, Feb 16, 2011 at 11:41 AM, Thiessen, Todd (Todd)
<tt...@avaya.com> wrote:
> If you have a CI server already building everything, why do you need to build everything every morning? Can't you just checkout only the one module you need to change and build that?
>
>> -----Original Message-----
>> From: Zilvinas Vilutis [mailto:cikasfm@gmail.com]
>> Sent: Wednesday, February 16, 2011 1:37 PM
>> To: a.geo
>> Cc: Maven Users List; Jeff
>> Subject: Re: subversion vs maven
>>
>> trust me, not so easy :)
>>
>> our project has like 20 subsystems which all have 5-10 sub-projects.
>>
>> Our "core" is extracted into a separate dependency maintained by
>> another team, it is also managed by maven ( ~30 subsystems, 10-50
>> projects each ).
>>
>> Yes, daily updates happen on 5-10 projects, that is why I don't want
>> to build the "full" build but only the changed projects and their
>> dependents ( web apps ).
>>
>> Žilvinas Vilutis
>>
>> Mobile: (+370) 652 38353
>> E-mail: cikasfm@gmail.com
>>
>>
>>
>> On Wed, Feb 16, 2011 at 10:37 AM, a.geo <aq...@gmail.com> wrote:
>> > You mus consider a "core" section, that contain your business main
>> code,
>> > usually you don't change it. Around it, is the implementation of the
>> > requirement.
>> >
>> >
>> >
>> > 2011/2/16 Jeff <pr...@gmail.com>
>> >>
>> >> Maybe this question will expose my ignorance, but I thought most build
>> >> systems only build the things that have changed unless you do a
>> "clean"
>> >> each
>> >> time or are starting from a fresh checkout as opposed to doing an "svn
>> >> update" and then running the build.
>> >>
>> >> Being new to Maven myself, there could there be an option in the POM
>> that
>> >> might be forcing a full build each time?
>> >>
>> >> I would think that as long as you aren't specifying "clean" in your
>> build
>> >> kickoff process or otherwise forcing a full biuld, you should only be
>> >> getting the incremental build, no? Am I off in my understanding?
>> >> On Wed, Feb 16, 2011 at 10:18 AM, Zilvinas Vilutis
>> >> <ci...@gmail.com>wrote:
>> >>
>> >> > Yes,
>> >> >
>> >> > However it does a "full build" which takes ~30-40 minutes. But I
>> want
>> >> > to build only specific projects and their dependents.
>> >> >
>> >> > Regards
>> >> >
>> >> > Žilvinas Vilutis
>> >> >
>> >> > Mobile: (+370) 652 38353
>> >> > E-mail: cikasfm@gmail.com
>> >> >
>> >> >
>> >> >
>> >> > On Wed, Feb 16, 2011 at 9:54 AM, Leon Rosenberg
>> >> > <ro...@gmail.com> wrote:
>> >> > > How about hudson?
>> >> > >
>> >> > > Hudson can watch for svn changes and trigger builds on commit.
>> >> > >
>> >> > > regards
>> >> > > Leon
>> >> > >
>> >> > > On Wed, Feb 16, 2011 at 5:46 PM, Zilvinas Vilutis
>> <ci...@gmail.com>
>> >> > wrote:
>> >> > >> Hello Maven Users!
>> >> > >>
>> >> > >> Probably this question was already asked, so if there is an
>> answer
>> >> > >> which I could not find - please point me to the right place.
>> >> > >>
>> >> > >>
>> >> > >> I'm working on an enterprise project where maven integration
>> plays a
>> >> > huge role.
>> >> > >>
>> >> > >> However the project is big as a lot of teams are working on it
>> and it
>> >> > >> takes quite some time to build it ( 30-40 minutes ), which I need
>> to
>> >> > >> do every morning after an svn update.
>> >> > >>
>> >> > >>
>> >> > >> So I was thinking - is there any way to configure maven to build
>> only
>> >> > >> the projects which were updated by SVN ( e.g. in the script time
>> )?
>> >> > >>
>> >> > >>
>> >> > >> Most likely there is no direct answer...however, I think that I
>> could
>> >> > >> find a way to gather the project names which were updated in the
>> >> > >> shell
>> >> > >> script - then I could pass the list of project names to maven
>> >> > >> command.
>> >> > >> Is there any way to make sure that those and dependent projects
>> would
>> >> > >> be built in the right order?
>> >> > >>
>> >> > >>
>> >> > >> The project structure is:
>> >> > >>
>> >> > >> parent
>> >> > >> -- subsystem1
>> >> > >> -- s1-project1
>> >> > >> -- s1-project2
>> >> > >> -- subsystem2
>> >> > >> -- s2-project1
>> >> > >> -- s2-project2
>> >> > >> -- s2-project3
>> >> > >> -- subsystem3
>> >> > >> -- s3-project1
>> >> > >>
>> >> > >>
>> >> > >> Thank you for any ideas!
>> >> > >>
>> >> > >>
>> >> > >> Žilvinas Vilutis
>> >> > >>
>> >> > >> Mobile: (+370) 652 38353
>> >> > >> E-mail: cikasfm@gmail.com
>> >> > >>
>> >> > >> -----------------------------------------------------------------
>> ----
>> >> > >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> >> > >> For additional commands, e-mail: users-help@maven.apache.org
>> >> > >>
>> >> > >>
>> >> > >
>> >> >
>> >> > --------------------------------------------------------------------
>> -
>> >> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> >> > For additional commands, e-mail: users-help@maven.apache.org
>> >> >
>> >> >
>> >>
>> >>
>> >> --
>> >> Jeff Vincent
>> >> predatorvi@gmail.com
>> >> See my LinkedIn profile at:
>> >> http://www.linkedin.com/in/rjeffreyvincent
>> >
>> >
>> >
>> > --
>> > Cesar De la Cruz Rojas
>> > -----------------------------------------------------------------------
>> ------
>> > Sennior Software Engineer
>> > -----------------------------------------------------------------------
>> ------
>> > Follow me in Facebook : http://www.facebook.com/aquiles.geo
>> > Twitter http://twitter.com/ageo
>> > Picture blog http://ageo.deviantart.com
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: subversion vs maven
Posted by "Thiessen, Todd (Todd)" <tt...@avaya.com>.
If you have a CI server already building everything, why do you need to build everything every morning? Can't you just checkout only the one module you need to change and build that?
> -----Original Message-----
> From: Zilvinas Vilutis [mailto:cikasfm@gmail.com]
> Sent: Wednesday, February 16, 2011 1:37 PM
> To: a.geo
> Cc: Maven Users List; Jeff
> Subject: Re: subversion vs maven
>
> trust me, not so easy :)
>
> our project has like 20 subsystems which all have 5-10 sub-projects.
>
> Our "core" is extracted into a separate dependency maintained by
> another team, it is also managed by maven ( ~30 subsystems, 10-50
> projects each ).
>
> Yes, daily updates happen on 5-10 projects, that is why I don't want
> to build the "full" build but only the changed projects and their
> dependents ( web apps ).
>
> Žilvinas Vilutis
>
> Mobile: (+370) 652 38353
> E-mail: cikasfm@gmail.com
>
>
>
> On Wed, Feb 16, 2011 at 10:37 AM, a.geo <aq...@gmail.com> wrote:
> > You mus consider a "core" section, that contain your business main
> code,
> > usually you don't change it. Around it, is the implementation of the
> > requirement.
> >
> >
> >
> > 2011/2/16 Jeff <pr...@gmail.com>
> >>
> >> Maybe this question will expose my ignorance, but I thought most build
> >> systems only build the things that have changed unless you do a
> "clean"
> >> each
> >> time or are starting from a fresh checkout as opposed to doing an "svn
> >> update" and then running the build.
> >>
> >> Being new to Maven myself, there could there be an option in the POM
> that
> >> might be forcing a full build each time?
> >>
> >> I would think that as long as you aren't specifying "clean" in your
> build
> >> kickoff process or otherwise forcing a full biuld, you should only be
> >> getting the incremental build, no? Am I off in my understanding?
> >> On Wed, Feb 16, 2011 at 10:18 AM, Zilvinas Vilutis
> >> <ci...@gmail.com>wrote:
> >>
> >> > Yes,
> >> >
> >> > However it does a "full build" which takes ~30-40 minutes. But I
> want
> >> > to build only specific projects and their dependents.
> >> >
> >> > Regards
> >> >
> >> > Žilvinas Vilutis
> >> >
> >> > Mobile: (+370) 652 38353
> >> > E-mail: cikasfm@gmail.com
> >> >
> >> >
> >> >
> >> > On Wed, Feb 16, 2011 at 9:54 AM, Leon Rosenberg
> >> > <ro...@gmail.com> wrote:
> >> > > How about hudson?
> >> > >
> >> > > Hudson can watch for svn changes and trigger builds on commit.
> >> > >
> >> > > regards
> >> > > Leon
> >> > >
> >> > > On Wed, Feb 16, 2011 at 5:46 PM, Zilvinas Vilutis
> <ci...@gmail.com>
> >> > wrote:
> >> > >> Hello Maven Users!
> >> > >>
> >> > >> Probably this question was already asked, so if there is an
> answer
> >> > >> which I could not find - please point me to the right place.
> >> > >>
> >> > >>
> >> > >> I'm working on an enterprise project where maven integration
> plays a
> >> > huge role.
> >> > >>
> >> > >> However the project is big as a lot of teams are working on it
> and it
> >> > >> takes quite some time to build it ( 30-40 minutes ), which I need
> to
> >> > >> do every morning after an svn update.
> >> > >>
> >> > >>
> >> > >> So I was thinking - is there any way to configure maven to build
> only
> >> > >> the projects which were updated by SVN ( e.g. in the script time
> )?
> >> > >>
> >> > >>
> >> > >> Most likely there is no direct answer...however, I think that I
> could
> >> > >> find a way to gather the project names which were updated in the
> >> > >> shell
> >> > >> script - then I could pass the list of project names to maven
> >> > >> command.
> >> > >> Is there any way to make sure that those and dependent projects
> would
> >> > >> be built in the right order?
> >> > >>
> >> > >>
> >> > >> The project structure is:
> >> > >>
> >> > >> parent
> >> > >> -- subsystem1
> >> > >> -- s1-project1
> >> > >> -- s1-project2
> >> > >> -- subsystem2
> >> > >> -- s2-project1
> >> > >> -- s2-project2
> >> > >> -- s2-project3
> >> > >> -- subsystem3
> >> > >> -- s3-project1
> >> > >>
> >> > >>
> >> > >> Thank you for any ideas!
> >> > >>
> >> > >>
> >> > >> Žilvinas Vilutis
> >> > >>
> >> > >> Mobile: (+370) 652 38353
> >> > >> E-mail: cikasfm@gmail.com
> >> > >>
> >> > >> -----------------------------------------------------------------
> ----
> >> > >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> > >> For additional commands, e-mail: users-help@maven.apache.org
> >> > >>
> >> > >>
> >> > >
> >> >
> >> > --------------------------------------------------------------------
> -
> >> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> > For additional commands, e-mail: users-help@maven.apache.org
> >> >
> >> >
> >>
> >>
> >> --
> >> Jeff Vincent
> >> predatorvi@gmail.com
> >> See my LinkedIn profile at:
> >> http://www.linkedin.com/in/rjeffreyvincent
> >
> >
> >
> > --
> > Cesar De la Cruz Rojas
> > -----------------------------------------------------------------------
> ------
> > Sennior Software Engineer
> > -----------------------------------------------------------------------
> ------
> > Follow me in Facebook : http://www.facebook.com/aquiles.geo
> > Twitter http://twitter.com/ageo
> > Picture blog http://ageo.deviantart.com
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
Re: subversion vs maven
Posted by Zilvinas Vilutis <ci...@gmail.com>.
trust me, not so easy :)
our project has like 20 subsystems which all have 5-10 sub-projects.
Our "core" is extracted into a separate dependency maintained by
another team, it is also managed by maven ( ~30 subsystems, 10-50
projects each ).
Yes, daily updates happen on 5-10 projects, that is why I don't want
to build the "full" build but only the changed projects and their
dependents ( web apps ).
Žilvinas Vilutis
Mobile: (+370) 652 38353
E-mail: cikasfm@gmail.com
On Wed, Feb 16, 2011 at 10:37 AM, a.geo <aq...@gmail.com> wrote:
> You mus consider a "core" section, that contain your business main code,
> usually you don't change it. Around it, is the implementation of the
> requirement.
>
>
>
> 2011/2/16 Jeff <pr...@gmail.com>
>>
>> Maybe this question will expose my ignorance, but I thought most build
>> systems only build the things that have changed unless you do a "clean"
>> each
>> time or are starting from a fresh checkout as opposed to doing an "svn
>> update" and then running the build.
>>
>> Being new to Maven myself, there could there be an option in the POM that
>> might be forcing a full build each time?
>>
>> I would think that as long as you aren't specifying "clean" in your build
>> kickoff process or otherwise forcing a full biuld, you should only be
>> getting the incremental build, no? Am I off in my understanding?
>> On Wed, Feb 16, 2011 at 10:18 AM, Zilvinas Vilutis
>> <ci...@gmail.com>wrote:
>>
>> > Yes,
>> >
>> > However it does a "full build" which takes ~30-40 minutes. But I want
>> > to build only specific projects and their dependents.
>> >
>> > Regards
>> >
>> > Žilvinas Vilutis
>> >
>> > Mobile: (+370) 652 38353
>> > E-mail: cikasfm@gmail.com
>> >
>> >
>> >
>> > On Wed, Feb 16, 2011 at 9:54 AM, Leon Rosenberg
>> > <ro...@gmail.com> wrote:
>> > > How about hudson?
>> > >
>> > > Hudson can watch for svn changes and trigger builds on commit.
>> > >
>> > > regards
>> > > Leon
>> > >
>> > > On Wed, Feb 16, 2011 at 5:46 PM, Zilvinas Vilutis <ci...@gmail.com>
>> > wrote:
>> > >> Hello Maven Users!
>> > >>
>> > >> Probably this question was already asked, so if there is an answer
>> > >> which I could not find - please point me to the right place.
>> > >>
>> > >>
>> > >> I'm working on an enterprise project where maven integration plays a
>> > huge role.
>> > >>
>> > >> However the project is big as a lot of teams are working on it and it
>> > >> takes quite some time to build it ( 30-40 minutes ), which I need to
>> > >> do every morning after an svn update.
>> > >>
>> > >>
>> > >> So I was thinking - is there any way to configure maven to build only
>> > >> the projects which were updated by SVN ( e.g. in the script time )?
>> > >>
>> > >>
>> > >> Most likely there is no direct answer...however, I think that I could
>> > >> find a way to gather the project names which were updated in the
>> > >> shell
>> > >> script - then I could pass the list of project names to maven
>> > >> command.
>> > >> Is there any way to make sure that those and dependent projects would
>> > >> be built in the right order?
>> > >>
>> > >>
>> > >> The project structure is:
>> > >>
>> > >> parent
>> > >> -- subsystem1
>> > >> -- s1-project1
>> > >> -- s1-project2
>> > >> -- subsystem2
>> > >> -- s2-project1
>> > >> -- s2-project2
>> > >> -- s2-project3
>> > >> -- subsystem3
>> > >> -- s3-project1
>> > >>
>> > >>
>> > >> Thank you for any ideas!
>> > >>
>> > >>
>> > >> Žilvinas Vilutis
>> > >>
>> > >> Mobile: (+370) 652 38353
>> > >> E-mail: cikasfm@gmail.com
>> > >>
>> > >> ---------------------------------------------------------------------
>> > >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> > >> For additional commands, e-mail: users-help@maven.apache.org
>> > >>
>> > >>
>> > >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> > For additional commands, e-mail: users-help@maven.apache.org
>> >
>> >
>>
>>
>> --
>> Jeff Vincent
>> predatorvi@gmail.com
>> See my LinkedIn profile at:
>> http://www.linkedin.com/in/rjeffreyvincent
>
>
>
> --
> Cesar De la Cruz Rojas
> -----------------------------------------------------------------------------
> Sennior Software Engineer
> -----------------------------------------------------------------------------
> Follow me in Facebook : http://www.facebook.com/aquiles.geo
> Twitter http://twitter.com/ageo
> Picture blog http://ageo.deviantart.com
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: subversion vs maven
Posted by "a.geo" <aq...@gmail.com>.
You mus consider a "core" section, that contain your business main code,
usually you don't change it. Around it, is the implementation of the
requirement.
2011/2/16 Jeff <pr...@gmail.com>
> Maybe this question will expose my ignorance, but I thought most build
> systems only build the things that have changed unless you do a "clean"
> each
> time or are starting from a fresh checkout as opposed to doing an "svn
> update" and then running the build.
>
> Being new to Maven myself, there could there be an option in the POM that
> might be forcing a full build each time?
>
> I would think that as long as you aren't specifying "clean" in your build
> kickoff process or otherwise forcing a full biuld, you should only be
> getting the incremental build, no? Am I off in my understanding?
> On Wed, Feb 16, 2011 at 10:18 AM, Zilvinas Vilutis <cikasfm@gmail.com
> >wrote:
>
> > Yes,
> >
> > However it does a "full build" which takes ~30-40 minutes. But I want
> > to build only specific projects and their dependents.
> >
> > Regards
> >
> > Žilvinas Vilutis
> >
> > Mobile: (+370) 652 38353
> > E-mail: cikasfm@gmail.com
> >
> >
> >
> > On Wed, Feb 16, 2011 at 9:54 AM, Leon Rosenberg
> > <ro...@gmail.com> wrote:
> > > How about hudson?
> > >
> > > Hudson can watch for svn changes and trigger builds on commit.
> > >
> > > regards
> > > Leon
> > >
> > > On Wed, Feb 16, 2011 at 5:46 PM, Zilvinas Vilutis <ci...@gmail.com>
> > wrote:
> > >> Hello Maven Users!
> > >>
> > >> Probably this question was already asked, so if there is an answer
> > >> which I could not find - please point me to the right place.
> > >>
> > >>
> > >> I'm working on an enterprise project where maven integration plays a
> > huge role.
> > >>
> > >> However the project is big as a lot of teams are working on it and it
> > >> takes quite some time to build it ( 30-40 minutes ), which I need to
> > >> do every morning after an svn update.
> > >>
> > >>
> > >> So I was thinking - is there any way to configure maven to build only
> > >> the projects which were updated by SVN ( e.g. in the script time )?
> > >>
> > >>
> > >> Most likely there is no direct answer...however, I think that I could
> > >> find a way to gather the project names which were updated in the shell
> > >> script - then I could pass the list of project names to maven command.
> > >> Is there any way to make sure that those and dependent projects would
> > >> be built in the right order?
> > >>
> > >>
> > >> The project structure is:
> > >>
> > >> parent
> > >> -- subsystem1
> > >> -- s1-project1
> > >> -- s1-project2
> > >> -- subsystem2
> > >> -- s2-project1
> > >> -- s2-project2
> > >> -- s2-project3
> > >> -- subsystem3
> > >> -- s3-project1
> > >>
> > >>
> > >> Thank you for any ideas!
> > >>
> > >>
> > >> Žilvinas Vilutis
> > >>
> > >> Mobile: (+370) 652 38353
> > >> E-mail: cikasfm@gmail.com
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > >> For additional commands, e-mail: users-help@maven.apache.org
> > >>
> > >>
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
> --
> Jeff Vincent
> predatorvi@gmail.com
> See my LinkedIn profile at:
> http://www.linkedin.com/in/rjeffreyvincent
>
--
Cesar De la Cruz Rojas
*
-----------------------------------------------------------------------------
*
Sennior Software Engineer
-----------------------------------------------------------------------------
Follow me in Facebook : http://www.facebook.com/aquiles.geo
Twitter http://twitter.com/ageo
Picture blog http://ageo.deviantart.com
Re: subversion vs maven
Posted by Jeff <pr...@gmail.com>.
Maybe this question will expose my ignorance, but I thought most build
systems only build the things that have changed unless you do a "clean" each
time or are starting from a fresh checkout as opposed to doing an "svn
update" and then running the build.
Being new to Maven myself, there could there be an option in the POM that
might be forcing a full build each time?
I would think that as long as you aren't specifying "clean" in your build
kickoff process or otherwise forcing a full biuld, you should only be
getting the incremental build, no? Am I off in my understanding?
On Wed, Feb 16, 2011 at 10:18 AM, Zilvinas Vilutis <ci...@gmail.com>wrote:
> Yes,
>
> However it does a "full build" which takes ~30-40 minutes. But I want
> to build only specific projects and their dependents.
>
> Regards
>
> Žilvinas Vilutis
>
> Mobile: (+370) 652 38353
> E-mail: cikasfm@gmail.com
>
>
>
> On Wed, Feb 16, 2011 at 9:54 AM, Leon Rosenberg
> <ro...@gmail.com> wrote:
> > How about hudson?
> >
> > Hudson can watch for svn changes and trigger builds on commit.
> >
> > regards
> > Leon
> >
> > On Wed, Feb 16, 2011 at 5:46 PM, Zilvinas Vilutis <ci...@gmail.com>
> wrote:
> >> Hello Maven Users!
> >>
> >> Probably this question was already asked, so if there is an answer
> >> which I could not find - please point me to the right place.
> >>
> >>
> >> I'm working on an enterprise project where maven integration plays a
> huge role.
> >>
> >> However the project is big as a lot of teams are working on it and it
> >> takes quite some time to build it ( 30-40 minutes ), which I need to
> >> do every morning after an svn update.
> >>
> >>
> >> So I was thinking - is there any way to configure maven to build only
> >> the projects which were updated by SVN ( e.g. in the script time )?
> >>
> >>
> >> Most likely there is no direct answer...however, I think that I could
> >> find a way to gather the project names which were updated in the shell
> >> script - then I could pass the list of project names to maven command.
> >> Is there any way to make sure that those and dependent projects would
> >> be built in the right order?
> >>
> >>
> >> The project structure is:
> >>
> >> parent
> >> -- subsystem1
> >> -- s1-project1
> >> -- s1-project2
> >> -- subsystem2
> >> -- s2-project1
> >> -- s2-project2
> >> -- s2-project3
> >> -- subsystem3
> >> -- s3-project1
> >>
> >>
> >> Thank you for any ideas!
> >>
> >>
> >> Žilvinas Vilutis
> >>
> >> Mobile: (+370) 652 38353
> >> E-mail: cikasfm@gmail.com
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Jeff Vincent
predatorvi@gmail.com
See my LinkedIn profile at:
http://www.linkedin.com/in/rjeffreyvincent
Re: subversion vs maven
Posted by Zilvinas Vilutis <ci...@gmail.com>.
Oh, the "-pl" option seems to be one of the possible solutions.
Thank you!!
Žilvinas Vilutis
Mobile: (+370) 652 38353
E-mail: cikasfm@gmail.com
On Wed, Feb 16, 2011 at 10:21 AM, Nord, James <JN...@nds.com> wrote:
> There is an option "Incremental build - only build changed modules" under the advanced section of the Build options (for an M2 build).
>
> If checked, Hudson will only build any modules with changes from SCM and any modules which depend on those changed modules, using Maven's "-amd -pl group1:artifact1,group1:artifact2" command-line options. If the SCM reports no changes to any modules, however, all modules will be built. See http://docs.codehaus.org/display/MAVEN/Make+Like+Reactor+Mode for more information on the Maven behavior this utilizes.
>
> This functionality requires Maven 2.1 or later, and will not have any impact if "Build modules in parallel" is selected.
>
> Any follow-up on this should be directed at the Jenkins or Hudson users lists.
>
> /James
>
> -----Original Message-----
> From: Zilvinas Vilutis [mailto:cikasfm@gmail.com]
> Sent: 16 February 2011 17:18
> To: Leon Rosenberg
> Cc: Maven Users List
> Subject: Re: subversion vs maven
>
> Yes,
>
> However it does a "full build" which takes ~30-40 minutes. But I want to build only specific projects and their dependents.
>
> Regards
>
> Žilvinas Vilutis
>
> Mobile: (+370) 652 38353
> E-mail: cikasfm@gmail.com
>
>
>
> On Wed, Feb 16, 2011 at 9:54 AM, Leon Rosenberg <ro...@gmail.com> wrote:
>> How about hudson?
>>
>> Hudson can watch for svn changes and trigger builds on commit.
>>
>> regards
>> Leon
>>
>> On Wed, Feb 16, 2011 at 5:46 PM, Zilvinas Vilutis <ci...@gmail.com> wrote:
>>> Hello Maven Users!
>>>
>>> Probably this question was already asked, so if there is an answer
>>> which I could not find - please point me to the right place.
>>>
>>>
>>> I'm working on an enterprise project where maven integration plays a huge role.
>>>
>>> However the project is big as a lot of teams are working on it and it
>>> takes quite some time to build it ( 30-40 minutes ), which I need to
>>> do every morning after an svn update.
>>>
>>>
>>> So I was thinking - is there any way to configure maven to build only
>>> the projects which were updated by SVN ( e.g. in the script time )?
>>>
>>>
>>> Most likely there is no direct answer...however, I think that I could
>>> find a way to gather the project names which were updated in the
>>> shell script - then I could pass the list of project names to maven command.
>>> Is there any way to make sure that those and dependent projects would
>>> be built in the right order?
>>>
>>>
>>> The project structure is:
>>>
>>> parent
>>> -- subsystem1
>>> -- s1-project1
>>> -- s1-project2
>>> -- subsystem2
>>> -- s2-project1
>>> -- s2-project2
>>> -- s2-project3
>>> -- subsystem3
>>> -- s3-project1
>>>
>>>
>>> Thank you for any ideas!
>>>
>>>
>>> Žilvinas Vilutis
>>>
>>> Mobile: (+370) 652 38353
>>> E-mail: cikasfm@gmail.com
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
> **************************************************************************************
> This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary.
>
> NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00
> **************************************************************************************
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: subversion vs maven
Posted by "Nord, James" <JN...@nds.com>.
There is an option "Incremental build - only build changed modules" under the advanced section of the Build options (for an M2 build).
If checked, Hudson will only build any modules with changes from SCM and any modules which depend on those changed modules, using Maven's "-amd -pl group1:artifact1,group1:artifact2" command-line options. If the SCM reports no changes to any modules, however, all modules will be built. See http://docs.codehaus.org/display/MAVEN/Make+Like+Reactor+Mode for more information on the Maven behavior this utilizes.
This functionality requires Maven 2.1 or later, and will not have any impact if "Build modules in parallel" is selected.
Any follow-up on this should be directed at the Jenkins or Hudson users lists.
/James
-----Original Message-----
From: Zilvinas Vilutis [mailto:cikasfm@gmail.com]
Sent: 16 February 2011 17:18
To: Leon Rosenberg
Cc: Maven Users List
Subject: Re: subversion vs maven
Yes,
However it does a "full build" which takes ~30-40 minutes. But I want to build only specific projects and their dependents.
Regards
Žilvinas Vilutis
Mobile: (+370) 652 38353
E-mail: cikasfm@gmail.com
On Wed, Feb 16, 2011 at 9:54 AM, Leon Rosenberg <ro...@gmail.com> wrote:
> How about hudson?
>
> Hudson can watch for svn changes and trigger builds on commit.
>
> regards
> Leon
>
> On Wed, Feb 16, 2011 at 5:46 PM, Zilvinas Vilutis <ci...@gmail.com> wrote:
>> Hello Maven Users!
>>
>> Probably this question was already asked, so if there is an answer
>> which I could not find - please point me to the right place.
>>
>>
>> I'm working on an enterprise project where maven integration plays a huge role.
>>
>> However the project is big as a lot of teams are working on it and it
>> takes quite some time to build it ( 30-40 minutes ), which I need to
>> do every morning after an svn update.
>>
>>
>> So I was thinking - is there any way to configure maven to build only
>> the projects which were updated by SVN ( e.g. in the script time )?
>>
>>
>> Most likely there is no direct answer...however, I think that I could
>> find a way to gather the project names which were updated in the
>> shell script - then I could pass the list of project names to maven command.
>> Is there any way to make sure that those and dependent projects would
>> be built in the right order?
>>
>>
>> The project structure is:
>>
>> parent
>> -- subsystem1
>> -- s1-project1
>> -- s1-project2
>> -- subsystem2
>> -- s2-project1
>> -- s2-project2
>> -- s2-project3
>> -- subsystem3
>> -- s3-project1
>>
>>
>> Thank you for any ideas!
>>
>>
>> Žilvinas Vilutis
>>
>> Mobile: (+370) 652 38353
>> E-mail: cikasfm@gmail.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
**************************************************************************************
This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary.
NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00
**************************************************************************************
Re: subversion vs maven
Posted by Zilvinas Vilutis <ci...@gmail.com>.
Yes,
However it does a "full build" which takes ~30-40 minutes. But I want
to build only specific projects and their dependents.
Regards
Žilvinas Vilutis
Mobile: (+370) 652 38353
E-mail: cikasfm@gmail.com
On Wed, Feb 16, 2011 at 9:54 AM, Leon Rosenberg
<ro...@gmail.com> wrote:
> How about hudson?
>
> Hudson can watch for svn changes and trigger builds on commit.
>
> regards
> Leon
>
> On Wed, Feb 16, 2011 at 5:46 PM, Zilvinas Vilutis <ci...@gmail.com> wrote:
>> Hello Maven Users!
>>
>> Probably this question was already asked, so if there is an answer
>> which I could not find - please point me to the right place.
>>
>>
>> I'm working on an enterprise project where maven integration plays a huge role.
>>
>> However the project is big as a lot of teams are working on it and it
>> takes quite some time to build it ( 30-40 minutes ), which I need to
>> do every morning after an svn update.
>>
>>
>> So I was thinking - is there any way to configure maven to build only
>> the projects which were updated by SVN ( e.g. in the script time )?
>>
>>
>> Most likely there is no direct answer...however, I think that I could
>> find a way to gather the project names which were updated in the shell
>> script - then I could pass the list of project names to maven command.
>> Is there any way to make sure that those and dependent projects would
>> be built in the right order?
>>
>>
>> The project structure is:
>>
>> parent
>> -- subsystem1
>> -- s1-project1
>> -- s1-project2
>> -- subsystem2
>> -- s2-project1
>> -- s2-project2
>> -- s2-project3
>> -- subsystem3
>> -- s3-project1
>>
>>
>> Thank you for any ideas!
>>
>>
>> Žilvinas Vilutis
>>
>> Mobile: (+370) 652 38353
>> E-mail: cikasfm@gmail.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: subversion vs maven
Posted by Leon Rosenberg <ro...@gmail.com>.
How about hudson?
Hudson can watch for svn changes and trigger builds on commit.
regards
Leon
On Wed, Feb 16, 2011 at 5:46 PM, Zilvinas Vilutis <ci...@gmail.com> wrote:
> Hello Maven Users!
>
> Probably this question was already asked, so if there is an answer
> which I could not find - please point me to the right place.
>
>
> I'm working on an enterprise project where maven integration plays a huge role.
>
> However the project is big as a lot of teams are working on it and it
> takes quite some time to build it ( 30-40 minutes ), which I need to
> do every morning after an svn update.
>
>
> So I was thinking - is there any way to configure maven to build only
> the projects which were updated by SVN ( e.g. in the script time )?
>
>
> Most likely there is no direct answer...however, I think that I could
> find a way to gather the project names which were updated in the shell
> script - then I could pass the list of project names to maven command.
> Is there any way to make sure that those and dependent projects would
> be built in the right order?
>
>
> The project structure is:
>
> parent
> -- subsystem1
> -- s1-project1
> -- s1-project2
> -- subsystem2
> -- s2-project1
> -- s2-project2
> -- s2-project3
> -- subsystem3
> -- s3-project1
>
>
> Thank you for any ideas!
>
>
> Žilvinas Vilutis
>
> Mobile: (+370) 652 38353
> E-mail: cikasfm@gmail.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org