[
http://jira.codehaus.org/browse/MAVENUPLOAD-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103558
]
Paul King commented on MAVENUPLOAD-1619:
----------------------------------------
Any suggestions on the path forward? Is there a standard maven way to handle
the above or is this use case outside what the standard model supports? Or to
rephrase, does moving forward while sticking with the current model involve
splitting the deliverables into two: one which would have the required
compile-time dependency, the other would have to remove the class and remove
the dependency? Is there something equivalent to ivy's profiles? I am not 100%
sure about the full capabilities of ivy's profiles but I believe they can
handle scenarios like this.
> Please upload XMLUnit for Java 1.1
> ----------------------------------
>
> Key: MAVENUPLOAD-1619
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1619
> Project: maven-upload-requests
> Issue Type: Wish
> Reporter: Stefan Bodewig
> Assignee: Carlos Sanchez
>
> XMLUnit for Java 1.1 has been released today.
> http://xmlunit.sf.net/
> I am listed as a project admin at http://sourceforge.net/projects/xmlunit/
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
