On 28 Aug 07, at 10:08 PM 28 Aug 07, Brett Porter wrote:
Where are we with this?
The thread went a bit off the rails for some other stuff, and the
only other suggestion I saw was:
On 23/08/2007, at 3:32 AM, Jason van Zyl wrote:
But the case that Atlassian wants solved would be very simple
with something like Proximity even today. One simple access
controller that blocked the source jars for particular users and
you're set.
But that conflicted with this:
On 22/08/2007, at 3:09 PM, James William Dumay wrote:
Customers currently download the sources from the website, not
checking
them out from the repository. Having a password protected repository
would mean we would have to add more admin overhead to the Developer
Network team.
Given that we're now talking about setting up something that is
logically equivalent (by blocking, or not promoting, some artifacts
to one repository but keeping them available from another internal
one), I think it makes sense to go with a solution that makes it as
easy as possible for the user, so I'm happy with the patch.
I ran up a quick test project, and if the artifacts are split in
this way, mvn idea:idea -DdownloadSources=true -
DdownloadJavadocs=true behaves as expected.
How if they are in different repositories?
Are there other objections?
-1
How can this possibly work in a coherent manner? How does the IDEA
and Eclipse know where to go if they are split up?
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]
