Re: [nebula-dev] In light of Restructuting - On our builds and CVS

[Nicolas Richeton <nicolas.richeton@xxxxxxxxx>]

Hi Nebula committers,

More updates on builds :
- I set up the incubation build.
- Javadocs are available for both builds. Please ensure it is complete :-)
- I made a parent pom which defines all required maven plugins and configuration. This makes the pom file which is added to projects very small. 

Current issues :
- radiogroup tests fail because they use protected methods of the main bundle. This works in Eclipse but not in an osgi environnment.
- Other test issues (see previous mail)
- Some widgets use maven without tycho (see previous mail)
- I tried to setup cobertura for test coverage but it seems to require tests to be in the same bundle as the main code. I'll investigate this.

To be done :
- Build features and update site
- Add remaining projects
- Publish to downloads.eclipse.org

Please tell me if I can change your widgets to add them in the build or fix the issues.
You can add your email in Hudson to be notified of build failures.

Donald: I won't remove releng files for now, and I will keep the xviewer one untouched if I do.

--
Nicolas



Le 18 nov. 2010 à 20:56, "Dunne, Donald G" <donald.g.dunne@xxxxxxxxxx> a écrit :

> Please don't remove XViewer .releng project.  We have a separate hudson build that we're managing. 
> 
> -----Original Message-----
> From: nebula-dev-bounces@xxxxxxxxxxx [mailto:nebula-dev-bounces@xxxxxxxxxxx] On Behalf Of Nicolas Richeton
> Sent: Thursday, November 18, 2010 10:47 AM
> To: Nebula Dev
> Subject: Re: [nebula-dev] In light of Restructuting - On our builds and CVS
> 
> A few comments after creating the nebula release build.
> 
> - compositetable.tests is a fragment. This causes issues with tycho. Can it be turned into a plugin ? 
> 
> - calendarcombo already uses maven like a standard java project. Can the current pom be removed and replaced by a tycho one ? 
> 
> - I did not add xviewer yet since it depends on calendarcombo.
> 
> - We should agree on groupId, artifactId, and versions conventions. My proposal is groupId : org.eclipse(.swat).nebula , artifactId : project name, version : per project, but with .qualifier (means -SNAPSHOT version for maven)
> 
> - We can now get rid of .releng projects. We only have to add a pom.xml file in each project to support building with maven.
> 
> - I can generate an update site easily with an additional project. I'll do it asap.
> 
> - I will make some refactoring in pom in order to reduce the duplication : most information can be moved to a parent pom.
> 
> 
> gallery, grid, pshelf, pgroup and compositetable latest builds can be downloaded from hudson.  
> 
> --
> Nicolas
> 
> 
> 
> 
> 
> Le 18 nov. 2010 à 18:32, Tom Schindl a écrit :
> 
>> Wonderful :-)
>> 
>> Tom
>> 
>> Am 18.11.10 18:18, schrieb Nicolas Richeton:
>>> Hi all, 
>>> 
>>> You should take a look at
>>> https://hudson.eclipse.org/hudson/view/Tycho%20+%20Maven/job/maven-nebula-1.0-nightly/
>>> 
>>> :-)
>>> Work in progress.....
>> 
>> 
>> -- 
>> B e s t S o l u t i o n . a t                        EDV Systemhaus GmbH
>> ------------------------------------------------------------------------
>> tom schindl                                        geschaeftsfuehrer/CEO
>> ------------------------------------------------------------------------
>> eduard-bodem-gasse 5/1    A-6020 innsbruck      phone    ++43 512 935834
>> _______________________________________________
>> nebula-dev mailing list
>> nebula-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/nebula-dev
> 
> _______________________________________________
> nebula-dev mailing list
> nebula-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/nebula-dev
> _______________________________________________
> nebula-dev mailing list
> nebula-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/nebula-dev