Extracting classpath for an application from maven

2009-03-07 Thread Roman Kournjaev
Hi All

I have a maven based application, well now i want to run it in cmd mode, it
means just executing the compiled class.
 How do i extract the classpath for this application from my pom easilly ?

Thanks in advance.
Roman


Re: Extracting classpath for an application from maven

2009-03-07 Thread Wim Deblauwe
This might be handy for this:
http://mojo.codehaus.org/appassembler/appassembler-maven-plugin/

2009/3/7 Roman Kournjaev kournj...@gmail.com

 Hi All

 I have a maven based application, well now i want to run it in cmd mode, it
 means just executing the compiled class.
  How do i extract the classpath for this application from my pom easilly ?

 Thanks in advance.
 Roman



Re: Extracting classpath for an application from maven

2009-03-07 Thread Roman Kournjaev
Thanks , that's a nice plugin.

But i see it places the jars into some assembled repository, but it would be
really nice to get the classpath to the jars that are in my local maven
repository.

Thanks in advance


On Sat, Mar 7, 2009 at 1:23 PM, Wim Deblauwe wim.debla...@gmail.com wrote:

 This might be handy for this:
 http://mojo.codehaus.org/appassembler/appassembler-maven-plugin/

 2009/3/7 Roman Kournjaev kournj...@gmail.com

  Hi All
 
  I have a maven based application, well now i want to run it in cmd mode,
 it
  means just executing the compiled class.
   How do i extract the classpath for this application from my pom easilly
 ?
 
  Thanks in advance.
  Roman
 



Re: Regarding junit test

2009-03-07 Thread Juven Xu
this should a properties file, which is available in your test classpath.

your can retrieve it in your testcase, like:

File testFile = new File(target/test-classes/test.properties);

Note that all files under src/test/resources will be moved to
target/test-classes/ when you run mvn test

On Sat, Mar 7, 2009 at 7:22 AM, nani2ratna nani2ra...@gmail.com wrote:


 Hi,

 Thanks for your reply.
 Now i understood that these tests run every time when ever we run the mvn
 test.
 There is a file called test.properties in the folder src/test/resources.
 Can you tell me how can we use that.

 Thanks and Regards
 Ratna


 VanIngen, Erik (ESTG) wrote:
 
  Maven follows the convention over configuration principal.
 
  This means that by convention, all your tests within {your
  project}/src/test/java will be run automatically.
 
  Another convention is that Maven follows always this lifecycle:
 
 http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.htm
  l
 
  Running the tests is part of the Maven lifecycle.
 
  Surefire is the xml representation of the report of the build you run by
  Maven. You can find this xml in the {your
  project}//target/surefire-reports
  This xml can be used to make nice reports of the build.
 
 
 
  -Original Message-
  From: nani2ratna [mailto:nani2ra...@gmail.com]
  Sent: Friday, March 06, 2009 8:36 AM
  To: users@maven.apache.org
  Subject: Regarding junit test
 
 
  Hi,
 
  How does maven calls junit test cases when we run command mvn test.
  and what is the surefire, how it runs, can any body send me the link of
  this
  documentation
 
  Thanks and regards
  ratna
  --
  View this message in context:
  http://www.nabble.com/Regarding-junit-test-tp22367494p22367494.html
  Sent from the Maven - Users mailing list archive at Nabble.com.
 
 
  -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org
 
 
 
  -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org
 
 
 

 --
 View this message in context:
 http://www.nabble.com/Regarding-junit-test-tp22367494p22382323.html
 Sent from the Maven - Users mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org




-- 
- juven


Re: How to assign a name for new archetype instead of unnamed

2009-03-07 Thread Raphaël Piéroni
Hi Sagara

the text inserted in the catalog is:
- the description or
- the name or
- Unamed - groupId:artifactId:packaging:
version.

The update catalog mojo uses the description of the project and if
empty uses the name.
the name attribute of the project is given Unamed... when no name is defined.

