Version control and high granularity

classic Classic list List threaded Threaded
21 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Version control and high granularity

isedwards
Hello,

I asked the pycsw team about the questions below and they suggested that
geonetwork may support version history for metadata records.  I can't see
any evidence of this, is it something that geonetwork can support?

I'm interested in the following issues:
a) accessing change log (revision history) of metadata records - including
who made changes, date/time of modification etc.

b) high granularity of access control, e.g. anyone can edit DC fields in a
metadata record, but only designated people can edit the custom "approved"
or "authorized" fields in the same record.

c) can database migrations be managed for evolving the structure of
metadata records? (changes to database schema in repeatable and consistent
ways).

Many thanks

Ian
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
GeoNetwork-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
Reply | Threaded
Open this post in threaded view
|

Re: Version control and high granularity

Francois Prunayre
Hi,

2013/7/23 Ian Edwards <[hidden email]>:
> Hello,
>
> I asked the pycsw team about the questions below and they suggested that
> geonetwork may support version history for metadata records.  I can't see
> any evidence of this, is it something that geonetwork can support?
That may be of interest :
http://geonetwork-opensource.org/manuals/trunk/eng/users/managing_metadata/versioning/index.html

Cheers.

Francois


>
> I'm interested in the following issues:
> a) accessing change log (revision history) of metadata records - including
> who made changes, date/time of modification etc.
>
> b) high granularity of access control, e.g. anyone can edit DC fields in a
> metadata record, but only designated people can edit the custom "approved"
> or "authorized" fields in the same record.
>
> c) can database migrations be managed for evolving the structure of
> metadata records? (changes to database schema in repeatable and consistent
> ways).
>
> Many thanks
>
> Ian
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> GeoNetwork-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/geonetwork-users
> GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
GeoNetwork-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
Reply | Threaded
Open this post in threaded view
|

Re: Version control and high granularity

kristjan
In reply to this post by isedwards
Hello,
To answer your first issue:
Geonetwork user documentation
<http://geonetwork-opensource.org/manuals/2.10.0/eng/users/managing_metadata/versioning/index.html#looking-at-the-revision-history-using-viewvc-a-graphical-user-interface>suggests
using viewvc as a graphical user interface. GN does not support it on its
own.
You can use also svn command line or TortoiseSVN to access the local
repository. I just opened the \WEB-INF\data\data\metadata_subversion with
my TortoiseSVN and voila.

PS.
Our company has been developing additional features to geonetwork 2.8.0.
One being, for example, viewing revision log history.
Please find attached the screenshot of the GUI. We can share the source
code if you want. Also, is it possible to give back to community and commit
this as a new feature? I read the terms on how to become a commiter and it
seemed like very hard and long process. There is probably a way to give the
source to an existing commiter for commiting, right?


On Tue, Jul 23, 2013 at 5:08 AM, Ian Edwards <[hidden email]> wrote:

> Hello,
>
> I asked the pycsw team about the questions below and they suggested that
> geonetwork may support version history for metadata records.  I can't see
> any evidence of this, is it something that geonetwork can support?
>
> I'm interested in the following issues:
> a) accessing change log (revision history) of metadata records - including
> who made changes, date/time of modification etc.
>
> b) high granularity of access control, e.g. anyone can edit DC fields in a
> metadata record, but only designated people can edit the custom "approved"
> or "authorized" fields in the same record.
>
> c) can database migrations be managed for evolving the structure of
> metadata records? (changes to database schema in repeatable and consistent
> ways).
>
> Many thanks
>
> Ian
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> GeoNetwork-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/geonetwork-users
> GeoNetwork OpenSource is maintained at
> http://sourceforge.net/projects/geonetwork
>

------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
GeoNetwork-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

versionloggui.png (38K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Version control and high granularity

Francois Prunayre
Hi Kristjan

2013/7/24 Kristjan Roosild <[hidden email]>:

> Hello,
> To answer your first issue:
> Geonetwork user documentation
> <http://geonetwork-opensource.org/manuals/2.10.0/eng/users/managing_metadata/versioning/index.html#looking-at-the-revision-history-using-viewvc-a-graphical-user-interface>suggests
> using viewvc as a graphical user interface. GN does not support it on its
> own.
> You can use also svn command line or TortoiseSVN to access the local
> repository. I just opened the \WEB-INF\data\data\metadata_subversion with
> my TortoiseSVN and voila.
>
> PS.
> Our company has been developing additional features to geonetwork 2.8.0.
> One being, for example, viewing revision log history.
Looks great !


> Please find attached the screenshot of the GUI. We can share the source
> code if you want. Also, is it possible to give back to community and commit
> this as a new feature?
Sure you can contribute !
The best way would be to create a fork off core-geonetwork on github,
add your feature in a new branch based on the develop branch and then
make a pull request (PR) eg. see previous PR[1].
Then committers could review it before adding it to GeoNetwork.


> I read the terms on how to become a commiter and it
> seemed like very hard and long process.
First contribute, and then it's not necessarily that hard.


> There is probably a way to give the
> source to an existing commiter for commiting, right?
Pull request is the easiest way to integrate new feature. If there is
any question ask the developer list.

Cheers.

Francois

[1] https://github.com/geonetwork/core-geonetwork/pulls?direction=desc&page=1&sort=created&state=closed


> On Tue, Jul 23, 2013 at 5:08 AM, Ian Edwards <[hidden email]> wrote:
>
>> Hello,
>>
>> I asked the pycsw team about the questions below and they suggested that
>> geonetwork may support version history for metadata records.  I can't see
>> any evidence of this, is it something that geonetwork can support?
>>
>> I'm interested in the following issues:
>> a) accessing change log (revision history) of metadata records - including
>> who made changes, date/time of modification etc.
>>
>> b) high granularity of access control, e.g. anyone can edit DC fields in a
>> metadata record, but only designated people can edit the custom "approved"
>> or "authorized" fields in the same record.
>>
>> c) can database migrations be managed for evolving the structure of
>> metadata records? (changes to database schema in repeatable and consistent
>> ways).
>>
>> Many thanks
>>
>> Ian
>>
>> ------------------------------------------------------------------------------
>> See everything from the browser to the database with AppDynamics
>> Get end-to-end visibility with application monitoring from AppDynamics
>> Isolate bottlenecks and diagnose root cause in seconds.
>> Start your free trial of AppDynamics Pro today!
>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> _______________________________________________
>> GeoNetwork-users mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/geonetwork-users
>> GeoNetwork OpenSource is maintained at
>> http://sourceforge.net/projects/geonetwork
>>
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> GeoNetwork-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/geonetwork-users
> GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
>

------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
GeoNetwork-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
Reply | Threaded
Open this post in threaded view
|

Re: Version control and high granularity

SimonPigot
In reply to this post by kristjan
Hi Kristjan,

