Re: Project groupIds
Ken-- Maven basically uses the groupId as a way to hierarchically name artifacts in a Maven repository. So, if something has a groupId of "tuscany", it would show up in a Maven2 repository as: /tuscany/ If the groupId is "org.apache.tuscany", it shows up as: /org/apache/tuscany/ Personally, I'm a fan of containing artifacts from a project under nested directories like this as it makes the grouping of related artifacts more obvious. Eddie On 7/21/06, Jeremy Boynes <[EMAIL PROTECTED]> wrote: On Jul 21, 2006, at 2:06 PM, Ken Tam wrote: > So right now sca doesn't define a groupId and is parented to > tuscany-project w/ groupId o.a.t.. That is so last night ... ;-) In r424080 I disinherited the project from its parent (like the other sdo and das poms) so that people could build sca without needed to build from the root first (or doing mvn -N at the root anyway) > would this mean sca would continue > to be parented to tuscany-project, but define a new groupId? What > difference would this make? (I don't really get how maven treats this > hierarchy to understand what the pros/cons are here) There is no significance to the heirarchy, it is just way of partitioning it up. This would mean that sdo, das and sca would all be peers under o.a.t rather than giving sca some perceived precedence in the root. We already have sub-hierarchies for containers, databinding, samples, ... -- Jeremy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Clickable SCA Composite Diagram
Raymond-- The Apache mail system is quite paranoid when it comes to accepting types of attachments. Typically, only text files pass through the filters. The best bet for attaching files for everyone is to put them on the wiki (which you did, thanks!) or to attach them to a JIRA issue. Hope that helps. Eddie On 7/10/06, Raymond Feng <[EMAIL PROTECTED]> wrote: Hi, It seems that even HTML and JPEG files cannot be attached. Here's the wiki page: http://wiki.apache.org/ws-data/attachments/Tuscany(2f)SCADiagram/attachments/sca.htm http://wiki.apache.org/ws-data/attachments/Tuscany(2f)SCADiagram/attachments/sca_composite.jpg Thanks, Raymond - Original Message - From: "haleh mahbod" <[EMAIL PROTECTED]> To: Sent: Monday, July 10, 2006 6:05 PM Subject: Re: Clickable SCA Composite Diagram > where is it? > > On 7/10/06, Raymond Feng <[EMAIL PROTECTED]> wrote: >> >> Hi, >> >> Here's a draft clickable diagram to illustrate the concepts for SCA >> composite. Multiple areas are defined with hyperlinks on the image. >> Please >> give a try to see if it's what we want on the web site. >> >> Thanks, >> Raymond >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Do we plan to move to JUnit 4.1?
Raymond-- What aspect of JDK 5 + Maven2 support are you concerned about? I've used this combination quite a bit with good success, but I suppose it depends on what you're using it for. Eddie On 7/5/06, Raymond Feng <[EMAIL PROTECTED]> wrote: Hmm, it seems that Surefire plugin 2.2 doesn't support JUnit 4.x yet. Here's the JIRA issue for the topic: http://jira.codehaus.org/browse/SUREFIRE-31 Thanks, Raymond - Original Message - From: "Jeremy Boynes" <[EMAIL PROTECTED]> To: Sent: Wednesday, July 05, 2006 6:10 PM Subject: Re: Do we plan to move to JUnit 4.1? > On Jul 5, 2006, at 5:05 PM, Raymond Feng wrote: > >> I'm wondering if we plan to move to JUnit 4.1? I see more flexibilities >> and simplicities offered by JUnit 4.x. Now I can also use the wizards >> from Eclipse 3.2 to take advantage of it. >> >> Do we see any issues? I understand Junit 4.x requires JDK 5. I'm not >> sure if maven 2.0.4 supports it. > > We had a look at junit 4 back in Sep but stayed with 3.8.1 due to the > lack of maven support. Can you find out if that has changed? If it has it > might be worth upgrading. > > -- > Jeremy > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Karma for Ant Elder
+1 On 3/1/06, Kevin Williams <[EMAIL PROTECTED]> wrote: > +1 > rick rineholt wrote: > > >+1 > > > >Jean-Sebastien Delfino wrote: > > > > > >>Jeremy Boynes wrote: > >> > >> > >> > >>>Ant has actively been contributing in several areas > >>> > >>> > >of the project and I > > > > > >>>for one am tired of applying patches :-) Ant is > >>> > >>> > >already a member of the > > > > > >>>Web Services project (and PMC), so I would like to > >>> > >>> > >suggest that he > > > > > >>>starts committing fixes directly. > >>> > >>>Naturally, here's my +1 > >>>-- > >>>Jeremy > >>> > >>> > >>> > >>> > >>+1 > >> > >> > >> > > > >__ > >Do You Yahoo!? > >Tired of spam? Yahoo! Mail has the best spam protection around > >http://mail.yahoo.com > > > > > > > > > > > > >
[jira] Commented: (TUSCANY-29) HelloWorldMC sample fails to build
[ http://issues.apache.org/jira/browse/TUSCANY-29?page=comments#action_12366985 ] Eddie O'Neil commented on TUSCANY-29: - The other option would be to remove the failing samples from the build and have tracking bugs (like this one) to re-enable their builds once the aggregate context work is done. Otherwise, the state of the tree is less obvious. Also, here's the top of the offending stack trace I'm seeing. java.lang.NullPointerException at org.apache.tuscany.core.invocation.jdk.JDKInvocationHandler.invoke(JDKInvocationHandler.java:81) at $Proxy41.getGreetingPortion(Unknown Source) at org.apache.tuscany.samples.helloworldmc.HelloWorldServiceComponentImpl.getGreetings(HelloWorldServiceComponentImpl.java:48) at org.apache.tuscany.samples.helloworldmc.HelloWorldServiceComponentTestCase.testGeetings(HelloWorldServiceComponentTestCase.java:49) > HelloWorldMC sample fails to build > -- > > Key: TUSCANY-29 > URL: http://issues.apache.org/jira/browse/TUSCANY-29 > Project: Tuscany > Type: Bug > Reporter: Jeremy Boynes > Priority: Blocker > > The test case fails with a NullPointerException -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Fwd: [jira] Created: (TUSCANY-29) HelloWorldMC sample fails to build
Heh...that was the next thing I ran into with a fresh sync as well. Thanks for filing the bug. :) Eddie -- Forwarded message -- From: Jeremy Boynes (JIRA) <[EMAIL PROTECTED]> Date: Feb 19, 2006 10:02 AM Subject: [jira] Created: (TUSCANY-29) HelloWorldMC sample fails to build To: tuscany-dev@ws.apache.org HelloWorldMC sample fails to build -- Key: TUSCANY-29 URL: http://issues.apache.org/jira/browse/TUSCANY-29 Project: Tuscany Type: Bug Reporter: Jeremy Boynes Priority: Blocker The test case fails with a NullPointerException -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: fresh sync -- build problem
Looks like Jeremy's SVN 378920 has covered this (and worked locally). Thanks for the quick fix! Eddie On 2/19/06, Eddie O'Neil <[EMAIL PROTECTED]> wrote: > All-- > > I've not done a sync in quite a while and am running into these > errors (with a fresh sync) from das/rdb: > > Compiling 83 source files to > C:\java\code\tuscany\java\das\rdb\target\test-classes > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] Compilation failure > > C:\java\code\tuscany\java\das\rdb\src\test\java\org\apache\tuscany\das\rdb\test\framework\SDOPrinter.java:[23,33] > packag > e org.eclipse.emf.ecore.sdo does not exist > > C:\java\code\tuscany\java\das\rdb\src\test\java\org\apache\tuscany\das\rdb\test\framework\SDOPrinter.java:[45,13] > cannot > find symbol > symbol : class EProperty > location: class org.apache.tuscany.das.rdb.test.framework.SDOPrinter > > C:\java\code\tuscany\java\das\rdb\src\test\java\org\apache\tuscany\das\rdb\test\framework\SDOPrinter.java:[53,35] > cannot > find symbol > symbol : class EProperty > location: class org.apache.tuscany.das.rdb.test.framework.SDOPrinter > > > The solution was to add a dependency to org.eclipse.ecore/ecore-sdo as: > > ::: > Index: das/rdb/pom.xml > === > --- das/rdb/pom.xml (revision 378913) > +++ das/rdb/pom.xml (working copy) > @@ -33,6 +33,13 @@ > compile > > > + > + > +org.eclipse.emf > +ecore-sdo > +2.1.1 > + > + > > org.apache.tuscany > tuscany-sdo-impl > ::: > > > Before I commit this change, I'd like to vet it with someone to make > sure that I'm not missing something. > > Thoughts? > > Cheers, > Eddie >
fresh sync -- build problem
All-- I've not done a sync in quite a while and am running into these errors (with a fresh sync) from das/rdb: Compiling 83 source files to C:\java\code\tuscany\java\das\rdb\target\test-classes [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure C:\java\code\tuscany\java\das\rdb\src\test\java\org\apache\tuscany\das\rdb\test\framework\SDOPrinter.java:[23,33] packag e org.eclipse.emf.ecore.sdo does not exist C:\java\code\tuscany\java\das\rdb\src\test\java\org\apache\tuscany\das\rdb\test\framework\SDOPrinter.java:[45,13] cannot find symbol symbol : class EProperty location: class org.apache.tuscany.das.rdb.test.framework.SDOPrinter C:\java\code\tuscany\java\das\rdb\src\test\java\org\apache\tuscany\das\rdb\test\framework\SDOPrinter.java:[53,35] cannot find symbol symbol : class EProperty location: class org.apache.tuscany.das.rdb.test.framework.SDOPrinter The solution was to add a dependency to org.eclipse.ecore/ecore-sdo as: ::: Index: das/rdb/pom.xml === --- das/rdb/pom.xml (revision 378913) +++ das/rdb/pom.xml (working copy) @@ -33,6 +33,13 @@ compile + + +org.eclipse.emf +ecore-sdo +2.1.1 + + org.apache.tuscany tuscany-sdo-impl ::: Before I commit this change, I'd like to vet it with someone to make sure that I'm not missing something. Thoughts? Cheers, Eddie
Re: subscribe
Rick-- Try subscribing via the address: [EMAIL PROTECTED] Eddie On 2/7/06, rick rineholt <[EMAIL PROTECTED]> wrote: > > > > __ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com >
Re: svn commit: r366393 - /incubator/tuscany/sandbox/sebastien/
Jack-- I don't think it's so much an Apache "convention" as it is just a way to sandbox some prototyping, experimentation, group think, or revolutionary changes. A sandbox might be populated with a branch of code -- it just uses the "sandbox" moniker to denote that it's not a real, supported branch. And, the username just scopes it to a particular owner of the stuff beneath the directory. My take is that it's a little early for a sandbox :) given that the build doesn't quite work yet (at least locally for me -- haven't dug in on that yet), but ultimately, they're useful things for collaborative and distributed projects. My $0.02... Eddie On 1/6/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Sebastien wrote: > > > I don't think that this will confuse people if we make clear that > everything > > understands that the tree under the sandbox directory is for prototypes, > > experiments, and under-construction stuff. I just took a look at other > > Apache projects, axis2, synapse and beehive, and they seem use a sandbox > (or > > scratch) directory in a similar way, but that doesn't necessarily mean > that > > it's the "right" thing to do... > > To the group at large, what's wrong with using branches with good names? > Just > curious how this particular Apache convention of sandboxes got started > (and I > realize that you are looking for pointers to that info as well). > > -- > Jack Unrue > [EMAIL PROTECTED] > >
useful links
All-- Have heard a bunch of questions about SCA at ApacheCon; figured some links would be useful for bootstrapping anyone who's interested. Cheers, Eddie === Original Incubator Proposal: http://wiki.apache.org/incubator/TuscanyProposal Assembly specification: http://download.boulder.ibm.com/ibmdl/pub/software/dw/specs/ws-sca/SCA_AssemblyModel_V09.pdf Java Client / Implementation specification: http://download.boulder.ibm.com/ibmdl/pub/software/dw/specs/ws-sca/SCA_ClientAndImplementationModelforJava_V09.pdf More specification links (SDO, C++ client / implementation, etc): http://www-128.ibm.com/developerworks/library/specification/ws-sca/