directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre-Arnaud Marcelot" ...@marcelot.net>
Subject [Studio] Heavy refactoring on Studio's build (was Re: [Studio] Using the Maven Release Plugin)
Date Tue, 23 Sep 2008 14:54:36 GMT
Hi all,

[WARNING]
I'm in the process of removing the MANIFEST.MF files from SVN and replace
them by generated ones.
This, and the modifications we've been doing with Felix on the Maven Studio
plugin, may have a huge impact on the build until everything has been
migrated.

Don't be surprised if you get a build error from time to time, or if the
generated RCP application does not work...
[/WARNING]

Just wanted to warn everybody. ;)

Regards,
Pierre-Arnaud

On Tue, Sep 23, 2008 at 2:15 PM, Pierre-Arnaud Marcelot <pa@marcelot.net>wrote:

> On Tue, Sep 23, 2008 at 2:07 PM, Felix Knecht <felixk@apache.org> wrote:
>
>> If we manage to get the eclipse:eclipse forked this shouldn't be a
>> problem anymore.
>
>
> Yeah, as we're running a command line, instead of just running 'mvn
> eclipse:eclipse', we could be running 'mvn eclipe:eclipse bundle:manifest'.
>
> We then also should think about adding the manifest
>> goal to the release plugin definition (meaning clone the one from the
>> TLP pom and add the manifest goal) to make sure that the latest uptodate
>> manifest is in the release.
>
>
> I don't think it's necessary, because it will still be defined in the
> pom.xml file of the project and the file won't be in SVN anymore... So the
> generated manifest will contain up-to-date informations about the version,
> dependencies versions etc.
>
>
>> ATM I try to get the eclipse:eclipse forked stuff running.
>
>
> Thanks!
>
> Regards,
> Pierre-Arnaud
>
>

Mime
View raw message