[
http://jira.codehaus.org/browse/MOJO-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260659#action_260659
]
Jakub Skoczen commented on MOJO-1478:
-------------------------------------
After upgrading to alpha-4 (alpha-3 no longer works with Maven 3 for some
reason) which has the fix applied, my generated (in
"generated-sources/apt/my/package") 'jaxb.index' files are no longer packaged
in the output jar. The workaround I came up with was to override
'outputDirectory' to '${project.build.directory}/generated-sources/apt', so
basically revert the previous behavior. The thing I've noticed is that, on
alpha-3 or with the workaround, the 'jaxb.index' also ends up in
'target/classes' and thus gets packaged.
Same behavior on OSX 10.6.6 and Debian Squeeze (6.0)
Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
Java version: 1.6.0_24, vendor: Apple Inc.
Java home: /Library/Java/JavaVirtualMachines/1.6.0_24-b07-334.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x", version: "10.6.6", arch: "x86_64", family: "mac"
Apache Maven 2.2.1 (rdebian-4)
Java version: 1.6.0_22
Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre
Default locale: en_US, platform encoding: ANSI_X3.4-1968
OS name: "linux" version: "2.6.32-5-amd64" arch: "amd64" Family: "unix"
> Distinguish between -d and -s correctly when invoking apt
> ---------------------------------------------------------
>
> Key: MOJO-1478
> URL: http://jira.codehaus.org/browse/MOJO-1478
> Project: Mojo
> Issue Type: Bug
> Components: apt
> Affects Versions: apt-maven-plugin-1.0-alpha-2
> Environment: Mac OSX, JDK 1.6, mvn 2.2.1, apt-maven-plugin 1.0-alpha-3
> Reporter: Peter Lynch
> Assignee: Mark Hobson
> Fix For: apt-maven-plugin-1.0-alpha-4
>
> Attachments: MOJO-1478.patch
>
>
> setting the outputDirectory on the apt config causes it to be passed to apt
> executable using the '-s' option.
> Unfortunately this does not work. Instead sources get put in the directory
> where mvn is launched.
> Comparing this behavior with the way Ant invokes apt shows that Ant uses '-d'
> option in all cases, whether compiling or not - and it works so a similar
> change to apt-maven-plugin would seem very safe and cause it to work as
> documented and described.
> Attached is a patch which fixes this.
--
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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
