You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Felix Knecht <fe...@apache.org> on 2007/10/17 08:37:07 UTC
Buildsystem studio
Hi all
I don't want to wake up sleeping dogs and fore sure there exists already
a lot of threads about this subject, but googling on the
mail-archives.apache.org (I haven't found a search functionality at the
mail-archives itself) didn't point me to a final decision.
The buildsystem for studio is ant/ivy based whereas all the others are
maven2 based. Is this on purpose (for a special reason) or just
historical based and not yet migrated?
Regards
Felix
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
Stefan Seelmann schrieb:
> Hi Felix,
>
> you have to use -Dstudio... instead of -Dldapstudio. I guess you get the
> wrong parameter from the "Building" website? I corrected it there, sorry
> for the incorrect information.
No problem. I experienced myself in 'my' project that at some point the deployed documentation gets outdated and nobody
notices it as all changes are already well known to everybody participating the project because of various reasons (e.g.
well discussed on a mailing list).
Thanks for updating the site - your really fast ;-)
Regards
Felix
> Regards,
> Stefan Seelmann
>
>
> Felix Knecht schrieb:
>> Try to create a simular build mechanism for maven as ant/ivy does at the moment I run into an unexpected situation using
>> ant/ivy (I'm using a linux amd64 machine):
>>
>> when I execute from project root
>> 'ANT_OPTS="-Xmx1024m -XX:MaxPermSize=1024m" ant -Dldapstudio-rcp.os.name=win32 -Dldapstudio-rcp.os.arch=x86'
>> I would expect to have in the target/ApacheDirectoryStudio directory a working app for windows. But I can't see a file
>> ApacheDirectoryStudio.exe instead I do have an executable file ApacheDirectoryStudio which I'm able to run and the
>> application starts (still under linux).
>>
>> Is this a special problem of mine or did somebody else noticed simular behaviour?
>>
>> Thanks and regards
>> Felix
>>
>
Re: Buildsystem studio
Posted by Stefan Seelmann <se...@apache.org>.
Hi Felix,
you have to use -Dstudio... instead of -Dldapstudio. I guess you get the
wrong paramter from the "Building" website? I corrected it there, sorry
for the incorrect information.
Regards,
Stefan Seelmann
Felix Knecht schrieb:
> Try to create a simular build mechanism for maven as ant/ivy does at the moment I run into an unexpected situation using
> ant/ivy (I'm using a linux amd64 machine):
>
> when I execute from project root
> 'ANT_OPTS="-Xmx1024m -XX:MaxPermSize=1024m" ant -Dldapstudio-rcp.os.name=win32 -Dldapstudio-rcp.os.arch=x86'
> I would expect to have in the target/ApacheDirectoryStudio directory a working app for windows. But I can't see a file
> ApacheDirectoryStudio.exe instead I do have an executable file ApacheDirectoryStudio which I'm able to run and the
> application starts (still under linux).
>
> Is this a special problem of mine or did somebody else noticed simular behaviour?
>
> Thanks and regards
> Felix
>
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
Try to create a simular build mechanism for maven as ant/ivy does at the moment I run into an unexpected situation using
ant/ivy (I'm using a linux amd64 machine):
when I execute from project root
'ANT_OPTS="-Xmx1024m -XX:MaxPermSize=1024m" ant -Dldapstudio-rcp.os.name=win32 -Dldapstudio-rcp.os.arch=x86'
I would expect to have in the target/ApacheDirectoryStudio directory a working app for windows. But I can't see a file
ApacheDirectoryStudio.exe instead I do have an executable file ApacheDirectoryStudio which I'm able to run and the
application starts (still under linux).
Is this a special problem of mine or did somebody else noticed simular behaviour?
Thanks and regards
Felix
Re: Buildsystem studio
Posted by Emmanuel Lecharny <el...@gmail.com>.
Stefan Seelmann wrote:
> Felix Knecht schrieb:
>
>> I've still no commit access to the sandbox directory.
>>
>
> That's bad. Emmanuel, could you help please?
>
Damnit !!! I have added Felix to the authorized committers, but I forgot
to commit the file :)
Fixed.
--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org
Re: Buildsystem studio
Posted by Emmanuel Lecharny <el...@gmail.com>.
>> Yes, we have a continous build. Chris Custine set it up together with PAM.
>>
>
> Is this 'tool' based or just a cron job - or do I missunderstand PAM (Pluggable Authentication Modul)?
>
It's a tool based.
Pam = Pierre-Arnaud Marcelot, aka 'Plugin Apache Master' ;)
> Felix
>
>
>
--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org
Re: Buildsystem studio
Posted by Stefan Seelmann <se...@apache.org>.
Felix Knecht schrieb:
>>> Never the less I started to adapt the doc "Build Apache Directory
>>> Studio" and put it into the Apache Directory Sandbox [1] (I think that's the way do to).
>>>
>> Just perfect, is the maven build already working? I am very curious :-)
>
> More or less. I can build
> - userguides
> - updatesite
> - single distribution for linux (at least I could yesterday).
>
> At the moment there are some things still done via ant-run tasks within maven. This could be avoided writing our own
> maven plugins for this.
>
>> Yes, we have a continous build. Chris Custine set it up together with PAM.
>
> Is this 'tool' based or just a cron job - or do I missunderstand PAM (Pluggable Authentication Modul)?
>
Oh, sorry. PAM is the acronym of Pierre-Arnaud Marcelot ;-)
@Chris, Pierre-Arnaud: Could you please give some more information?
Regards,
Stefan
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
>> Never the less I started to adapt the doc "Build Apache Directory
>> Studio" and put it into the Apache Directory Sandbox [1] (I think that's the way do to).
>>
>
> Just perfect, is the maven build already working? I am very curious :-)
More or less. I can build
- userguides
- updatesite
- single distribution for linux (at least I could yesterday).
At the moment there are some things still done via ant-run tasks within maven. This could be avoided writing our own
maven plugins for this.
>
> Yes, we have a continous build. Chris Custine set it up together with PAM.
Is this 'tool' based or just a cron job - or do I missunderstand PAM (Pluggable Authentication Modul)?
Felix
Re: Buildsystem studio
Posted by Stefan Seelmann <se...@apache.org>.
Felix Knecht schrieb:
> I've still no commit access to the sandbox directory.
That's bad. Emmanuel, could you help please?
> Never the less I started to adapt the doc "Build Apache Directory
> Studio" and put it into the Apache Directory Sandbox [1] (I think that's the way do to).
>
Just perfect, is the maven build already working? I am very curious :-)
> Still some questions I couldn't find (or haven't seen) an answer in the docs:
>
> a) Which svn:keywords are set and used? Looking at some files I can see different svn:keywords set, but they not always
> seem to match with the references in the code.
>
> If no rule exists yet I'd like to suggest the following:
>
> svn:keyword Id
>
> /**
> * Foo bar
> *
> * @author <a href="mailto:dev@directory.apache.org">Apache Directory Project</a>
> * @version $Id: AbstractStudioMojo.java 350 2007-10-28 12:01:17Z felix $
> */
>
Hm, I am not familiar with svn:keywords. However in our source file we
use the following header:
/**
* ...
*
* @author <a href="mailto:dev@directory.apache.org">Apache Directory
Project</a>
* @version $Rev$, $Date$
*/
> b) I haven't found any documentation about project/modules/code which is done automatically (e.g. maven reports, maven
> site, JavaDocs, ...).
> Is this all done either in the cwiki or packaged into a downloadable/buildable distribution?
>
We have an ant task "javadoc" to generate Javadocs. But no other
automatically generated docu. The other cwiki pages are created manually.
>
> c) Do any ideas about automated continuous integration exists, e.g. continuum?
Yes, we have a continous build. Chris Custine set it up together with PAM.
>
> Regards
> Felix
>
> [1] http://cwiki.apache.org/confluence/x/txEB
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
After having some diner apologize for the questions below. For sure you'll this has been discussed in the beginning and
it's not up to me to rise such questions (they just came up because obviously not that much people new about the CI server).
Reading Chris' mail to setup a new server maybe this weekend it's definitely not the time to put a working system into
question.
Sorry
Felix
>>
>> I think Chris setup TeamCity from JetBrains on his servers.
>
> Just back from the TeamCity page to questions:
> 1. maven 2.0.6 is bundled but you can also configure an external one 2.0.4 - 2.0.6. We should be sure that 2.0.7 works
> also because 2.0.6 is quite buggy (probably it will work).
> 2. It's recommend to use MySQL instead of hsqldb as backend db. I'm not sure if ASF can run into license problems when
> using MySQL instead of hsqldb (which I also wouldn't recommend). This should be check in advance even when we get
> TeamCity as OSS project for free.
> 3. Do we have some (internal or external) synergies when using TeamCity instead of an ASF product?
>
>
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
>
> >
> > c) Do any ideas about automated continuous integration exists,
> e.g. continuum?
> >
> We tried continuum once upon a time, we also tried bamboo, and we
> currently have some another continuous integration server running,
>
>
> I think Chris setup TeamCity from JetBrains on his servers.
Just back from the TeamCity page to questions:
1. maven 2.0.6 is bundled but you can also configure an external one 2.0.4 - 2.0.6. We should be sure that 2.0.7 works
also because 2.0.6 is quite buggy (probably it will work).
2. It's recommend to use MySQL instead of hsqldb as backend db. I'm not sure if ASF can run into license problems when
using MySQL instead of hsqldb (which I also wouldn't recommend). This should be check in advance even when we get
TeamCity as OSS project for free.
3. Do we have some (internal or external) synergies when using TeamCity instead of an ASF product?
Once Chris
> get's some free
> time we intend to move this setup over to a dedicated server with much
> more power and
> network bandwidth. The resources have been acquired it's just a time thing.
>
> Felix if you want to be involved in building up this environment let me
> know and we can
> work together with Chris as well to set it up sooner rather than later.
>
If I can help I'll do.
> but
> we would like to speed up the tests a lot before fully activating the
> continuous build again. FYI, building the server 'cost' 20 minutes on my
> laptop, and around 10 minutes on a fast server. We also have had by
> spamming experience with continuous integration (a mail every 3 minutes
> sent to the full dev list - 200 peeps - 2 days long ...), so we are not
> really keen to play this game again, unless someone who *knows* how to
> correctly setup such an environment handle it (ie, not me, obviously :)
>
>
> Yes this was killing Chris' hardware and there were some other issues.
> However
> we should not have the same issues with the new dedicated machine. Once
> we have
> this changelog and the ability to revert the server for tests instead of
> stopping,
> destroying, reinstalling and restarting the server the tests will run on
> the order of
> 5-10X faster. I personally use a ramdrive to speed things up but I only
> get a 2X
> improvement: this is a hack.
>
> Anyways I would like to setup the new build/CI server to do a few things:
>
> o synchronize a partial read-only mirror repository off of
> http://svn.apache.org/repos/asf/directory
> o use this read-only repository for checkouts and to trigger events via
> custom hooks
> - takes load off of Apache repository
> - much faster since checkouts are local
> - simplifies managing custom hooks
> o build unofficial daily snapshots and expose for testing and download
> o perform standard CI sequence with repository changes
> o integrate VSLDAP conformance tests with CI on dedicated VSLDAP server
> o deploy builds to SLAMD environment for accumulating a panel of simple
> performance metrics
> used to correlate changes to the server
>
> This is pretty ambitious and will take some time but we have the tools
> to do the job. The pay
> off I think with automating all this is huge and so the time expense is
> well worth it.
Yep it sounds like a lot of work is waiting.
Felix
>
> Alex
>
>
>
>
>
Re: Buildsystem studio
Posted by Alex Karasulu <ak...@apache.org>.
Hi guys,
On 11/5/07, Emmanuel Lecharny <el...@gmail.com> wrote:
>
> Hi Felix,
>
> Felix Knecht wrote:
> > I've still no commit access to the sandbox directory. Never the less I
> started to adapt the doc "Build Apache Directory
> > Studio" and put it into the Apache Directory Sandbox [1] (I think that's
> the way do to).
> >
> Hmmm... Let me check that this afternoon...
> > Still some questions I couldn't find (or haven't seen) an answer in the
> docs:
> >
> > a) Which svn:keywords are set and used? Looking at some files I can see
> different svn:keywords set, but they not always
> > seem to match with the references in the code.
> >
> There is no current list of used svn:keywords...
> > If no rule exists yet I'd like to suggest the following:
> >
> > svn:keyword Id
> >
> > /**
> > * Foo bar
> > *
> > * @author <a href="mailto:dev@directory.apache.org">Apache Directory
> Project</a>
> > * @version $Id: AbstractStudioMojo.java 350 2007-10-28 12:01:17Z felix
> $
> > */
> >
> We are not using names into header. Here are our coding standards :
>
> http://cwiki.apache.org/DIRxDEV/coding-standards.html
I guess this is the result of a substitution performed by SVN on the Id
macro. I don't think
Felix was intending to add an @author tag which is essentially the basis of
the ASF wide
recommendation.
I know there are distinct rules about the @author tag but did we ever agree
on whether or not
to use other tags like Id, Date, Revision etc? Can't remember sorry.
> b) I haven't found any documentation about project/modules/code which is
> done automatically (e.g. maven reports, maven
> > site, JavaDocs, ...).
> > Is this all done either in the cwiki or packaged into a
> downloadable/buildable distribution?
> >
> We don't anymore generate the site from code, we use confluence for that.
>
> We should generate Javadocs though, but I'm not a maven guru enough to
> guarantee that the current maven configuration allows that. And I would
> add that I would be very pleased if you can tell me ;)
>
> Generating maven reports would be a very valuable addition, too !
+1
It would be nice if we integrated nicely the javadocs and reports so they
deployed to areas that our
confluence generated site can point to by default.
>
> > c) Do any ideas about automated continuous integration exists, e.g.
> continuum?
> >
> We tried continuum once upon a time, we also tried bamboo, and we
> currently have some another continuous integration server running,
I think Chris setup TeamCity from JetBrains on his servers. Once Chris
get's some free
time we intend to move this setup over to a dedicated server with much more
power and
network bandwidth. The resources have been acquired it's just a time thing.
Felix if you want to be involved in building up this environment let me know
and we can
work together with Chris as well to set it up sooner rather than later.
but
> we would like to speed up the tests a lot before fully activating the
> continuous build again. FYI, building the server 'cost' 20 minutes on my
> laptop, and around 10 minutes on a fast server. We also have had by
> spamming experience with continuous integration (a mail every 3 minutes
> sent to the full dev list - 200 peeps - 2 days long ...), so we are not
> really keen to play this game again, unless someone who *knows* how to
> correctly setup such an environment handle it (ie, not me, obviously :)
Yes this was killing Chris' hardware and there were some other issues.
However
we should not have the same issues with the new dedicated machine. Once we
have
this changelog and the ability to revert the server for tests instead of
stopping,
destroying, reinstalling and restarting the server the tests will run on the
order of
5-10X faster. I personally use a ramdrive to speed things up but I only get
a 2X
improvement: this is a hack.
Anyways I would like to setup the new build/CI server to do a few things:
o synchronize a partial read-only mirror repository off of
http://svn.apache.org/repos/asf/directory
o use this read-only repository for checkouts and to trigger events via
custom hooks
- takes load off of Apache repository
- much faster since checkouts are local
- simplifies managing custom hooks
o build unofficial daily snapshots and expose for testing and download
o perform standard CI sequence with repository changes
o integrate VSLDAP conformance tests with CI on dedicated VSLDAP server
o deploy builds to SLAMD environment for accumulating a panel of simple
performance metrics
used to correlate changes to the server
This is pretty ambitious and will take some time but we have the tools to do
the job. The pay
off I think with automating all this is huge and so the time expense is well
worth it.
Alex
Re: Buildsystem studio
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Hey Chris,
No problem.
Tell me if you need some help to build this up.
P-A
On Nov 5, 2007 8:06 PM, Chris Custine <cc...@apache.org> wrote:
>
> We are in the process of moving the build server over to a more powerful
> platform and I have been delayed because of the new job. I think we have
> all of the hardware in order now so maybe this weekend...
>
> Chris
>
Re: Buildsystem studio
Posted by Chris Custine <cc...@apache.org>.
On 11/5/07, Pierre-Arnaud Marcelot <pa...@marcelot.net> wrote:
>
> Hi Felix and everyone,
>
> I can't wait to test this new Maven build... :)
>
> As Stefan said, we have a continuous integration build system running on
> Chris Custine's server. The address is : http://builds.organicelement.com, but it seems to be down today...
We are in the process of moving the build server over to a more powerful
platform and I have been delayed because of the new job. I think we have
all of the hardware in order now so maybe this weekend...
Chris
As far as I remember the server is running TeamCity and uses the 'release'
> ant task from Studio's build system to generate archives (.zip and .tar.gz
> files) for each OS/Platform.
>
> Regards,
> Pierre-Arnaud (aka PAM...)
>
> On Nov 5, 2007 11:57 AM, Felix Knecht <fe...@apache.org> wrote:
>
> > >>
> > > There is no current list of used svn:keywords...
> > >> If no rule exists yet I'd like to suggest the following:
> > >>
> > >> svn:keyword Id
> > >>
> > >> /**
> > >> * Foo bar
> > >> *
> > >> * @author <a href="mailto:dev@directory.apache.org">Apache Directory
> > >> Project</a>
> > >> * @version $Id: AbstractStudioMojo.java 350 2007-10-28 12:01:17Z
> > felix $
> > >> */
> > >>
> > > We are not using names into header. Here are our coding standards :
> > >
> > > http://cwiki.apache.org/DIRxDEV/coding-standards.html
> >
> > It's not a fix name, but just the name of the committer who did the
> > latest commit:
> >
> >
> > http://svnbook.red-bean.com/en/1.4/svn.advanced.props.special.keywords.html
> >
> > In most java classes I can find the svn:keywords [date and/or revision]
> > already now. But they are not used consequently
> > the same way and also not always set as svn:keywords to the file when
> > used within the file.
> >
> > >
> > >> b) I haven't found any documentation about project/modules/code which
> > >> is done automatically (e.g. maven reports, maven
> > >> site, JavaDocs, ...).
> > >> Is this all done either in the cwiki or packaged into a
> > >> downloadable/buildable distribution?
> > >>
> > > We don't anymore generate the site from code, we use confluence for
> > that.
> > >
> > > We should generate Javadocs though, but I'm not a maven guru enough to
> >
> > > guarantee that the current maven configuration allows that. And I
> > would
> > > add that I would be very pleased if you can tell me ;)
> > >
> > > Generating maven reports would be a very valuable addition, too !
> >
> > I'll try to add this to the maven studio build.
> >
> > >>
> > >> c) Do any ideas about automated continuous integration exists, e.g.
> > >> continuum?
> > >>
> > > We tried continuum once upon a time, we also tried bamboo, and we
> > > currently have some another continuous integration server running, but
> > > we would like to speed up the tests a lot before fully activating the
> > > continuous build again. FYI, building the server 'cost' 20 minutes on
> > my
> > > laptop, and around 10 minutes on a fast server. We also have had by
> > > spamming experience with continuous integration (a mail every 3
> > minutes
> > > sent to the full dev list - 200 peeps - 2 days long ...), so we are
> > not
> > > really keen to play this game again, unless someone who *knows* how to
> > > correctly setup such an environment handle it (ie, not me, obviously
> > :)
> >
> > I think there are already running some continuum instances within
> > apache. Maybe the infrastructure team has more
> > knowledge about such running instances and if the directory project can
> > hang on onto an already existing instance.
> >
> >
> > > I have added you in
> > > http://cwiki.apache.org/confluence/display/directory/The+team
> >
> > Thanks. I already did but haven't noticed the alphabetic ordering and
> > added me at the bottom. So this is fixed now.
> > >
> > > Fell free to add a picture (small one :), your web site, blog, to this
> > > page !
> >
> > I only have my companys website if this would also be ok?
> >
> > >
> > > Thanks !
> > >
> >
> >
>
Re: Buildsystem studio
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Hi Felix and everyone,
I can't wait to test this new Maven build... :)
As Stefan said, we have a continuous integration build system running on
Chris Custine's server. The address is : http://builds.organicelement.com ,
but it seems to be down today...
As far as I remember the server is running TeamCity and uses the 'release'
ant task from Studio's build system to generate archives (.zip and .tar.gz
files) for each OS/Platform.
Regards,
Pierre-Arnaud (aka PAM...)
On Nov 5, 2007 11:57 AM, Felix Knecht <fe...@apache.org> wrote:
> >>
> > There is no current list of used svn:keywords...
> >> If no rule exists yet I'd like to suggest the following:
> >>
> >> svn:keyword Id
> >>
> >> /**
> >> * Foo bar
> >> *
> >> * @author <a href="mailto:dev@directory.apache.org">Apache Directory
> >> Project</a>
> >> * @version $Id: AbstractStudioMojo.java 350 2007-10-28 12:01:17Z felix
> $
> >> */
> >>
> > We are not using names into header. Here are our coding standards :
> >
> > http://cwiki.apache.org/DIRxDEV/coding-standards.html
>
> It's not a fix name, but just the name of the committer who did the latest
> commit:
>
>
> http://svnbook.red-bean.com/en/1.4/svn.advanced.props.special.keywords.html
>
> In most java classes I can find the svn:keywords [date and/or revision]
> already now. But they are not used consequently
> the same way and also not always set as svn:keywords to the file when used
> within the file.
>
> >
> >> b) I haven't found any documentation about project/modules/code which
> >> is done automatically (e.g. maven reports, maven
> >> site, JavaDocs, ...).
> >> Is this all done either in the cwiki or packaged into a
> >> downloadable/buildable distribution?
> >>
> > We don't anymore generate the site from code, we use confluence for
> that.
> >
> > We should generate Javadocs though, but I'm not a maven guru enough to
> > guarantee that the current maven configuration allows that. And I would
> > add that I would be very pleased if you can tell me ;)
> >
> > Generating maven reports would be a very valuable addition, too !
>
> I'll try to add this to the maven studio build.
>
> >>
> >> c) Do any ideas about automated continuous integration exists, e.g.
> >> continuum?
> >>
> > We tried continuum once upon a time, we also tried bamboo, and we
> > currently have some another continuous integration server running, but
> > we would like to speed up the tests a lot before fully activating the
> > continuous build again. FYI, building the server 'cost' 20 minutes on my
> > laptop, and around 10 minutes on a fast server. We also have had by
> > spamming experience with continuous integration (a mail every 3 minutes
> > sent to the full dev list - 200 peeps - 2 days long ...), so we are not
> > really keen to play this game again, unless someone who *knows* how to
> > correctly setup such an environment handle it (ie, not me, obviously :)
>
> I think there are already running some continuum instances within apache.
> Maybe the infrastructure team has more
> knowledge about such running instances and if the directory project can
> hang on onto an already existing instance.
>
>
> > I have added you in
> > http://cwiki.apache.org/confluence/display/directory/The+team
>
> Thanks. I already did but haven't noticed the alphabetic ordering and
> added me at the bottom. So this is fixed now.
> >
> > Fell free to add a picture (small one :), your web site, blog, to this
> > page !
>
> I only have my companys website if this would also be ok?
>
> >
> > Thanks !
> >
>
>
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
>>
> There is no current list of used svn:keywords...
>> If no rule exists yet I'd like to suggest the following:
>>
>> svn:keyword Id
>>
>> /**
>> * Foo bar
>> *
>> * @author <a href="mailto:dev@directory.apache.org">Apache Directory
>> Project</a>
>> * @version $Id: AbstractStudioMojo.java 350 2007-10-28 12:01:17Z felix $
>> */
>>
> We are not using names into header. Here are our coding standards :
>
> http://cwiki.apache.org/DIRxDEV/coding-standards.html
It's not a fix name, but just the name of the committer who did the latest commit:
http://svnbook.red-bean.com/en/1.4/svn.advanced.props.special.keywords.html
In most java classes I can find the svn:keywords [date and/or revision] already now. But they are not used consequently
the same way and also not always set as svn:keywords to the file when used within the file.
>
>> b) I haven't found any documentation about project/modules/code which
>> is done automatically (e.g. maven reports, maven
>> site, JavaDocs, ...).
>> Is this all done either in the cwiki or packaged into a
>> downloadable/buildable distribution?
>>
> We don't anymore generate the site from code, we use confluence for that.
>
> We should generate Javadocs though, but I'm not a maven guru enough to
> guarantee that the current maven configuration allows that. And I would
> add that I would be very pleased if you can tell me ;)
>
> Generating maven reports would be a very valuable addition, too !
I'll try to add this to the maven studio build.
>>
>> c) Do any ideas about automated continuous integration exists, e.g.
>> continuum?
>>
> We tried continuum once upon a time, we also tried bamboo, and we
> currently have some another continuous integration server running, but
> we would like to speed up the tests a lot before fully activating the
> continuous build again. FYI, building the server 'cost' 20 minutes on my
> laptop, and around 10 minutes on a fast server. We also have had by
> spamming experience with continuous integration (a mail every 3 minutes
> sent to the full dev list - 200 peeps - 2 days long ...), so we are not
> really keen to play this game again, unless someone who *knows* how to
> correctly setup such an environment handle it (ie, not me, obviously :)
I think there are already running some continuum instances within apache. Maybe the infrastructure team has more
knowledge about such running instances and if the directory project can hang on onto an already existing instance.
> I have added you in
> http://cwiki.apache.org/confluence/display/directory/The+team
Thanks. I already did but haven't noticed the alphabetic ordering and added me at the bottom. So this is fixed now.
>
> Fell free to add a picture (small one :), your web site, blog, to this
> page !
I only have my companys website if this would also be ok?
>
> Thanks !
>
Re: Buildsystem studio
Posted by Emmanuel Lecharny <el...@gmail.com>.
Hi Felix,
Felix Knecht wrote:
> I've still no commit access to the sandbox directory. Never the less I started to adapt the doc "Build Apache Directory
> Studio" and put it into the Apache Directory Sandbox [1] (I think that's the way do to).
>
Hmmm... Let me check that this afternoon...
> Still some questions I couldn't find (or haven't seen) an answer in the docs:
>
> a) Which svn:keywords are set and used? Looking at some files I can see different svn:keywords set, but they not always
> seem to match with the references in the code.
>
There is no current list of used svn:keywords...
> If no rule exists yet I'd like to suggest the following:
>
> svn:keyword Id
>
> /**
> * Foo bar
> *
> * @author <a href="mailto:dev@directory.apache.org">Apache Directory Project</a>
> * @version $Id: AbstractStudioMojo.java 350 2007-10-28 12:01:17Z felix $
> */
>
We are not using names into header. Here are our coding standards :
http://cwiki.apache.org/DIRxDEV/coding-standards.html
> b) I haven't found any documentation about project/modules/code which is done automatically (e.g. maven reports, maven
> site, JavaDocs, ...).
> Is this all done either in the cwiki or packaged into a downloadable/buildable distribution?
>
We don't anymore generate the site from code, we use confluence for that.
We should generate Javadocs though, but I'm not a maven guru enough to
guarantee that the current maven configuration allows that. And I would
add that I would be very pleased if you can tell me ;)
Generating maven reports would be a very valuable addition, too !
>
> c) Do any ideas about automated continuous integration exists, e.g. continuum?
>
We tried continuum once upon a time, we also tried bamboo, and we
currently have some another continuous integration server running, but
we would like to speed up the tests a lot before fully activating the
continuous build again. FYI, building the server 'cost' 20 minutes on my
laptop, and around 10 minutes on a fast server. We also have had by
spamming experience with continuous integration (a mail every 3 minutes
sent to the full dev list - 200 peeps - 2 days long ...), so we are not
really keen to play this game again, unless someone who *knows* how to
correctly setup such an environment handle it (ie, not me, obviously :)
> Regards
> Felix
>
> [1] http://cwiki.apache.org/confluence/x/txEB
>
>
Thanks a lot for those insights, felix. There are really interesting.
I have added you in
http://cwiki.apache.org/confluence/display/directory/The+team
Fell free to add a picture (small one :), your web site, blog, to this
page !
Thanks !
--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
I've still no commit access to the sandbox directory. Never the less I started to adapt the doc "Build Apache Directory
Studio" and put it into the Apache Directory Sandbox [1] (I think that's the way do to).
Still some questions I couldn't find (or haven't seen) an answer in the docs:
a) Which svn:keywords are set and used? Looking at some files I can see different svn:keywords set, but they not always
seem to match with the references in the code.
If no rule exists yet I'd like to suggest the following:
svn:keyword Id
/**
* Foo bar
*
* @author <a href="mailto:dev@directory.apache.org">Apache Directory Project</a>
* @version $Id: AbstractStudioMojo.java 350 2007-10-28 12:01:17Z felix $
*/
b) I haven't found any documentation about project/modules/code which is done automatically (e.g. maven reports, maven
site, JavaDocs, ...).
Is this all done either in the cwiki or packaged into a downloadable/buildable distribution?
c) Do any ideas about automated continuous integration exists, e.g. continuum?
Regards
Felix
[1] http://cwiki.apache.org/confluence/x/txEB
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
Felix Knecht schrieb:
>> Since, the build system works well now, I think we'll stay like that
>> for a little while. But if you have links for building Eclipse plugins
>> and Eclipse RCP applications with Maven, I would love to read them... ;)
>>
>
>
There's even more documentation about it:
http://www.eclipse.org/articles/article.php?file=Article-Eclipse-and-Maven2/index.html
> [1] Describes the build of an EclipseRCP Application with maven using
> the pde-maven-plugin [2]. [1] is unfortunately written in German. Maybe
> this could give a hint. Reading [1] it's expected to have an Eclipse
> installation somewhere on the build system what makes me not really
> happy - but it seems to be possible.
>
> For now I'm almost on 80% - I can build the updatesite including all the
> jars (haven't tested it yet). But as usual the last 20% (RCP) will
> probably beome 80% of work ;-)
>
> Felix
>
> [1] http://www.breskeby.com/240
> [2] http://mojo.codehaus.org/pde-maven-plugin/index.html
>
>
>
Re: Buildsystem studio
Posted by Alex Karasulu <ak...@apache.org>.
I'd like to see everything use the same build system eventually: but I know
how
much of an odd ball this eclipse environment is to deal with when using
maven
It's better for the project overall to stick to a single build system.
On 10/18/07, Felix Knecht <fe...@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).
+1
- 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.
Couldn't have said it better myself.
- 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.
+1 and u can use the same techniques for continuous integration instead of
having two of everything to accommodate each project.
- 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.
+1
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).
Yeah there are tradeoffs with all these tools. Sometimes they are better at
some tasks than others but things also change over time. So yes the build
system chosen is not the issue, being consistent is across projects.
Alex
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
Pierre-Arnaud Marcelot schrieb:
>
> PS: As you're starting to have something working, maybe it could be
> interesting that we create in a sandbox a branch for Maven build of
> Studio. It could help us work together on this.
> What do you think guys ?
> If I create a branch in my sandox
> (/directory/sandbox/pamarcelot/trunks), will Felix be allowed to
> commit in it ?
Ups, I absolutely overread this, sorry.
Normally you can subversion like this, but I don't know exactly how it
is done at Apache. Maybe you should ask this question in the
infrastructure list (of course only if the the other agree about your
suggestion).
Felix
Re: Buildsystem studio
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
On 10/26/07, Felix Knecht <fe...@apache.org> wrote:
> The only one I could see is getting the Bundle-ClassPath updated by
> maven instead of doing it manually when a version of a referenced jar in
> the Bundle-ClassPath is changed in the root pom.xml.
Oh, yeah. That could be a good point...
It could help a lot with the 'Bundle-ClassPath' property but it may also be
painful with the 'Require-Bundle' property (as we use Eclipse to manage
them).
It's difficult to have the perfect balance between day-to-day usability for
developers and automation.
Thanks for spotting.
Thanks for helping with the Maven build. :)
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
Pierre-Arnaud Marcelot schrieb:
> Ok I see, something like the eclipse:eclipse task (which creates the
> .project and .classpath)...
>
> But, the fact is we use Eclipse editors [1][2] to edit this
> MANIFEST.MF file as well as the plugin.xml file.
> So I don't know if it's really an advantage to have it generated by
> Maven...
> Is there any advantage we could have from using a Maven generated
> MANIFEST.MF file ?
The only one I could see is getting the Bundle-ClassPath updated by
maven instead of doing it manually when a version of a referenced jar in
the Bundle-ClassPath is changed in the root pom.xml.
But I haven't known about the this feature of eclipse. So there is no
need to do it.
Thanks for spotting.
Felix
>
> Regards,
> P-A
>
> [1]
> http://www.ibm.com/developerworks/cn/aix/library/au-fiteclipse2/AddPluginDependency.jpg
> - The "Required Plugins" are represented in the MANIFEST.MF file by
> the 'Require-Bundle' property.
> [2] http://cs.unibg.it/gargantini/didattica/eclipse/libs_runtime.png -
> The "Classpath" is represented in the the MANIFEST.MF file as by the
> 'Bundle-ClassPath' property.
>
>
> On 10/26/07, *Felix Knecht* <felixk@apache.org
> <ma...@apache.org>> wrote:
>
> From my POV it would be nice, if this can be done as well for the
> MANIFEST.MF .
> I'd like to get rid of adapting versions of dependencies in the
> Bundle-Classpath. I could imagine having a task in a
> maven-studio-plugin
> writing the MANIFEST.MF in the same manor as done for the lib
> directory.
> The configuration for the MANIFEST.MF will stay in pom.xml where
> we can
> also reference to dependencies.
>
> WDYT?
>
> Felix
>
Re: Buildsystem studio
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Ok I see, something like the eclipse:eclipse task (which creates the
.project and .classpath)...
But, the fact is we use Eclipse editors [1][2] to edit this MANIFEST.MF file
as well as the plugin.xml file.
So I don't know if it's really an advantage to have it generated by Maven...
Is there any advantage we could have from using a Maven generated
MANIFEST.MF file ?
Regards,
P-A
[1]
http://www.ibm.com/developerworks/cn/aix/library/au-fiteclipse2/AddPluginDependency.jpg-
The "Required Plugins" are represented in the
MANIFEST.MF file by the 'Require-Bundle' property.
[2] http://cs.unibg.it/gargantini/didattica/eclipse/libs_runtime.png - The
"Classpath" is represented in the the MANIFEST.MF file as by the
'Bundle-ClassPath' property.
On 10/26/07, Felix Knecht <felixk@apache.org > wrote:
>
> From my POV it would be nice, if this can be done as well for the
> MANIFEST.MF .
> I'd like to get rid of adapting versions of dependencies in the
> Bundle-Classpath. I could imagine having a task in a maven-studio-plugin
> writing the MANIFEST.MF in the same manor as done for the lib directory.
> The configuration for the MANIFEST.MF will stay in pom.xml where we can
> also reference to dependencies.
>
> WDYT?
>
> Felix
>
>
> Pierre-Arnaud Marcelot schrieb:
> > Ok, then it's not an issue... :)
> >
> > We need to run "$ ant resolve" to get the dependencies right now, so
> > it's not really a problem. As long as it is in the documentation on
> > how to build the trunk, then I think it's ok.
> >
> > Thanks,
> > P-A
> >
> > On 10/22/07, *Felix Knecht* <felixk@apache.org
> > <ma...@apache.org>> wrote:
> >
> > Pierre-Arnaud Marcelot schrieb:
> > > Ok, thanks Felix.
> > >
> > > I'm also realizing there could be another problem with the jar
> > > dependencies.
> > > I know that usualy (that's what is done in ApacheDS projects) jar
> > > dependencies declared in Maven are linked in Eclipse using the
> > M2_REPO
> > > location (basically '~/.m2/repository') in the classpath
> > properties of
> > > a project.
> > >
> > > Here (in Studio), we really need the dependencies to be copied
> > in the
> > > a 'lib' folder because:
> > > - they need to be bundled in the jar of the plugin to work
> > > - Eclipse needs them when bundling the plugin to launch it for
> > testing
> > > and debugging (same situation as the MANIFEST.MF file).
> > >
> > > Do you think this is possible to have such a behavior for
> > dependencies
> > > in Maven (I'm really not a Maven expert... :'( ) ?
> >
> > Yes, this can be done - but you would need to run once maven to have
> > them there. This could be done havind a specific profile. After a
> new
> > svn checkout of a project you'll need to run e.g.
> > $ mvn install -Pprepare-for-eclipse to have all the needed jar files
> > copied to ${module}/lib.
> >
> > Felix
> >
> >
>
>
Re: Buildsystem studio
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Hi Felix,
Hmm, what is about the durectories located in the modules root know like
> e.g. resources? Do they need to stay there or could the be moved to the
> 'maven standard' directory src/main/resources?
I think they can be moved there. But some files like about.ini,
plugin.properties, plugin.xml or studio.png for example, must stay where
they are.
P-A
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
>From my POV it would be nice, if this can be done as well for the
MANIFEST.MF.
I'd like to get rid of adapting versions of dependencies in the
Bundle-Classpath. I could imagine having a task in a maven-studio-plugin
writing the MANIFEST.MF in the same manor as done for the lib directory.
The configuration for the MANIFEST.MF will stay in pom.xml where we can
also reference to dependencies.
WDYT?
Felix
Pierre-Arnaud Marcelot schrieb:
> Ok, then it's not an issue... :)
>
> We need to run "$ ant resolve" to get the dependencies right now, so
> it's not really a problem. As long as it is in the documentation on
> how to build the trunk, then I think it's ok.
>
> Thanks,
> P-A
>
> On 10/22/07, *Felix Knecht* <felixk@apache.org
> <ma...@apache.org>> wrote:
>
> Pierre-Arnaud Marcelot schrieb:
> > Ok, thanks Felix.
> >
> > I'm also realizing there could be another problem with the jar
> > dependencies.
> > I know that usualy (that's what is done in ApacheDS projects) jar
> > dependencies declared in Maven are linked in Eclipse using the
> M2_REPO
> > location (basically '~/.m2/repository') in the classpath
> properties of
> > a project.
> >
> > Here (in Studio), we really need the dependencies to be copied
> in the
> > a 'lib' folder because:
> > - they need to be bundled in the jar of the plugin to work
> > - Eclipse needs them when bundling the plugin to launch it for
> testing
> > and debugging (same situation as the MANIFEST.MF file).
> >
> > Do you think this is possible to have such a behavior for
> dependencies
> > in Maven (I'm really not a Maven expert... :'( ) ?
>
> Yes, this can be done - but you would need to run once maven to have
> them there. This could be done havind a specific profile. After a new
> svn checkout of a project you'll need to run e.g.
> $ mvn install -Pprepare-for-eclipse to have all the needed jar files
> copied to ${module}/lib.
>
> Felix
>
>
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
Pierre-Arnaud Marcelot schrieb:
> Ok, then it's not an issue... :)
>
> We need to run "$ ant resolve" to get the dependencies right now, so
> it's not really a problem. As long as it is in the documentation on
> how to build the trunk, then I think it's ok.
Hmm, what is about the durectories located in the modules root know like
e.g. resources? Do they need to stay there or could the be moved to the
'maven standard' directory src/main/resources?
Regards
Felix
Re: Buildsystem studio
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Ok, then it's not an issue... :)
We need to run "$ ant resolve" to get the dependencies right now, so it's
not really a problem. As long as it is in the documentation on how to build
the trunk, then I think it's ok.
Thanks,
P-A
On 10/22/07, Felix Knecht <fe...@apache.org> wrote:
>
> Pierre-Arnaud Marcelot schrieb:
> > Ok, thanks Felix.
> >
> > I'm also realizing there could be another problem with the jar
> > dependencies.
> > I know that usualy (that's what is done in ApacheDS projects) jar
> > dependencies declared in Maven are linked in Eclipse using the M2_REPO
> > location (basically '~/.m2/repository') in the classpath properties of
> > a project.
> >
> > Here (in Studio), we really need the dependencies to be copied in the
> > a 'lib' folder because:
> > - they need to be bundled in the jar of the plugin to work
> > - Eclipse needs them when bundling the plugin to launch it for testing
> > and debugging (same situation as the MANIFEST.MF file).
> >
> > Do you think this is possible to have such a behavior for dependencies
> > in Maven (I'm really not a Maven expert... :'( ) ?
>
> Yes, this can be done - but you would need to run once maven to have
> them there. This could be done havind a specific profile. After a new
> svn checkout of a project you'll need to run e.g.
> $ mvn install -Pprepare-for-eclipse to have all the needed jar files
> copied to ${module}/lib.
>
> Felix
>
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
Pierre-Arnaud Marcelot schrieb:
> Ok, thanks Felix.
>
> I'm also realizing there could be another problem with the jar
> dependencies.
> I know that usualy (that's what is done in ApacheDS projects) jar
> dependencies declared in Maven are linked in Eclipse using the M2_REPO
> location (basically '~/.m2/repository') in the classpath properties of
> a project.
>
> Here (in Studio), we really need the dependencies to be copied in the
> a 'lib' folder because:
> - they need to be bundled in the jar of the plugin to work
> - Eclipse needs them when bundling the plugin to launch it for testing
> and debugging (same situation as the MANIFEST.MF file).
>
> Do you think this is possible to have such a behavior for dependencies
> in Maven (I'm really not a Maven expert... :'( ) ?
Yes, this can be done - but you would need to run once maven to have
them there. This could be done havind a specific profile. After a new
svn checkout of a project you'll need to run e.g.
$ mvn install -Pprepare-for-eclipse to have all the needed jar files
copied to ${module}/lib.
Felix
Re: Buildsystem studio
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Ok, thanks Felix.
I'm also realizing there could be another problem with the jar dependencies.
I know that usualy (that's what is done in ApacheDS projects) jar
dependencies declared in Maven are linked in Eclipse using the M2_REPO
location (basically '~/.m2/repository') in the classpath properties of a
project.
Here (in Studio), we really need the dependencies to be copied in the a
'lib' folder because:
- they need to be bundled in the jar of the plugin to work
- Eclipse needs them when bundling the plugin to launch it for testing and
debugging (same situation as the MANIFEST.MF file).
Do you think this is possible to have such a behavior for dependencies in
Maven (I'm really not a Maven expert... :'( ) ?
Thank,
P-A
PS: As you're starting to have something working, maybe it could be
interesting that we create in a sandbox a branch for Maven build of Studio.
It could help us work together on this.
What do you think guys ?
If I create a branch in my sandox (/directory/sandbox/pamarcelot/trunks),
will Felix be allowed to commit in it ?
On 10/22/07, Felix Knecht <fe...@apache.org> wrote:
>
> Pierre-Arnaud Marcelot schrieb:
> > Hi Felix,
> >
> > On 10/22/07, *Felix Knecht* <felixk@apache.org
> > <ma...@apache.org>> wrote:
> >
> > For the moment I'm stating 2 problems I haven't found a solution
> > for and
> > where I think it make sense to write an own plugin:
> >
> > - Adapting the <Bundle-Classpath> in Manifest files
> > <configuration>
> > <classpath>., ...</classpath>
> > <artifactItems>
> > <artifact>
> > <groupId></groupId>
> > <artifactId></artifactId>
> > </artifact>
> > ....
> > </artifactItems>
> > </configuration>
> >
> >
> > Does this mean you want to get rid of the META-INF folder and the
> > MANIFEST.MF file in SVN and replace it by one generated by Maven when
> > creating the jar of the plugin ?
> > In this case, it could be a problem, as when we develop the plugins,
> > we usually launch our plugins within eclipse (the green arrow "Run"
> > button) for testing and debugging.
> > To be able to do that, Eclipse bundles the plugins (only the opened
> > projects) in it workspace and launches a new instance of itself with
> > the plugin under development loaded.
> > A part of this mechanism is based on this MANIFEST.MF file which
> > stores the name and id of the plugins and their classpathes.
> > Are you sure that automating the generation of such file(s) will not
> > corrupt this functionality, which we really use every day and is
> > really a must-have.
>
> No, I'm absolutely not sure, thanks for the hint.
> It'll probably not work when MANIFEST.MF is create automatically,
> because it would exist only after a maven build within the generated
> jar. Therefore Eclipse wouldn't know about the MANIFEST.MF.
> I don't think that it makes sense to automate MANIFEST creation automated.
>
> Felix
>
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
Pierre-Arnaud Marcelot schrieb:
> Hi Felix,
>
> On 10/22/07, *Felix Knecht* <felixk@apache.org
> <ma...@apache.org>> wrote:
>
> For the moment I'm stating 2 problems I haven't found a solution
> for and
> where I think it make sense to write an own plugin:
>
> - Adapting the <Bundle-Classpath> in Manifest files
> <configuration>
> <classpath>., ...</classpath>
> <artifactItems>
> <artifact>
> <groupId></groupId>
> <artifactId></artifactId>
> </artifact>
> ....
> </artifactItems>
> </configuration>
>
>
> Does this mean you want to get rid of the META-INF folder and the
> MANIFEST.MF file in SVN and replace it by one generated by Maven when
> creating the jar of the plugin ?
> In this case, it could be a problem, as when we develop the plugins,
> we usually launch our plugins within eclipse (the green arrow "Run"
> button) for testing and debugging.
> To be able to do that, Eclipse bundles the plugins (only the opened
> projects) in it workspace and launches a new instance of itself with
> the plugin under development loaded.
> A part of this mechanism is based on this MANIFEST.MF file which
> stores the name and id of the plugins and their classpathes.
> Are you sure that automating the generation of such file(s) will not
> corrupt this functionality, which we really use every day and is
> really a must-have.
No, I'm absolutely not sure, thanks for the hint.
It'll probably not work when MANIFEST.MF is create automatically,
because it would exist only after a maven build within the generated
jar. Therefore Eclipse wouldn't know about the MANIFEST.MF.
I don't think that it makes sense to automate MANIFEST creation automated.
Felix
Re: Buildsystem studio
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Hi Felix,
On 10/22/07, Felix Knecht <fe...@apache.org> wrote:
>
> For the moment I'm stating 2 problems I haven't found a solution for and
> where I think it make sense to write an own plugin:
>
> - Adapting the <Bundle-Classpath> in Manifest files
> <configuration>
> <classpath>., ...</classpath>
> <artifactItems>
> <artifact>
> <groupId></groupId>
> <artifactId></artifactId>
> </artifact>
> ....
> </artifactItems>
> </configuration>
Does this mean you want to get rid of the META-INF folder and the
MANIFEST.MF file in SVN and replace it by one generated by Maven when
creating the jar of the plugin ?
In this case, it could be a problem, as when we develop the plugins, we
usually launch our plugins within eclipse (the green arrow "Run" button) for
testing and debugging.
To be able to do that, Eclipse bundles the plugins (only the opened
projects) in it workspace and launches a new instance of itself with the
plugin under development loaded.
A part of this mechanism is based on this MANIFEST.MF file which stores the
name and id of the plugins and their classpathes.
Are you sure that automating the generation of such file(s) will not corrupt
this functionality, which we really use every day and is really a must-have.
- Updating jar archives in a given location (e.g. replace plugin.xml)
> <configuration>
> <!-- Location of the jar archives to replace a file within -->
> <location>target/ApacheDirectoryStudio/plugins</location>
> <!-- Src of the replacing file -->
>
>
> <replaceSrc>src/main/configuration/org.eclipse.search/plugin.xml</replaceSrc>
> <!-- target location in jar archive for the src file -->
> <!-- target location in jar archive for the src file -->
> <replaceDest>plugin.xml</replaceDest>
> <!-- The archives the replace the file within -->
> <artifactItems>
> <artifact>
> <groupId></groupId>
> <artifactId></artifactId>
> </artifact>
> ....
> </artifactItems>
> </configuration>
>
>
> If nobody nows about a plugins providing such features I'm going to
> write one.
I have no idea if such a plugin exists, but I'm far from a Maven expert...
;)
Thanks,
p-A
Regards
> Felix
>
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
Alex Karasulu schrieb:
> Hi Felix,
>
> Just curious what were those two problems?
>
> I did not know off the top of my head if there was a clear way now
> besides some workarounds I've
> seen in the past for building eclipse RCP bundles using Maven. I
> guess this is what you want to
> do right?
Yes.
In general http://docs.codehaus.org/display/MAVENUSER/Eclipse+Plugin is
the way I'm going to try.
But:
Within the plugins studio creates you'll find entries in the Manifest
file like
<Bundle-ClassPath>lib/commons-io-1.3.1.jar, .</Bundle-ClassPath>
It would be nice to have commons-io-1.3.1.jar resolved via indicating an
artifact and not having it hardcoded somewhere in the pom to avoid
adapting versions in case of.
Studio adapts plugins distributed by eclipse, see
studio-rcp/build.xml: "Replacing some plugin.xml to get rid of unused
actions, menus, wizard, views, ..."
For those two issues I haven't found a way todo.
Felix
> I just googled it for the heck of it and there seems to be a lot
> around this topic in the
> works. There seems to be a lot here to weed through but it looks like
> workarounds are still in play.
>
> http://www.google.com/search?hl=en&rls=com.microsoft%3A*%3AIE-SearchBox&rlz=1I7ADBR&q=maven+rcp+plugin
> <http://www.google.com/search?hl=en&rls=com.microsoft%3A*%3AIE-SearchBox&rlz=1I7ADBR&q=maven+rcp+plugin>
>
> Perhaps another more specific plugin is in order that just pulls all
> these approaches together in
> a clean way.
>
> Also I found a PDE maven plugin. Don't know if this has any value
> towards what you're looking into.
>
> Alex
>
>
> On 10/22/07, *Felix Knecht* <felixk@apache.org
> <ma...@apache.org>> wrote:
>
> For the moment I'm stating 2 problems I haven't found a solution
> for and
> where I think it make sense to write an own plugin:
>
> - Adapting the <Bundle-Classpath> in Manifest files
> <configuration>
> <classpath>., ...</classpath>
> <artifactItems>
> <artifact>
> <groupId></groupId>
> <artifactId></artifactId>
> </artifact>
> ....
> </artifactItems>
> </configuration>
>
> - Updating jar archives in a given location (e.g. replace plugin.xml)
> <configuration>
> <!-- Location of the jar archives to replace a file within -->
> <location>target/ApacheDirectoryStudio/plugins</location>
> <!-- Src of the replacing file -->
>
> <replaceSrc>src/main/configuration/org.eclipse.search/plugin.xml</replaceSrc>
>
> <!-- target location in jar archive for the src file -->
> <!-- target location in jar archive for the src file -->
> <replaceDest>plugin.xml</replaceDest>
> <!-- The archives the replace the file within -->
> <artifactItems>
> <artifact>
> <groupId></groupId>
> <artifactId></artifactId>
> </artifact>
> ....
> </artifactItems>
> </configuration>
>
>
> If nobody nows about a plugins providing such features I'm going to
> write one.
>
>
> Regards
> Felix
>
>
Re: Buildsystem studio
Posted by Alex Karasulu <ak...@apache.org>.
Hi Felix,
Just curious what were those two problems?
I did not know off the top of my head if there was a clear way now besides
some workarounds I've
seen in the past for building eclipse RCP bundles using Maven. I guess this
is what you want to
do right? I just googled it for the heck of it and there seems to be a lot
around this topic in the
works. There seems to be a lot here to weed through but it looks like
workarounds are still in play.
http://www.google.com/search?hl=en&rls=com.microsoft%3A*%3AIE-SearchBox&rlz=1I7ADBR&q=maven+rcp+plugin
Perhaps another more specific plugin is in order that just pulls all these
approaches together in
a clean way.
Also I found a PDE maven plugin. Don't know if this has any value towards
what you're looking into.
Alex
On 10/22/07, Felix Knecht <fe...@apache.org> wrote:
>
> For the moment I'm stating 2 problems I haven't found a solution for and
> where I think it make sense to write an own plugin:
>
> - Adapting the <Bundle-Classpath> in Manifest files
> <configuration>
> <classpath>., ...</classpath>
> <artifactItems>
> <artifact>
> <groupId></groupId>
> <artifactId></artifactId>
> </artifact>
> ....
> </artifactItems>
> </configuration>
>
> - Updating jar archives in a given location (e.g. replace plugin.xml)
> <configuration>
> <!-- Location of the jar archives to replace a file within -->
> <location>target/ApacheDirectoryStudio/plugins</location>
> <!-- Src of the replacing file -->
>
>
> <replaceSrc>src/main/configuration/org.eclipse.search/plugin.xml</replaceSrc>
> <!-- target location in jar archive for the src file -->
> <!-- target location in jar archive for the src file -->
> <replaceDest>plugin.xml</replaceDest>
> <!-- The archives the replace the file within -->
> <artifactItems>
> <artifact>
> <groupId></groupId>
> <artifactId></artifactId>
> </artifact>
> ....
> </artifactItems>
> </configuration>
>
>
> If nobody nows about a plugins providing such features I'm going to
> write one.
>
>
> Regards
> Felix
>
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
For the moment I'm stating 2 problems I haven't found a solution for and
where I think it make sense to write an own plugin:
- Adapting the <Bundle-Classpath> in Manifest files
<configuration>
<classpath>., ...</classpath>
<artifactItems>
<artifact>
<groupId></groupId>
<artifactId></artifactId>
</artifact>
....
</artifactItems>
</configuration>
- Updating jar archives in a given location (e.g. replace plugin.xml)
<configuration>
<!-- Location of the jar archives to replace a file within -->
<location>target/ApacheDirectoryStudio/plugins</location>
<!-- Src of the replacing file -->
<replaceSrc>src/main/configuration/org.eclipse.search/plugin.xml</replaceSrc>
<!-- target location in jar archive for the src file -->
<!-- target location in jar archive for the src file -->
<replaceDest>plugin.xml</replaceDest>
<!-- The archives the replace the file within -->
<artifactItems>
<artifact>
<groupId></groupId>
<artifactId></artifactId>
</artifact>
....
</artifactItems>
</configuration>
If nobody nows about a plugins providing such features I'm going to
write one.
Regards
Felix
Re: Buildsystem studio
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Hi Felix,
On 10/20/07, Felix Knecht <fe...@apache.org> wrote:
>
> Just to understand the App generation a little bit better. Loosely said an
> dist can be build
> - Unzipping the RCP download from Eclipse (e.g. [1]
> - Patch some configuration files of the unzipped RCP
> - Add the jars of the studio modules (plugin, feature help)
>
> and you have a working sutdio application which can be distributed?
Yes, this could work I think but, there will be too many plugins bundled
with the Eclipse ( like the Java perspective for example). As Studio does
not depend on this plugins, it make no sense to overload the application
size with useless plugins.
That's why we only bundle a subset of the plugins of a standard Eclipse
installation, getting only the ones we need.
For information, here are all the plugins we need (they are located in the
'dependencies/eclipse/3.2/plugins' folder):
/studio/dependencies/eclipse/3.2/plugins/org.apache.lucene_1.4.103.v20060601
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.core.runtime.compatibility.registry_3.2.1.R32x_v20060907
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.help.webapp_3.2.1.R321_v20060803
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.sdk_3.2.1.r321_v20060705
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.tomcat_4.1.130.v20060601
/studio/dependencies/eclipse/3.2/plugins/com.ibm.icu_3.4.5.jar
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.core.commands_3.2.0.I20060605-
1400.jar
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.core.contenttype_3.2.0.v20060603.jar
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.core.expressions_3.2.1.r321_v20060721.jar
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.core.filebuffers_3.2.1.r321_v20060721.jar
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.core.filesystem_1.0.0.v20060603.jar
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.core.jobs_3.2.0.v20060603.jar
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.core.resources_3.2.1.R32x_v20060914.jar/studio/dependencies/eclipse/3.2/plugins/org.eclipse.core.runtime.compatibility.auth_3.2.0.v20060511.jar
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.core.runtime.compatibility_3.1.100.v20060603.jar
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.core.runtime_3.2.0.v20060603.jar
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.equinox.common_3.2.0.v20060603.jar
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.equinox.preferences_3.2.1.R32x_v20060717.jar
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.equinox.registry_3.2.1.R32x_v20060814.jar
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.help.appserver_3.1.100.v20060602.jar
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.help.base_3.2.1.R321_v20060822.jar
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.help.ui_3.2.0.v20060602.jar/studio/dependencies/eclipse/3.2/plugins/org.eclipse.help_3.2.1.R321_v20060920.jar
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.jface.databinding_1.0.0.I20060605-
1400.jar
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.jface.text_3.2.1.r321_v20060810.jar
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.jface_3.2.1.M20060908-
1000.jar
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.osgi_3.2.1.R32x_v20060919.jar
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.rcp_3.2.0.v20060605.jar
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.search_3.2.1.r321_v20060726.jar
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.search_3.2.1.r321_v20060726.plugin.xml
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.swt_3.2.1.v3235e.jar
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.text_3.2.0.v20060605-
1400.jar
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.ui.editors_3.2.1.r321_v20060721.jar
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.ui.editors_3.2.1.r321_v20060721.plugin.xml
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.ui.forms_3.2.0.v20060602.jar
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.ui.ide_3.2.1.M20060915-
1030.jar
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.ui.ide_3.2.1.M20060915-
1030.plugin.xml
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.ui.intro_3.2.1.R321_v20060810.jar
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.ui.views_3.2.1.M20060906-
0800.jar
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.ui.workbench.texteditor_3.2.0.v20060605-
1400.jar
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.ui.workbench_3.2.1.M20060906-
0800.jar
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.ui_3.2.1.M20060913-
0800.jar
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.update.configurator_3.2.1.v20092006.jar
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.update.core_3.2.1.v20092006.jar
/studio/dependencies/eclipse/3.2/plugins/org.eclipse.update.ui_3.2.1.v20092006.jar
P-A
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
> Don't hesitate to ask if you have specific questions about the build.
Just to understand the App generation a little bit better. Loosely said an dist can be build
- Unzipping the RCP download from Eclipse (e.g. [1]
- Patch some configuration files of the unzipped RCP
- Add the jars of the studio modules (plugin, feature help)
and you have a working sutdio application which can be distributed?
Felix
[1]
http://archive.eclipse.org/eclipse/downloads/drops/R-3.2.2-200702121330/download.php?dropFile=eclipse-RCP-3.2.2-linux-gtk.tar.gz
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
Pierre-Arnaud Marcelot schrieb:
>
> Nevertheless the failing test testResponseWith2Attr1Value could
> still be
> a problem of mine.
>
>
> If you haven't touch the files used by the testcase, it can't be your
> problem...
>
> Strangely, I only got the testRequestWithSubEntriesControl test case
> failing here (running on JDK 5 update 12 within eclipse 3.3)...
> What is your environment ?
>
JSDK 1.6.0_03, maven 2.0.7, linux i386/amd64. If it works for you, then
it'll be a problem of my environment. It's well possible that I have
still some configurations for tests missing.
I just came across the failing tests and wondered if it's a general
problem of mine ...
Felix
Re: Buildsystem studio
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
>
> Nevertheless the failing test testResponseWith2Attr1Value could still be
> a problem of mine.
If you haven't touch the files used by the testcase, it can't be your
problem...
Strangely, I only got the testRequestWithSubEntriesControl test case failing
here (running on JDK 5 update 12 within eclipse 3.3)...
What is your environment ?
Thanks.
P-A
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
Pierre-Arnaud Marcelot schrieb:
> Oops I had not finished yet... I didn't want to sent the mail.
>
> Let me start again...
>
> Thanks for the heads up.
>
> It is normal that testRequestWithSubEntriesControl fails, I still need
> to find a way to fix this.
>
> testResponseWith1Attr1Base64Value and
> testRequestWith1ModificationBase64Value fails due to a file encoding
> issue for accents (from Mac to Windows/Linux maybe). I'm going to look
> at that.
>
> testResponseWith2Attr1Value is not supposed to be failing... I'm going
> to look at that too...
It's good to read that there are failing testcases, so it's not only
problem of my build ;-)
Nevertheless the failing test testResponseWith2Attr1Value could still be
a problem of mine.
Felix
Re: Buildsystem studio
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Oops I had not finished yet... I didn't want to sent the mail.
Let me start again...
Thanks for the heads up.
It is normal that testRequestWithSubEntriesControl fails, I still need to
find a way to fix this.
testResponseWith1Attr1Base64Value and
testRequestWith1ModificationBase64Value fails due to a file encoding issue
for accents (from Mac to Windows/Linux maybe). I'm going to look at that.
testResponseWith2Attr1Value is not supposed to be failing... I'm going to
look at that too...
I haven't seen running any tests when building the project with ant/ivy. Did
> I miss a flag howto run ant/ivy including testcases?
>
Yeah, we don't run tests in the build ATM, they are run separately inside
Eclipse.
But, you're right, we should be running them when building.
Thanks
P-A
On 10/26/07, Pierre-Arnaud Marcelot <pa...@marcelot.net> wrote:
>
> Thanks for the heads up.
>
> It is normal that testRequestWithSubEntriesControl fails, I still need to
> find a way to fix this.
>
> testResponseWith1Attr1Base64Value and
>
> On 10/25/07, Felix Knecht <fe...@apache.org> wrote:
> >
> > Pierre-Arnaud Marcelot schrieb:
> > > Hi Felix,
> > >
> > > After the build of Studio, the configuration folder only contains the
> > > 'config.ini' file.
> > >
> > > Then, at runtime, the 'org.eclipse.core.runtime ' 'org.eclipse.osgi'
> > > 'org.eclipse.update ' folders are created and filled with data by the
> > > Eclipse core of Apache Directory Studio.
> > >
> > > Hope this helps,
> >
> > Yes, thanks.
> >
> > Next question ;-)
> >
> > Trying to (maven-)build the project I get some test failures [1]. I
> > haven't seen running any tests when building the
> > project with ant/ivy. Did I miss a flag howto run ant/ivy including
> > testcases?
> >
> > Thanks
> > Felix
> >
> > [1]
> > http://people.apache.org/~felixk/studio-dsml-parser/surefire-report.html<http://people.apache.org/%7Efelixk/studio-dsml-parser/surefire-report.html>
> >
>
>
Re: Buildsystem studio
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Thanks for the heads up.
It is normal that testRequestWithSubEntriesControl fails, I still need to
find a way to fix this.
testResponseWith1Attr1Base64Value and
On 10/25/07, Felix Knecht <fe...@apache.org> wrote:
>
> Pierre-Arnaud Marcelot schrieb:
> > Hi Felix,
> >
> > After the build of Studio, the configuration folder only contains the
> > 'config.ini' file.
> >
> > Then, at runtime, the 'org.eclipse.core.runtime' 'org.eclipse.osgi'
> > 'org.eclipse.update ' folders are created and filled with data by the
> > Eclipse core of Apache Directory Studio.
> >
> > Hope this helps,
>
> Yes, thanks.
>
> Next question ;-)
>
> Trying to (maven-)build the project I get some test failures [1]. I
> haven't seen running any tests when building the
> project with ant/ivy. Did I miss a flag howto run ant/ivy including
> testcases?
>
> Thanks
> Felix
>
> [1]
> http://people.apache.org/~felixk/studio-dsml-parser/surefire-report.html
>
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
Pierre-Arnaud Marcelot schrieb:
> Hi Felix,
>
> After the build of Studio, the configuration folder only contains the
> 'config.ini' file.
>
> Then, at runtime, the 'org.eclipse.core.runtime' 'org.eclipse.osgi'
> 'org.eclipse.update ' folders are created and filled with data by the
> Eclipse core of Apache Directory Studio.
>
> Hope this helps,
Yes, thanks.
Next question ;-)
Trying to (maven-)build the project I get some test failures [1]. I haven't seen running any tests when building the
project with ant/ivy. Did I miss a flag howto run ant/ivy including testcases?
Thanks
Felix
[1] http://people.apache.org/~felixk/studio-dsml-parser/surefire-report.html
Re: Buildsystem studio
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Hi Felix,
After the build of Studio, the configuration folder only contains the '
config.ini' file.
Then, at runtime, the 'org.eclipse.core.runtime' 'org.eclipse.osgi' '
org.eclipse.update' folders are created and filled with data by the Eclipse
core of Apache Directory Studio.
Hope this helps,
P-A
On 10/25/07, Felix Knecht <fe...@apache.org> wrote:
>
> Pierre-Arnaud Marcelot schrieb:
> > Don't hesitate to ask if you have specific questions about the build.
> >
>
> I can't find out how an when the additional directories in the
> ApacheDirectorySutdio/configuration (org.eclipse.core.runtime,
> org.eclipse.osgi, org.eclipse.update) are created and how/when they are
> filled with data. Can somebeody give me a hint?
>
> Thanks
> Felix
>
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
Pierre-Arnaud Marcelot schrieb:
> Don't hesitate to ask if you have specific questions about the build.
>
I can't find out how an when the additional directories in the
ApacheDirectorySutdio/configuration (org.eclipse.core.runtime,
org.eclipse.osgi, org.eclipse.update) are created and how/when they are
filled with data. Can somebeody give me a hint?
Thanks
Felix
Re: Buildsystem studio
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
On 10/19/07, Felix Knecht <fe...@apache.org> wrote:
> It's sounds like a hard and interesting challenge I'm willing to accept
> if you don't mind ;-)
Sure! Please, go ahead... My pleasure. :)
Don't hesitate to ask if you have specific questions about the build.
P-A
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
>
> The files needed for RCP are a subset of plugins of a standard eclipse
> distribution + each architecture specific version of SWT and native
> launcher for Apache Directory Studio (which also includes a reorder of
> folders for the Mac OS X specific version, for a more Mac OS X
> experience with an application distributed as a single file) + a few
> hacks on some plugin.xml files of some eclipse plugins (for hiding
> unwanted contributions, such as menus, actions, etc.).
> That's why we're still using eclipse 3.2 packages.
>
> I don't if your proposal could work in that case.
>
It's sounds like a hard and interesting challenge I'm willing to accept
if you don't mind ;-)
Felix
Re: Buildsystem studio
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
On 10/18/07, Felix Knecht <fe...@apache.org> wrote:
> My suggestion is to have the needed files for RCP in a local maven
> repository in the project to be sure to have them.
> Having a script building/updating the local repository from a RCP
> download (not stored in svn). This gives an initial work to download the
> RCPs for the different platforms and run the script to create the repo
> with the needed eclipse artifacts.
> The eclipse artifacts are still in svn stored, but you never now when
> Eclipse will deploy its artifacts. Whenever a newer version of RCP is
> available you can download it, run the script and your fine with the
> dependencies for this.
>
> WDYT?
The files needed for RCP are a subset of plugins of a standard eclipse
distribution + each architecture specific version of SWT and native launcher
for Apache Directory Studio (which also includes a reorder of folders for
the Mac OS X specific version, for a more Mac OS X experience with an
application distributed as a single file) + a few hacks on some
plugin.xmlfiles of some eclipse plugins (for hiding unwanted
contributions, such as
menus, actions, etc.).
That's why we're still using eclipse 3.2 packages.
I don't if your proposal could work in that case.
WDYT?
P-A
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
> 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. The Studio
> team is regularly looking for the best way to do that (and we
> discussed about that with the Maven guys in May).
>
>
My suggestion is to have the needed files for RCP in a local maven
repository in the project to be sure to have them.
Having a script building/updating the local repository from a RCP
download (not stored in svn). This gives an initial work to download the
RCPs for the different platforms and run the script to create the repo
with the needed eclipse artifacts.
The eclipse artifacts are still in svn stored, but you never now when
Eclipse will deploy its artifacts. Whenever a newer version of RCP is
available you can download it, run the script and your fine with the
dependencies for this.
WDYT?
Felix
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
Emmanuel Lecharny schrieb:
>> What do you mean by 'clear'?
>>
>
> I was refering to one of the previous Pierre-Arnaud mail about the
> need to have a pre-installed Eclipse on the computer on which you
> build the package, and to have it for every platforms (ie, I want to
> be able to build the mac, linux and windows package from my linux box
> without having to install eclipse at all)
>
Yep, this must be the goal.
Re: Buildsystem studio
Posted by Emmanuel Lecharny <el...@gmail.com>.
> What do you mean by 'clear'?
I was refering to one of the previous Pierre-Arnaud mail about the
need to have a pre-installed Eclipse on the computer on which you
build the package, and to have it for every platforms (ie, I want to
be able to build the mac, linux and windows package from my linux box
without having to install eclipse at all)
I'm sure that we can find out a solution for that, it just had to be done :)
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
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 <fe...@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
>>
>>
>>
>
>
>
Re: Buildsystem studio
Posted by Emmanuel Lecharny <el...@gmail.com>.
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...
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. 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 <fe...@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
>
>
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
Re: Buildsystem studio
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Ok, I understand and I agree with all these points...
You're right, from a community POV, it would be better to have a unique
build system.
I just hope we can find a way to do in Maven what we are doing right now
with Ant+Ivy and keep the build as flexible and simple to use as it is.
Maybe we need to create specific Maven plugins for bundling our Eclipse
Plugins (compiling code with Eclipse dependencies, adding specific jar
dependencies in the bundle package), Features (just bundle the feature
project as a simple jar), Help Plugins (compiling eclipse and html dockbook
generated outputs) and the RCP Application (selecting the correct
architecture target and adding the needed plugins and features).
Regards,
P-A
On 10/18/07, Felix Knecht <fe...@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
>
>
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
> 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
Re: Buildsystem studio
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Hi Felix,
I confirm Alex and Emmanuel answers about the dependencies question. I would
also add that, as we depend on some parts of the server (Apache DS),
basically shared-ldap, server-core, etc., we needed to use snapshot versions
of some of these jars (because bugs had ben fixed but no new version
released), so we're storing them inside our own repo.
[1] http://www.breskeby.com/240
> [2] http://mojo.codehaus.org/pde-maven-plugin/index.html
Thanks for these links.
[1] Describes the build of an EclipseRCP Application with maven using
> the pde-maven-plugin [2]. [1] is unfortunately written in German. Maybe
> this could give a hint. Reading [1] it's expected to have an Eclipse
> installation somewhere on the build system what makes me not really
> happy - but it seems to be possible.
I already took a look at the PDE Maven Plugin but the fact that it is using
eclipse to build the application forces us, as you noticed, to have an
eclipse installation somewhere (or maybe multiple - one for each OS - I did
not test it that much).
So I didn't like that much this idea.
For now I'm almost on 80% - I can build the updatesite including all the
> jars (haven't tested it yet). But as usual the last 20% (RCP) will
> probably beome 80% of work ;-)
>
If you can build each separate plugin (excluding the RCP app), then you can
build the update site.
It's just matter of packaging, putting plugins jars in the 'plugins' folder
and features jars in the 'features' folder.
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...
Regards,
P-A
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
>
> Since, the build system works well now, I think we'll stay like that
> for a little while. But if you have links for building Eclipse plugins
> and Eclipse RCP applications with Maven, I would love to read them... ;)
[1] Describes the build of an EclipseRCP Application with maven using
the pde-maven-plugin [2]. [1] is unfortunately written in German. Maybe
this could give a hint. Reading [1] it's expected to have an Eclipse
installation somewhere on the build system what makes me not really
happy - but it seems to be possible.
For now I'm almost on 80% - I can build the updatesite including all the
jars (haven't tested it yet). But as usual the last 20% (RCP) will
probably beome 80% of work ;-)
Felix
[1] http://www.breskeby.com/240
[2] http://mojo.codehaus.org/pde-maven-plugin/index.html
Re: Buildsystem studio
Posted by Emmanuel Lecharny <el...@gmail.com>.
Felix,
not only nobody objects, but this would be welcomed !
On 10/17/07, Felix Knecht <fe...@apache.org> wrote:
> If nobody objects I'll try to get a maven2 build working on the studio
> as well.
>
> Felix
>
>
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
If nobody objects I'll try to get a maven2 build working on the studio
as well.
Felix
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
>
> On 10/17/07, *Felix Knecht* <felixk@apache.org
> <ma...@apache.org>> wrote:
>
> Pierre-Arnaud Marcelot schrieb:
> > Hi Felix,
> >
> > Well, the answer is: both...
> >
> > At the beginning at the project, when we started the build
> system, we
> > tried to use Maven first. Maven is really great for building
> jars but
> > building Eclipse plugins is very special. We couldn't find a way for
> > Maven to resolve the Eclipse dependencies of the plugins (like
> Eclipse
> > Core, Eclipse SWT for example).
>
For the dependencies stored in svn you can define a local repository to
use for maven. The directory structure would be equal to a remote maven
repo.
Definition of a local maven repo within the project.
<repositories>
<repository>
<releases>
<checksumPolicy>ignore</checksumPolicy>
</releases>
<snapshots>
<checksumPolicy>ignore</checksumPolicy>
</snapshots>
<id>provided.local</id>
<name>Locally Provided Repository</name>
<url>file:${project.basedir}/../dependencies</url>
</repository>
> >
> > It became even more difficult when we tried to build the RCP
> > application for each environment (Mac OS X Intel & PPC, Linux i386,
> > PPC, AMD64, and Windows i386) and incorporate the plugins in it.
> >
> > So, we turned to Ant+Ivy instead.
> >
> > I've already tried to move to Maven our build system several times,
> > but I could not find a way to make it work.
> >
> > For the 1.0 release, we've simplified the Ant+Ivy build system to be
> > easier to use to define a new Plugin, Feature, Help Plugin, or
> simple
> > utility Jar.
> > A common Ant script is inherited from each project specific
> build.xml
> > file. This common Ant script defines base tasks for building,
> > packaging, generating documentation, etc., that each project
> specific
> > build.xml file can override if it needs a special behavior.
> >
> > For a simple Eclipse Plugin, the build.xml file could look as simple
> > as this:
> > <project default="plugin">
> > <import file="../studio-build/build.xml"/>
> > </project>
> >
> > Since, the build system works well now, I think we'll stay like that
> > for a little while. But if you have links for building Eclipse
> plugins
> > and Eclipse RCP applications with Maven, I would love to read
> them... ;)
>
> Not yet, but I hope to find some time to figure it out.
> First I need to understand how the ant/ivy build works in detail. Can
> you give me a hint where Ivy has the configuration for dependencies?
>
> Felix
>
>
Re: Buildsystem studio
Posted by Emmanuel Lecharny <el...@gmail.com>.
Long, long discussion :)
>From the philosophical point of view, I personally think we should
store the jars in svn (for many reasons), but this is just me, I
think.
As Alex stated, when Studio has been started, all the eclipse jars
where missing in mavn repo, so the decision was made to store them in
svn.
If we switch to maven, as all the Apache projects which use maven
depends on a repo, I see no reason why we should make an exception for
Studio.
On 10/18/07, Alex Karasulu <ak...@apache.org> wrote:
> I think they were not available in the remote repository as you suggest.
>
> Alex
>
>
> On 10/18/07, Felix Knecht <felixk@apache.org > wrote:
> >
> > > We have the '/dependencies' folder that is divided into two parts. The
> > > 'eclipse' folder is the store for our eclipse dependencies for plugins
> > > and RCP application. The 'externals' folder is the Ivy repository for
> > > our dependencies.
> > >
> >
> > Is it policy to have all the dependencies in svn repository as well or
> where the dependencies (at least the external)
> > just not remote available at that time?
> >
> > Felix
> >
>
>
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
Re: Buildsystem studio
Posted by Alex Karasulu <ak...@apache.org>.
I think they were not available in the remote repository as you suggest.
Alex
On 10/18/07, Felix Knecht <fe...@apache.org> wrote:
>
>
> > We have the '/dependencies' folder that is divided into two parts. The
> > 'eclipse' folder is the store for our eclipse dependencies for plugins
> > and RCP application. The 'externals' folder is the Ivy repository for
> > our dependencies.
> >
>
> Is it policy to have all the dependencies in svn repository as well or
> where the dependencies (at least the external)
> just not remote available at that time?
>
> Felix
>
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
> We have the '/dependencies' folder that is divided into two parts. The
> 'eclipse' folder is the store for our eclipse dependencies for plugins
> and RCP application. The 'externals' folder is the Ivy repository for
> our dependencies.
>
Is it policy to have all the dependencies in svn repository as well or where the dependencies (at least the external)
just not remote available at that time?
Felix
Re: Buildsystem studio
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
The configuration of Ivy is situated in the '/tools/ivyconf.xml'.
We have the '/dependencies' folder that is divided into two parts. The
'eclipse' folder is the store for our eclipse dependencies for plugins and
RCP application. The 'externals' folder is the Ivy repository for our
dependencies.
Pierre-Arnaud
On 10/17/07, Felix Knecht <fe...@apache.org> wrote:
>
> Pierre-Arnaud Marcelot schrieb:
> > Hi Felix,
> >
> > Well, the answer is: both...
> >
> > At the beginning at the project, when we started the build system, we
> > tried to use Maven first. Maven is really great for building jars but
> > building Eclipse plugins is very special. We couldn't find a way for
> > Maven to resolve the Eclipse dependencies of the plugins (like Eclipse
> > Core, Eclipse SWT for example).
> >
> > It became even more difficult when we tried to build the RCP
> > application for each environment (Mac OS X Intel & PPC, Linux i386,
> > PPC, AMD64, and Windows i386) and incorporate the plugins in it.
> >
> > So, we turned to Ant+Ivy instead.
> >
> > I've already tried to move to Maven our build system several times,
> > but I could not find a way to make it work.
> >
> > For the 1.0 release, we've simplified the Ant+Ivy build system to be
> > easier to use to define a new Plugin, Feature, Help Plugin, or simple
> > utility Jar.
> > A common Ant script is inherited from each project specific build.xml
> > file. This common Ant script defines base tasks for building,
> > packaging, generating documentation, etc., that each project specific
> > build.xml file can override if it needs a special behavior.
> >
> > For a simple Eclipse Plugin, the build.xml file could look as simple
> > as this:
> > <project default="plugin">
> > <import file="../studio-build/build.xml"/>
> > </project>
> >
> > Since, the build system works well now, I think we'll stay like that
> > for a little while. But if you have links for building Eclipse plugins
> > and Eclipse RCP applications with Maven, I would love to read them... ;)
>
> Not yet, but I hope to find some time to figure it out.
> First I need to understand how the ant/ivy build works in detail. Can
> you give me a hint where Ivy has the configuration for dependencies?
>
> Felix
>
>
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
Pierre-Arnaud Marcelot schrieb:
> Hi Felix,
>
> Well, the answer is: both...
>
> At the beginning at the project, when we started the build system, we
> tried to use Maven first. Maven is really great for building jars but
> building Eclipse plugins is very special. We couldn't find a way for
> Maven to resolve the Eclipse dependencies of the plugins (like Eclipse
> Core, Eclipse SWT for example).
>
> It became even more difficult when we tried to build the RCP
> application for each environment (Mac OS X Intel & PPC, Linux i386,
> PPC, AMD64, and Windows i386) and incorporate the plugins in it.
>
> So, we turned to Ant+Ivy instead.
>
> I've already tried to move to Maven our build system several times,
> but I could not find a way to make it work.
>
> For the 1.0 release, we've simplified the Ant+Ivy build system to be
> easier to use to define a new Plugin, Feature, Help Plugin, or simple
> utility Jar.
> A common Ant script is inherited from each project specific build.xml
> file. This common Ant script defines base tasks for building,
> packaging, generating documentation, etc., that each project specific
> build.xml file can override if it needs a special behavior.
>
> For a simple Eclipse Plugin, the build.xml file could look as simple
> as this:
> <project default="plugin">
> <import file="../studio-build/build.xml"/>
> </project>
>
> Since, the build system works well now, I think we'll stay like that
> for a little while. But if you have links for building Eclipse plugins
> and Eclipse RCP applications with Maven, I would love to read them... ;)
Not yet, but I hope to find some time to figure it out.
First I need to understand how the ant/ivy build works in detail. Can
you give me a hint where Ivy has the configuration for dependencies?
Felix
Re: Buildsystem studio
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Hi Felix,
Well, the answer is: both...
At the beginning at the project, when we started the build system, we tried
to use Maven first. Maven is really great for building jars but building
Eclipse plugins is very special. We couldn't find a way for Maven to resolve
the Eclipse dependencies of the plugins (like Eclipse Core, Eclipse SWT for
example).
It became even more difficult when we tried to build the RCP application for
each environment (Mac OS X Intel & PPC, Linux i386, PPC, AMD64, and Windows
i386) and incorporate the plugins in it.
So, we turned to Ant+Ivy instead.
I've already tried to move to Maven our build system several times, but I
could not find a way to make it work.
For the 1.0 release, we've simplified the Ant+Ivy build system to be easier
to use to define a new Plugin, Feature, Help Plugin, or simple utility Jar.
A common Ant script is inherited from each project specific build.xml file.
This common Ant script defines base tasks for building, packaging,
generating documentation, etc., that each project specific build.xml file
can override if it needs a special behavior.
For a simple Eclipse Plugin, the build.xml file could look as simple as
this:
<project default="plugin">
<import file="../studio-build/build.xml"/>
</project>
Since, the build system works well now, I think we'll stay like that for a
little while. But if you have links for building Eclipse plugins and Eclipse
RCP applications with Maven, I would love to read them... ;)
Regards,
Pierre-Arnaud Marcelot
On 10/17/07, Felix Knecht <fe...@apache.org> wrote:
>
> Hi all
>
> I don't want to wake up sleeping dogs and fore sure there exists already
> a lot of threads about this subject, but googling on the
> mail-archives.apache.org (I haven't found a search functionality at the
> mail-archives itself) didn't point me to a final decision.
>
> The buildsystem for studio is ant/ivy based whereas all the others are
> maven2 based. Is this on purpose (for a special reason) or just
> historical based and not yet migrated?
>
> Regards
> Felix
>
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
Emmanuel Lecharny schrieb:
> Hi Felix,
>
> when Studio has been started, there were no way to build Eclipse based
> applications with Maven (at least, no easy ways). This is the reason
> why we are still using ant+ivy for Studio.
>
> Now, we could migrate to maven, but "when it works, don't fix it" ;)
>
I see, thanks.
Re: Buildsystem studio
Posted by Emmanuel Lecharny <el...@gmail.com>.
Hi Felix,
when Studio has been started, there were no way to build Eclipse based
applications with Maven (at least, no easy ways). This is the reason
why we are still using ant+ivy for Studio.
Now, we could migrate to maven, but "when it works, don't fix it" ;)
On 10/17/07, Felix Knecht <fe...@apache.org> wrote:
> Hi all
>
> I don't want to wake up sleeping dogs and fore sure there exists already
> a lot of threads about this subject, but googling on the
> mail-archives.apache.org (I haven't found a search functionality at the
> mail-archives itself) didn't point me to a final decision.
>
> The buildsystem for studio is ant/ivy based whereas all the others are
> maven2 based. Is this on purpose (for a special reason) or just
> historical based and not yet migrated?
>
> Regards
> Felix
>
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com