axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <>
Subject [jira] Resolved: (AXIS2-2647) axis2-maven-aar-plugin does not honor classifier
Date Thu, 18 Dec 2008 19:35:44 GMT


Andreas Veithen resolved AXIS2-2647.

    Resolution: Cannot Reproduce
      Assignee: Andreas Veithen  (was: Jochen Wiedmann)

I tested this with the axis2-aar-maven-plugin and axis2-mar-maven-plugin from trunk and it
works like a charm (with Maven 2.0.9). I used the following configuration:


> axis2-maven-aar-plugin does not honor classifier
> ------------------------------------------------
>                 Key: AXIS2-2647
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 1.2
>         Environment: Windows XP; Eclipse; JDK 1.5; Maven2 2.0.4; Axis2 1.2; Axis Tools
(aar and wsdl2code plugin) 1.2
>            Reporter: Eddie Bush
>            Assignee: Andreas Veithen
> I define multiple profiles (dvel, test, prod), and aim to leverage those profiles to
build distinct artifacts for each profile.
> I can define a simple JAR project using maven and this behaves correctly -- the artifacts
are generated and include the classifier in the artifact name.  However, using the axis2-maven-aar-plugin,
which explicitly states in the documentation that it may be configured with a classifier,
this does not work.  The documentation is a bit lacking, but I have tried placing the configuration
in every legal location, and have tried setting the classifier in ever possible fashion --
including defining it as a command-line option (-Dclassifier=foo).  Regardless of what approach
I take, the axis2-maven-aar-plugin still generates the artifact without respecting the classifier.
> I had spoken with Martin Gainty about this, and I believe he thinks this is not an Axis2
issue, but based off my experience with the jar plugin actually working it seems as though
this issue must exist at the plugin level.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message