I would be very interested in looking at your revision log history viewer for GeoNetwork 2.8.0 with the aim of including it in trunk. You could do this by generating a pull request in github (see https://help.github.com/articles/using-pull-requests) but I'd be happy to see and review it just as a plain old patch for 2.8.0.

I don't think that the process of becoming a GeoNetwork committer is any longer or harder than it is for any other open source project - contributions like this are certainly a good way to start down that path!

Cheers and thanks,
Simon
________________________________________
From: Kristjan Roosild [[hidden email]]
Sent: Wednesday, 24 July 2013 8:15 AM
To: Ian Edwards
Cc: [hidden email]
Subject: Re: [GeoNetwork-users] Version control and high granularity

Hello,
To answer your first issue:
Geonetwork user documentation
<http://geonetwork-opensource.org/manuals/2.10.0/eng/users/managing_metadata/versioning/index.html#looking-at-the-revision-history-using-viewvc-a-graphical-user-interface>suggests
using viewvc as a graphical user interface. GN does not support it on its
own.
You can use also svn command line or TortoiseSVN to access the local
repository. I just opened the \WEB-INF\data\data\metadata_subversion with
my TortoiseSVN and voila.

PS.
Our company has been developing additional features to geonetwork 2.8.0.
One being, for example, viewing revision log history.
Please find attached the screenshot of the GUI. We can share the source
code if you want. Also, is it possible to give back to community and commit
this as a new feature? I read the terms on how to become a commiter and it
seemed like very hard and long process. There is probably a way to give the
source to an existing commiter for commiting, right?


On Tue, Jul 23, 2013 at 5:08 AM, Ian Edwards <[hidden email]> wrote:

> Hello,
>
> I asked the pycsw team about the questions below and they suggested that
> geonetwork may support version history for metadata records.  I can't see
> any evidence of this, is it something that geonetwork can support?
>
> I'm interested in the following issues:
> a) accessing change log (revision history) of metadata records - including
> who made changes, date/time of modification etc.
>
> b) high granularity of access control, e.g. anyone can edit DC fields in a
> metadata record, but only designated people can edit the custom "approved"
> or "authorized" fields in the same record.
>
> c) can database migrations be managed for evolving the structure of
> metadata records? (changes to database schema in repeatable and consistent
> ways).
>
> Many thanks
>
> Ian
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> GeoNetwork-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/geonetwork-users
> GeoNetwork OpenSource is maintained at
> http://sourceforge.net/projects/geonetwork
>

------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
GeoNetwork-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
Reply | Threaded
Open this post in threaded view
|

Re: Version control and high granularity

kristjan
Hi Francois, Simon!

Yes, this pull request sounds perfect!

I thought becoming a commiter is the only way to contribute. I am new in
this, don't know all the terminology yet :)
We will plan the time for me to create the pull request or patch during our
next iteration meeting.

Thanks!
Kristjan



On Sun, Jul 28, 2013 at 7:42 PM, <[hidden email]> wrote:

> Hi Kristjan,
>
> I would be very interested in looking at your revision log history viewer
> for GeoNetwork 2.8.0 with the aim of including it in trunk. You could do
> this by generating a pull request in github (see
> https://help.github.com/articles/using-pull-requests) but I'd be happy to
> see and review it just as a plain old patch for 2.8.0.
>
> I don't think that the process of becoming a GeoNetwork committer is any
> longer or harder than it is for any other open source project -
> contributions like this are certainly a good way to start down that path!
>
> Cheers and thanks,
> Simon
> ________________________________________
> From: Kristjan Roosild [[hidden email]]
> Sent: Wednesday, 24 July 2013 8:15 AM
> To: Ian Edwards
> Cc: [hidden email]
> Subject: Re: [GeoNetwork-users] Version control and high granularity
>
> Hello,
> To answer your first issue:
> Geonetwork user documentation
> <
> http://geonetwork-opensource.org/manuals/2.10.0/eng/users/managing_metadata/versioning/index.html#looking-at-the-revision-history-using-viewvc-a-graphical-user-interface
> >suggests
> using viewvc as a graphical user interface. GN does not support it on its
> own.
> You can use also svn command line or TortoiseSVN to access the local
> repository. I just opened the \WEB-INF\data\data\metadata_subversion with
> my TortoiseSVN and voila.
>
> PS.
> Our company has been developing additional features to geonetwork 2.8.0.
> One being, for example, viewing revision log history.
> Please find attached the screenshot of the GUI. We can share the source
> code if you want. Also, is it possible to give back to community and commit
> this as a new feature? I read the terms on how to become a commiter and it
> seemed like very hard and long process. There is probably a way to give the
> source to an existing commiter for commiting, right?
>
>
> On Tue, Jul 23, 2013 at 5:08 AM, Ian Edwards <[hidden email]>
> wrote:
>
> > Hello,
> >
> > I asked the pycsw team about the questions below and they suggested that
> > geonetwork may support version history for metadata records.  I can't see
> > any evidence of this, is it something that geonetwork can support?
> >
> > I'm interested in the following issues:
> > a) accessing change log (revision history) of metadata records -
> including
> > who made changes, date/time of modification etc.
> >
> > b) high granularity of access control, e.g. anyone can edit DC fields in
> a
> > metadata record, but only designated people can edit the custom
> "approved"
> > or "authorized" fields in the same record.
> >
> > c) can database migrations be managed for evolving the structure of
> > metadata records? (changes to database schema in repeatable and
> consistent
> > ways).
> >
> > Many thanks
> >
> > Ian
> >
> >
> ------------------------------------------------------------------------------
> > See everything from the browser to the database with AppDynamics
> > Get end-to-end visibility with application monitoring from AppDynamics
> > Isolate bottlenecks and diagnose root cause in seconds.
> > Start your free trial of AppDynamics Pro today!
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> > _______________________________________________
> > GeoNetwork-users mailing list
> > [hidden email]
> > https://lists.sourceforge.net/lists/listinfo/geonetwork-users
> > GeoNetwork OpenSource is maintained at
> > http://sourceforge.net/projects/geonetwork
> >
>
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
GeoNetwork-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
Reply | Threaded
Open this post in threaded view
|

Re: Version control and high granularity

kristjan
In reply to this post by SimonPigot
Better late than never:
https://github.com/kristjanr/core-geonetwork/compare/geonetwork:2.8.x...MetadataVersioningLog

Still working on fixing an encoding bug where the title of the metadata is not read correctly when letters with diacritics etc is used....

Will create pull request after I get this fixed. I suppose Ill do the pull request to 2.8.x and develop branch.

PS. Should the datetime format and time stay server-dependent (show the same datetime that is in repository) or should I follow good practice and let the server always send out UTC and let the browser/JS do the conversion into clients locale?
Reply | Threaded
Open this post in threaded view
|

Re: Version control and high granularity

Carlos Toledo
Because it is a versioning control I think keep the server time it´s more
accurate. Any datatime filter query to the SVN should use the SVN host
server datetime reference, not the clients.

Carlos.


On Fri, Nov 8, 2013 at 9:09 PM, kristjan <[hidden email]> wrote:

> Better late than never:
>
> https://github.com/kristjanr/core-geonetwork/compare/geonetwork:2.8.x...MetadataVersioningLog
> <
> https://github.com/kristjanr/core-geonetwork/compare/geonetwork:2.8.x...MetadataVersioningLog
> >
>
> Still working on fixing an encoding bug where the title of the metadata is
> not read correctly when letters with diacritics etc is used....
>
> Will create pull request after I get this fixed. I suppose Ill do the pull
> request to 2.8.x and develop branch.
>
> PS. Should the datetime format and time stay server-dependent (show the
> same
> datetime that is in repository) or should I follow good practice and let
> the
> server always send out UTC and let the browser/JS do the conversion into
> clients locale?
>
>
>
>
> --
> View this message in context:
> http://osgeo-org.1560.x6.nabble.com/Version-control-and-high-granularity-tp5068139p5088295.html
> Sent from the GeoNetwork users mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> November Webinars for C, C++, Fortran Developers
> Accelerate application performance with scalable programming models.
> Explore
> techniques for threading, error checking, porting, and tuning. Get the most
> from the latest Intel processors and coprocessors. See abstracts and
> register
> http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
> _______________________________________________
> GeoNetwork-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/geonetwork-users
> GeoNetwork OpenSource is maintained at
> http://sourceforge.net/projects/geonetwork
>
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
GeoNetwork-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
Reply | Threaded
Open this post in threaded view
|

Re: Codelist url: hostname is enforced for each particular ISO19115 Profile? [SEC=UNCLASSIFIED]

kater2
In reply to this post by kristjan
Dear colleagues:

When editting using a profile (ANZLIC or MCP), GeoNetwork seems to enforce a particular base hostname, for all codelist urls.
For instance:
for MD_KeywordTypeCode, within a record copied from the ANZLIC Profile template, the codelist value* starts as http://asdd.ga.gov.au....
E.g.
<gmd:MD_KeywordTypeCode codeList="http://asdd.ga.gov.au/asdd/profileinfo/gmxCodelists.xml#MD_KeywordTypeCode" codeListValue="discipline"/>