Regards,

Raphaël

2009/3/7 Sagara Gunathunga sagar...@gmail.com

 Hi,
 Anyone have any ideas on how to do this .?

 On 3/6/09, Sagara Gunathunga sagar...@gmail.com wrote:
  Hi all ,
   I have created a my own archetype , then add the archetype  to my
   local catalog using  mvn archetype:update-local-catalog command , it
   worked fine , when i call mvn archetype:generate
   -DarchetypeRepository=local it will show a  list of archetype  and my
   archetype  also there ,but my archetype is   listed as unnamed (
   please refer following list) . How can i set a name for my archetype
   so that it will display that name instead of   unnamed ..?
 
 
   
   Choose archetype:
   1: local - myquickstart (Unnamed - org.my:myquickstart:jar:1.0.0)
   2: internal - appfuse-basic-jsf (AppFuse archetype for creating a web
   application with Hibernate, Spring and JSF)
   3: internal - appfuse-basic-spring (AppFuse archetype for creating a
   web application with Hibernate, Spring and Spring
   MVC)
 
 
 
   Thanks ,
 
 
   --
   Sagara Gunathunga
 
   Blog - ssagara.blogspot.com
   Web - http://sagaras.awardspace.com/
 


 --
 Sagara Gunathunga

 Blog - ssagara.blogspot.com
 Web - http://sagaras.awardspace.com/

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Version range excluding SNAPSHOTs

2009-03-07 Thread Markus KARG
My project is dependent of some library. I want to always use the latest
bugfix but not any new features. So I added version[1.0,1.1)/version
which allows me to use all bugfixes of the 1.0 release. But when I check the
actually used version, I see that 1.1-SNAPSHOT is getting used! How can I
prevent this? Is there a way to say anything between 1.0 smaller than 1.1,
but NOT SNAPSHOTS?

 

 



Re: JAX-RPC client generation in Maven2 project

2009-03-07 Thread Ryan de Laplante

Ryan de Laplante wrote:

Wayne Fay wrote:

On Fri, Mar 6, 2009 at 11:19 AM, Ryan de Laplante r...@ijws.com wrote:
 
For anyone following this thread now or in the future, here is the 
solution

I used:



Ryan, you're a model citizen... I assume this will go on your blog
too, right? ;-)

Wayne
  

Thank you!  That is a good idea, I will blog about it too.

Ryan


http://www.ryandelaplante.com/rdelaplante/entry/jax_rpc_client_with_maven2



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: Regarding junit test

2009-03-07 Thread Stephen Connolly
2009/3/7 Juven Xu ju...@sonatype.com

 this should a properties file, which is available in your test classpath.

 your can retrieve it in your testcase, like:

 File testFile = new File(target/test-classes/test.properties);


n

access it as a resource from the classpath





 Note that all files under src/test/resources will be moved to
 target/test-classes/ when you run mvn test
 - Show quoted text -

 On Sat, Mar 7, 2009 at 7:22 AM, nani2ratna nani2ra...@gmail.com wrote:

 
  Hi,
 
  Thanks for your reply.
  Now i understood that these tests run every time when ever we run the mvn
  test.
  There is a file called test.properties in the folder src/test/resources.
  Can you tell me how can we use that.
 
  Thanks and Regards
  Ratna
 
 
  VanIngen, Erik (ESTG) wrote:
  
   Maven follows the convention over configuration principal.
  
   This means that by convention, all your tests within {your
   project}/src/test/java will be run automatically.
  
   Another convention is that Maven follows always this lifecycle:
  
 
 http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.htm
   l
  
   Running the tests is part of the Maven lifecycle.
  
   Surefire is the xml representation of the report of the build you run
 by
   Maven. You can find this xml in the {your
   project}//target/surefire-reports
   This xml can be used to make nice reports of the build.
  
  
  
   -Original Message-
   From: nani2ratna [mailto:nani2ra...@gmail.com]
   Sent: Friday, March 06, 2009 8:36 AM
   To: users@maven.apache.org
   Subject: Regarding junit test
  
  
   Hi,
  
   How does maven calls junit test cases when we run command mvn test.
   and what is the surefire, how it runs, can any body send me the link of
   this
   documentation
  
   Thanks and regards
   ratna
   --
   View this message in context:
   http://www.nabble.com/Regarding-junit-test-tp22367494p22367494.html
   Sent from the Maven - Users mailing list archive at Nabble.com.
  
  
   -
   To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
   For additional commands, e-mail: users-h...@maven.apache.org
  
  
  
   -
   To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
   For additional commands, e-mail: users-h...@maven.apache.org
  
  
  
 
  --
  View this message in context:
  http://www.nabble.com/Regarding-junit-test-tp22367494p22382323.html
  Sent from the Maven - Users mailing list archive at Nabble.com.
 
 
  -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org
 
 


 --
 - juven



