Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[emf-dev] Re: EMF 2.6.0 Nightly build w/ RAP published using Athena

OK, I just took a closer look at the contents of each of the ZIP archives produced by the build. Unfortunately, despite the exclude statements in buildExtra.xml, the new 'build' feature and all of the new RAP features are still being included in the runtime and SDK archives for EMF. How can I exclude these features (and plug-ins) from those archives?



On Fri, Mar 12, 2010 at 10:10 AM, Kenn Hussey <kenn.hussey@xxxxxxxxx> wrote:

Regarding #3 (the test failure), it looks like there's a test that tries to run the doc build, and since you've essentially disabled the custom build for doc, it's not working anymore. Does anyone (Dave, Marcelo, or Ed) have a suggestion as to what to do here? I know we had a discussion on that bug about what to do about Javadoc in the doc plug-ins, but I'm not sure we came to any conclusions...

Note, also, that there are warning related to use of the new @SuppressWarnings("rawtypes") annotation. Is this something we need to inform the build compiler about (or ask it to ignore)?



On Fri, Mar 12, 2010 at 3:26 AM, Nick Boldt <nickboldt@xxxxxxxxx> wrote:
First EMF 2.6 build (including new RAP features) published thanx to Kenn and my work today.

The build project is here [0], which includes the promote.xml and promote-?.properties files for publishing builds:


The promote command, which can be set up to run via crontab, is this:

ant -f promote.xml

With full paths:

/opt/public/common/apache-ant-1.7.1/bin/ant -f \

/opt/users/hudsonbuild/.hudson/jobs/cbi-emf-core-2.6-nightly/workspace/org.eclipse.emf/org.eclipse.emf/releng/org.eclipse.emf.releng.athena/promote.xml \


/opt/public/common/apache-ant-1.7.1/bin/ant -f \

/opt/users/hudsonbuild/.hudson/jobs/cbi-emf-core-2.6-integration/workspace/org.eclipse.emf/org.eclipse.emf/releng/org.eclipse.emf.releng.athena/promote.xml \

Still left to do is setting up the correct properties in the such that the Helios .build file will be automatically updated when EMF 2.6M6 (and subsequent milestones/RCs) are published [1].


And, if Kenn (or someone else) wants to own the automated publishing of I or N builds, then they can add the above command(s) to their crontab [2].


I also have a suspicion that either a junit test needs to be updated, or the doc features/plugins are not being built correctly [3]:


Also, tagging and releasing is not yet integrated into Athena. However, you can still do so via commandline script [4], [5] or using Eclipse Releng Tools plugin.


Nick Boldt ::
Release Engineer :: Eclipse Modeling & Dash Athena

Back to the top