Re: Branching for Release 1.3 was: Re: Release 1.3?
On Sat, Jun 14, 2008 at 12:11 AM, Luciano Resende [EMAIL PROTECTED] wrote: I'm done with the JSR 250 issues, and got a clean build from latest svn revision. On Fri, Jun 13, 2008 at 1:34 PM, Simon Laws [EMAIL PROTECTED] wrote: On Fri, Jun 13, 2008 at 9:32 PM, Raymond Feng [EMAIL PROTECTED] wrote: I just checked in some improvements in the databinding area after a full clean build. Now I will stay away from the code :-). Thanks, Raymond -- From: Simon Laws [EMAIL PROTECTED] Sent: Friday, June 13, 2008 11:16 AM To: tuscany-dev@ws.apache.org Subject: Branching for Release 1.3 was: Re: Release 1.3? I'm just trying to finish up the changes required to unhook the old domain modules from the runtime, tests and samples. Then I'm pretty much done with things I want to do before cutting the R1.3 branch. I'm planning on doing this first thing tomorrow morning UK time. Can you let me know if there are changes you are working on that you want to finish before I cut the branch. Also if there are changes you have that don't need to go in the branch can you hold back for a little while as I get this done. Obviously I'd like to keep the trunk as stable as possible for the next 12 hours so if people have time to give the code a spin and do a build that would be great. Particularly after I've checked in the build changes related to domain. I'll post when I'm done. Regards Simon Great, thanks Raymond. I'll do an update and another build. Could you do the same to try the domain removal changes I checked in? Simon -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://people.apache.org/%7Elresende http://lresende.blogspot.com/ OK, thanks everyone. I've now taken the branch for 1.3 so feel free to do as you will with trunk. I'll start the process of tidying release, removing the dead modules etc. shortly. I've created a Java-SCA-1.3 category in JIRA so any new issues for the branch in there please. Thanks Simon
Re: Changing SCA trunk version from 2.0-incubating-SNAPSHOT to SNAPSHOT
Trunk is now 1.4-SNAPSHOT in r667767 and a fresh build runs ok for me. Based on all this thread 1.4-SNAPSHOT isn't perfect but seemed what there was best consensus for right now. Feel free to revisit and I'd be happy to do the work to change trunk version to something else if anyone can get consensus on something else. ...ant On Fri, Jun 13, 2008 at 9:45 AM, Rajini Sivaram [EMAIL PROTECTED] wrote: On 6/13/08, ant elder [EMAIL PROTECTED] wrote: Are the OSGI real versions required to be numeric, which would also mean 1.x wouldn't work so well as a version for OSGi right? Yes, the versions need to be numeric, 1.x wont work. ...ant On Fri, Jun 13, 2008 at 9:24 AM, Rajini Sivaram [EMAIL PROTECTED] wrote: Ant, I am not sure how relevant this is, but in the context of versioning Tuscany for OSGi, Tuscany modules are being built as OSGi bundles with real versions (eg. the current build uses 2.0). The version used is not currently derived from the maven version, instead it is specified independently as a property in modules/pom.xml - so it won't actually break if you modified 2.0-incubating-SNAPSHOT to SNAPSHOT. But it will become less obvious to OSGi users what version a Tuscany build really is. We will need a real version for the snapshot builds for building OSGi bundles regardless of whether we use that as the version for maven. The question is whether we need OSGi build versioning to be consistent with maven versions - OSGi users building against Tuscany 1.4-SNAPSHOT probably expect to use the 1.4 release, while non-OSGi users as you say may expect to use the latest SNAPSHOT. Anyway, I just thought I will point this out, I dont actually mind either way. On 6/13/08, ant elder [EMAIL PROTECTED] wrote: On Tue, Jun 10, 2008 at 9:41 AM, ant elder [EMAIL PROTECTED] wrote: On Sat, Jun 7, 2008 at 1:11 AM, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote: Luciano Resende wrote: How about 1.5-SNAPSHOT ? This would probably give us some room to have couple releases without the necessity to keep updating the trunk pom version. And this would probably make everybody happy :) On Fri, Jun 6, 2008 at 1:14 AM, ant elder [EMAIL PROTECTED] wrote: On Fri, Jun 6, 2008 at 9:05 AM, Luciano Resende [EMAIL PROTECTED] wrote: I guess part of problem here is because a lot of people assume that the maven artifact version represents what is going to be our next release and then, if it's set as 2.0-SNAPSHOT, it means our next release would be 2.0. I agree, this is exactly the issue. But I'm not sure its that much of an unreasonable assumption, it does feel odd to me to have 2.0-SNAPSHOT as the trunk version before there has been any decision to start working on a 2.0 in trunk. ...ant I'd prefer the next logical number, 1.3 for example. I still think plain SNAPSHOT would be simplest but as no one else seems to like that I think I agree with this - the next logical number seems better than things like 1.x or 2.0 etc. So, I plan to change trunk to 1.4-SNAPSHOT when the 1.3 branch is taken, do say if you really don't like this but its what we've been doing most of the time in the past so i hope most can live with it. ...ant I've been asked off list to highlight an issue that may not have been clear from whats already been said in this thread. If we use 1.4-SNAPSHOT in trunk then external people who want to stay up to date with the latest code will use that version in their dependencies. They may not pay that close attention to the dev list so when we create the branch for a real 1.4 release and change the trunk to 1.5-SNAPSHOT the users dependencies will still use 1.4-SNAPSHOT but now instead of getting the latest code they're getting the stable branch code. One way this could be avoided is by using a trunk version of simply SNAPSHOT. Is anyone really against SNAPSHOT if we went for that instead of 1.4-SNAPSHOT? ...ant -- Thank you... Regards, Rajini -- Thank you... Regards, Rajini
Re: Tuscany SCA Chinese Discussion Forum (Tuscany SCA中文论坛)
This is awesome, Thanks Raymond. ;) -Jeff On Sat, Jun 14, 2008 at 6:28 AM, Raymond Feng [EMAIL PROTECTED] wrote: Hi, I have created a Google group to provide a forum for Chinese-speaking developers and users to exchange ideas and practices in Chinese about Tuscany and SCA. The group home page is: http://groups.google.com/group/tuscany-sca-chinese. You are invited to join and contribute to the forum! Please note tuscany-dev and tuscany-user mailing lists are the official ways to interact within the Tuscany project. The group is more like a user group for the Chinese community who prefers to communicate in Chinese. Thanks, Raymond -- Cheers, Jeff Yu http://people.apache.org/~jeffyu http://jeffyuchang.blogspot.com
[jira] Created: (TUSCANY-2391) Tuscany SCA support in the Geronimo Admin Console
Tuscany SCA support in the Geronimo Admin Console - Key: TUSCANY-2391 URL: https://issues.apache.org/jira/browse/TUSCANY-2391 Project: Tuscany Issue Type: New Feature Components: Java SCA Tools Reporter: Thilina Buddhika This is the primary implementation of this Admin Console Extension. It does not contain any functionality related to Tuscany. But it is intended to use this as the basis for developing the ACE. The patch contains the source, and provides a maven build file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2391) Tuscany SCA support in the Geronimo Admin Console
[ https://issues.apache.org/jira/browse/TUSCANY-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thilina Buddhika updated TUSCANY-2391: -- Attachment: geronimo_ACE.zip This is the primary installation of the geronimo ACE for managing Tuscany SCA. Tuscany SCA support in the Geronimo Admin Console - Key: TUSCANY-2391 URL: https://issues.apache.org/jira/browse/TUSCANY-2391 Project: Tuscany Issue Type: New Feature Components: Java SCA Tools Reporter: Thilina Buddhika Attachments: geronimo_ACE.zip This is the primary implementation of this Admin Console Extension. It does not contain any functionality related to Tuscany. But it is intended to use this as the basis for developing the ACE. The patch contains the source, and provides a maven build file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2391) Tuscany SCA support in the Geronimo Admin Console
[ https://issues.apache.org/jira/browse/TUSCANY-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder reassigned TUSCANY-2391: -- Assignee: ant elder Tuscany SCA support in the Geronimo Admin Console - Key: TUSCANY-2391 URL: https://issues.apache.org/jira/browse/TUSCANY-2391 Project: Tuscany Issue Type: New Feature Components: Java SCA Tools Reporter: Thilina Buddhika Assignee: ant elder Attachments: geronimo_ACE.zip This is the primary implementation of this Admin Console Extension. It does not contain any functionality related to Tuscany. But it is intended to use this as the basis for developing the ACE. The patch contains the source, and provides a maven build file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2391) Tuscany SCA support in the Geronimo Admin Console
[ https://issues.apache.org/jira/browse/TUSCANY-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12605074#action_12605074 ] ant elder commented on TUSCANY-2391: Patch applied to your sandbos area at: https://svn.apache.org/repos/asf/incubator/tuscany/sandbox/thilina/geronimo_ACE/ It tried building and deploying to Geronimo 2.1.1 and it appears in the admin console and runs. Cool! Tuscany SCA support in the Geronimo Admin Console - Key: TUSCANY-2391 URL: https://issues.apache.org/jira/browse/TUSCANY-2391 Project: Tuscany Issue Type: New Feature Components: Java SCA Tools Reporter: Thilina Buddhika Assignee: ant elder Attachments: geronimo_ACE.zip This is the primary implementation of this Admin Console Extension. It does not contain any functionality related to Tuscany. But it is intended to use this as the basis for developing the ACE. The patch contains the source, and provides a maven build file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Updating the Geronimo Tuscany plugin to work with Geronimo 2.1
I've tried the Tuscany-Geronimo integration code [1] with Geronimo 2.1.1 releases and it doesn't work anymore. Could anyone help or say what is required to get it working again? This would be useful for a GSoC student whos writing a Gernimo console extension to manage SCA apps - http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Tuscany+SCA+support+in+the+Apache+Geronimo+Admin+Console TIA, ...ant [1] https://svn.apache.org/repos/asf/geronimo/plugins/tuscany/
Re: Updating the Geronimo Tuscany plugin to work with Geronimo 2.1
Could you give us some idea what problems you are having? Most likely you'll need a 2.1 to 2.1.1 adapter plugin (not yet written or in svn AFAIK) and possibly some other modifications. thanks david jencks On Jun 14, 2008, at 6:33 AM, ant elder wrote: I've tried the Tuscany-Geronimo integration code [1] with Geronimo 2.1.1 releases and it doesn't work anymore. Could anyone help or say what is required to get it working again? This would be useful for a GSoC student whos writing a Gernimo console extension to manage SCA apps - http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Tuscany+SCA+support+in+the+Apache+Geronimo+Admin+Console TIA, ...ant [1] https://svn.apache.org/repos/asf/geronimo/plugins/tuscany/
Re: Updating the Geronimo Tuscany plugin to work with Geronimo 2.1
Following the instructions at: https://svn.apache.org/repos/asf/geronimo/plugins/tuscany/trunk/README.TXTwhen i do step (3) it says: Installation FAILED: A plugin configuration must include one plugin artifact, not 0 Looking in the geronimo-plugin.xml at https://svn.apache.org/repos/asf/geronimo/plugins/tuscany/trunk/tuscany-tomcat/src/main/resources/META-INF/geronimo-plugin.xmlit only mentions Geronimo version 2.0.1, 2.0.2 and 2.0.3-SNAPSHOT so i guessed that means its not ready for 2.1.1 right? If thats the case is there any doc anywhere on what might be needed to update it? ...ant On Sat, Jun 14, 2008 at 5:38 PM, David Jencks [EMAIL PROTECTED] wrote: Could you give us some idea what problems you are having? Most likely you'll need a 2.1 to 2.1.1 adapter plugin (not yet written or in svn AFAIK) and possibly some other modifications. thanks david jencks On Jun 14, 2008, at 6:33 AM, ant elder wrote: I've tried the Tuscany-Geronimo integration code [1] with Geronimo 2.1.1 releases and it doesn't work anymore. Could anyone help or say what is required to get it working again? This would be useful for a GSoC student whos writing a Gernimo console extension to manage SCA apps - http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Tuscany+SCA+support+in+the+Apache+Geronimo+Admin+Console TIA, ...ant [1] https://svn.apache.org/repos/asf/geronimo/plugins/tuscany/
Re: SCA Getting started tutorial is missing on the website!
Thank you. On 6/13/08, Charuka Jayarathna [EMAIL PROTECTED] wrote: Here is the link, http://incubator.apache.org/tuscany/getting-started-with-tuscany.html I found it at Apache Tuscany Home SCA Overview SCA Java Also you can find here, Apache Tuscany Home SCA Overview SCA Java Java SCA Documentation Menu cheers charuka On Fri, Jun 13, 2008 at 1:20 PM, haleh mahbod [EMAIL PROTECTED] wrote: Hi, I cannot find the getting started tutorial on the website any longer. We used to have a link to this on the main page and on the SCA download page. Was this moved intentionally? If yes, to where? If not, I recover it. Haleh