Re: Extracting classpath for an application from maven

2009-03-07 Thread Trevor Harmon

On Mar 7, 2009, at 3:11 AM, Roman Kournjaev wrote:

I have a maven based application, well now i want to run it in cmd  
mode, it

means just executing the compiled class.


I use exec:java for this.

Trevor


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: Version range excluding SNAPSHOTs

2009-03-07 Thread Stephen Connolly
[1.0,1.1-!)

1.0-SNAPSHOT  1.0  1.1-SNAPSHOT  1.1

But in ASCII ! is  A

therefore

1.1-!  1.1-SNAPSHOT  1.1

1.1-! is also  1.1-alpha-1

2009/3/7 Markus KARG markus.k...@gmx.net

 My project is dependent of some library. I want to always use the latest
 bugfix but not any new features. So I added version[1.0,1.1)/version
 which allows me to use all bugfixes of the 1.0 release. But when I check
 the
 actually used version, I see that 1.1-SNAPSHOT is getting used! How can I
 prevent this? Is there a way to say anything between 1.0 smaller than 1.1,
 but NOT SNAPSHOTS?








Re: How to assign a name for new archetype instead of unnamed

2009-03-07 Thread Wayne Fay
On Fri, Mar 6, 2009 at 2:03 PM, Seb Martel smar...@real.com wrote:
 YOiioOOoouyh
 Sent via BlackBerry by ATT

I think someone has their BlackBerry in the back pocket, and their
butt is emailing us...

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



war:war not including src/main/java

2009-03-07 Thread Mansour
I am facing this problem where maven is not including the sources in 
src/main/java.

With jetty:run on the develpoment everthing is fine.
But, when I create the war, the directory is not included.

?xml version=1.0?
project xmlns=http://maven.apache.org/POM/4.0.0; 
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; 
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd;

 modelVersion4.0.0/modelVersion
 groupIdcom.mysite/groupId
 artifactIdwebsite/artifactId
 packagingwar/packaging
 version1.0-SNAPSHOT/version
 namewebsite Maven Webapp/name
 urlhttp://maven.apache.org/url
 build
   finalNamewebsite/finalName
   plugins
 plugin
   groupIdorg.mortbay.jetty/groupId
   artifactIdmaven-jetty-plugin/artifactId
   configuration
 contextPath//contextPath
 scanIntervalSeconds1/scanIntervalSeconds
   /configuration
 /plugin
 plugin
   groupIdorg.apache.maven.plugins/groupId
   artifactIdmaven-war-plugin/artifactId
   version2.0/version
 /plugin
 plugin
   groupIdorg.apache.maven.plugins/groupId
   artifactIdmaven-compiler-plugin/artifactId
   configuration
 source1.5/source
 target1.5/target
   /configuration
 /plugin
   /plugins
 /build
 dependencies
   dependency
 groupIdopensymphony/groupId
 artifactIdsitemesh/artifactId
 version2.3/version
   /dependency
   dependency
 groupIdjavax.servlet/groupId
 artifactIdservlet-api/artifactId
 version2.3/version
 scopeprovided/scope
   /dependency
   dependency
 groupIdjavax.mail/groupId
 artifactIdmail/artifactId
 version1.4.2/version
   /dependency
   dependency
 groupIdjunit/groupId
 artifactIdjunit/artifactId
 version4.5/version
 scopetest/scope
   /dependency
 /dependencies
/project


I don't know what 's going on. Any advice ?


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: war:war not including src/main/java

2009-03-07 Thread Mick Knutson
did you try *mvn clean install jetty:run -e*

---
Thank You…

Mick Knutson, President

BASE Logic, Inc.
Enterprise Architecture, Design, Mentoring  Agile Consulting
p. (866) BLiNC-411: (254-6241-1)
f. (415) 685-4233

Website: http://baselogic.com
Linked IN: http://linkedin.com/in/mickknutson
Twitter: http://twitter.com/mickknutson
Vacation Rental: http://tahoe.baselogic.com
---



On Sat, Mar 7, 2009 at 1:11 PM, Mansour mansou...@yahoo.com wrote:

 I am facing this problem where maven is not including the sources in
 src/main/java.
 With jetty:run on the develpoment everthing is fine.
 But, when I create the war, the directory is not included.

 ?xml version=1.0?
 project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=
 http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=
 http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd
 
  modelVersion4.0.0/modelVersion
  groupIdcom.mysite/groupId
  artifactIdwebsite/artifactId
  packagingwar/packaging
  version1.0-SNAPSHOT/version
  namewebsite Maven Webapp/name
  urlhttp://maven.apache.org/url
  build
   finalNamewebsite/finalName
   plugins
 plugin
   groupIdorg.mortbay.jetty/groupId
   artifactIdmaven-jetty-plugin/artifactId
   configuration
 contextPath//contextPath
 scanIntervalSeconds1/scanIntervalSeconds
   /configuration
 /plugin
 plugin
   groupIdorg.apache.maven.plugins/groupId
   artifactIdmaven-war-plugin/artifactId
   version2.0/version
 /plugin
 plugin
   groupIdorg.apache.maven.plugins/groupId
   artifactIdmaven-compiler-plugin/artifactId
   configuration
 source1.5/source
 target1.5/target
   /configuration
 /plugin
   /plugins
  /build
  dependencies
   dependency
 groupIdopensymphony/groupId
 artifactIdsitemesh/artifactId
 version2.3/version
   /dependency
   dependency
 groupIdjavax.servlet/groupId
 artifactIdservlet-api/artifactId
 version2.3/version
 scopeprovided/scope
   /dependency
   dependency
 groupIdjavax.mail/groupId
 artifactIdmail/artifactId
 version1.4.2/version
   /dependency
   dependency
 groupIdjunit/groupId
 artifactIdjunit/artifactId
 version4.5/version
 scopetest/scope
   /dependency
  /dependencies
 /project


 I don't know what 's going on. Any advice ?


 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org




RE: war:war not including src/main/java

2009-03-07 Thread Martin Gainty

your projects pom.xml will have a directory specifying the sourcedir
properties

jsp.precompilation.java${pom.basedir}/../src/main/java/jsp.precomilcation.java
   ..
/properties

then in maven.xml your javac task will use the predefined 
jsp.precompilation.java property..
ant:javac srcdir=${jsp.precompilation.java}
classpathref=jsp.precompilation.classpath
destdir=${jsp.precompilation.webapp}/WEB-INF/classes
deprecation=on/

HTH
Martin 
__ 
Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relates to the official business 
of Sender. This transmission is of a confidential nature and Sender does not 
endorse distribution to any party other than intended recipient. Sender does 
not necessarily endorse content contained within this transmission. 




 Date: Sat, 7 Mar 2009 17:11:23 -0400
 From: mansou...@yahoo.com
 To: users@maven.apache.org
 Subject: war:war not including src/main/java
 
 I am facing this problem where maven is not including the sources in 
 src/main/java.
 With jetty:run on the develpoment everthing is fine.
 But, when I create the war, the directory is not included.
 
 ?xml version=1.0?
 project xmlns=http://maven.apache.org/POM/4.0.0; 
 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; 
 xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 
 http://maven.apache.org/maven-v4_0_0.xsd;
   modelVersion4.0.0/modelVersion
   groupIdcom.mysite/groupId
   artifactIdwebsite/artifactId
   packagingwar/packaging
   version1.0-SNAPSHOT/version
   namewebsite Maven Webapp/name
   urlhttp://maven.apache.org/url
   build
 finalNamewebsite/finalName
 plugins
   plugin
 groupIdorg.mortbay.jetty/groupId
 artifactIdmaven-jetty-plugin/artifactId
 configuration
   contextPath//contextPath
   scanIntervalSeconds1/scanIntervalSeconds
 /configuration
   /plugin
   plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-war-plugin/artifactId
 version2.0/version
   /plugin
   plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-compiler-plugin/artifactId
 configuration
   source1.5/source
   target1.5/target
 /configuration
   /plugin
 /plugins
   /build
   dependencies
 dependency
   groupIdopensymphony/groupId
   artifactIdsitemesh/artifactId
   version2.3/version
 /dependency
 dependency
   groupIdjavax.servlet/groupId
   artifactIdservlet-api/artifactId
   version2.3/version
   scopeprovided/scope
 /dependency
 dependency
   groupIdjavax.mail/groupId
   artifactIdmail/artifactId
   version1.4.2/version
 /dependency
 dependency
   groupIdjunit/groupId
   artifactIdjunit/artifactId
   version4.5/version
   scopetest/scope
 /dependency
   /dependencies
 /project
 
 
 I don't know what 's going on. Any advice ?
 
 
 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org
 

_
Windows Live™: Life without walls.
http://windowslive.com/explore?ocid=TXT_TAGLM_WL_allup_1a_explore_032009

Re: war:war not including src/main/java

2009-03-07 Thread David C. Hicks
I don't think that the war plugin includes source for your Java classes 
in the WAR, at least, not by default.  The classes that are generated in 
the compile phase would be included, but not the source.  Sources in 
src/main/webapp would be included, I think.  Looking at the 
maven-war-plugin documentation, it appears that there are options to 
include sources.



Mansour wrote:
I am facing this problem where maven is not including the sources in 
src/main/java.

With jetty:run on the develpoment everthing is fine.
But, when I create the war, the directory is not included.

?xml version=1.0?
project xmlns=http://maven.apache.org/POM/4.0.0; 
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; 
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd;

 modelVersion4.0.0/modelVersion
 groupIdcom.mysite/groupId
 artifactIdwebsite/artifactId
 packagingwar/packaging
 version1.0-SNAPSHOT/version
 namewebsite Maven Webapp/name
 urlhttp://maven.apache.org/url
 build
   finalNamewebsite/finalName
   plugins
 plugin
   groupIdorg.mortbay.jetty/groupId
   artifactIdmaven-jetty-plugin/artifactId
   configuration
 contextPath//contextPath
 scanIntervalSeconds1/scanIntervalSeconds
   /configuration
 /plugin
 plugin
   groupIdorg.apache.maven.plugins/groupId
   artifactIdmaven-war-plugin/artifactId
   version2.0/version
 /plugin
 plugin
   groupIdorg.apache.maven.plugins/groupId
   artifactIdmaven-compiler-plugin/artifactId
   configuration
 source1.5/source
 target1.5/target
   /configuration
 /plugin
   /plugins
 /build
 dependencies
   dependency
 groupIdopensymphony/groupId
 artifactIdsitemesh/artifactId
 version2.3/version
   /dependency
   dependency
 groupIdjavax.servlet/groupId
 artifactIdservlet-api/artifactId
 version2.3/version
 scopeprovided/scope
   /dependency
   dependency
 groupIdjavax.mail/groupId
 artifactIdmail/artifactId
 version1.4.2/version
   /dependency
   dependency
 groupIdjunit/groupId
 artifactIdjunit/artifactId
 version4.5/version
 scopetest/scope
   /dependency
 /dependencies
