Re: [openejb-dev] openejb3 testing notes

2006-03-10 Thread Jacek Laskowski
2006/3/9, [EMAIL PROTECTED] [EMAIL PROTECTED]:

 Not sure if this mail thread helps you..
 http://www.mail-archive.com/users@maven.apache.org/msg36818.html

Yes! That was this! Used it in one project successfully. Thanks John.
I was about to become worried I wouldn't find it ;)

 John

Jacek

--
Jacek Laskowski
http://www.laskowski.org.pl


[openejb-dev] please vote for this bug! (Re: [openejb-dev] openejb3 testing notes)

2006-03-08 Thread David Blevins


On Mar 8, 2006, at 3:04 AM, Gianny Damour wrote:


 - Having any assembly run with the build as in 'mvn install' it
causes everything to build twice


I think that this is this very annoying bug http:// 
jira.codehaus.org/browse/MASSEMBLY-37.  Also, it seems that  
fileSets defined in assembly descriptors are resolved based on the  
directory from which Maven is executed.


Oh man, that bug has been open for two months!

Could everyone vote for this one to be fixed by clicking the link below:

  http://jira.codehaus.org/browse/MASSEMBLY-37?vote=vote

We'll never be able to automatically test an assembly during a build  
unless we can have the assembly run as part of the build.  We need  
this fixed.


-David



Re: [openejb-dev] openejb3 testing notes

2006-03-08 Thread David Blevins


On Mar 8, 2006, at 2:34 AM, Jacek Laskowski wrote:


2006/3/8, David Blevins [EMAIL PROTECTED]:


  - Would love to find a way to create an executable jar assembly,
but it doesn't seem possible.


What's wrong with it? Where can I find the assembly descriptor?


I mean the maven-assembly-plugin allows you to create uber-jars, but  
there doesn't seem to be a way to specify manifest values, such as  
Main-Class.



  - Can't use m2 to execute the tests until the assembly-plugin issue
is fixed and available, going to use m1


Do you mean geronimo-assembly-plugin? If so, I could start migrating
it straight away since I'm in a great need to see how M2 plugins are
built.


The maven-assembly-plugin.


  - The auto unpack of our logging config file doesn't work.
  - Need to port over the client code that tries harder to make valid
provider URLs


I'm not even going to look into these in a near future, so don't even
try to explain them ;)


Already got the first one finished, on to the second item.


Thanks for the brain dump of yours! Keem'em posting...



Will do.

-David