And when I amend it, using the XML editor, to
 http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/gmxCodelists.xml#MD_KeywordTypeCode
and try to save it, the hostname is changed back to  http://asdd.ga.gov.au....
(Testing has been on some earlier GeoNetwork versions, and 2.10, using just the ANZLIC and MCP Profiles)

* And all the codelist values, in an ANZLIC Profile record, are made to have that hostname of
   http://asdd.ga.gov.au/asdd/profileinfo/gmxCodelists.xml#
When creating an MCP record, all codelist values are made to have a hostname of
   "http://bluenet3.antcrc.utas.edu.au/mcp-1.5-experimental/schema/resources/Codelist/gmxCodelists.xml#
 so MD_KeywordTypeCode is
<gmd:MD_KeywordTypeCode codeList="http://bluenet3.antcrc.utas.edu.au/mcp-1.5-experimental/schema/resources/Codelist/gmxCodelists.xml#MD_KeywordTypeCode" codeListValue="discipline"/>


Ideally  (unless there are standards/rules, or other good reasons against it), we would like to use the ISO codelist url
 [ http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/gmxCodelists.xml],
A) within profiles, for codelists that have not been altered within that profile.
B) within profiles, for codelists that HAVE been altered within that profile, but the term being used is in the original 19115 codelist.


That is:
if the MCP Profile extends the MD_KeywordTypeCode by adding the term "dataParam", then within one MCP record, when applying a KeywordTypeCode term that is in the original ISO19115 codelist (such as 'discipline' or 'place'), we'd like to use
<gmd:MD_KeywordTypeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/gmxCodelists.xml#MD_KeywordTypeCode" codeListValue="discipline"/>

But when using the MCP-introduced term of "dataParam", we would want to use:
<gmd:MD_KeywordTypeCode codeList="http://bluenet3.antcrc.utas.edu.au/mcp-1.5-experimental/schema/resources/Codelist/gmxCodelists.xml#MD_KeywordTypeCode" codeListValue="discipline"/>

If we have to regularly produce 3 Profile versions of a record (ANZLIC, MCP and WMO Profiles), it makes sense (and seems to be more interoperability-friendly) to only use a Profile-specific codelist url where the term being used is Profile-specific.


Is there is a rule, within ISO19139 or ISO19115, that says that the codelist [hostname] can be defined, and then must be consistent throughout the record.
(I haven't been able to find it, but others may know of a rule that justifies GeoNetwork's behaviour?)


Kate

------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
GeoNetwork-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
Reply | Threaded
Open this post in threaded view
|

Re: [GeoNetwork-devel] Codelist url: hostname is enforced for each particular ISO19115 Profile? [SEC=UNCLASSIFIED]

SimonPigot
Hi Kate,

This all takes place in update-fixed-info.xsl for the specific metadata schema/profile you are using.

You could customize this behaviour in that XSLT so that only extended elements are given the profile specific codelist and the rest are given the standard codelist URL. You could do this by adding a template to that XSLT that matches the particular codelist URL (or adding extra conditions to the generic template that handles all codelists) and apply the appropriate URL there. In fact I think there is an example update-fixed-info.xsl for iso19139.anzlic that does that for MD_ScopeCode.

I suspect it is mostly using just one codelist URL to cut down on the amount of code/maintenance and because the profile codelist URLs include all the standard codelist items anyway. This could be modified to work in the way you want.

Cheers,
Simon
________________________________________
From: Kate Roberts [[hidden email]]
Sent: Tuesday, 12 November 2013 12:12 PM
To: [hidden email]
Cc: Kate Roberts; [hidden email]
Subject: Re: [GeoNetwork-devel] [GeoNetwork-users] Codelist url: hostname is enforced for each particular ISO19115 Profile? [SEC=UNCLASSIFIED]

Dear colleagues:

When editting using a profile (ANZLIC or MCP), GeoNetwork seems to enforce a particular base hostname, for all codelist urls.
For instance:
for MD_KeywordTypeCode, within a record copied from the ANZLIC Profile template, the codelist value* starts as http://asdd.ga.gov.au....
E.g.
<gmd:MD_KeywordTypeCode codeList="http://asdd.ga.gov.au/asdd/profileinfo/gmxCodelists.xml#MD_KeywordTypeCode" codeListValue="discipline"/>

And when I amend it, using the XML editor, to
 http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/gmxCodelists.xml#MD_KeywordTypeCode
and try to save it, the hostname is changed back to  http://asdd.ga.gov.au....
(Testing has been on some earlier GeoNetwork versions, and 2.10, using just the ANZLIC and MCP Profiles)

* And all the codelist values, in an ANZLIC Profile record, are made to have that hostname of
   http://asdd.ga.gov.au/asdd/profileinfo/gmxCodelists.xml#
When creating an MCP record, all codelist values are made to have a hostname of
   "http://bluenet3.antcrc.utas.edu.au/mcp-1.5-experimental/schema/resources/Codelist/gmxCodelists.xml#
 so MD_KeywordTypeCode is
<gmd:MD_KeywordTypeCode codeList="http://bluenet3.antcrc.utas.edu.au/mcp-1.5-experimental/schema/resources/Codelist/gmxCodelists.xml#MD_KeywordTypeCode" codeListValue="discipline"/>


Ideally  (unless there are standards/rules, or other good reasons against it), we would like to use the ISO codelist url
 [ http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/gmxCodelists.xml],
A) within profiles, for codelists that have not been altered within that profile.
B) within profiles, for codelists that HAVE been altered within that profile, but the term being used is in the original 19115 codelist.


That is:
if the MCP Profile extends the MD_KeywordTypeCode by adding the term "dataParam", then within one MCP record, when applying a KeywordTypeCode term that is in the original ISO19115 codelist (such as 'discipline' or 'place'), we'd like to use
<gmd:MD_KeywordTypeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/gmxCodelists.xml#MD_KeywordTypeCode" codeListValue="discipline"/>

But when using the MCP-introduced term of "dataParam", we would want to use:
<gmd:MD_KeywordTypeCode codeList="http://bluenet3.antcrc.utas.edu.au/mcp-1.5-experimental/schema/resources/Codelist/gmxCodelists.xml#MD_KeywordTypeCode" codeListValue="discipline"/>

If we have to regularly produce 3 Profile versions of a record (ANZLIC, MCP and WMO Profiles), it makes sense (and seems to be more interoperability-friendly) to only use a Profile-specific codelist url where the term being used is Profile-specific.


Is there is a rule, within ISO19139 or ISO19115, that says that the codelist [hostname] can be defined, and then must be consistent throughout the record.
(I haven't been able to find it, but others may know of a rule that justifies GeoNetwork's behaviour?)


Kate

------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
GeoNetwork-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
GeoNetwork-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
Reply | Threaded
Open this post in threaded view
|

Re: [GeoNetwork-devel] Codelist url: hostname is enforced for each particular ISO19115 Profile? [SEC=UNCLASSIFIED]

kater2
Hi Simon,

Thanks for the quick reply, and for the advice.
I'll try that tonight.

