[
https://issues.apache.org/activemq/browse/AMQ-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=53891#action_53891
]
David Jencks commented on AMQ-1040:
-----------------------------------
I'm not sure if what is requested is a source jar for each maven project as
produced by the source:jar goal or a source archive of the entire project, and
its not clear if snapshots are requested or just the actual release.
The latter is the only actual official released apache artifact, any binary goo
is purely for the convenience of users. While this is not the attitude of most
java users, it is very definitely apache policy.
In either case, the maven build (trunk, currently 5.3) is set up to produce
both of these as long as you build with -Papache-release. This works for both
snapshots and releases using the release plugin.
I'd suggest that the hudson build be set up to use this profile all the time.
Source jars (not the source archive) are extremely convenient for IDEs, both
IDEA and eclipse. Since you aren't forcing anyone to download these, and not
paying for the apache disk space for the snapshot storage in the nexus repo, I
don't see how there could be a problem.
> Full src-jar distributed with binary
> ------------------------------------
>
> Key: AMQ-1040
> URL: https://issues.apache.org/activemq/browse/AMQ-1040
> Project: ActiveMQ
> Issue Type: Improvement
> Affects Versions: 4.1.0
> Environment: n/a
> Reporter: Endre Stølsvik
> Assignee: Rob Davies
> Fix For: 5.4.0
>
> Attachments: pom.xml.diff.txt
>
>
> For absolutely all developers (extrapolating from one person, myself), a
> src-jar that comes with the "bin" distribution makes the world a better place
> to live.
> With a src jar, you only add the full jar, "attach" the src-jar, and you're
> _rellay_ good to go both developing but not least stack-tracing and
> debugging. The src-jar should include sources for most of the stuff that
> actually reside in the full jar, if not all.
> Eclipse: if you include the "full jar", it's slightly problematic to include
> a whole bunch of dirs from the src-distro. You'll end up having to include
> all those lib jars, and on each of them put the corresponding src dir.
> The whole thing won't bloat the distro very much - but will relieve very many
> developers from having to download the extra distro, and from the annoyance
> of not being able to just configure one simple jar with src-attachment.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
