I always got confused about what to get from svn. Why don't you provide nightly tar balls for downloading latest version for "phoneme feature", or provide some kind of script?
When I look through component/tags, I saw names like "midp-feature-mr2-promo-b07". If I checkout same tag for each component, does it mean building should complete?
Yes, each component's tag folder contains the "latest known stable" snapshot of the source code. The various component trunks are possibly unstable, though of course we try to keep instability to a minimum. Another source of "instability" is interdependent changes among the components. A component's trunk might be fine by itself, but sometimes it depends on a change made in another component's trunk (or vice versa). This doesn't happen very often, but if it does occur, it might mean that the trunk of one component won't build with a tag of another component. We do try to keep all the component trunks in sync, though.
To your second question, yes, if you check out the corresponding tags of each component, they should all work together. That is, the tag "*-feature-mr2-promo-b07" for each component should all work together; they constitute what we're calling a "development release" of phoneME Feature. (Occasionally we'll get a broken build, but if that occurs we'll try to fix it quickly and replace the tags or issue a new set of tags.) If this doesn't work, please let us know.
For convenience, we collect all the matching tags together into a "supertag" under /builds. For example, the b04 development release is collected under /builds/phoneme_feature-mr2-dev-b04. Each of the subdirectories is a copy of the component's tag for that build, for instance, cldc is copy of cldc-mr2-promo-b04.
Unfortunately it doesn't look like we've done this since b04, so the supertags for b05, b06, and b07 are missing. I'll look into this. Meanwhile, though it's a bit tedious, you can check out the individual component tags for b07 and it should work.
I've posted an explanation of the repository structure on the wiki.
There's more info that needs to be added, but I hope this information helps get you started.
I got the point. Does each component's tag folder contains latest-working folder? and trunk can be broken (not buildable) at any moment?
Could you explain what you find confusing about getting stuff from svn? I could guess, but I'd rather get a fresh perspective from you. We certainly need to put some more information about the svn repository structure out there, possibly along with some tools for dealing with it more effectively. If you have any thoughts or insights, it would help us with this.
No real instructions to get an up-to-date copy of phoneme instead of mr2_b4 package.
"svn checkout https://phoneme.dev.java.net/svn/phoneme/trunk phoneme --username guest"
should get source code but command resulted with a web site on my disk :)
You might want to browse a little before you try the download:
The terse instructions should be corrected.
> No real instructions to get an up-to-date copy of phoneme instead of mr2_b4 package.
> "svn checkout https://phoneme.dev.java.net/svn/phoneme/trunk phoneme --username guest"
> should get source code but command resulted with a web site on my disk :)
> [Message sent by forum member 'selenau' (selenau)]
> To unsubscribe, e-mail: email@example.com
> For additional commands, e-mail: firstname.lastname@example.org
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
That's right but I still can't get a simple mirror on my disk with a single command.
You probably do not want to submit "svn checkout .../components". :)
Now I'm going to get each component's trunk manually. I mean
svn checkout .../components/cldc/trunk
svn checkout .../components/midp/trunk
You're quite right that dealing with the svn repository is confusing. It's on my list of things to work on to get additional doc and some tools out there to help people deal with it. It's even getting near the top of the list. :-)
Unfortunately, as you noticed, the default svn page provided by java.net assumes that the svn repository has a particular structure. Since all the code is under /components instead of /trunk, following the instructions there just gets you a copy of the website. Even more unfortunately, it's turned out to be difficult to get that page changed. So, we're going to have to put up some other doc about the repository that says something like "ignore the instructions over there." :-(
Also, you're correct that you probably don't want to do "svn checkout .../components" since you'll get all branches and tags for each component, which is probably 10 or 20 times the amount of files you'll need. You're right that you need to do individual "svn checkout" commands for each component. This is rather tedious, but we have a script that helps automate the process of maintaining multiple working copies and keeping them up to date. I intend to post this script and some instructions for how to use it in the near future.
If you don't want the absolute latest and greatest stuff, you can also look in the /builds directory in the repository. This directory aggregates recent tags of the components, so you can get it all at once. For example, /builds/phoneme_feature-mr2-dev-b04 is a "development build" that contains all the components for build #4 of phoneME Feature MR2. You can get it all with one "svn co" command. However, this is a snapshot of the past, about six weeks old at this point, and active development is occurring on the trunks.
I would say that it is not so difficult to do from technical point of view. On the other hand, as far as I know, it should be a Project Management Committee (PMC) decision that will request to have a nightly builds available.
Also I can say to you that we were going to start regularly publish the numbers of the latest stable revisions soon. I hope that it would make your life a bit easier :)
Your use of this web site or any of its content or software indicates your agreement to be bound by these Terms of Participation.
Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.