Hi Kyle,
thanks for your replay.
The compilation error was not fixed, even entering the command mvn clean -U
-Prelease package.
I noticed that inside my ~/.m2/repository/com/lowagie/itext/4.2.1 there
isn't the itext-4.2.1.jar file, even using the commands mvn clean -U
-Prelease package, mvn -U -Prelease package, etc;
Visiting the page http://mvnrepository.com/artifact/com.lowagie/itext/4.2.1
we can notice that the artifact was moved to a new group.
So, I will download a package from gbif build repository for our purpose.
If possible, I would ask you to let me know when the source from github are
ready to build.
Br,
Francisco Moura
+55 (31) 8277-8448 (Claro)
2015-08-26 5:45 GMT-03:00 Kyle Braak <kbraak(a)gbif.org>:
> Hi Francisco,
>
> I noticed this error myself when testing an upgrade to a newer version of
> the com.lowagie:itext dependency.
>
> Why don’t you try the command below including -U to tell Maven to use the
> latest dependency versions.
>
> #mvn clean -U -Prelease package
>
> Below are my Maven, Java, and OS versions I am using in case that helps
> you:
>
> dhcp-12:ipt kbraak$ mvn --version
> Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4;
> 2014-08-11T22:58:10+02:00)
> Java version: 1.8.0_45, vendor: Oracle Corporation
> OS name: "mac os x", version: "10.9.5", arch: "x86_64", family: “mac"
>
> Let me know if you have success or not,
>
> Kyle
>
> PS1: You can monitor whether the IPT will build successfully from source
> here: http://builds.gbif.org/job/ipt/ If the last build was ‘blue’ it
> will build successfully :)
>
> PS2: The IPT mailing list (http://lists.gbif.org/mailman/listinfo/ipt) is
> ideal for these types of questions. That way your question reaches a
> broader audience around the world, and you have a better chance of getting
> a response when the GBIF Secretariat is out of office
>
> On 26 Aug 2015, at 05:56, Francisco Moura <franciscomoura(a)gmail.com>
> wrote:
>
> > Hi Kyle, I hope you are doing well!
> >
> > I need to build IPT from source. So, my environment setup is:
> > - Oracle JDK 7 and 8
> > - Maven 3.3.3
> >
> > When I try to build the application, a lot of errors are showed.
> > The output process is inside the attached file.
> >
> > I had cloned the source from github.com/gbif/ipt, and I issued the mvn
> install command and the build failed.
> >
> > My questions are:
> > 1) The source from github are ready to do the IPT build?
> > 2) Which is the correct environment setup to build the IPT with success
> from source?
> >
> > Thanks for your attention.
> >
> > Best regards,
> >
> > Francisco Moura
> > +55 (31) 8277-8448 (Claro)
> > <build-error.txt>
>
>
Dear IPT users,
A release candidate of IPT v2.3 is now available for download [1]. Please note this release is only intended for testing, and should not be installed in production. If you don’t have time to install it, you can always try it out at http://ipt.gbif-uat.org/ [2] (just email me if you want an account).
Its most notable enhancements include:
Support for publishing sample-based datasets, incorporating all the changes now in the prototype at the EU BON IPT [3]
Support for versionable IPT extensions, making it possible to update to newer versions whenever they become available
A slightly redesigned mapping page, making it easier to map your source data
If no major problems are uncovered during testing, IPT v2.3 will be released next week. In the meantime, volunteer translators are hard at work, and the user manual is being updated.
Thank you for your attention and help,
Kyle, on behalf of the IPT development team and the GBIF Secretariat
[1] https://dl.dropboxusercontent.com/u/4552753/ipt-2.3-rc1.war
[2] http://ipt.gbif-uat.org/
[3] http://eubon-ipt.gbif.org/
Hi,
I have just installed an instance of IPT 2.3RC on my Mac OS X laptop
using Tomcat 7 (manually installed).
It's working perfectly fine as long as I access it on the local machine,
using localhost URLs. I'd like to make it accessible from other hosts on
the local network (to be used as a test server during GB22 training
events in Antananarivo).
It seems the (generated) URLs for IPT static assets (CSS, JS, ...)
always start with "http://localhost:8080", even when the page is
requested from a different URL such as
http://10.209.1.58:8080/ipt-2.3-rc1 . So from another machine, I can get
the basic page, but with 404 errors on all static files.
I feel this is maybe related to https://github.com/gbif/ipt/issues/817,
and comes from the fact that the IPT doesn't use the queried URL as a
base for generating other URLs. Is there an easy way for me to
circumvent this problem? Should I put a reverse proxy in front of Tomcat
? Any sample, working configuration for that ?
Thanks,
Nicolas
