[jira] Closed: (TUSCANY-3844) Complex Component level property attributed not being save back

[ https://issues.apache.org/jira/browse/TUSCANY-3844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-3844. -- Resolution: Not A Problem I heard from the user that this issue was not due to a Tuscany problem > C

[jira] Updated: (TUSCANY-3496) Develop a simple tool that can be used to generate composite diagrams from the xml files

[ https://issues.apache.org/jira/browse/TUSCANY-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder updated TUSCANY-3496: --- Labels: gsoc gsoc2010 gsoc2011 mentor (was: gsoc gsoc2010 mentor) > Develop a simple tool that can

[jira] Updated: (TUSCANY-3512) Develop a command line tool that is able to report active endpoint information and export WSDL for a configured contribution

[ https://issues.apache.org/jira/browse/TUSCANY-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder updated TUSCANY-3512: --- Labels: gsoc gsoc2010 gsoc2011 mentor (was: gsoc gsoc2010 mentor) > Develop a command line tool th

[jira] Updated: (TUSCANY-3518) <*!*> Add JMX management capabilities to Apache Tuscany

[ https://issues.apache.org/jira/browse/TUSCANY-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder updated TUSCANY-3518: --- Labels: gsoc gsoc2010 gsoc2011 mentor (was: gsoc gsoc2010 mentor) > <*!*> Add JMX management capab

[jira] Updated: (TUSCANY-3519) <*!*> Develop a manager webapp for Tuscany Tomcat embedded runtime

[ https://issues.apache.org/jira/browse/TUSCANY-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder updated TUSCANY-3519: --- Labels: gsoc gsoc2010 gsoc2011 mentor (was: gsoc gsoc2010 mentor) > <*!*> Develop a manager webapp

[jira] Updated: (TUSCANY-3513) Develop a tool that is able to report on the runtime configuration of a running Tuscany node

[ https://issues.apache.org/jira/browse/TUSCANY-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder updated TUSCANY-3513: --- Labels: gsoc gsoc2010 gsoc2011 mentor (was: gsoc gsoc2010 mentor) > Develop a tool that is able to

Re: GSoC project ideas

On Mon, Mar 14, 2011 at 1:53 PM, Florian Moga wrote: > Hi, > I've started raising some JIRAs with a couple of ideas for GSoC projects. > Feel free to check them out, edit the description and add more resources. I > might have not expressed myself 100% correctly in SCA terms. > From my experience l

Re: 2.0 Beta2 samples (was: [VOTE] Release Tuscany SCA 2.0 Beta2 RC2)

On Thu, Mar 3, 2011 at 4:04 PM, Simon Laws wrote: > On Thu, Mar 3, 2011 at 3:43 PM, ant elder wrote: >> On Thu, Mar 3, 2011 at 12:23 PM, Simon Nash wrote: >> >> I meant to add, if working offline using local artifacts is >> useful/important then i wonder if that should also be p

Re: GSoC project ideas

I've started a wiki page for this [1]. Apparently, I don't have enough JIRA privileges to make my filters public. Can someone with admin rights make a filter that selects the Tuscany issues labeled gsoc2011? We can then share that on the wiki and on the website homepage. [1] https://cwiki.apache.o

Re: 2.0 Beta2 samples (was: [VOTE] Release Tuscany SCA 2.0 Beta2 RC2)

>> >> Doesn't that just mean that we need to separate the binary samples >> distribution from the binary runtime distribution that users use to >> run them. >> > > We did talk about having a sample distribution earlier in the thread. > I guess whether or not we do ever release a separate sample > d

Re: 2.0 Beta2 samples (was: [VOTE] Release Tuscany SCA 2.0 Beta2 RC2)

On Tue, Mar 15, 2011 at 1:33 PM, Simon Laws wrote: >>> >>> Doesn't that just mean that we need to separate the binary samples >>> distribution from the binary runtime distribution that users use to >>> run them. >>> >> >> We did talk about having a sample distribution earlier in the thread. >> I g

Re: Building problem with the trunk

Hi all, Sorry to embarrass you, the fault was on my side. I used a wrong command when I manually install an artifact. After removing some files from the m2 repository I recovered from the error. The good news is that after do some manual installing some artifacts now I have a fully I built trunk.