Issue Details (XML | Word | Printable)

Key: MAVENUPLOAD-960
Type: Task Task
Status: Closed Closed
Resolution: Fixed
Assignee: Carlos Sanchez
Reporter: Marc Guillemot
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Maven Upload Requests

HtmlUnit 1.9 upload request

Created: 27/Jun/06 04:12 PM   Updated: 28/Jun/06 03:09 PM   Resolved: 28/Jun/06 11:39 AM

Bundle URL: http://htmlunit.sourceforge.net/htmlunit-1.9-bundle.jar
Project URL: http://htmlunit.sourceforge.net/
Contributor URL: http://htmlunit.sourceforge.net/team-list.html



Sort Order: Ascending order - Click to sort in descending order
Carlos Sanchez added a comment - 28/Jun/06 09:11 AM
I'd need to know which of the dependencies are only needed at build time, which only needed for testing htmlunit and which ones only needed at runtime, to tag them in the m2 pom.
Is any of them optional or are all required?

Marc Guillemot added a comment - 28/Jun/06 09:40 AM
As you guess are not all depencies need at runtime. How do you want the information?

Carlos Sanchez added a comment - 28/Jun/06 09:58 AM
the maven 1 pom can have inside dependencies/properties

<scope>provided</scope> (for the servlet api)
<scope>runtime</scope> (only needed at runtime)
<scope>test</scope> (only needed for testing htmlunit, so not needed by people using it)

plus

<optional>true</optional>
if it's only needed at build time or is optional

Marc Guillemot added a comment - 28/Jun/06 10:29 AM
the required library are tagged with <htmlunit.group>required</htmlunit.group>, the ones marked with <htmlunit.group>test</htmlunit.group> are only needed for testing htmlunit and all marked with <htmlunit.group>jelly</htmlunit.group> are optional

Carlos Sanchez added a comment - 28/Jun/06 11:39 AM
Please check http://www.ibiblio.org/maven/htmlunit/poms/htmlunit-1.9.pom and add those improvements to your sources for next release. It'll automate the pom generation for Maven 2 that will benefit users

Marc Guillemot added a comment - 28/Jun/06 03:09 PM
thanks for the info. We will try to fix this for next release (or better, move to maven 2).