As an aside, though, I am wondering what that means for my MCP record (once I've made the adjustment that you suggest), when it gets harvested into another instance of GeoNetwork, as an MCP record.  
Would it be rejected as "invalid"?  
Would it be converted, so that the URLS matched the "normal" MCP template?

As a failsafe, are these changes ones that would need to be done to the schema profile info that is (very usefully) rolled out as part of GN?
 
Kate

-----Original Message-----
From: [hidden email] [mailto:[hidden email]]
Sent: Tuesday, 12 November 2013 12:54 PM
To: Kate Roberts; [hidden email]
Cc: [hidden email]
Subject: RE: [GeoNetwork-devel] [GeoNetwork-users] Codelist url: hostname is enforced for each particular ISO19115 Profile? [SEC=UNCLASSIFIED]

Hi Kate,

This all takes place in update-fixed-info.xsl for the specific metadata schema/profile you are using.

You could customize this behaviour in that XSLT so that only extended elements are given the profile specific codelist and the rest are given the standard codelist URL. You could do this by adding a template to that XSLT that matches the particular codelist URL (or adding extra conditions to the generic template that handles all codelists) and apply the appropriate URL there. In fact I think there is an example update-fixed-info.xsl for iso19139.anzlic that does that for MD_ScopeCode.

I suspect it is mostly using just one codelist URL to cut down on the amount of code/maintenance and because the profile codelist URLs include all the standard codelist items anyway. This could be modified to work in the way you want.

Cheers,
Simon
________________________________________
From: Kate Roberts [[hidden email]]
Sent: Tuesday, 12 November 2013 12:12 PM
To: [hidden email]
Cc: Kate Roberts; [hidden email]
Subject: Re: [GeoNetwork-devel] [GeoNetwork-users] Codelist url: hostname is enforced for each particular ISO19115 Profile? [SEC=UNCLASSIFIED]

Dear colleagues:

When editting using a profile (ANZLIC or MCP), GeoNetwork seems to enforce a particular base hostname, for all codelist urls.
For instance:
for MD_KeywordTypeCode, within a record copied from the ANZLIC Profile template, the codelist value* starts as http://asdd.ga.gov.au....
E.g.
<gmd:MD_KeywordTypeCode codeList="http://asdd.ga.gov.au/asdd/profileinfo/gmxCodelists.xml#MD_KeywordTypeCode" codeListValue="discipline"/>

And when I amend it, using the XML editor, to  http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/gmxCodelists.xml#MD_KeywordTypeCode
and try to save it, the hostname is changed back to  http://asdd.ga.gov.au....
(Testing has been on some earlier GeoNetwork versions, and 2.10, using just the ANZLIC and MCP Profiles)

* And all the codelist values, in an ANZLIC Profile record, are made to have that hostname of
   http://asdd.ga.gov.au/asdd/profileinfo/gmxCodelists.xml#
When creating an MCP record, all codelist values are made to have a hostname of
   "http://bluenet3.antcrc.utas.edu.au/mcp-1.5-experimental/schema/resources/Codelist/gmxCodelists.xml#
 so MD_KeywordTypeCode is
<gmd:MD_KeywordTypeCode codeList="http://bluenet3.antcrc.utas.edu.au/mcp-1.5-experimental/schema/resources/Codelist/gmxCodelists.xml#MD_KeywordTypeCode" codeListValue="discipline"/>


Ideally  (unless there are standards/rules, or other good reasons against it), we would like to use the ISO codelist url  [ http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/gmxCodelists.xml],
A) within profiles, for codelists that have not been altered within that profile.
B) within profiles, for codelists that HAVE been altered within that profile, but the term being used is in the original 19115 codelist.


That is:
if the MCP Profile extends the MD_KeywordTypeCode by adding the term "dataParam", then within one MCP record, when applying a KeywordTypeCode term that is in the original ISO19115 codelist (such as 'discipline' or 'place'), we'd like to use <gmd:MD_KeywordTypeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/gmxCodelists.xml#MD_KeywordTypeCode" codeListValue="discipline"/>

But when using the MCP-introduced term of "dataParam", we would want to use:
<gmd:MD_KeywordTypeCode codeList="http://bluenet3.antcrc.utas.edu.au/mcp-1.5-experimental/schema/resources/Codelist/gmxCodelists.xml#MD_KeywordTypeCode" codeListValue="discipline"/>

If we have to regularly produce 3 Profile versions of a record (ANZLIC, MCP and WMO Profiles), it makes sense (and seems to be more interoperability-friendly) to only use a Profile-specific codelist url where the term being used is Profile-specific.


Is there is a rule, within ISO19139 or ISO19115, that says that the codelist [hostname] can be defined, and then must be consistent throughout the record.
(I haven't been able to find it, but others may know of a rule that justifies GeoNetwork's behaviour?)


Kate

------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
GeoNetwork-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
GeoNetwork-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
Reply | Threaded
Open this post in threaded view
|

Re: [GeoNetwork-devel] Codelist url: hostname is enforced for each particular ISO19115 Profile? [SEC=UNCLASSIFIED]

SimonPigot
Hi Kate,

Harvesting into another instance would not mean the record is invalid - the only place this would be checked is in the codelist schematron - it uses the URL provided to look up the codelist and check that the codelist value is actually in that codelist so as long as you supplied a valid URL it would be fine (many of these URLs can be mapped to local files if required as well).

The codelist URL wouldn't be changed unless the record was edited - usually shouldn't happen with harvested records.

Cheers,
Simon
________________________________________
From: Kate Roberts [[hidden email]]
Sent: Tuesday, 12 November 2013 1:10 PM
To: Pigot, Simon (CMAR, Hobart); [hidden email]
Cc: [hidden email]
Subject: RE: [GeoNetwork-devel] [GeoNetwork-users] Codelist url: hostname is enforced for each particular ISO19115 Profile? [SEC=UNCLASSIFIED]

Hi Simon,

Thanks for the quick reply, and for the advice.
I'll try that tonight.

As an aside, though, I am wondering what that means for my MCP record (once I've made the adjustment that you suggest), when it gets harvested into another instance of GeoNetwork, as an MCP record.
Would it be rejected as "invalid"?
Would it be converted, so that the URLS matched the "normal" MCP template?

As a failsafe, are these changes ones that would need to be done to the schema profile info that is (very usefully) rolled out as part of GN?

Kate

-----Original Message-----
From: [hidden email] [mailto:[hidden email]]
Sent: Tuesday, 12 November 2013 12:54 PM
To: Kate Roberts; [hidden email]
Cc: [hidden email]
Subject: RE: [GeoNetwork-devel] [GeoNetwork-users] Codelist url: hostname is enforced for each particular ISO19115 Profile? [SEC=UNCLASSIFIED]

Hi Kate,

This all takes place in update-fixed-info.xsl for the specific metadata schema/profile you are using.

You could customize this behaviour in that XSLT so that only extended elements are given the profile specific codelist and the rest are given the standard codelist URL. You could do this by adding a template to that XSLT that matches the particular codelist URL (or adding extra conditions to the generic template that handles all codelists) and apply the appropriate URL there. In fact I think there is an example update-fixed-info.xsl for iso19139.anzlic that does that for MD_ScopeCode.

I suspect it is mostly using just one codelist URL to cut down on the amount of code/maintenance and because the profile codelist URLs include all the standard codelist items anyway. This could be modified to work in the way you want.

Cheers,
Simon
________________________________________
From: Kate Roberts [[hidden email]]
Sent: Tuesday, 12 November 2013 12:12 PM
To: [hidden email]
Cc: Kate Roberts; [hidden email]
Subject: Re: [GeoNetwork-devel] [GeoNetwork-users] Codelist url: hostname is enforced for each particular ISO19115 Profile? [SEC=UNCLASSIFIED]

Dear colleagues:

When editting using a profile (ANZLIC or MCP), GeoNetwork seems to enforce a particular base hostname, for all codelist urls.
For instance:
for MD_KeywordTypeCode, within a record copied from the ANZLIC Profile template, the codelist value* starts as http://asdd.ga.gov.au....
E.g.
<gmd:MD_KeywordTypeCode codeList="http://asdd.ga.gov.au/asdd/profileinfo/gmxCodelists.xml#MD_KeywordTypeCode" codeListValue="discipline"/>

And when I amend it, using the XML editor, to  http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/gmxCodelists.xml#MD_KeywordTypeCode
and try to save it, the hostname is changed back to  http://asdd.ga.gov.au....
(Testing has been on some earlier GeoNetwork versions, and 2.10, using just the ANZLIC and MCP Profiles)

* And all the codelist values, in an ANZLIC Profile record, are made to have that hostname of
   http://asdd.ga.gov.au/asdd/profileinfo/gmxCodelists.xml#
When creating an MCP record, all codelist values are made to have a hostname of
   "http://bluenet3.antcrc.utas.edu.au/mcp-1.5-experimental/schema/resources/Codelist/gmxCodelists.xml#
 so MD_KeywordTypeCode is
<gmd:MD_KeywordTypeCode codeList="http://bluenet3.antcrc.utas.edu.au/mcp-1.5-experimental/schema/resources/Codelist/gmxCodelists.xml#MD_KeywordTypeCode" codeListValue="discipline"/>


Ideally  (unless there are standards/rules, or other good reasons against it), we would like to use the ISO codelist url  [ http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/gmxCodelists.xml],
A) within profiles, for codelists that have not been altered within that profile.
B) within profiles, for codelists that HAVE been altered within that profile, but the term being used is in the original 19115 codelist.


