jira-issues-migration issueshttps://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues2018-03-02T15:51:34Zhttps://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/1615Improve services logging messages and levels2018-03-02T15:51:34Zkevin desir kevin desirImprove services logging messages and levelshttps://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/1584Poppler does not remove temporary content2018-01-12T18:10:08Zkevin desir kevin desirPoppler does not remove temporary contentwhen it fails for example, but not only, poppler does not remove temporary content created under temp folderwhen it fails for example, but not only, poppler does not remove temporary content created under temp folderhttps://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/1503Create parents 1.2.8.1 with a fix enabling deployment using sftp2017-10-24T14:17:02ZYann MombrunCreate parents 1.2.8.1 with a fix enabling deployment using sftpIt seem that it not possible anymore to deploy using scp on WebLab-project.org.
However, sftp works.
It would be good to update the parent to re-enable deployment.
Moreover, the use of build-helper plugin ease the deployment of associa...It seem that it not possible anymore to deploy using scp on WebLab-project.org.
However, sftp works.
It would be good to update the parent to re-enable deployment.
Moreover, the use of build-helper plugin ease the deployment of associated jar with war project. It would be good to add that in the profile instead of previous profilehttps://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/1456Use an external solr instance (not tomcat embedded) + increase to latest solr...2017-10-24T14:17:42ZLaurent MartinUse an external solr instance (not tomcat embedded) + increase to latest solr version (6.0.0)BUNDLE-2.1.0https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/1378Release core, helpers, services and bundle2017-06-23T13:55:33ZYann MombrunRelease core, helpers, services and bundleThe core in 1.2.8 can be released and should be used in bundle 2.0.3 that need to be released too.
All the services/Components/portlets involved in that bundle should be released prior to the bundle test.The core in 1.2.8 can be released and should be used in bundle 2.0.3 that need to be released too.
All the services/Components/portlets involved in that bundle should be released prior to the bundle test.BUNDLE-2.0.3https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/1364Remove open-search-connector from the trunk2017-10-24T14:16:53ZYann MombrunRemove open-search-connector from the trunkThis component has a stable tagged version.
But it is not used so instead of letting it an out-dated version on the trunk, remove it.This component has a stable tagged version.
But it is not used so instead of letting it an out-dated version on the trunk, remove it.https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/1356Update services to uses latest core and components 2016-10-19T16:09:48ZYann MombrunUpdate services to uses latest core and components WebLab Core 1.2.8https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/1224Jar are not deployed on OW2 for projects that inherit from the defined profile2016-10-19T16:09:50ZYann MombrunJar are not deployed on OW2 for projects that inherit from the defined profileI tried for Open AXES to extend the simple file repository using a proper jar dependency instead of deprecated warpath.
A few months ago Laurent and I introduced a profile in service/components parent in charge of producing a jar aside e...I tried for Open AXES to extend the simple file repository using a proper jar dependency instead of deprecated warpath.
A few months ago Laurent and I introduced a profile in service/components parent in charge of producing a jar aside each webapps to ease their overriding.
It was working correctly. However, I suppose that this kind or tricky configuration is dependent on the Maven version in use.
I reported months ago a problem that appeared for gate-extraction (#1179) were the jar was deployed but the linked pom was a generated empty one.
I figure out that for other services that relies on the same parent decribing that profile (i.e. ngramj, geonames and simple file repo) that problem 1179 does not appear anymore. But instead the jar is not deployed at all; thus I cannot dependent on it.
WebLab Core 1.2.8https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/1179Profiles that generates jar associated with war introduces empty POM2017-10-24T14:17:03ZYann MombrunProfiles that generates jar associated with war introduces empty POMThe profile that has been introduced a few months ago in order to generate a jar associated with each war (to ease overriding) is a good thing.
However, it seems that it introduces false pom files on Maven repositories.
For instance the ...The profile that has been introduced a few months ago in order to generate a jar associated with each war (to ease overriding) is a good thing.
However, it seems that it introduces false pom files on Maven repositories.
For instance the included pom file has been gathered on our Maven repository : http://maven-snapshot.weblab-project.org/org/ow2/weblab/webservices/gate-extraction/2.5.0-SNAPSHOT/gate-extraction-2.5.0-SNAPSHOT.pom
As you can seen it is an empty pom. We have missed all the dependencies. As a result, the service cannot be overridden (it does not compile since dependencies are missing).https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/1126WebLab web service cannot compile2017-10-24T14:16:52ZTan Yee fanWebLab web service cannot compileWhen the $HOME/.m2/repositories directory does not exist, compilation of any WebLab web service will fail. Error message from "mvn clean package" is:
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The projec...When the $HOME/.m2/repositories directory does not exist, compilation of any WebLab web service will fail. Error message from "mvn clean package" is:
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project com.kaisquare.ssipo.osia.weblab.service:AuthorFilter:1.0 (/Users/yeefan/WebLab/services/Dummy/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Could not find artifact org.ow2.weblab.webservices:parent:pom:1.2.5 in WebLab OW2 (http://maven.ow2.org/maven2/) and 'parent.relativePath' points at wrong local POM @ line 5, column 10 -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[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/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
My pom.xml contained the following:
<parent>
<groupId>org.ow2.weblab.webservices</groupId>
<artifactId>parent</artifactId>
<version>1.2.5</version>
</parent>
...
<repositories>
<repository>
<id>WebLab OW2</id>
<name>WebLab OW2 Maven repository</name>
<url>http://maven.ow2.org/maven2/</url>
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>
</repositories>
Observation:
At some recent time any URL under http://maven.ow2.org/maven2/ gets redirected to http://repository.ow2.org/nexus/content/repositories/ow2-legacy/ . But under the new URL, the directory org/ow2/weblab/services/parent/1.2.5 does not exist, although this directory previously existed at the old URL.https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/1116Migrate to JDK 1.7 2017-10-24T14:16:54ZYann MombrunMigrate to JDK 1.7 It would be better to migrate to Java 1.7 at a time since JDK 1.6 updates are not public anymore
This will enable us to use "new" features provided by Oracle a few years ago.
On top of that the 1.6 JDK is not maintained any more...It would be better to migrate to Java 1.7 at a time since JDK 1.6 updates are not public anymore
This will enable us to use "new" features provided by Oracle a few years ago.
On top of that the 1.6 JDK is not maintained any more...https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/1076For web projects, build a jar behind war during maven install / deploy phases...2017-12-21T13:05:40ZLaurent MartinFor web projects, build a jar behind war during maven install / deploy phases so that project could be use as maven dependencyProper way to "inherite" a portlet / service will so be :
- to use maven overlay plugin to overwrite "static" files (jsp, js, css, resources, conf files...)
- to add "parent" project as dependency (jar) in case some java code need to be ...Proper way to "inherite" a portlet / service will so be :
- to use maven overlay plugin to overwrite "static" files (jsp, js, css, resources, conf files...)
- to add "parent" project as dependency (jar) in case some java code need to be inherited https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/1040"mvn test" for dummy Analyser web service fail2018-05-23T20:51:44ZTan Yee fan"mvn test" for dummy Analyser web service fail0. Start with empty local Maven repository (i.e., .m2/repositories deleted)
1. Create new Analyser web service: mvn weblab:generate ...
2. Modify process() method in generated web service code to return the input resource unchanged
3. Re...0. Start with empty local Maven repository (i.e., .m2/repositories deleted)
1. Create new Analyser web service: mvn weblab:generate ...
2. Modify process() method in generated web service code to return the input resource unchanged
3. Remove expected exception from generated testAnalyserMultiThread() test case.
4. Execute test case: mvn test
Result: testAnalyserMultiThread() test case failed. The org.ow2.weblab.core.helper.impl.JenaResourceStructureHelperExtended class could not be found.
Analysis: At some point of time, the generated test cases started to include a resource validator that I didn't see before. But in the rdf-helper-jena-structure package, some classes were removed when the version was upgraded from 1.4.0 to 1.4.1.
Workaround: Modify the pom.xml to force the version of rdf-helper-jena-structure to 1.4.0.
See attached files for details.https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/976Catalina.out file becomes huge 2017-10-24T14:16:58ZArnaud SavalCatalina.out file becomes huge When heavily used, by default, Tomcat and Liferay are logging in the catalina.out file. It becomes bigger and bigger over time.When heavily used, by default, Tomcat and Liferay are logging in the catalina.out file. It becomes bigger and bigger over time.https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/920Update pom parent with new libraries2017-10-24T14:16:53ZArnaud SavalUpdate pom parent with new librariesUpdate annotator to 1.2.6 version
Update weblab-client to 0.2.2 version
Update weblab-filter to 0.2.1 versionUpdate annotator to 1.2.6 version
Update weblab-client to 0.2.2 version
Update weblab-filter to 0.2.1 versionhttps://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/913Change the ResulSet description to ease its use.2017-10-24T14:16:55ZArnaud SavalChange the ResulSet description to ease its use.We must update the ResultSet description according to common proposal (
http://weblab-project.org/index.php?title=WebLab_Search#ResultSet ) to ease the integration with current and future functionalities.
We must update the ResultSet description according to common proposal (
http://weblab-project.org/index.php?title=WebLab_Search#ResultSet ) to ease the integration with current and future functionalities.
https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/837Add monitoring on services calls using JMX integration with CXF2015-10-02T14:20:08ZArnaud SavalAdd monitoring on services calls using JMX integration with CXFAdd metrics monitoring of CXF services calls through JMX, see [documentation|http://cxf.apache.org/docs/jmx-management.html#JMXManagement-Howtogetwebserviceperformancemetrics%28Request/Responsetime,numberofcalls,etc.%29?].Add metrics monitoring of CXF services calls through JMX, see [documentation|http://cxf.apache.org/docs/jmx-management.html#JMXManagement-Howtogetwebserviceperformancemetrics%28Request/Responsetime,numberofcalls,etc.%29?].WebLab Bundle 1.2.6https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/818DependencyManagement of service contains incompatible versions2017-10-24T14:16:52ZYann MombrunDependencyManagement of service contains incompatible versionsThe dependency management of WebLabServices parent fixes version 1.4.1 for the rdf-structure-helper and 1.0.0 for the resource validator but these version are not compatible between each other (#817). The dependency management of WebLabServices parent fixes version 1.4.1 for the rdf-structure-helper and 1.0.0 for the resource validator but these version are not compatible between each other (#817). https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/773Upgrade to CXF 2.6.32013-01-10T10:10:41ZArnaud SavalUpgrade to CXF 2.6.3Update to CXF 2.6.3
See https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12322964Update to CXF 2.6.3
See https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12322964WebLab Bundle 1.2.5https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/736Update parent dependency to CXF 2.6.22012-11-26T10:43:27ZYann MombrunUpdate parent dependency to CXF 2.6.2The last commit set up CXF 2.6.1 but since then a newer version 2.6.2 that only contains (a lot) of bug fixes has been release.
We should upgrade the dependencyMangement with this version.The last commit set up CXF 2.6.1 but since then a newer version 2.6.2 that only contains (a lot) of bug fixes has been release.
We should upgrade the dependencyMangement with this version.WebLab Bundle 1.2.5