Re: Maven port to current version 3

Hi, frank;

While your general description about how a decision should be done is
the way to go, i feel a bit pushed by your move. I have already expressed
some doubts in the thread. I pointed out that ant is used not only for
building but also during runtime and i have not checked if you got that=20
addressed
with your changes.

So now i have to ask the question how you can remove working functionality
without getting approval first. I thought we had started the process of
discussion, but you just went ahead without waiting for the decisions.
It would have been fair at least to ask back if all project owners=20
approve the change.
Just remember, that i am one of them and it was me who has been maintaining
the trunk version almost alone for the last 2 years...

Although i appreciate your intentions, i still believe that was no good=20
move.
Especially i rely on ant to work and i have maintained the ant build all=20
the time
since about 6 years i believe. So i strongly believe that you just can=20
not drop
this work without full project owner approval.

I have not yet checked if "skipping support for ant" is equal to "make=20
it impossible
to build with ant" or just "maintenance has been dropped". but even that is
very questionable as i am actually doing maintenance for the ant build.

So have you dropped my work then ?
That would be unfair to the least without my approval,
even if you and us where the only users of Scarab.

However, i do not want to block any improvements on Scarab,
i actually appreciate that you are back on the track, and that
gives me some "hope for the future of Scarab"!

But i think that you have to take care of a few constraints. Here
is what should be done IMHO:

1.) Switch from Maven1 to maven3 is ok for me as long
       as the maintenance functions for builders are kept
       intact:
       - update repository
       - update the default build properties files
       - update the properties documentation.

2.) Keep ant support intact until all builders/developers have
       approved that they are willing to switch (better  "have switched")
       from ant to maven3

3.) Ensure that complete removal of ant also keeps deploying and
      starting Scarab intact. I know there is a dependencency to ant in=20
the code
      during the startup sequence. I have added that by myself
      about 4 years ago.

4.) Strongly support local build directories! there are users who
      explicitly have addressed this topic in the past. Scarab must be
      buildable without internet access and out of the distribution package=
.
      And that's the main reason why we have the build repository
      distributed along with Scarab.

Can you accept this roadmap ? then all is well ...

regards,
Hussayn


On 30.04.2012 11:44, memoComp Open Source Team wrote:
> Hi Hussayn,
>
> concerning your question for the "decision process":
> The step was proposed and explained in the first post of this thread
> including a request for comments/suggestions.
> The second post pointed out the changes made on the branch and announced
> the merge to the trunk - including an according ticket SCB3096 on the
> selfhost.
> As there were no objections, Johannes went on and merged as announced.
> 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 -
> relying on publicly available and released versions.
> The second point is still not done, but as you might see on the Turbine4
> branch, we hope the get this resolved as soon as Turbine 4 will released.
> Additionally we hope to improve the options for future
> improvements/changes concerning the used libraries/frameworks, but this
> may be a roadmap/what's next topic we should (and like to) discuss separa=
tly
>
> 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 tru=
nk.
>>>
>>> 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 t=
he
>>>> 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 y=
ou
>>>> 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 deploy=
s
>>>> 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 fo=
r
>>>> this, Nexus or else, or use your own local repository, as this should =
be
>>>> 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 t=
his
>>>>>> reason we want to merge the resulting sources back to trunk at the e=
nd
>>>>>> 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 s=
tart
>>>>>>> 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. th=
e
>>>>>>> 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 u=
s,
>>>>>>> Maven 3 is a good choice and our currently working build environmen=
t 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=3D=
2956201
>
> To unsubscribe from this discussion, e-mail: [[email protected]=
is.org].

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

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