That is:
if the MCP Profile extends the MD_KeywordTypeCode by adding the term "dataParam", then within one MCP record, when applying a KeywordTypeCode term that is in the original ISO19115 codelist (such as 'discipline' or 'place'), we'd like to use <gmd:MD_KeywordTypeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/gmxCodelists.xml#MD_KeywordTypeCode" codeListValue="discipline"/>

But when using the MCP-introduced term of "dataParam", we would want to use:
<gmd:MD_KeywordTypeCode codeList="http://bluenet3.antcrc.utas.edu.au/mcp-1.5-experimental/schema/resources/Codelist/gmxCodelists.xml#MD_KeywordTypeCode" codeListValue="discipline"/>

If we have to regularly produce 3 Profile versions of a record (ANZLIC, MCP and WMO Profiles), it makes sense (and seems to be more interoperability-friendly) to only use a Profile-specific codelist url where the term being used is Profile-specific.


Is there is a rule, within ISO19139 or ISO19115, that says that the codelist [hostname] can be defined, and then must be consistent throughout the record.
(I haven't been able to find it, but others may know of a rule that justifies GeoNetwork's behaviour?)


Kate

------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
GeoNetwork-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
GeoNetwork-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
Reply | Threaded
Open this post in threaded view
|

Re: Version control and high granularity

Francois Prunayre
In reply to this post by kristjan
Thanks for your contribution. About the pull request you could probably
concentrate on making it for the develop branch only (because we'll
probably not have resources to make any other release in 2.8.x branch)

One minor comment about the service configuration:
<output sheet="xmlToJson.xsl"
in develop branch, this is not needed anymore because you can add
<serviceName>@json?<serviceParam> in URLs to convert the XML to JSON
response.

Cheers.

Francois


2013/11/9 kristjan <[hidden email]>
>
> Better late than never:
>
https://github.com/kristjanr/core-geonetwork/compare/geonetwork:2.8.x...MetadataVersioningLog
> <
https://github.com/kristjanr/core-geonetwork/compare/geonetwork:2.8.x...MetadataVersioningLog
>
>
> Still working on fixing an encoding bug where the title of the metadata is
> not read correctly when letters with diacritics etc is used....
>
> Will create pull request after I get this fixed. I suppose Ill do the pull
> request to 2.8.x and develop branch.
>
> PS. Should the datetime format and time stay server-dependent (show the
same
> datetime that is in repository) or should I follow good practice and let
the
> server always send out UTC and let the browser/JS do the conversion into
> clients locale?
>
>
>
>
> --
> View this message in context:
http://osgeo-org.1560.x6.nabble.com/Version-control-and-high-granularity-tp5068139p5088295.html
> Sent from the GeoNetwork users mailing list archive at Nabble.com.
>
>
------------------------------------------------------------------------------
> November Webinars for C, C++, Fortran Developers
> Accelerate application performance with scalable programming models.
Explore
> techniques for threading, error checking, porting, and tuning. Get the
most
> from the latest Intel processors and coprocessors. See abstracts and
register
>
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
> _______________________________________________
> GeoNetwork-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/geonetwork-users
> GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
GeoNetwork-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
Reply | Threaded
Open this post in threaded view
|

Re: Version control and high granularity

kristjan
I spent the whole day to build and run the develop branch with linux and windows....

 1) Windows: failure when building GeoNetwork user interface module:
[DEBUG] Executing command line: fixjsstyle --strict -r src/main/resources/catalog/js -r src/main/resources/catalog/components
Traceback (most recent call last):
  File "C:\Python33\Scripts\fixjsstyle-script.py", line 9, in <module>
    load_entry_point('closure-linter==2.3.12', 'console_scripts', 'fixjsstyle')()
  File "C:\Python33\lib\site-packages\setuptools-1.3.2-py3.3.egg\pkg_resources.py", line 357, in load_entry_point
  File "C:\Python33\lib\site-packages\setuptools-1.3.2-py3.3.egg\pkg_resources.py", line 2394, in load_entry_point
  File "C:\Python33\lib\site-packages\setuptools-1.3.2-py3.3.egg\pkg_resources.py", line 2108, in load
  File "<frozen importlib._bootstrap>", line 1567, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1534, in _find_and_load_unlocked
  File "C:\Python33\lib\site-packages\closure_linter-2.3.12-py3.3.egg\closure_linter\fixjsstyle.py", line 23, in <module>
  File "<frozen importlib._bootstrap>", line 1567, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1534, in _find_and_load_unlocked
  File "C:\Python33\lib\site-packages\python_gflags-2.0-py3.3.egg\gflags.py", line 1091
    except gflags_validators.Error, e:

version info:
Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 12:22:22-0300)
Maven home: C:\apache-maven-3.1.1
Java version: 1.6.0_29, vendor: Sun Microsystems Inc.
Java home: C:\Program Files\Java\jdk1.6.0_29\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows nt (unknown)", version: "6.2", arch: "amd64", family: "windows"
                                  ^
 2) Ubuntu-13.10-desktop-i386, Oracle Java1.6_29:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile (default-compile) on project services: Compilation failure
[ERROR] /home/kris/geonetwor/services/src/main/java/org/fao/geonet/services/statistics/RequestsByDate.java:[81,44] newBuilder() in com.google.common.cache.CacheBuilder cannot be applied to <java.lang.String,org.jdom.Element>()
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile (default-compile) on project services: Compilation failure
/home/kris/geonetwor/services/src/main/java/org/fao/geonet/services/statistics/RequestsByDate.java:[81,44] newBuilder() in com.google.common.cache.CacheBuilder cannot be applied to <java.lang.String,org.jdom.Element>()


        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure
/home/kris/geonetwor/services/src/main/java/org/fao/geonet/services/statistics/RequestsByDate.java:[81,44] newBuilder() in com.google.common.cache.CacheBuilder cannot be applied to <java.lang.String,org.jdom.Element>()


        at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:516)
        at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114)
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
        ... 19 more
[ERROR]
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

version info:
Apache Maven 3.0.4
Maven home: /usr/share/maven
Java version: 1.6.0_29, vendor: Sun Microsystems Inc.
Java home: /usr/lib/jvm/jdk1.6.0_29/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.11.0-13-generic", arch: "i386", family: "unix"

Should I stop banging my head on the wall and only do the pull request on some older version, that I am able to build and run or is there still a solution to this? The exact configuration of a working system would help, I guess... Which Linux, Java, maven, python etc is proven to be working (building and running the develop geonetwork )?

Thanks,
Kristjan
Reply | Threaded
Open this post in threaded view
|

Re: Version control and high granularity

Francois Prunayre
Hi


2013/11/13 kristjan <[hidden email]>

