Hi Alex,

I think what I propose is better to do the next time. Right now better to
finish the ticket.

Regarding the maven plugin, as I understand, is not broken...there's
nothing to fix, as I understand is a problem os code broken. If not I'm
missing something and better Chris to throw some light on this

Thanks!


2016-10-03 20:12 GMT+02:00 Alex Harui <aha...@adobe.com>:

>
>
> On 10/3/16, 10:55 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
> <carlos.rov...@gmail.com on behalf of carlosrov...@apache.org> wrote:
>
> >Hi,
> >
> >since Friday Jenkins build is broken (check :
> >https://builds.apache.org/view/E-G/view/Flex/)
> >
> > I suppose that is caused by the changes Alex are doing in develop to
> >compjsc changes.
> >
> >Hope you guys could consider to make those kind of changes in a branch
> >(Chris talked about a way of doing this and generate automatic jobs)
> >
> >If we do this, we could always ensure blue state.
> >
> >Then,as the ticket is finished (is doing what is supposed to do and build
> >passes localy), it could be safely merged in develop to maintain the blue
> >state.
> >
> >In other way this could potentially stop other works. For example, I can't
> >right now use the archetype tool created by Chris due to red state.
> >
> >Please, could you consider this?
>
> Yes, I should have done this in a branch, but I didn't and it got
> accidentally pushed.  I also was thinking I'd find the order of
> COMPC/COMPJSC somewhere in the pom.xml files.  Now the question is, should
> I go through the trouble to revert it, or how can myself and others learn
> to fix the Maven plugin?  It isn't good that we are dependent on a single
> committer for things like this.  I spent time trying to understand how the
> plugin works but could not figure it out.  Some advice on how to fix it
> might actually be better than just having Chris fix it.
>
> -Alex
>
>


-- 

Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
http://www.avant2.es


Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o confidencial. Si ha recibido este mensaje por
error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
proceda a su destrucción.

De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
S.A. La finalidad de dicho tratamiento es facilitar la prestación del
servicio o información solicitados, teniendo usted derecho de acceso,
rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
necesaria.

Reply via email to