[
https://jira.codehaus.org/browse/MAPPASM-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MAPPASM-145:
-----------------------------------
Summary: Wrong order of artifacts in generated classpath (was: Wrond order
of artifact in generated classpath)
> Wrong order of artifacts in generated classpath
> -----------------------------------------------
>
> Key: MAPPASM-145
> URL: https://jira.codehaus.org/browse/MAPPASM-145
> Project: Mojo AppAssembler Plugin
> Issue Type: Improvement
> Affects Versions: 1.1.1
> Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
> Maven home: D:\usr\share\java\apache-maven
> Java version: 1.6.0_30, vendor: Sun Microsystems Inc.
> Java home: D:\usr\share\java\jdk\jre
> Default locale: cs_CZ, platform encoding: Cp1250
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
> Reporter: Petr Prochazka
> Priority: Minor
> Fix For: 1.2.1
>
> Attachments: MAPPASM-145.patch
>
>
> In generated scripts is wrong order of artifacts. Project artifact is placed
> as last element of artifacts.
> This behavior creates problems, e.g. Log4J configuration, which is placed in
> some dependency artifact.
> Exists workaround. Configuration is placed to etc directory, which is placed
> as first element of classpath.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
