[recommenders-dev] 答复: [args] setting up a build and update site

["Tong Wu" <tong.wu.stap@xxxxxxxxx>]

Hi Andreas:
 Thanks very much for your help  : )
 
 But we still have some questions.
 1. If we follow the two steps, then Hudson will automated run maven and
publishes the update site when we commit changes, right?
 2. Hudson will publish the site to 'dist' folder, is there any update site
URL for users?
 3. As our project have many dependences like
"org.eclipse.recommenders.utils.rcp ", "
org.eclipse.recommenders.completion.rcp"... Maybe it's different from Jayes.
Essentially, our project is mostly like the sub project of
"org.eclipse.recommenders.completion.rcp.overrides". So we want to know if
there's a lot of dependences what should be done to solve this problem? Or
is there any examples, so we can learn from it.


-----------------------------------
Best,
Tong Wu


 

-----邮件原件-----
发件人: recommenders-dev-bounces@xxxxxxxxxxx
[mailto:recommenders-dev-bounces@xxxxxxxxxxx] 代表 Andreas Sewe
发送时间: 2013年2月4日 22:19
收件人: Recommenders developer discussions
主题: Re: [recommenders-dev] [args] setting up a build and update site

Hi,

>          We are trying to create an automated build and update site. 
> But we didn’t find any useful information about it.
> 
> Now we have three projects (plug-in project, feature project and 
> update site project) in our workspace. Is that means if we push the 
> plug-in and feature projects to the repository in a specific 
> structure, then the update site will be automated built and generated 
> without uploading the update site project from our workspace?
> 
> If you have some reference material will be appreciated.

have a look at how we organize things at
<https://git.eclipse.org/c/recommenders/org.eclipse.recommenders.git/tree/>.

First of all, we use Maven+Tycho
<http://wiki.eclipse.org/Category:Tycho> to do the build. So, the following
is enough to build Code Recommenders:

> git clone
git://git.eclipse.org/gitroot/recommenders/org.eclipse.recommenders.git
> cd org.eclipse.recommenders
> mvn clean install

And this is essentially what Hudson (our CI server) does as well. If this
Maven build is successful, Hudson then publishes the update site.

Now, what does this mean for your incubator project?

First of all, please follow our directory structure of "plugins", "tests",
"features", and "dist" (the latter contains a project that produces your
update site which is then published by Hudson).

Second, please inherit from our parent POM (Maven coordinates
org.eclipse.recommenders:org.eclipse.recommenders.parent:1.0.3-SNAPSHOT).
This ensures that you are using the same (tried and tested) settings for the
various Maven plugins as we do.

If you want to have a look at another project that does this, have a look at
<https://github.com/kutschkem/Jayes>, where Michael develops the next
version of the Jayes library used in Code Recommenders.

All this makes it easier to eventually graduate your project from the
incubator and merge it with the main codebase.

Hope this helps, but if you have any more questions, please ask.

Andreas
--
Codetrails.com - the knowledge transfer company
_______________________________________________
recommenders-dev mailing list
recommenders-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/recommenders-dev