Re: Help getting m2 poms for 3.0.2 release

Why did you repackage unit tests from tests.javax to javax?

I don't think that surefire is going to be able to load javax classes  
very easily.  I also think you might need to create a new jar before  
surefire runs which includes all of the mx4j code and its  
dependencies, and then force the forked surefire to  -Xbootclasspath/ 
p:target/mx4juber.jar, or perhaps setting java.endorsed.dirs may  
work?  I dunno, been a while since I had to hack on this stuff.

But, I think there are a few issues... at least that show up on my  
Mac OS X Java 5 jvm.  Don't think that javax.* is going to fly for  
test names.  I'd recommend putting them all into mx4j.javax.*  And  
then need to shove the mx4j code + its deps into the bootclasspath of  
surefire so that they are used instead of any versions which are  
included with the jvm.

I guess I recommend making an mx4juber.jar before the tests so that  
only one jar needs to be specified with Xbootclasspath/p: (via  
surefires argLine configuration) else the command-line gets really  
nasty.

But maybe you know of a better way to hack in the javax classes?

--jason


On Mar 16, 2007, at 2:48 AM, Simone Bordet wrote:

> Hi Jason,
>
>> I folks, I'm trying to get the mx4j 3.0.2 release artifacts published
>> to the central m2 repository.  The repo admins want dependencies in
>> the poms... was currious if you guys have any idea what they  
>> should be.
>>
>> There is an opened issue here for this:
>>
>>      http://jira.codehaus.org/browse/MAVENUPLOAD-1220
>>
>> Its got a set of bundle files, which is the artifact + pom.  If
>> anyone knows what the deps should be for these, or knows of any other
>> details that should make it into the poms can you please update the
>> issue?
>
> SVN head builds mx4j with Maven 2, so everything should be in there.
> Unfortunately I did not have time to fix the tests (classloader
> issues), but the artifacts build fine. Never tried any maven deploy
> though.
>
> I guess moving mx4j to a maven build would fix the issue 1220 and  
> help G.
>
> If you want to take a look and/or help, I guess we can exit with a
> 3.1.0 built on Maven that should be ok for the future.
> I'll try to find some time to complete the build port to Maven 2.
>
> I'd be interested in your thoughts.
>
> Simon
> -- 
> http://bordet.blogspot.com


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV