thanks for these catches. I've looked at them all in detail, and indeed there is a small amount of redundant text in the notices file, but the licenses file contain the appropriate licenses. I plan to fix this in the trunk, and let the release stand, unless anyone demands otherwise. As to your comments in the building.txt file there are some useful comments in there that again I will take note of post M2. I have added comments to your comments which I attach. The main point I would say is that the instructions in BUILDING.txt are what is required to build the binary distribution and the samples distribution. If you have this in mind, rather than getting to the point where you have just built binary artifacts, or are able to run the samples, then the instructions should seem clearer. this is why the instructions do not take you through running the samples, since you will have buildt a samples distribution which does have the instructions of how to run the samples.
Best Regards, Kelvin.
On 25/10/06, Venkata Krishnan <[EMAIL PROTECTED]> wrote:
Hi Kelvin,
Sorry could not get to this any earlier than this.... here is what I did and found...
1) Extracted tuscany-sdo-api-1.0-incubator-M2-src.zip and extracted into a SDO_API dir.
- License.txt has a reference to Service Component Architecture at line 233 - just bringing it up just in case it was a slip otherwise please ignore
- Notice.txt mentions using software developed by osoa and that the license for that is in the License.txt. But the License.txt has nothing specific to this (maybe I am missing something here or maybe this is actually not required)
- Status.txt (typo on line 36 C+ = C++)
- Successfully built the source
2) Extracted tuscany-sdo-impl-1.0-incubator-M2-src.zip and extracted into a SDO_API dir.
- License.txt, Notice.txt, Status.txt - same observations as above.
- Building.txt - I have put in comments and attactched that file here. My comments are enclosed in "<<svkrish : .....>>"
3) Moved into sdo/sample and built the sdo/sample successfully.
4) Unable to build the distribution due to ...
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).
Project ID: woodstox:wstx-asl
Reason: Error getting POM for 'woodstox:wstx-asl' from the repository: Error tra
nsferring file
woodstox:wstx-asl:pom:3.0.1
5) When I tried building the distribution offline I ended up with
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
GroupId: org.apache.maven.plugins
ArtifactId: maven-javadoc-plugin
Version: 2.1-20061005.000031-3
Reason: System is offline.
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.maven.plugins -DartifactId=mav
en-javadoc-plugin \
-Dversion=2.1-20061005.000031-3 -Dpackaging=maven-plugin -Dfile=/path/to
/file
org.apache.maven.plugins:maven-javadoc-plugin:maven-plugin:2.1-20061005.0000313
I will try to give this a few more tries later in the evening.
Thanks
- Venkat
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Building SDO Releases
=====================
The SDO specification source distribution and the SDO implementation source
distribution
together with a computer with a live internet connection, maven 2.0.4 installed
and java 1.4.2
or above installed are all you need to build
<<svkrish: do you want to mention the above as a 'Pre-Req' just to keep it
simple...
<< kgoodson: not sure waht you mean, this looks like a prereq statement to
me, are you implying there is a
more conventional best practice for specifying pre-reqs >>
>>1) the SDO binary distribution 2) the SDO samples source distribution (note that the source distribution is a derivative of the binary distribution, since it ships with javadoc, which is generated by the binary distribution) << svkrish: this point seems to be a bit confusing << agreed, I will fix it up in the trunk, but I'm hoping not to have to respin the release, and I don't think that so far this warrants a respin >> Building the SDO Java Implementation Project Binary Release from the source distribution ======================================================================================== (note, these instructions are for building the SDO binary release from source, not for establishing a development environment. If you wish to participate in sdo development, follow the instructions at http://incubator.apache.org/tuscany/java_sdo_overview.html Building -------- 1) Download the corresponding SDO specification source distribution from http://incubator.apache.org/tuscany <<svkrish: Do we plan to update this link to something more specific - helping the user to directly reach the source distribution << kgoodson: i left this vague in order not to make it brittle, If we are too explicit here then when a further release is done then we are sure to rearrange the site and break explicit links, either that or we will find that the fact that we have made explicit links will constrain what we want to do with the site >> >> 2) Execute the instructions in that archive for building the SDO specification component Note: following this step you will have maven installed, and a Java JDK at level 1.4.2 or above installed. 3) If you have chosen to install a JDK at level 5 then all will be fine, but there is one value add component in the Tuscany SDO implementation which relies on new JDK 5.0 features. If you do not wish to use JDK 5 for the following build step, then you will need to delete the file sdo/tools/src/main/java/org/apache/tuscany/sdo/generate/Interface2JavaGenerator.java before proceding 4) Change to the top level directory of the Tuscany SDO Java Implementation project (sdo) of this source distribution. 6) Execute: mvn This will install the sdo implementation jar in you local repository 5) Execute: mvn package javadoc:javadoc assembly:assembly This will build the Tuscany SDO for Java binary distribution artefacts in the sdo/distribution/target directory. <<svkrish: It would be good to say a bit on why we need this or point to the site if this info is there ... the user might wonder why this... for example I am tempted to ask 'what is this and why this' .. if this is required to just run the samples, then can we say that here << kgoodson: we nned this to complete the objective of the title, i.e. building the binary release, at step 4, all you have done is put artifacts in your maven repository, so i think this is clear, but i can add some more words to the file in the trunk if you think it is necessary >> Note: Depending on the load being experienced by remote Maven 2.0 repositories you may have to execute mvn several times until required dependencies are all located in your local maven repository. After you have completed a full successful build you can use "mvn -o" which is much faster. 6) To run the sample programs, change directory to the "sample" directory, and run the command "mvn". Then look in the sample/target/site/apidocs/index.html file for javadoc that describes how to run the samples. <<svkrish: why don't we pull this out into a separate section as follows: Building and Running the SDO Impl Samples ----------------------------- The SDO Impl. Samples are located in the 'sample' sub-directory of the SDO Impl source distribution. The SDO Impl maven build does not include the samples and hence they need to be built separately as follows: - - Change directory to sdo/sample and run the command "mvn" - ... <<kgoodson: I see your point, but again this comes back to the point that these instructions are to get you to the point where you have recreated the artifacts of the M2 releae, one of which is the samples distibution. that samples distribution then contains the instructions to run the samples. >> Building the SDO Samples Source distribution ============================================ To build the SDO Samples source distribution 1) copy the sdo/sample directory from the SDO implementation source distribution to a temporary folder 2) Build the SDO binary distribution as instructed above 3) From the top level directory of your SDO implementation build tree change directory to the sample directory and execute the command mvn javadoc:javadoc to create javadoc for the samples in the target/site directory 4) copy the site folder to the temporary directory created for step 1 4) create .zip and .tar.gz archives of the sample source and javadoc <<svkrish: not clear why we are doing this especially after having mentioned already, in the building section above ...Is this to run the samples then it seems incomplete... or maybe I am missing the picture here >>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
