On 21 Aug 07, at 4:58 PM 21 Aug 07, Brett Porter wrote:
On 22/08/2007, at 8:17 AM, Grzegorz Kossakowski wrote:
(I'm resending this mail from another account because previous one
seems to be stuck in moderation queue)
Brian E. Fox pisze:
I believe this came from Atlassian. (I386 on irc). They ship
their jars
and javadocs to users who want to write plugins etc, but the sources
stay internal (or to paying customers I think).
Sorry if I'm missing something but why they can't just publish
everything to their private repo and just mirror things
they want share to the public repository afterwards?
This was my initial response too.
As being Maven user (I'm from Apache Cocoon) I support Jason's
opinion here. If you have very specific requirements that
could be fulfilled by existing tools (few lines of script) just
use them and don't pollute other tools with your
specific needs.
This solution is easier for the end user than having to write syncs
with includes/excludes themselves. It all gets done in one hit.
I'm not fan of featuritis, but it sounded like a valid use case,
and since it gives the same net effect and doesn't affect any
backwards compatibility I thought it was worth going ahead with.
I don't think applying them is a good idea. Any separation of the
primary and secondary artifacts will cause a problem and I don't see
any value in doing so, it makes tooling harder and will only cause
confusion. So for me it's a -1.
Cheers,
Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
