Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Received:Mime-Version:In-Reply-To:References:Content-Type:Message-Id:Content-Transfer-Encoding:From:Subject:Date:To:X-Mailer;
  b=LEc6cquER0JJ+NOuYANo2AVkiuZaD2VnmM05SAX3AQ9aTdcJQY91IK9YXFCLyzYIgyK1glo/7MumXrVDMXK1XRXubzlqgqEypYzAagQ4Hr6+pepQpRuA6Bv2azYi99RNZYC28Mz0EEr4Sak5eHHdwXYbywuuWZqDTSnhyx4PwBQ=
  ;
Mime-Version: 1.0 (Apple Message framework v749.3)
In-Reply-To: <1B1842CD-CF73-4B16-9ABE-75F5EEECA953@apache.org>
References: <1B1842CD-CF73-4B16-9ABE-75F5EEECA953@apache.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <9397CDED-70B7-4176-9B32-0A0315AD682C@yahoo.com>
Content-Transfer-Encoding: 7bit
From: David Jencks <david_jencks@yahoo.com>
Subject: Re: j2ee-builder tests?
Date: Thu, 24 Aug 2006 14:29:14 -0400
To: dev@geronimo.apache.org

On a related note I've been creating a bunch of little m2 projects to  
build apps to verify defects and their fixes.  Usually you have to  
look at the output to see if it passed.  I've been attaching these  
projects to the issues in question.  I think we should consider  
putting these in svn somewhere and if we can get the itest plugin to  
run them that would be even better.

Not exactly the same situation as you have here but it seems somewhat  
related.  Anyway you might consider making an m2 project to build  
this sample app.

thanks
david jencks

On Aug 23, 2006, at 6:59 PM, Bill Dudney wrote:

> Hi All,
>
> The tests in the j2ee-builder do not currently have valid  
> deployment descriptors. While that's ok for this module because of  
> the mocked out deployment bits I was hoping to use them in other  
> tests. I have most of the stuff fixed up but there are a few things  
> that I don't want to do without feedback.
>
> 1) there rar is empty, no jar's no xml in the deployment  
> descriptors its just a place holder. Thoughts on what to do with  
> that? cook up a simple rar? delete it? I lean towards making a  
> simple rar.
>
> 2) The web.xml references a bogus bunch of ejb's with refs like  
> 'fake-ejb-ref'. Couple of things we could do with this, make them  
> point to valid ejb references in the ejb jar files that are part of  
> this ear or delete them. I would/could add some extra EJB's to the  
> ejb jar to make sure we covered all the reference types.
>
> 3) This is less important but I'd like to change the artifactId's  
> so they are unique (i.e. test-ear-j2ee-1.{3,4}) so that I can  
> deploy both of the ear files when its all said and done.
>
> 4) I'm not sure exactly how to do this with ear/war/ejb-jar but I'd  
> like to have this module produce a 'tests' jar (we do this in  
> cayenne with simple junit tests so we can reuse it across modules)  
> and then reuse these deployment units in other automated tests. I'm  
> game to poke at it but figure I might get a few of Jason's brain  
> cells so I can be a bit lazier :-)
>
> I posted this jira;
>
> https://issues.apache.org/jira/browse/GERONIMO-2352
>
> to track this issue.
>
> Thanks!
>
> -bd-