Hi David,

Thanks for your quick response. Based on your and your fellow committer's 
comments on this thread, I suspected you were as frustrated as well.

To answer your immediate question: I may be best to put a short but prominent 
comment here: https://cwiki.apache.org/GMOxDEV/index.html
In addition, it may be helpful to update the build instructions included in the 
source and put the same warning there.

At least that way, interested developers would be aware of the current issues.

-Ulrich

Ulrich Romahn
Sr. MTS, Architect

PayPal
The safer, easier way to pay online

2211 North First Street, San Jose, CA 95131
Direct  408 967 6808  |  Cell  650 430 4499
Skype  uliromahn

From: David Jencks [via Apache Geronimo] 
[mailto:ml-node+s328035n3676516...@n3.nabble.com]
Sent: Friday, January 20, 2012 12:12 PM
To: Romahn, Ulrich
Subject: Re: Geronimo 3 and karaf 3

HI Ulrich,

I appreciate your frustration... I've been struggling with various forms of the 
current problems for more than a year and think we may finally be close to a 
working stable solution.  How and if these problems show up seems to be quite 
dependent on your local maven environment.  For instance I have nexus installed 
locally and configured to never download any org.apache.geronimo.* artifacts 
and that has stabilized my builds considerably but concealed the problems other 
people are having from me.

I have been trying to update the build status on the geronimo dev list, and you 
seem to have found the current thread on the topic.  Do you have a suggestion 
on a better way?

We also have a buildbot set up but I haven't figured out when it runs or how to 
trigger it.  Sometimes it reports interesting errors quickly and other times it 
seems to just not run.

thanks for your interest!
david jencks

On Jan 20, 2012, at 11:54 AM, uromahn wrote:

> Gentlemen:
>
> I am following the development on Geronimo 3 for quite a while since we are
> very interested in potentially using it to support a new OSGI-based server
> framework that we will use here.
>
> Today, I have refreshed my G3 sources of trunk and was trying to build G3.
> After reading through this thread and doing the build step-by-step (I had to
> go into various sub-systems and do a mvn clean install first before I could
> run the top level build successfully) I finally ended up with the completed
> assemblies. However, when trying to start G3 using the command "./bin/karaf"
> I am getting a failed start because some dependencies are missing.
>
> Unfortunately, it appears that the current state of trunk is somewhat
> unstable. I completely understand that this happens, but I would kindly
> suggest to post a message somewhere "warning" people wanting to build
> G3-trunk themselves, that the result may actually not really what they hoped
> for.
>
> With a little frustration and hope for a more stable situation soon,
>
> kind regards,
> -Ulrich
>
> --
> View this message in context: 
> http://apache-geronimo.328035.n3.nabble.com/Geronimo-3-and-karaf-3-tp3600027p3676480.html
> Sent from the Development mailing list archive at Nabble.com.


________________________________
If you reply to this email, your message will be added to the discussion below:
http://apache-geronimo.328035.n3.nabble.com/Geronimo-3-and-karaf-3-tp3600027p3676516.html
To unsubscribe from Geronimo 3 and karaf 3, click 
here<http://apache-geronimo.328035.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=3600027&code=dXJvbWFobkBwYXlwYWwuY29tfDM2MDAwMjd8LTEyMzk5MjQ3OTg=>.
NAML<http://apache-geronimo.328035.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.InstantMailNamespace&breadcrumbs=instant+emails%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>


--
View this message in context: 
http://apache-geronimo.328035.n3.nabble.com/Geronimo-3-and-karaf-3-tp3600027p3676525.html
Sent from the Development mailing list archive at Nabble.com.

Reply via email to