> I spent the whole day to build and run the develop branch with linux and
> windows....
>
> * 1) Windows: *failure when building GeoNetwork user interface module:
> [DEBUG] Executing command line: fixjsstyle --strict -r
> src/main/resources/catalog/js -r src/main/resources/catalog/components
> Traceback (most recent call last):
>   File "C:\Python33\Scripts\fixjsstyle-script.py", line 9, in <module>
>     load_entry_point('closure-linter==2.3.12', 'console_scripts',
> 'fixjsstyle')()
>   File
>
> "C:\Python33\lib\site-packages\setuptools-1.3.2-py3.3.egg\pkg_resources.py",
> line 357, in load_entry_point
>   File
>
> "C:\Python33\lib\site-packages\setuptools-1.3.2-py3.3.egg\pkg_resources.py",
> line 2394, in load_entry_point
>   File
>
> "C:\Python33\lib\site-packages\setuptools-1.3.2-py3.3.egg\pkg_resources.py",
> line 2108, in load
>   File "<frozen importlib._bootstrap>", line 1567, in _find_and_load
>   File "<frozen importlib._bootstrap>", line 1534, in
> _find_and_load_unlocked
>   File
>
> "C:\Python33\lib\site-packages\closure_linter-2.3.12-py3.3.egg\closure_linter\fixjsstyle.py",
> line 23, in <module>
>   File "<frozen importlib._bootstrap>", line 1567, in _find_and_load
>   File "<frozen importlib._bootstrap>", line 1534, in
> _find_and_load_unlocked
>   File
> "C:\Python33\lib\site-packages\python_gflags-2.0-py3.3.egg\gflags.py", line
> 1091
>     except gflags_validators.Error, e:
>

Not sure what this error is, but you could try to disable it for the time
being in
https://github.com/geonetwork/core-geonetwork/blob/develop/web-ui/pom.xml#L48


version info:

> Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17
> 12:22:22-0300)
> Maven home: C:\apache-maven-3.1.1
> Java version: 1.6.0_29, vendor: Sun Microsystems Inc.
> Java home: C:\Program Files\Java\jdk1.6.0_29\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows nt (unknown)", version: "6.2", arch: "amd64", family:
> "windows"
>                                   ^
> * 2) Ubuntu-13.10-desktop-i386, Oracle Java1.6_29:*
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile
> (default-compile) on project services: Compilation failure
> [ERROR]
>
> /home/kris/geonetwor/services/src/main/java/org/fao/geonet/services/statistics/RequestsByDate.java:[81,44]
> newBuilder() in com.google.common.cache.CacheBuilder cannot be applied to
> <java.lang.String,org.jdom.Element>()
> [ERROR] -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile
> (default-compile) on project services: Compilation failure
>
> /home/kris/geonetwor/services/src/main/java/org/fao/geonet/services/statistics/RequestsByDate.java:[81,44]
> newBuilder() in com.google.common.cache.CacheBuilder cannot be applied to
> <java.lang.String,org.jdom.Element>()
>
> No idea about this one. Maybe Jesse has an idea ?

Cheers.

Francois



>         at
>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
>         at
>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>         at
>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>         at
>
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>         at
>
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>         at
>
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>         at
>
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>         at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>         at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at
>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:597)
>         at
>
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>         at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>         at
>
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>         at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation
> failure
>
> /home/kris/geonetwor/services/src/main/java/org/fao/geonet/services/statistics/RequestsByDate.java:[81,44]
> newBuilder() in com.google.common.cache.CacheBuilder cannot be applied to
> <java.lang.String,org.jdom.Element>()
>
>
>         at
>
> org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:516)
>         at
> org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114)
>         at
>
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
>         at
>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>         ... 19 more
> [ERROR]
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>
> version info:
> Apache Maven 3.0.4
> Maven home: /usr/share/maven
> Java version: 1.6.0_29, vendor: Sun Microsystems Inc.
> Java home: /usr/lib/jvm/jdk1.6.0_29/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.11.0-13-generic", arch: "i386", family:
> "unix"
>
> Should I stop banging my head on the wall and only do the pull request on
> some older version, that I am able to build and run or is there still a
> solution to this? The exact configuration of a working system would help, I
> guess... Which Linux, Java, maven, python etc is proven to be working
> (building and running the develop geonetwork )?
>
> Thanks,
> Kristjan
>
>
>
>
> --
> View this message in context:
> http://osgeo-org.1560.x6.nabble.com/Version-control-and-high-granularity-tp5068139p5088886.html
> Sent from the GeoNetwork users mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
> OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
> Free app hosting. Or install the open source package on any LAMP server.
> Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
> http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
> _______________________________________________
> GeoNetwork-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/geonetwork-users
> GeoNetwork OpenSource is maintained at
> http://sourceforge.net/projects/geonetwork
>
------------------------------------------------------------------------------
DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
Free app hosting. Or install the open source package on any LAMP server.
Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
_______________________________________________
GeoNetwork-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
Reply | Threaded
Open this post in threaded view
|

Re: Version control and high granularity

Jose Garcia
Hi

In develop branch, check you have the requirements described in
https://github.com/geonetwork/core-geonetwork/wiki/Refactoring-Admin-console
.

I get it running in OSX, with this config, but at least last week had some
issues mostly due to tests failing (now should be fine):


   - Maven: 3.0.5
   - Java: Oracle JDK 1.7.0_45
   - Closure (as described in previous link)

Related to using develop branch, I would only use to test it or develop
features that you want to contribute for next version. If you want to
develop for a project that has to go to production, I would recommend to
use the actual stable branch: 2.10.X.

Possibly others disagree, but I don't like to be in the risky side for a
project. Develop branch is for development of next stable version and it's
unstable and can get big changes in newer revisions (like the spring jpa or
the new admin ui). Using it for a production project in my opinion is not a
good decision.


Regards,

Jose García








On Wed, Nov 13, 2013 at 7:44 AM, Francois Prunayre <[hidden email]>wrote:

> Hi
>
>
> 2013/11/13 kristjan <[hidden email]>
>
> > I spent the whole day to build and run the develop branch with linux and
> > windows....
> >
> > * 1) Windows: *failure when building GeoNetwork user interface module:
> > [DEBUG] Executing command line: fixjsstyle --strict -r
> > src/main/resources/catalog/js -r src/main/resources/catalog/components
> > Traceback (most recent call last):
> >   File "C:\Python33\Scripts\fixjsstyle-script.py", line 9, in <module>
> >     load_entry_point('closure-linter==2.3.12', 'console_scripts',
> > 'fixjsstyle')()
> >   File
> >
> >
> "C:\Python33\lib\site-packages\setuptools-1.3.2-py3.3.egg\pkg_resources.py",
> > line 357, in load_entry_point
> >   File
> >
> >
> "C:\Python33\lib\site-packages\setuptools-1.3.2-py3.3.egg\pkg_resources.py",
> > line 2394, in load_entry_point
> >   File
> >
> >
> "C:\Python33\lib\site-packages\setuptools-1.3.2-py3.3.egg\pkg_resources.py",
> > line 2108, in load
> >   File "<frozen importlib._bootstrap>", line 1567, in _find_and_load
> >   File "<frozen importlib._bootstrap>", line 1534, in
> > _find_and_load_unlocked
> >   File
> >
> >
> "C:\Python33\lib\site-packages\closure_linter-2.3.12-py3.3.egg\closure_linter\fixjsstyle.py",
> > line 23, in <module>
> >   File "<frozen importlib._bootstrap>", line 1567, in _find_and_load
> >   File "<frozen importlib._bootstrap>", line 1534, in
> > _find_and_load_unlocked
> >   File
> > "C:\Python33\lib\site-packages\python_gflags-2.0-py3.3.egg\gflags.py",
> line
> > 1091
> >     except gflags_validators.Error, e:
> >
>
> Not sure what this error is, but you could try to disable it for the time
> being in
>
> https://github.com/geonetwork/core-geonetwork/blob/develop/web-ui/pom.xml#L48
>
>
> version info:
> > Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17
> > 12:22:22-0300)
> > Maven home: C:\apache-maven-3.1.1
> > Java version: 1.6.0_29, vendor: Sun Microsystems Inc.
> > Java home: C:\Program Files\Java\jdk1.6.0_29\jre
> > Default locale: en_US, platform encoding: Cp1252
> > OS name: "windows nt (unknown)", version: "6.2", arch: "amd64", family:
> > "windows"
> >                                   ^
> > * 2) Ubuntu-13.10-desktop-i386, Oracle Java1.6_29:*
> >
> > [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile
> > (default-compile) on project services: Compilation failure
> > [ERROR]
> >
> >
> /home/kris/geonetwor/services/src/main/java/org/fao/geonet/services/statistics/RequestsByDate.java:[81,44]
> > newBuilder() in com.google.common.cache.CacheBuilder cannot be applied to
> > <java.lang.String,org.jdom.Element>()
> > [ERROR] -> [Help 1]
> > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> > goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile
> > (default-compile) on project services: Compilation failure
> >
> >
> /home/kris/geonetwor/services/src/main/java/org/fao/geonet/services/statistics/RequestsByDate.java:[81,44]
> > newBuilder() in com.google.common.cache.CacheBuilder cannot be applied to
> > <java.lang.String,org.jdom.Element>()
> >
> > No idea about this one. Maybe Jesse has an idea ?
>
> Cheers.
>
> Francois
>
>
>
> >         at
> >
> >
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> >         at
> >
> >
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> >         at
> >
> >
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> >         at
> >
> >
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> >         at
> >
> >
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> >         at
> >
> >
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> >         at
> >
> >
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> >         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> >         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> >         at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> >         at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> >         at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> >         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >         at
> >
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> >         at
> >
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> >         at java.lang.reflect.Method.invoke(Method.java:597)
> >         at
> >
> >
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> >         at
> >
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> >         at
> >
> >
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> >         at
> > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> > Caused by: org.apache.maven.plugin.CompilationFailureException:
> Compilation
> > failure
> >
> >
> /home/kris/geonetwor/services/src/main/java/org/fao/geonet/services/statistics/RequestsByDate.java:[81,44]
> > newBuilder() in com.google.common.cache.CacheBuilder cannot be applied to
> > <java.lang.String,org.jdom.Element>()
> >
> >
> >         at
> >
> >
> org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:516)
> >         at
> > org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114)
> >         at
> >
> >
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> >         at
> >
> >
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> >         ... 19 more
> > [ERROR]
> > [ERROR]
> > [ERROR] For more information about the errors and possible solutions,
> > please
> > read the following articles:
> > [ERROR] [Help 1]
> > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> >
> > version info:
> > Apache Maven 3.0.4
> > Maven home: /usr/share/maven
> > Java version: 1.6.0_29, vendor: Sun Microsystems Inc.
> > Java home: /usr/lib/jvm/jdk1.6.0_29/jre
> > Default locale: en_US, platform encoding: UTF-8
> > OS name: "linux", version: "3.11.0-13-generic", arch: "i386", family:
> > "unix"
> >
> > Should I stop banging my head on the wall and only do the pull request on
> > some older version, that I am able to build and run or is there still a
> > solution to this? The exact configuration of a working system would
> help, I
> > guess... Which Linux, Java, maven, python etc is proven to be working
> > (building and running the develop geonetwork )?
> >
> > Thanks,
> > Kristjan
> >
> >
> >
> >
> > --
> > View this message in context:
> >
> http://osgeo-org.1560.x6.nabble.com/Version-control-and-high-granularity-tp5068139p5088886.html
> > Sent from the GeoNetwork users mailing list archive at Nabble.com.
> >
> >
> >
> ------------------------------------------------------------------------------
> > DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
> > OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
> > Free app hosting. Or install the open source package on any LAMP server.
> > Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
> > _______________________________________________
> > GeoNetwork-users mailing list
> > [hidden email]
> > https://lists.sourceforge.net/lists/listinfo/geonetwork-users
> > GeoNetwork OpenSource is maintained at
> > http://sourceforge.net/projects/geonetwork
> >
>
> ------------------------------------------------------------------------------
> DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
> OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
> Free app hosting. Or install the open source package on any LAMP server.
> Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
> http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
> _______________________________________________
> GeoNetwork-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/geonetwork-users
> GeoNetwork OpenSource is maintained at
> http://sourceforge.net/projects/geonetwork
>



--

* GeoCat Bridge for ArcGIS allows instant publishing of data and metadata
on GeoServer and GeoNetwork. Visit http://geocat.net
<http://geocat.net/> for details.  _________________________Jose
GarcíaGeoCat bvVeenderweg 13 6721 WD BennekomThe
Netherlandshttp://GeoCat.net <http://geocat.net/> *
------------------------------------------------------------------------------
DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
Free app hosting. Or install the open source package on any LAMP server.
Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
_______________________________________________
GeoNetwork-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
Reply | Threaded
Open this post in threaded view
|

Re: Version control and high granularity

Jose Garcia
Hi

I miss to comment a issue that happens when starting up develop branch and
requires some manual fix for now: check
https://github.com/geonetwork/core-geonetwork/issues/186

Regards,
Jose García


On Wed, Nov 13, 2013 at 8:36 AM, Jose Garcia <[hidden email]> wrote:

