Hiram Chirino wrote:
As I see it, it comes down to a choice of having the user configure
his pom with either
1) an artifact id or group id or version id that
includes incubator in it.
or
2) a repository id that include incubator in it.
Or, as I see it, both. Since the artifacts are
Hi Noel,
I'm expecting you'll probably respond to my other mail too, but I just
wanted to pick up on this point.
On 17/06/06, Noel J. Bergman [EMAIL PROTECTED] wrote:
Distinguishing between what was put out during Incubation and what was put
out post-Incubation is a good thing.
Why would a
Hi Chris,
I don't think this is intentional. Something is broken in the JIRA setup.
I have posted this email on general@incubator.apache.org to see if folks
there may know what's the problem and fix it.
Thanks for noticing
-- George
-Original Message-
From: Chris Hostetter
Thanks Hoss.
If this is the case, who ever has the karma to fix this, can you take care
of it?
Also, I can't figure out how to assign, close or even edit a JIRA issue
opened against Lucene.Net. For example, take a look at:
http://issues.apache.org/jira/browse/LUCENENET-6 and I can't see
Jira required for incubating project Abdera
---
Key: INCUBATOR-21
URL: http://issues.apache.org/jira/browse/INCUBATOR-21
Project: Incubator
Type: New Feature
Reporter: Gavin
Priority: Critical
Hope this is the right
Should this have gone on @infra Jira request instead?
If so let me know.
Gav...
-Original Message-
From: Gavin (JIRA) [mailto:[EMAIL PROTECTED]
Sent: Sunday, 18 June 2006 10:15 AM
To: general@incubator.apache.org
Subject: [jira] Created: (INCUBATOR-21) Jira required for incubating
[
http://issues.apache.org/jira/browse/INCUBATOR-21?page=comments#action_12416656
]
Gavin commented on INCUBATOR-21:
Sorry, close this, I'll re-create it on @infra instead.
Jira required for incubating project Abdera
