Re: Maven port to current version 3
Hussayn Dabbous <[email protected]> Fri, 27 Apr 2012 00:34:13 +0200
| Newsgroups | gmane.comp.java.scarab.devel |
|---|---|
| Message-ID | <[email protected]> |
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 trunk= . > > You now will need: > * scarab-maven-plugin installed (extensions directory) > * all patched and licensed libraries installed in your local repo, see=20 > 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 the >> 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 you >> 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 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 thi= s >>>> reason we want to merge the resulting sources back to trunk at the end >>>> 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 sta= rt >>>>> 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 >>>>> --=20 Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenh=C3=B6fer Allee 125 D 50935 K=C3=B6ln tel.: 0221 560 1111 http://www.saxess.de ------------------------------------------------------ http://scarab.tigris.org/ds/viewMessage.do?dsForumId=3D455&dsMessageId=3D29= 53158 To unsubscribe from this discussion, e-mail: [[email protected]= .org].