btw Tom, I've been glancing at some of the work you've been doing. When
you're getting close to finishing things, can you post the bundles you
have in Orbit so some of us can run a sanity check?
Happy Orbiting ;)
On Fri, May 1, 2009 at 9:22 AM, Tom Ware <tom.ware@xxxxxxxxxx
<mailto:tom.ware@xxxxxxxxxx>> wrote:
Hi DJ,
Thanks for the response. One question inline:
DJ Houghton wrote:
Hey Tom, off the top of my head those sound like the right steps
to take. I usually initially forget to tag the feature and
update the feature entry in the map file so you are already one
up on me. :-)
One thing I would do it double-check your JAR that you are
committing to ensure that you have an about.html file and its
structure is what you expect.
So far I have not committed a jar. Have I missed something? I have
an Eclipse project and a set of files in the Orbit CVS repository
(including an about.html file), but no jar. Is there a step I have
missed that involves building a jar? My assumption was that the
Orbit build would produce a jar.
Thanks,
Tom
If you don't feel like waiting for the builder to automatically
discover your changes you should be able to kick off a new build
from the dashboard.
http://build.eclipse.org:9777/dashboard/tab/builds
dj
orbit-dev-bounces@xxxxxxxxxxx
<mailto:orbit-dev-bounces@xxxxxxxxxxx> wrote on 04/30/2009
03:46:30 PM:
> Hi All,
>
> I have started the work to get my first bundle into Orbit.
>
> I started with http://wiki.eclipse.org/Adding_Bundles_to_Orbit
> and believe I
> have the correct pieces in the CVS repository. Now I want to
figure
> out how to
> get my bundle into the build.
>
> I was able to find the following two pages:
>
>
http://wiki.eclipse.org/Orbit_Builds#Orbit_Builds_for_Orbit_Committers
> http://wiki.eclipse.org/Adding_Bundles_To_Orbit_In_5_Minutes
>
> After looking at those pages, I am following the steps
from the
> Adding_Bundles_To_Orbit_In_5_Minutes page. The steps I am
following
> are below,
> but they are just a slightly edited version of what is on the web
> page. Since a
> number of the steps below involve comitting changes, I am
wondering
> if there is
> an easy way to test my changes before committing. Do I need to
> check-out all of
> orbit to do that?
>
> Steps I plan on taking are here:
>
> 1. Get org.eclipse.orbit.releng and
org.eclipse.orbit.build.feature.
> set1 from CVS
>
> 2. Add a plugin entry to
org.eclipse.orbit.build.feature.set1/feature.xml
> following the conventions used by the existing plugins
>
> <plugin
> id="javax.persistence"
> download-size="0"
> install-size="0"
> version="1.0.0.qualifier"
> unpack="false"/>
>
> 3. Commit my changes and tag feature.xml with appropriate
versioning info
> (vYYYYMMDDHHMM) Lets use v200905010100 as an example
>
> 4. Tag my javax.persistence 1_0_0 branch version with the same
> version as in #3
> above (v200905010100)
>
> 5. Add a reference to org.eclipse.orbit.releng/psf/orbit.psf
>
> <project
>
reference="1.0,:extssh:dev.eclipse.org:/cvsroot/tools,org.eclipse.
> orbit/javax.persistence,javax.persistence_v1.0.0,v1_0_0"/>
>
> 6. Add to org.eclipse.orbit.releng/maps/bundles.map
>
> plugin@javax.persistence=v200905010100,:pserver:anonymous@dev.
> eclipse.org:/cvsroot/tools,,org.eclipse.orbit/javax.persistence
>
> 7. Change feature in bundles.map to have my new version number
>
>
feature@org.eclipse.orbit.build.feature.set1=v200905010100,:pserver:
> anonymous@xxxxxxxxxxxxxxx:/cvsroot/tools,,org.eclipse.orbit/org.
> eclipse.orbit.build.feature.set1
>
> 8 Commit
>
> 9 Wait for the automated build to run
>
> Thanks in advance for any information or hints.
> -Tom
>
> _______________________________________________
> orbit-dev mailing list
> orbit-dev@xxxxxxxxxxx <mailto:orbit-dev@xxxxxxxxxxx>
> https://dev.eclipse.org/mailman/listinfo/orbit-dev
------------------------------------------------------------------------
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx <mailto:orbit-dev@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/orbit-dev
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx <mailto:orbit-dev@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/orbit-dev
--
Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/eclipsesource | http://twitter.com/caniszczyk
------------------------------------------------------------------------
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev