You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Martijn Dashorst (JIRA)" <ji...@codehaus.org> on 2007/04/12 23:34:46 UTC
[jira] Commented: (MSOURCES-15) Sources jar increases in size
(possibly includes whole harddisk volume)
[ http://jira.codehaus.org/browse/MSOURCES-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92787 ]
Martijn Dashorst commented on MSOURCES-15:
------------------------------------------
Good one. I'll go and submit another bug report in the future trying to help out. Next thing I'll be responsible for fixing the issue myself?
I did say I tried 2.0.3, but I don't have the time and the energy to check out the plugin, build it, get a whole lot of other (development? snapshot?) plugins downloaded into my repo, to confirm this. The original bug is marked critical, I assume one of the maintainers of this plugin has the snapshot readily available to check this pom. So yes, please expect me to become a full maven developer to confirm this.
> Sources jar increases in size (possibly includes whole harddisk volume)
> -----------------------------------------------------------------------
>
> Key: MSOURCES-15
> URL: http://jira.codehaus.org/browse/MSOURCES-15
> Project: Maven 2.x Sources Plugin
> Issue Type: Bug
> Reporter: Martijn Dashorst
> Assignee: Carlos Sanchez
> Attachments: pom.xml
>
>
> This may be fixed with the following issue: http://jira.codehaus.org/browse/MSOURCES-6
> However, I wanted to submit my testcase, just to make sure it is solved, or this may be another issue (it didn't bite us before).
> The attached pom.xml shows the same problem as in http://jira.codehaus.org/browse/MSOURCES-6: the whole project directory is included, instead of just the sources (and resources).
> In this pom the difference is that the referenced file in the resources section is not available. This might be a special case, or not. Given that 2.0.3 is not released yet, I wasn't able to determine if that would solve this problem.
--
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