Release Issues with Eclipse Projects

2008-07-12 Thread ChrisGWarp
Hi all. From what I can gather, the release plugin has been fixed to work with the flattened eclipse based project structure. I have 4 directories, all at the same level so that they work with eclipse. \FireDragon (the J2EE Multi Module Project) \FireDragonResources (the resour

Re: Ampersand problem

2008-07-12 Thread Geoffrey Wiseman
2008/7/11 Lee Meador <[EMAIL PROTECTED]>: > If its in the xml, you might be able to use CDATA to get the ampersand in > there. The XML parser probably is looking for an < sort of thingy. > That occurred to me as well. You could use & if that's true. Artur, can you give us the actual error? -

Starting a plugin

2008-07-12 Thread Andreas Gies
Hi, I have the task to start a new plugin, that kind iterates over it's dependencies, generate some code, produce some custom reports and finally assemble something like an ear file for deployment. Actually, I think the functionality will go in a group of plugins, but that's not the aim for m

Re: Continuous integration build fails if tests fails

2008-07-12 Thread Andreas Gies
Hello, you could achieve something like this in Hudson as well, if you create a "Free Style" Hudson job that scans the build output und only triggers a mvn deploy when the log file contains "BUILD SUCCESS". The initial job should not execute "mvn deploy", but rather a "mvn package". You can

question about dependency issue in maven

2008-07-12 Thread wohlgemuth
hello, I just got a short question about maven and depedencies. Basically I got a project with several sub projects which got more subprojects and so on. The exact structure can be seen here: http://binbase.fiehnlab.ucdavis.edu:8060/browse/BinBase/trunk/binbase including all the needed poms. N

Re: EJB Jar packaging

2008-07-12 Thread ChrisGWarp
Stephen Coy-3 wrote: > > The usual way of doing this is to package the EJB jar together with > its dependencies in an EAR file. In a JEE5 environment the deps can > either go in a "lib" directory in the EAR or (and for J2EE 1.3/4) be > at the root of the EAR and a manifest classpath entry