> Hi
>
> In develop branch, check you have the requirements described in
> https://github.com/geonetwork/core-geonetwork/wiki/Refactoring-Admin-console
> .
>
> I get it running in OSX, with this config, but at least last week had some
> issues mostly due to tests failing (now should be fine):
>
>
>    - Maven: 3.0.5
>    - Java: Oracle JDK 1.7.0_45
>    - Closure (as described in previous link)
>
> Related to using develop branch, I would only use to test it or develop
> features that you want to contribute for next version. If you want to
> develop for a project that has to go to production, I would recommend to
> use the actual stable branch: 2.10.X.
>
> Possibly others disagree, but I don't like to be in the risky side for a
> project. Develop branch is for development of next stable version and it's
> unstable and can get big changes in newer revisions (like the spring jpa or
> the new admin ui). Using it for a production project in my opinion is not a
> good decision.
>
>
> Regards,
>
> Jose García
>
>
>
>
>
>
>
>
> On Wed, Nov 13, 2013 at 7:44 AM, Francois Prunayre <[hidden email]>wrote:
>
>> Hi
>>
>>
>> 2013/11/13 kristjan <[hidden email]>
>>
>> > I spent the whole day to build and run the develop branch with linux and
>> > windows....
>> >
>> > * 1) Windows: *failure when building GeoNetwork user interface module:
>> > [DEBUG] Executing command line: fixjsstyle --strict -r
>> > src/main/resources/catalog/js -r src/main/resources/catalog/components
>> > Traceback (most recent call last):
>> >   File "C:\Python33\Scripts\fixjsstyle-script.py", line 9, in <module>
>> >     load_entry_point('closure-linter==2.3.12', 'console_scripts',
>> > 'fixjsstyle')()
>> >   File
>> >
>> >
>> "C:\Python33\lib\site-packages\setuptools-1.3.2-py3.3.egg\pkg_resources.py",
>> > line 357, in load_entry_point
>> >   File
>> >
>> >
>> "C:\Python33\lib\site-packages\setuptools-1.3.2-py3.3.egg\pkg_resources.py",
>> > line 2394, in load_entry_point
>> >   File
>> >
>> >
>> "C:\Python33\lib\site-packages\setuptools-1.3.2-py3.3.egg\pkg_resources.py",
>> > line 2108, in load
>> >   File "<frozen importlib._bootstrap>", line 1567, in _find_and_load
>> >   File "<frozen importlib._bootstrap>", line 1534, in
>> > _find_and_load_unlocked
>> >   File
>> >
>> >
>> "C:\Python33\lib\site-packages\closure_linter-2.3.12-py3.3.egg\closure_linter\fixjsstyle.py",
>> > line 23, in <module>
>> >   File "<frozen importlib._bootstrap>", line 1567, in _find_and_load
>> >   File "<frozen importlib._bootstrap>", line 1534, in
>> > _find_and_load_unlocked
>> >   File
>> > "C:\Python33\lib\site-packages\python_gflags-2.0-py3.3.egg\gflags.py",
>> line
>> > 1091
>> >     except gflags_validators.Error, e:
>> >
>>
>> Not sure what this error is, but you could try to disable it for the time
>> being in
>>
>> https://github.com/geonetwork/core-geonetwork/blob/develop/web-ui/pom.xml#L48
>>
>>
>> version info:
>> > Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17
>> > 12:22:22-0300)
>> > Maven home: C:\apache-maven-3.1.1
>> > Java version: 1.6.0_29, vendor: Sun Microsystems Inc.
>> > Java home: C:\Program Files\Java\jdk1.6.0_29\jre
>> > Default locale: en_US, platform encoding: Cp1252
>> > OS name: "windows nt (unknown)", version: "6.2", arch: "amd64", family:
>> > "windows"
>> >                                   ^
>> > * 2) Ubuntu-13.10-desktop-i386, Oracle Java1.6_29:*
>> >
>> > [ERROR] Failed to execute goal
>> > org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile
>> > (default-compile) on project services: Compilation failure
>> > [ERROR]
>> >
>> >
>> /home/kris/geonetwor/services/src/main/java/org/fao/geonet/services/statistics/RequestsByDate.java:[81,44]
>> > newBuilder() in com.google.common.cache.CacheBuilder cannot be applied
>> to
>> > <java.lang.String,org.jdom.Element>()
>> > [ERROR] -> [Help 1]
>> > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>> execute
>> > goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile
>> > (default-compile) on project services: Compilation failure
>> >
>> >
>> /home/kris/geonetwor/services/src/main/java/org/fao/geonet/services/statistics/RequestsByDate.java:[81,44]
>> > newBuilder() in com.google.common.cache.CacheBuilder cannot be applied
>> to
>> > <java.lang.String,org.jdom.Element>()
>> >
>> > No idea about this one. Maybe Jesse has an idea ?
>>
>> Cheers.
>>
>> Francois
>>
>>
>>
>> >         at
>> >
>> >
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
>> >         at
>> >
>> >
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>> >         at
>> >
>> >
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>> >         at
>> >
>> >
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>> >         at
>> >
>> >
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>> >         at
>> >
>> >
>> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>> >         at
>> >
>> >
>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>> >         at
>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>> >         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>> >         at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>> >         at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>> >         at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>> >         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> >         at
>> >
>> >
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>> >         at
>> >
>> >
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> >         at java.lang.reflect.Method.invoke(Method.java:597)
>> >         at
>> >
>> >
>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>> >         at
>> >
>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>> >         at
>> >
>> >
>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>> >         at
>> >
>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
>> > Caused by: org.apache.maven.plugin.CompilationFailureException:
>> Compilation
>> > failure
>> >
>> >
>> /home/kris/geonetwor/services/src/main/java/org/fao/geonet/services/statistics/RequestsByDate.java:[81,44]
>> > newBuilder() in com.google.common.cache.CacheBuilder cannot be applied
>> to
>> > <java.lang.String,org.jdom.Element>()
>> >
>> >
>> >         at
>> >
>> >
>> org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:516)
>> >         at
>> > org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114)
>> >         at
>> >
>> >
>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
>> >         at
>> >
>> >
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>> >         ... 19 more
>> > [ERROR]
>> > [ERROR]
>> > [ERROR] For more information about the errors and possible solutions,
>> > please
>> > read the following articles:
>> > [ERROR] [Help 1]
>> > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>> >
>> > version info:
>> > Apache Maven 3.0.4
>> > Maven home: /usr/share/maven
>> > Java version: 1.6.0_29, vendor: Sun Microsystems Inc.
>> > Java home: /usr/lib/jvm/jdk1.6.0_29/jre
>> > Default locale: en_US, platform encoding: UTF-8
>> > OS name: "linux", version: "3.11.0-13-generic", arch: "i386", family:
>> > "unix"
>> >
>> > Should I stop banging my head on the wall and only do the pull request
>> on
>> > some older version, that I am able to build and run or is there still a
>> > solution to this? The exact configuration of a working system would
>> help, I
>> > guess... Which Linux, Java, maven, python etc is proven to be working
>> > (building and running the develop geonetwork )?
>> >
>> > Thanks,
>> > Kristjan
>> >
>> >
>> >
>> >
>> > --
>> > View this message in context:
>> >
>> http://osgeo-org.1560.x6.nabble.com/Version-control-and-high-granularity-tp5068139p5088886.html
>> > Sent from the GeoNetwork users mailing list archive at Nabble.com.
>> >
>> >
>> >
>> ------------------------------------------------------------------------------
>> > DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
>> > OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
>> > Free app hosting. Or install the open source package on any LAMP server.
>> > Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
>> >
>> http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
>> > _______________________________________________
>> > GeoNetwork-users mailing list
>> > [hidden email]
>> > https://lists.sourceforge.net/lists/listinfo/geonetwork-users
>> > GeoNetwork OpenSource is maintained at
>> > http://sourceforge.net/projects/geonetwork
>> >
>>
>> ------------------------------------------------------------------------------
>> DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
>> OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
>> Free app hosting. Or install the open source package on any LAMP server.
>> Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
>> _______________________________________________
>> GeoNetwork-users mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/geonetwork-users
>> GeoNetwork OpenSource is maintained at
>> http://sourceforge.net/projects/geonetwork
>>
>
>
>
> --
>
> * GeoCat Bridge for ArcGIS allows instant publishing of data and metadata
> on GeoServer and GeoNetwork. Visit http://geocat.net
> <http://geocat.net/> for details.  _________________________Jose
> GarcíaGeoCat bvVeenderweg 13 6721 WD BennekomThe
> Netherlandshttp://GeoCat.net <http://geocat.net/> *
>



--

* GeoCat Bridge for ArcGIS allows instant publishing of data and metadata
on GeoServer and GeoNetwork. Visit http://geocat.net
<http://geocat.net/> for details.  _________________________Jose
GarcíaGeoCat bvVeenderweg 13 6721 WD BennekomThe
Netherlandshttp://GeoCat.net <http://geocat.net/> *
------------------------------------------------------------------------------
DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
Free app hosting. Or install the open source package on any LAMP server.
Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
_______________________________________________
GeoNetwork-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
Reply | Threaded
Open this post in threaded view
|

Re: Version control and high granularity

kristjan
Thank you Jose and Francois!

Thanks to Francois I got the Closure working in windows also.

Then I arrived to the same problem that I already had in Linux:
newBuilder() in com.google.common.cache.CacheBuilder cannot be applied to java.lang.String,org.jdom.Element>()

After changing to JDK 1.7.0_45 as Jose has, I got a successful build on both Win and Linux!

The  JZKitConfig.xml.tem to JZKitConfig.xml workaround was nessessary also.
Reply | Threaded
Open this post in threaded view
|

Re: Version control and high granularity

kristjan
In reply to this post by Francois Prunayre
Here is PR for develop branch.

I could not figure out how to use the <serviceName>@json?<serviceParam> so still using <output sheet="xmlToJson.xsl"

I would like to do a PR for 2.10.x branch also, since it seems that in the develop branch only a small number of changes in SVN are tracked.
In develop there are only metadata addition and deletion.
In 2.10.x the changes in metadata, ownership, status, category are also tracked.
Reply | Threaded
Open this post in threaded view
|

Re: Version control and high granularity

kristjan
And here is the PR for 2.10.x branch

Let me know if something needs to be fixed, changed before accepting the pull request!

All the best!
Kristjan
12