eccn
hi, Please inform about the Export Control Code (ECCN) for your product: ant easymockclassextension easymock thanks in advance, Edgar Rego SIEMENS, S.A. IC RD1 NMP TS Rua Irmãos Siemens, 1 2720-093 Amadora PORTUGAL Phone +351 21420 4558 Fax +351 21416 7388 E-mail: edgar mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]
Re: eccn
easymock is not an Apache project, so no idea there. Ant isn't a Jakarta project, see ant.apache.org, however I don't think it ships with anything to warrant needing an ECCN. If you see something in there that you think is relevant, then contacting Ant would be a good way to go. Hen On Fri, 7 Apr 2006, Rego, Edgar (ext) wrote: hi, Please inform about the Export Control Code (ECCN) for your product: ant easymockclassextension easymock thanks in advance, Edgar Rego SIEMENS, S.A. IC RD1 NMP TS Rua Irm?os Siemens, 1 2720-093 Amadora PORTUGAL Phone +351 21420 4558 Fax +351 21416 7388 E-mail: edgar mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] Jakarta Sandbox
Calling a vote to create a Jakarta Sandbox; which entails: * Move Jakarta Commons Sandbox to Jakarta Sandbox * Migrate Jakarta Taglibs Sandbox into Jakarta Sandbox * Create development mailing list ([EMAIL PROTECTED]) * Create wiki (and migrate wiki bits from j-c-s/j-t-s) * Jakarta Sandbox to initially use the Commons sandbox processes. [ ] +1 [ ] -1 Vote to last no shorter than a week. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Jakarta Sandbox
On 4/7/06, Henri Yandell [EMAIL PROTECTED] wrote: Calling a vote to create a Jakarta Sandbox; which entails: * Move Jakarta Commons Sandbox to Jakarta Sandbox * Migrate Jakarta Taglibs Sandbox into Jakarta Sandbox * Create development mailing list ([EMAIL PROTECTED]) * Create wiki (and migrate wiki bits from j-c-s/j-t-s) * Jakarta Sandbox to initially use the Commons sandbox processes. What would be the constraints on what could go in there? Anything, as long as it's written in or for Java? [ ] +1 [X] -1 This just seems like too big of a can of worms to me. -- Martin Cooper Vote to last no shorter than a week. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Jakarta Sandbox
On Fri, 2006-04-07 at 16:28 -0700, Martin Cooper wrote: On 4/7/06, Henri Yandell [EMAIL PROTECTED] wrote: Calling a vote to create a Jakarta Sandbox; which entails: * Move Jakarta Commons Sandbox to Jakarta Sandbox * Migrate Jakarta Taglibs Sandbox into Jakarta Sandbox * Create development mailing list ([EMAIL PROTECTED]) * Create wiki (and migrate wiki bits from j-c-s/j-t-s) * Jakarta Sandbox to initially use the Commons sandbox processes. What would be the constraints on what could go in there? Anything, as long as it's written in or for Java? And who is expected to subscribe to [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Jakarta Sandbox
On Fri, 7 Apr 2006, Martin Cooper wrote: On 4/7/06, Henri Yandell [EMAIL PROTECTED] wrote: Calling a vote to create a Jakarta Sandbox; which entails: * Move Jakarta Commons Sandbox to Jakarta Sandbox * Migrate Jakarta Taglibs Sandbox into Jakarta Sandbox * Create development mailing list ([EMAIL PROTECTED]) * Create wiki (and migrate wiki bits from j-c-s/j-t-s) * Jakarta Sandbox to initially use the Commons sandbox processes. What would be the constraints on what could go in there? Anything, as long as it's written in or for Java? My fault, I thought we'd had a long thread on this before so didn't do much explaining. The same as Commons Sandbox contains potential Commons components, Jakarta Sandbox would be much the same but contain potential Jakarta components. Maybe I'm jumping the gun. One of the reasons this was brought up again in last months naval introspection threads was that if we have a Jakarta Language Components grouping (ie: part of Commons moves out), then the Commons sandbox would no longer be applicable. Plus it allows us to bring the Taglibs sandbox plus it gives us a nice home for the Taglibs sandbox to be dormantized to. [ ] +1 [X] -1 This just seems like too big of a can of worms to me. It's the same can of worms as Jakarta as a whole, so I'm not sure if we can view this as being worrisome and the general scope of Jakarta as not worrisome. I'm probably jumping the gun - next vote maybe should have been to have restricted the scope of Jakarta rather than promote the sandbox up. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Jakarta Sandbox
On Sat, 8 Apr 2006, Simon Kitching wrote: On Fri, 2006-04-07 at 16:28 -0700, Martin Cooper wrote: On 4/7/06, Henri Yandell [EMAIL PROTECTED] wrote: Calling a vote to create a Jakarta Sandbox; which entails: * Move Jakarta Commons Sandbox to Jakarta Sandbox * Migrate Jakarta Taglibs Sandbox into Jakarta Sandbox * Create development mailing list ([EMAIL PROTECTED]) * Create wiki (and migrate wiki bits from j-c-s/j-t-s) * Jakarta Sandbox to initially use the Commons sandbox processes. What would be the constraints on what could go in there? Anything, as long as it's written in or for Java? And who is expected to subscribe to [EMAIL PROTECTED] Those who want to? :) I imagine those working on sandbox components at the moment, plus a handful of people who tend to subscribe to such lists. Out of interest - if we take a list with N mails a day, and have 2 lists with N/2 mails a day, is that something you'd view as more painful or the same amount of pain? I know that when subscribing to Jakarta subprojects I'm not interested in as a coder, I subscribe to both the -user and -dev and funnel them both into the same folder. For my level of interest it's just [EMAIL PROTECTED], not ecs-xxx@ etc. So I'm probably answering more pain to the above, but I've got a simple solution that hides the minor pain increase. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
