Yes, it is Isis version 1.9.0 .
Yes, it worked adding dependency to my webapp dom file for bootstrap 3.3.5:
<dependency>
<groupId>org.webjars</groupId>
<artifactId>bootstrap</artifactId>
<version>3.3.4</version>
</dependency>
Now the bootlint error message is gone. Thank you!
Also tried using Isis 1.10.0, but seems like it is not there just yet, the
project's dom coundn’t find the wicked viewer with using that version. I will
look forward for it to be released.
Cesar.
-----Original Message-----
From: Martin Grigorov [mailto:[email protected]]
Sent: Tuesday, October 27, 2015 10:25 AM
To: users
Subject: Re: Booltint error
Hi,
Which version of Isis is this ? 1.9.0 ?
I think 1.10.0 (currently being voted) uses Bootstrap 3.3.5.
If upgrading to 1.10.0 is not an option for you then you can add a Maven
dependency for Bootstrap's WebJar version 3.3.5 to your webapp module.
See
https://github.com/l0rdn1kk0n/wicket-bootstrap/blob/master/bootstrap-core/pom.xml#L33-L36
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Tue, Oct 27, 2015 at 4:59 PM, Cesar Lugo <[email protected]>
wrote:
> Sure, it is the following, messages and copy of the screen showing the
> messages and the script:
>
>
>
> JQMIGRATE: Logging is active
>
> jquery-...4122.js (line 21)
>
> bootlint: W013 Bootstrap version might be outdated. Latest version is
> at least 3.3.4 ; saw what appears to be usage of Bootstrap 3.2.0
>
> bootlin...4122.js (line 11518)
>
> bootlint: For details, look up the lint problem IDs in the Bootlint wiki:
> https://github.com/twbs/bootlint/wiki
>
> bootlin...4122.js (line 11528)
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> -----Original Message-----
> From: Martin Grigorov [mailto:[email protected]]
> Sent: Tuesday, October 27, 2015 1:30 AM
> To: users
> Subject: Re: Booltint error
>
>
>
> Hi Cesar,
>
>
>
> Could you please paste the content of the JavaScript console?
>
>
>
> The Bootlint errors say that there is some misuse of Bootstrap's HTML
> and/or CSS. We just need to identify where it is.
>
>
>
> Martin Grigorov
>
> Wicket Training and Consulting
>
> https://twitter.com/mtgrigorov
>
>
>
> On Tue, Oct 27, 2015 at 2:24 AM, Cesar Lugo <[email protected]>
>
> wrote:
>
>
>
> > Hello.
>
> >
>
> >
>
> >
>
> > Last friday I started experienced an error in my Apache ISIS prototype:
>
> > every page I open issues the error "bootlint found errors in this
>
> > document, see the Javascript console for details". After trying
>
> > several options, I went back to a backup I have from earlier last
>
> > week, when this bootlint error was not present. After building and
>
> > running the backup repository, the bootlint error showed up again .
> > I
>
> > tried deleting the directories under local ~/.m2/repo/org/isisaddons/.
>
> > (all modules there) and re-building and re-running, and the bootlint
>
> > error message keeps showing. I also removed all isisaddons from my
> > pom
>
> > modules, leaving only gmap3 and fullcalendar2, and the bootlint
>
> > continues. I also monitored the browser's Javascript console, and
>
> > there are not any errors there, only 1 warning and 1 info.
>
> >
>
> >
>
> >
>
> > Any suggestions where should I be looking for?
>
> >
>
> >
>
> >
>
> > Thank you.
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> > ---
>
> > This email has been checked for viruses by Avast antivirus software.
>
> > https://www.avast.com/antivirus
>
> >
>
>
> ------------------------------
> [image: Avast logo] <https://www.avast.com/antivirus>
>
> This email has been checked for viruses by Avast antivirus software.
> www.avast.com <https://www.avast.com/antivirus>
>
>
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
