directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Felix Knecht <fel...@apache.org>
Subject Re: Buildsystem studio
Date Thu, 18 Oct 2007 09:22:06 GMT
Emmanuel Lecharny schrieb:
> You are right, Felix.
>
> However, when Studio has been started, back one year and a half, we
> were still fighting with Maven (not sure we moved to Maven 2 yet), and
> trust me, it was a nightmare...
>
>   
I can imagin ...

> Situation is way better now, and we are considering the transition
> from ant to maven, but we will do it if and only if we have a clear
> solution to manage the packaging for multiple platforms. 

What do you mean by 'clear'?
You can have different profiles activated either by the os of your
building the system on or by indicating the profile (=platform) to use. E.g.

    <profiles>
        <profile>
            <id>org.eclipse.swt.win32</id>
            <activation>
                <os>
                    <name>windows xp</name>
                    <arch>x86</arch>
                </os>
            </activation>
            <dependencies>
                <dependency>
                    <groupId>org.eclipse.swt</groupId>
                    <artifactId>org.eclipse.swt.win32.win32.x86</artifactId>
                    <version>3.2.1</version>
                    <type>jar</type>
                </dependency>
            </dependencies>
        </profile>
        <profile>
            <id>org.eclipse.swt.macosx</id>
            <activation>
                <os>
                    <name>mac os x</name>
                    <arch>i386</arch>
                </os>
            </activation>
            <dependencies>
                <dependency>
                    <groupId>org.eclipse.swt</groupId>
                    <artifactId>org.eclipse.swt.carbon.macosx</artifactId>
                    <version>3.2.1</version>
                    <type>jar</type>
                </dependency>
            </dependencies>
        </profile>

To build dist for different platforms of the rcp (I think for the
plugins (updatesite) the platform doesn't matters) you can have
different assemblys (profile-driven). To build dist for more than one
platform use
mvn clean install -Porg.eclipse.swt.win32,org.eclipse.swt.macosx
Whill build dist for win32 and macosx

> The Studio
> team is regularly looking for the best way to do that (and we
> discussed about that with the Maven guys in May).
>
> At this point, any help is welcomed !
>
> On 10/18/07, Felix Knecht <felixk@apache.org> wrote:
>   
>>> Thanks for trying to find a way to build Studio with Maven. :)
>>> Do you think there could be any benefit we could gain from using Maven
>>> instead of the current build system ?
>>> I'm just wondering if it's worth changing of build system...
>>>       
>> - Well, it looked somehow strange to me using different buildsystems
>> within a project (directory).
>> - From a POV as developer I don't like having different build systems
>> within a main project. You need to have knowledge of different build
>> systems developing 'at the bleeding edge'. From a community view you
>> don't need to have different 'build specialists' to fix/adapt/maintain
>> the build- / deployment- and release-process.
>> - I think it's easier to maintain 1 build system all over the top
>> project because you're able to use knowledge and other synergies.
>> - It reduces the learning curve for developers having a kind of standard
>> within the main project. You also use coding standards to make life
>> easier and code better readable.
>>
>> I'm not saying that maven is more preferable than ant/ivy but it just
>> looks strange to me having different build systems for subprojects
>> within a project (and less subprojects use ant/ivy than maven).
>>
>> Regards
>> Felix
>>
>>
>>     
>
>
>   


Mime
View raw message