Here they are:

https://issues.apache.org/activemq/browse/SM-608
https://issues.apache.org/activemq/browse/SM-838

http://www.nabble.com/Maven-repository-problem-tf2811096s12049.html#a7851593
http://www.nabble.com/WSDL-First-example-tf2373483s12049.html#a6612649
http://www.nabble.com/Installing-loan-broker-bpel-example-tf2374581s12049.html#a6783204
http://www.nabble.com/Error-building-tooling-projects-tf2500901s12049.html#a6996849
http://www.nabble.com/Help-running-Maven-examples-tf2598289s12049.html#a7346692


Just a few notes:
  We have somewhat managed to lower the problems which were caused
mainly by the examples
   shipped in ServiceMix distribution that did not include the
incubating repository: this means that
  users could not even use our examples out of the box :-( 

  While I think ServiceMix is known as being in incubator at the ASF
(the distribution, main dir and
   all jars have incubator in their name, in addition to the incubator
logo on the web site, disclaimers,
   etc ...), i have exchanged mails from people who do not understand
what incubator is.  They are really
   thinking it is a sandbox for non mature projects (i don't say
community here): they are referring to code,
   so that it is clear that they don't get what the incubator is about.

  Usually, when you use maven to reference a project, you know this
project, so that it seems quite
   unnecessary to force people to add the incubating repo in their pom,
as they already know that the
   project is in incubation (even if they don't understand what it
means, but this is another problem).
  For people who already understand maven, this is not a problem.  For
beginners, it is quite a problem
   to understand why this does not work.  Some may post a mail to the
mailing list, but how many did not
   and gave up ?

While the incubator is a good idea, it seems that it is more difficult
to build a community inside the incubator
than outside, because of all the existing rules.  And remember that the
release early, release often mantra can
not be applied on podlings, given the pain to release a project in
incubation.

Cheers,
Guillaume Nodet

Davanum Srinivas wrote:
> Sorry, i lost you. this whole "we need podling artifacts in central
> repo" because right now you are putting our user through a meat
> grinder has no basis in fact. Am asking for JIRA issues, email threads
> that show that this is indeed a serious issue and not just a made up
> issue. Show me the evidence is what i am asking.
>
> thanks,
> dims
>
> On 3/16/07, Jochen Wiedmann <[EMAIL PROTECTED]> wrote:
>> On 3/16/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
>>
>> > Please see #1 item here:
>> > http://marc.info/?l=incubator-general&m=117397443306478&w=2
>>
>> Did you read #5 as well? It contradicts your point.
>>
>> -- 
>> Emacs 22 will support MacOS and CygWin. It is not yet decided, whether
>> these will be used to run Emacs or the other way round.
>>
>> ---------------------------------------------------------------------
>> 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]

Reply via email to