Hahaha...nice one ;)
Gonzalo Vásquez Sáez
Gerente Investigación y Desarrollo (R&D)
Altiuz Soluciones Tecnológicas de Negocios Ltda.
Av. Nueva Tajamar 555 Of. 802, Las Condes - CP 7550099
+56 2 335 2461
gvasq...@altiuz.cl
http://www.altiuz.cl
http://www.altiuzreports.com
El 26-12-2013, a las 20
It'll be released on Tuesday. The trick is determining which Tuesday
Sorry! Couldn't resist...
Being an Apache and open source project, release schedules can be hard to find.
IOW, no, there's no estimated release date.
Cheers!
Clay
--
"My religion is simple. My religion is kindness."
- HH
Thanks Glenn,
Is there an estimated date for the next release?
Regards,
Gonzalo Vásquez Sáez
Gerente Investigación y Desarrollo (R&D)
Altiuz Soluciones Tecnológicas de Negocios Ltda.
Av. Nueva Tajamar 555 Of. 802, Las Condes - CP 7550099
+56 2 335 2461
gvasq...@altiuz.cl
http://www.altiuz.cl
htt
We don't retroactively change release images. As Chris stated in his
previous email "the avalon dependency will be fixed in the next release."
On Thu, Dec 26, 2013 at 9:52 AM, Carlos wrote:
> Hi,
>
> Was this change commited? I'm using this dependecy:
>
>
> org.apache.xmlgraphi
Hi,
Was this change commited? I'm using this dependecy:
org.apache.xmlgraphics
fop
1.1
But still find the same problem:
The following artifacts could not be resolved:
org.apache.avalon.framework:avalon-framework-api:jar:4.2.0,
org.apache.avalon.
Thanks for the suggestion Stephen. I have changed the POM template so
that the avalon dependency will be fixed in the next release.
Committed in revision 1416937
Thanks,
Chris
On 02/12/2012 21:29, Stephen More wrote:
avalon 4.2.0 artifact is already loaded in repo, it just has a
different g
avalon 4.2.0 artifact is already loaded in repo, it just has a different
group id.
Changing fop-1.1.pom from:
org.apache.avalon.framework
avalon-framework-api
4.2.0
org.apache.avalon.framework
avalon-framework-impl
4.2.0
to
avalon-framew
I rolled it back to 4.2.0 because that is the version of
avalon-framework-api that is included in the lib directory of fop's binary
distribution (for both fop 1.0 and fop 1.1). I think the correct fix is
either to add the 4.2.0 artifact to maven repo or to update the binary copy
of that artifact to