/project


I don't know what 's going on. Any advice ?


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



[ANN] Maven Doxia 1.1 Released

2009-03-07 Thread Vincent Siveton
The Maven team is pleased to announce the release of the Maven Doxia,
Doxia Sitetools, version 1.1 and Maven Doxia Tools, version 1.0.

Doxia is a content generation framework which aims to provide its
users with powerful techniques for generating static and dynamic
content: Doxia can be used in web-based publishing context to generate
static sites, in addition to being incorporated into dynamic content
generation systems like blogs, wikis and content management systems.

http://maven.apache.org/doxia/

Release Notes - Maven Doxia - Version 1.1

** Bug
* [DOXIA-51] - RtfSink supports only .ppm image type in figureGraphics()
* [DOXIA-59] - Doxia creates files with inconsistent new lines
* [DOXIA-99] - Figures require extension in APT and they should not
* [DOXIA-127] - Twiki module cannot parse two forced links in the
same paragraph
* [DOXIA-148] - FmlParser emits HTML specific events
* [DOXIA-152] - Xdoc parser shouldn't insert anchors for section titles
* [DOXIA-156] - XhtmlSink#tableCell( boolean headerRow, String
width ) uses a COLSPAN attribute instead of WIDTH attribute
* [DOXIA-157] - Doxia Book doesn't work with xdoc source files
* [DOXIA-160] - Book output in doc-book format is not well formed
* [DOXIA-161] - filename with dot have a false output name
* [DOXIA-162] - Failure to parse paragraph line with an EOL
* [DOXIA-166] - Book output ignores book, chapter and section titles
* [DOXIA-168] - Confluence module does not allow nested formatting
- e.g. a bullet cannot contain *bold* text or a [link]
* [DOXIA-169] - Confluence module does not recognize line breaks (\\)
* [DOXIA-171] - Confluence quote macro not recognised
* [DOXIA-173] - Support for Confluence anchor macro
* [DOXIA-175] - Confluence module does not recognise backslash as
escape character
* [DOXIA-176] - Confluence parser doesn't strip leading space for
section titles
* [DOXIA-177] - Invalid XHTML because of wrong position of table caption
* [DOXIA-178] - Confluence: nested wiki formats (e.g. bold italic)
do not work
* [DOXIA-180] - Confluence module should remove leading '#' from anchor link
* [DOXIA-181] - Confluence ParagraphBlockParser does not offer
lines to other parsers
* [DOXIA-182] - Confluence support for img macro
* [DOXIA-183] - Remove xhtml specific events from xdoc parser
* [DOXIA-189] - newline added after every closing tag
* [DOXIA-190] - text like (=something=) is parsed incorrectly
* [DOXIA-193] - forced url links where parsed as WikiWords links
* [DOXIA-201] - param tags are always parsed as macro parameters
* [DOXIA-212] - There is no way to include images using relative urls
* [DOXIA-215] - Trailing spaces after table definition causes exception
* [DOXIA-216] - Linkcheck broken
* [DOXIA-221] - Fix ArrayIndexOutOfBoundsException in XhtmlBaseSink
* [DOXIA-222] - XhtmlBaseParser swallows significant whitespace
* [DOXIA-225] - DocBookParser swallows significant whitespace
* [DOXIA-227] - [regression] attributes stripped from img tags
* [DOXIA-230] - Review Doxia generation for Apt and Docbook
* [DOXIA-235] - Confluence parser doesn't strip leading spaces for
list items
* [DOXIA-240] - NPE when building documentation
* [DOXIA-241] - Xdoc/XhtmlBaseParser doesn't close sections properly
* [DOXIA-242] - Echo macro outputs internal params
* [DOXIA-246] - TOC macro: higher entries are ignored
* [DOXIA-247] - unable to parse document when the last character is '}'
* [DOXIA-250] - Xml parser should handle entities defined in doctype
* [DOXIA-251] - The AbstractXmlParser should take care of EOL
* [DOXIA-257] - APT local anchor / link doesn't work when there is
a whitespace in the anchor name
* [DOXIA-259] - Source code snippets are not indented automatically
* [DOXIA-261] - The Twiki noautolink is not used at all
* [DOXIA-270] - Review doxia-converter artefact to respect ASF rules
* [DOXIA-273] - Broken link in External Resources page
* [DOXIA-274] - Broken link in What is Doxia? page
* [DOXIA-291] - Wrong classid in SwfMacro
* [DOXIA-292] - Be sure to call tableRows(int[], boolean) to be
backward compatible with Doxia 1.0

