Ok.
I just tested and adding the snippet below resolved most issues besides the
menu was overlaying the content. I googled and older versions of IE don't
handle well the combination of position:fixed and using float so I removed the
fixed position for now.
Robby
From: Jasha Joachimsthal
The build was broken after your check-ins, can you fix it?
https://builds.apache.org/view/A-F/view/Cocoon/job/Cocoon-trunk/
Jasha
On 6 January 2012 09:53, Robby Pelssers robby.pelss...@nxp.com wrote:
Ok.
** **
I just tested and adding the snippet below resolved most issues besides
Hi Jos!
Looks like the class
org/apache/cocoon/components/serializers/util/XMLSerializer is
contained in C2 cocoon-serializers-charsets, you have to add the
following dependency in your pom:
dependency
groupIdorg.apache.cocoon/groupId
artifactIdcocoon-serializers-charsets/artifactId
I rechecked and found that 1 href was wrong.
a href=object-model/request-parameters?a=1amp;b=2amp;c=3
I copied that over verbatim so that probably can't have broken the build.
This is fixed now but I wonder if anything else could have broken the build.
Robby
From: Jasha Joachimsthal
Thanks, Simo!
We should document these dependencies, I think.
The cocoon side projects are not always easy to find.
Cheers,
Jos
On Fri, Jan 6, 2012 at 11:05 AM, Simone Tripodi simonetrip...@apache.orgwrote:
Hi Jos!
Looks like the class
Hi guys,
I think the cocoon-parent pom is causing issues. But as I am using maven3 it
might be wise that I don't touch that file as it might break with others still
using maven 2.
Can someone using maven 2 take a look if he finds errors in that pom?
Thx in advance,
Robby
Hi Jos,
indeed, it was not immediate also for me, I had to play a little with
the grep command :P
Thanks for your feedbacks, all the best!
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On Fri, Jan
On 06/01/2012 11:41, Robby Pelssers wrote:
Hi guys,
I think the cocoon-parent pom is causing issues. But as I am using
maven3 it might be wise that I don't touch that file as it might break
with others still using maven 2.
Can someone using maven 2 take a look if he finds errors
The RAT Maven plugin complains about licenses:
https://builds.apache.org/view/A-F/view/Cocoon/job/Cocoon-trunk/134/console
message : Failed to execute goal
org.codehaus.mojo:rat-maven-plugin:1.0-alpha-3:check (default) on project
cocoon-archetype-sample: Too many unapproved licenses: 74
Jasha
Ok. So you're saying every single file needs the ASL header? Or do we have a
list of which files should have that header?
Curious to find out if that plugin is able to handle different filetypes
correct as I will need to use different types of commenting for java, css, xml
etc.
Robby
From:
I only added the style.css without a license. That is fixed now.
Sorry for the inconvenience people. Was not fully aware of this.
Robby
From: Robby Pelssers [mailto:robby.pelss...@nxp.com]
Sent: Friday, January 06, 2012 11:56 AM
To: dev@cocoon.apache.org
Subject: RE: cocoon-parent pom breaking
On 6 January 2012 11:55, Robby Pelssers robby.pelss...@nxp.com wrote:
Ok. So you’re saying every single file needs the ASL header? Or do we
have a list of which files should have that header?
In general each source code and configuration file should have the correct
license header.
The
Remember we don't make mistakes, we have happy little accidents (Bob Ross)
;)
Something to read http://www.apache.org/legal/src-headers.html
On 6 January 2012 11:59, Robby Pelssers robby.pelss...@nxp.com wrote:
I only added the style.css without a license. That is fixed now.
** **
Update Cocoon to be OSGi compliant
--
Key: COCOON3-87
URL: https://issues.apache.org/jira/browse/COCOON3-87
Project: Cocoon 3
Issue Type: Improvement
Components: cocoon-controller, cocoon-databases,
[
https://issues.apache.org/jira/browse/COCOON3-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated COCOON3-87:
Attachment: COCOON3-87.patch
First patch part.
Update Cocoon to
[
https://issues.apache.org/jira/browse/COCOON3-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13181371#comment-13181371
]
Jean-Baptiste Onofré commented on COCOON3-87:
-
This first patch turns Cocoon
Add JavaWrapper for JsLint to the project
-
Key: COCOON3-88
URL: https://issues.apache.org/jira/browse/COCOON3-88
Project: Cocoon 3
Issue Type: Improvement
Components: cocoon-optional
Hi Peter,
I was wondering if we should care much about it. I found a link with the
result of the most common used browsers:
http://html5test.com/results.html
Perhaps we can move to HTML5 and use a bare minimum of it. :)
Best Regards,
Antonio Gallardo.
On 05/01/12 14:17, Peter Hunsberger
I think it would be reasonable enough if we tested against the latest versions
of IE, Chrome and Firefox and skip using features that are not yet supported by
all 3 of them. But the extra check I baked in on Jasha's advice is a no
brainer and resolves most issues for older versions of IE.
Hey Robby,
which Cocoon version are you using for your project? In C2.1 and C2.2
there's not only a XMLSerializer but also an HTMLSerializer and
XHTMLSerializer for their specific needs. So why not create your own
HTML5Serializer?
In HTML5 the specification teams tried to specify what browsers
Moving to HTML5 is good, as long as slightly older browsers (not only IE8
but also the feature phones) can render the page. For IE8 you only have to
add a js to be able to apply styling to new elements as section, nav etc.
If you use one of the new input methods, like type=number, the browser
will
I am using Cocoon2.2 but am planning to switch to C3 in the upcoming months.
And in my mail I was actually referring to C3.You are right about what you
write but I'd prefer to have a Serializer which follows the spec so I can just
copy the output and validate it without errors and too
On Fri, Jan 6, 2012 at 9:36 AM, Antonio Gallardo agalla...@agssa.netwrote:
Hi Peter,
I was wondering if we should care much about it. I found a link with the
result of the most common used browsers:
http://html5test.com/results.html
Perhaps we can move to HTML5 and use a bare minimum of
Ok, then create an HTML5Serializer that extends the current Serializer. An
other solution would be to add a boolean that will output differently for
html5 but I'd prefer extension above a number of if statements.
Jasha
On 6 January 2012 16:56, Robby Pelssers robby.pelss...@nxp.com wrote:
I am
For all I know the serializer does not actually output anything directly. It
hands over the task to the transformerhandler and this is where the culprit
resides.
There is no need to extend the current serializer if I adapt the current way
of working.
XmlSerializer, Html4Serializer and
Le 06/01/12 15:48, Robby Pelssers a écrit :
Hi all,
I've been looking at how to add a HTML5 serializer to the project.
So far my investigations have led to add following code to
org.apache.cocoon.sax.component.XMLSerializer
public static XMLSerializer createHTML5Serializer() {
Hi Sylvain,
Thx for the pointer.
Using the same test but with some changes to the html5serializer
public static XMLSerializer createHTML5Serializer() {
XMLSerializer serializer = new XMLSerializer();
serializer.setContentType(TEXT_HTML_UTF_8);
27 matches
Mail list logo
