It's already listed as a "new feature". Surely if it's that, and
unscheduled, it's out of the defect filters but the work still there
for anyone that picks it up. I did review the original code, but lost
track of the issue that seems to now have updated patches.
I'd like to reconsider how this fits into the artifact redesign. Can
I reopen it? There are a number of other new features recently closed
I think should be in the same category.
There are also some defects which were closed because the patches
were no good but still appears to be problems. Should they be
reopened and the patch flag turned off?
- Brett
On 04/06/2007, at 12:44 PM, Jason van Zyl wrote:
On 3 Jun 07, at 7:52 PM 3 Jun 07, Brett Porter wrote:
I disagree. What sacred ritual must I perform to reopen this?
Write something that works or find someone who will. Most of these
issues are just sitting with no one doing anything. At best put it
somewhere like "nice idea, but no one is actually going to do
anything about it right now".
What I want to see is a clear view of what technical issues there
are with the project and not a bunch "nice to haves". And I want to
be able to know when we actually have zero defects (yes, maybe a
pipe dream) but the organization of our issues makes this
impossible with documentation, ideas and everything else. The only
time anyone notices them is when I try to close them. I would also
like to differentiate between new feature submissions versus
patches for existing problems. Something I'm trying to do as I
process all the patches and categorize the issues.
I think what IDEA does is a good idea where they basically have a
place for users to enter whatever they want and then the real
schedules and plans are made in project that is worked from.
- Brett
On 03/06/2007, at 7:08 AM, Jason van Zyl (JIRA) wrote:
[ http://jira.codehaus.org/browse/MNG-671?
page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl closed MNG-671.
-----------------------------
Yah, I don't think this is a burning issue anymore. At least not
with respect to click through license handling of things like
hibernate which maven is just going to take from the repository
(I don't know what the status is now honestly) and there are
impls of things like JavaMail/Activation now. So we'll let this
one rest for now.
implement a license clickthrough
--------------------------------
Key: MNG-671
URL: http://jira.codehaus.org/browse/MNG-671
Project: Maven 2
Issue Type: New Feature
Reporter: Brett Porter
Fix For: 2.1.x
Attachments: maven-artifact-manager-patch-2.txt, maven-
artifact-manager-patch.txt, maven-artifact-patch-2.txt, maven-
license-patches-3.zip, maven-settings-patch-2.txt, maven-
settings-patch.txt
we need some basic license acceptance policy for downloadable
artifacts. For now, this can just be a Y/N that is saved forever.
--
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
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