** Improvement
* [DOXIA-78] - Doxia XDOC parser and XHTML renderer ignore
rowspan and colspan attributes for tables
* [DOXIA-137] - Add comments to sink API
* [DOXIA-142] - Allow snippet macro contents to be output as-is,
instead of verbatim
* [DOXIA-144] - Review signature methods
* [DOXIA-153] - HTML tags in twiki not rendered correctly
* [DOXIA-154] - Xdoc parser should recognize script tag
* [DOXIA-155] - AbstractXmlParser should recognize CDATA, entities
and comments
* [DOXIA-163] - Add support for underscores
* [DOXIA-164] - Add support for strikethroughs
* [DOXIA-191] - Display images given an url
* [DOXIA-192] - checkstyle
* [DOXIA-194] - Generate 

[ANN] Maven EAR Plugin 2.3.2 Released

2009-03-07 Thread Stephane Nicoll
The Maven team is pleased to announce the release of the Maven EAR
Plugin, version 2.3.2

This version supports JBoss5 and filtering of the ear resources
directory, namely.

http://maven.apache.org/plugins/maven-ear-plugin/

You should specify the version in your project's plugin configuration:

plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-ear-plugin/artifactId
 version2.3.2/version
/plugin


Release Notes - Maven 2.x Ear Plugin - Version 2.3.2

** Bug
* [MEAR-70] - loader-repository node for jboss configuration
* [MEAR-79] - generated application.xml is empty (0 bytes) if
generatedDescriptorLocation is redefined
* [MEAR-82] - From version 2.3 on, resources are not always copied
to the EAR structure
* [MEAR-94] - Synchronize module releases and documentation releases
* [MEAR-96] - earSourceExcludes does not work for jar dependency
filtering like warSourceExcludes / packagingExcludes for the
maven-war-plugin
* [MEAR-99] - Corrupted deployment descriptor if configured
encoding does not match platform encoding
* [MEAR-100] - Support altDeploymentDescriptor for J2EE 1.4
* [MEAR-101] - workDirectory contents added to target/ear file.

** Improvement
* [MEAR-78] - Library directory configuration
* [MEAR-81] - Suppressing application.xml creation (and inclusion)
completely
* [MEAR-86] - Add a property to automatically add jars
dependencies into application.xml (TEST AND PATCH ATTACHED).
* [MEAR-102] - Support for JBoss 5 as well as some missing elements

** New Feature
* [MEAR-43] - add ability to do filtering (i.e. template var
replacement) for files in src/main/application/
* [MEAR-97] - Add ability to generate jboss-app.xml for JBoss 5

** Wish
* [MEAR-52] - Ability to add jboss dataosources (*ds.xml) files as
a jarModule

Enjoy,

-The Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org