Re: Maven port to current version 3

Hi Hussayn,

concerning your question for the "decision process":
The step was proposed and explained in the first post of this thread=20
including a request for comments/suggestions.
The second post pointed out the changes made on the branch and announced=20
the merge to the trunk - including an according ticket SCB3096 on the=20
selfhost.
As there were no objections, Johannes went on and merged as announced.=20
We think this is the way to go - remarks/comments/hints?

The two main goals we want to achieve by switching to maven were:
* using a *single* build tool to easy the build process
* provide the basis for being able to update the used libraries -=20
relying on publicly available and released versions.
The second point is still not done, but as you might see on the Turbine4=20
branch, we hope the get this resolved as soon as Turbine 4 will released.
Additionally we hope to improve the options for future=20
improvements/changes concerning the used libraries/frameworks, but this=20
may be a roadmap/what's next topic we should (and like to) discuss separatl=
y

regards,
Frank

Am 27.04.2012 00:34, schrieb Hussayn Dabbous:
> Who has decided that ant is no longer supported to build Scarab ?
>
> regards,
> Hussayn
>
> Am 26.04.2012 11:34, schrieb Johannes H=C3=B6chst=C3=A4dter:
>> Hi all,
>>
>> SCB3096: Today I merged our current branch for Maven 3 port back to trun=
k.
>>
>> You now will need:
>> * scarab-maven-plugin installed (extensions directory)
>> * all patched and licensed libraries installed in your local repo, see
>> www/repository/README.txt
>> * Maven 3
>>
>> Ant is not longer supported for building Scarab.
>>
>> cheers,
>> Johannes
>>
>> Am 17.04.2012 16:49, schrieb Johannes H=C3=B6chst=C3=A4dter:
>>> Am 17.04.2012 16:17, schrieb Hussayn Dabbous:
>>>> Hi, Johannes;
>>>>
>>>> Are you going to completely remove the ant build ?
>>>> I remember a discussion about kicking ant in favor
>>>> of maven-2 some time ago. At that time there was
>>>> strong evidence to keep ant although i do not rember
>>>> the exact reasoning.
>>> Yes, removing Ant is the plan for Scarab's build. We want to migrate th=
e
>>> whole build to Maven 3, to avoid a two-tier build system. Keeping Ant
>>> for this has no reason for us.
>>>
>>>> Are you aware of the fact that ant is also used during
>>>> runtime
>>> Can you please point out where Ant is used exactly during runtime, and
>>> how this is related to the build? Are you sure that this is still in
>>> use? For webinstall we have this standalone webapp as alternative as yo=
u
>>> can see here: http://itlabs.memocomp.de/ScarabWebBuilder.
>>>> and the ant jars are also deployed to WEB-INF/lib ?
>>> The default war build, by "package", from Maven is taken, which deploys
>>> all jars correctly.
>>>> Are you going to remove this dependency also ?
>>>> And how would the normal build change with Maven-3 ?
>>> As you might know, Maven and Ant behave nearly compatible, so no real
>>> "change" is expected, e.g. for some special Ant tasks of Scarab we use
>>> Mojos for Maven now, but there are some differences in our plan. The
>>> major one might be:  All jars will be taken from official Maven
>>> repositories during build, and no local repository is kept, as this is
>>> not the way to go for Maven I think. You are free to set up a proxy for
>>> this, Nexus or else, or use your own local repository, as this should b=
e
>>> more comfortable.
>>>
>>> cheers,
>>> Johannes
>>>
>>>
>>>     Am 17.04.2012 15:57, schrieb Johannes H=C3=B6chst=C3=A4dter:
>>>>> Hi,
>>>>>
>>>>> the branch work for the announced maven port seems to be done. For th=
is
>>>>> reason we want to merge the resulting sources back to trunk at the en=
d
>>>>> of next week.
>>>>>
>>>>> We opened an issue for this: SCB3096.
>>>>>
>>>>> cheers,
>>>>> Johannes
>>>>>
>>>>> Am 16.04.2012 15:22, schrieb Johannes H=C3=B6chst=C3=A4dter:
>>>>>> Hi everybody,
>>>>>>
>>>>>> back on trunk, we want to migrate Scarab's build to Maven, and to st=
art
>>>>>> to get rid of the dependencies to the build tools Ant and Maven 1.1.
>>>>>>
>>>>>> Therefore we have the following suggestion:
>>>>>>
>>>>>> * There will be a new dependant project scarab-maven-plugin which
>>>>>> contains a Maven plugin for some special Scarab build tasks e.g. the
>>>>>> database. This subproject will reside in directory
>>>>>> "Scarab/extensions/scarab-maven-plugin" for now.
>>>>>>
>>>>>> We will start the Maven port soon, on a newly created branch. For us=
,
>>>>>> Maven 3 is a good choice and our currently working build environment=
 for
>>>>>> Scarab.
>>>>>>
>>>>>> We are looking forward to your replies if there are any suggestions.=
..
>>>>>>
>>>>>> cheers,
>>>>>> Johannes
>>>>>>
>

------------------------------------------------------
http://scarab.tigris.org/ds/viewMessage.do?dsForumId=3D455&dsMessageId=3D29=
56201

To unsubscribe from this discussion, e-mail: [[email protected]=
.org].