maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Barrie Treloar (JIRA)" <>
Subject [jira] Commented: (MNG-2705) add jar sources in repository for snapshot builds
Date Fri, 01 Jan 2010 05:33:55 GMT


Barrie Treloar commented on MNG-2705:

I'm being lazy and lowering the barrier for people to submit bugs.

For example, a common problem I had while trying to fix problems:
I am working on plugin A which has more than one other snapshot dependency B, C, D, etc.

I only want to checkout plugin A since I am pretty sure the bug is there.
I do not want to have to chase the dragons tail and check out all snapshot dependencies on
the chance that the problem is in one of those. 

Now when I am debugging plugin A because the snapshot dependencies have been downloaded from
the snapshot repository and because the source jar is not available I can not step the debugger
into these dependencies - since all I get is the bytecodes. 

If I find that the problem is in a dependent plugin, only then do I want to checkout from
svn and run mvn install so I can fix it.

As has been noted I can checkout the source for these myself and install them locally, but
this is a waste of time and effort for all the plugins that work as expected.

> add jar sources in repository for snapshot builds
> -------------------------------------------------
>                 Key: MNG-2705
>                 URL:
>             Project: Maven 2 & 3
>          Issue Type: Task
>          Components: Bootstrap & Build
>            Reporter: Barrie Treloar
>            Priority: Minor
> When using IDE like eclipse, it would be great to have dependecies sources (optionnaly)
added to repository.
> This way eclipse plugin (and others) could generate a .classpath file that set "source
attachement" and allow code and javadoc consult, debuging and inherited methods implementation
with original parameters names.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message