db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jdo-dev-h...@db.apache.org
Subject warning from jdo-dev@db.apache.org
Date Thu, 03 Sep 2009 09:08:48 GMT
Hi! This is the ezmlm program. I'm managing the
jdo-dev@db.apache.org mailing list.

I'm working for my owner, who can be reached
at jdo-dev-owner@db.apache.org.


Messages to you from the jdo-dev mailing list seem to
have been bouncing. I've attached a copy of the first bounce
message I received.

If this message bounces too, I will send you a probe. If the probe bounces,
I will remove your address from the jdo-dev mailing list,
without further notice.


I've kept a list of which messages from the jdo-dev mailing list have 
bounced from your address.

Copies of these messages may be in the archive.
To retrieve a set of messages 123-145 (a maximum of 100 per request),
send a short message to:
   <jdo-dev-get.123_145@db.apache.org>

To receive a subject and author list for the last 100 or so messages,
send a short message to:
   <jdo-dev-index@db.apache.org>

Here are the message numbers:

   8268
   8269
   8267
   8270
   8271

--- Enclosed is a copy of the bounce message I received.

Return-Path: <>
Received: (qmail 58997 invoked by uid 99); 22 Aug 2009 03:54:05 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Aug 2009 03:54:05 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=10.0
	tests=ALL_TRUSTED,MISSING_MID
X-Spam-Check-By: apache.org
Received: from [140.211.11.9] (HELO minotaur.apache.org) (140.211.11.9)
    by apache.org (qpsmtpd/0.29) with SMTP; Sat, 22 Aug 2009 03:54:02 +0000
Received: (qmail 37046 invoked for bounce); 22 Aug 2009 03:53:18 -0000
Date: 22 Aug 2009 03:53:18 -0000
From: MAILER-DAEMON@minotaur.apache.org
To: jdo-dev-return-8268-apmail-db-jdo-dev-archive=www.apache.org@db.apache.org
Subject: failure notice
X-Virus-Checked: Checked by ClamAV on apache.org
Message-Id: <20090822035404.1228481601B@nike.apache.org>

Hi. This is the qmail-send program at minotaur.apache.org.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<apmail-db-jdo-dev-archive@www.apache.org>:
Sorry, no mailbox here by that name. (#5.1.1)

--- Below this line is a copy of the message.

Return-Path: <jdo-dev-return-8268-apmail-db-jdo-dev-archive=www.apache.org@db.apache.org>
Received: (qmail 37030 invoked from network); 22 Aug 2009 03:53:18 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 22 Aug 2009 03:53:18 -0000
Received: (qmail 55086 invoked by uid 500); 21 Aug 2009 18:53:39 -0000
Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:jdo-dev-help@db.apache.org>
List-Unsubscribe: <mailto:jdo-dev-unsubscribe@db.apache.org>
List-Post: <mailto:jdo-dev@db.apache.org>
List-Id: <jdo-dev.db.apache.org>
Reply-To: jdo-dev@db.apache.org
Delivered-To: mailing list jdo-dev@db.apache.org
Received: (qmail 54883 invoked by uid 99); 21 Aug 2009 18:53:38 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Aug 2009 18:53:38 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Aug 2009 18:53:35 +0000
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id E5456234C1E9
	for <jdo-dev@db.apache.org>; Fri, 21 Aug 2009 11:53:14 -0700 (PDT)
Message-ID: <1111185575.1250880794938.JavaMail.jira@brutus>
Date: Fri, 21 Aug 2009 11:53:14 -0700 (PDT)
From: "Craig Russell (JIRA)" <jira@apache.org>
To: jdo-dev@db.apache.org
Subject: [jira] Updated: (JDO-621) Add javax.jdo.JDOEnhancerMain to call the
 enhancer via standard API
In-Reply-To: <1831060777.1228526504210.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


     [ https://issues.apache.org/jira/browse/JDO-621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Craig Russell updated JDO-621:
------------------------------

    Attachment: jdo-621.patch

Please try this patch. 

It fixes the EnhancerTest to create a thread for stdout and stderr streams so even Windows
should be able to complete the Enhancer process.



> Add javax.jdo.JDOEnhancerMain to call the enhancer via standard API
> -------------------------------------------------------------------
>
>                 Key: JDO-621
>                 URL: https://issues.apache.org/jira/browse/JDO-621
>             Project: JDO
>          Issue Type: New Feature
>          Components: api2
>    Affects Versions: JDO 2 maintenance release 2
>            Reporter: Craig Russell
>            Assignee: Craig Russell
>             Fix For: JDO 2 maintenance release 3
>
>         Attachments: jdo-621.patch
>
>
> The proposed new class will use the standard enhancer API to enhance classes. The command
line parameters would be similar to the original proposal of JDO-591, with changes as needed
to use the new class in the TCK.
> java -cp classpath {enhancer-class} [options] [jdo-files] [class-files] 
>     where options can be 
>         -persistenceUnit persistence-unit-name : Name of a "persistence-unit" to enhance
the classes for 
>         -d target-dir-name : Write the enhanced classes to the specified directory 
>         -checkonly : Just check the classes for enhancement status 
>         -v : verbose output 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message