[JBoss JIRA] (RTGOV-239) Documentation insufficient
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-239?page=com.atlassian.jira.plugin.... ]
Gary Brown resolved RTGOV-239.
------------------------------
Resolution: Done
Added auto generation of REST API documentation which is now included in the distribution along with javadocs.
Currently (see RTGV-508) the REST APIs don't provide as much typed info as would like, but hopefully that can be fixed shortly.
The query method is being deprecated as it exposes too much of the internal implementation being used for the activity store.
> Documentation insufficient
> --------------------------
>
> Key: RTGOV-239
> URL: https://issues.jboss.org/browse/RTGOV-239
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Documentation
> Environment: N/A
> Reporter: Cojan van Ballegooijen
> Assignee: Gary Brown
> Priority: Minor
> Fix For: 2.0.0.Final
>
>
> Documentation insufficient: for example the REST interface
> documentation is incomplete; for example paragraph 3.2.2 in the user
> guide; which formats are supported, which expressions are supported,
> what is the expression format, which objects can be used and how, etc?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months
[JBoss JIRA] (RTGOV-508) Test RTGov REST services with typed args/return values
by Gary Brown (JIRA)
Gary Brown created RTGOV-508:
--------------------------------
Summary: Test RTGov REST services with typed args/return values
Key: RTGOV-508
URL: https://issues.jboss.org/browse/RTGOV-508
Project: RTGov (Run Time Governance)
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 2.0.0.Final
When initially porting RTGov onto Karaf (RTGOV-373) we used the built in JAX-RS support provided by CXF. However the version of Karaf we needed to use, to support Fuse 6.1, had some issues with the typed signature.
The solution was to untyped the methods and just pass strings, and handle json marshalling in the REST service.
Now that REST API docs are being generated, this causes the problem that it does not document the true types being used.
We are now using RESTEasy to provide the JAX-RS services, so we need to retest with typed signatures in Karaf/Fuse, to see whether they now work. This will allow better API documentation to be automatically produced.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months
[JBoss JIRA] (SRAMP-482) Errors maven repository facade
by David virgil naranjo (JIRA)
[ https://issues.jboss.org/browse/SRAMP-482?page=com.atlassian.jira.plugin.... ]
David virgil naranjo commented on SRAMP-482:
--------------------------------------------
closed, because this work is related to an open issue not merged yet:
https://issues.jboss.org/browse/SRAMP-471
> Errors maven repository facade
> ------------------------------
>
> Key: SRAMP-482
> URL: https://issues.jboss.org/browse/SRAMP-482
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: David virgil naranjo
> Assignee: David virgil naranjo
>
> 1) the *.pom file is added with an artifact type of "Document" - it
> should be "MavenPom"
> 2) when uploading maven-metadata.xml the GAV properties are incorrect
> for the one in the parent folder (at least). For example, here is the
> s-ramp meta-data for maven-metadata.xml in the artifactId folder:
> maven.groupId: org.overlord
> maven.hash.sha1: 0e48bd3e6279b419c8d111763bfa88143fff9aff
> maven.artifactId: sramp
> maven.type: xml
> maven.hash.md5: 241a18e0cceb8dfc0ca01640dffc5db5
> maven.version: maven-facade-test-api
> These properties are incorrect (artifactId, groupId, and version are all
> wrong).
> 3) I don't see an option to disable/enable SNAPSHOT support in the
> facade. I think we need this option for this release and I think it
> should default to "disabled". In other words, let's turn off SNAPSHOT
> support by default. It should be controlled via a property in
> sramp.properties.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months
[JBoss JIRA] (SRAMP-482) Errors maven repository facade
by David virgil naranjo (JIRA)
[ https://issues.jboss.org/browse/SRAMP-482?page=com.atlassian.jira.plugin.... ]
David virgil naranjo closed SRAMP-482.
--------------------------------------
Resolution: Rejected
> Errors maven repository facade
> ------------------------------
>
> Key: SRAMP-482
> URL: https://issues.jboss.org/browse/SRAMP-482
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: David virgil naranjo
> Assignee: David virgil naranjo
>
> 1) the *.pom file is added with an artifact type of "Document" - it
> should be "MavenPom"
> 2) when uploading maven-metadata.xml the GAV properties are incorrect
> for the one in the parent folder (at least). For example, here is the
> s-ramp meta-data for maven-metadata.xml in the artifactId folder:
> maven.groupId: org.overlord
> maven.hash.sha1: 0e48bd3e6279b419c8d111763bfa88143fff9aff
> maven.artifactId: sramp
> maven.type: xml
> maven.hash.md5: 241a18e0cceb8dfc0ca01640dffc5db5
> maven.version: maven-facade-test-api
> These properties are incorrect (artifactId, groupId, and version are all
> wrong).
> 3) I don't see an option to disable/enable SNAPSHOT support in the
> facade. I think we need this option for this release and I think it
> should default to "disabled". In other words, let's turn off SNAPSHOT
> support by default. It should be controlled via a property in
> sramp.properties.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months
[JBoss JIRA] (SRAMP-482) Errors maven repository facade
by David virgil naranjo (JIRA)
[ https://issues.jboss.org/browse/SRAMP-482?page=com.atlassian.jira.plugin.... ]
David virgil naranjo updated SRAMP-482:
---------------------------------------
Description:
1) the *.pom file is added with an artifact type of "Document" - it
should be "MavenPom"
2) when uploading maven-metadata.xml the GAV properties are incorrect
for the one in the parent folder (at least). For example, here is the
s-ramp meta-data for maven-metadata.xml in the artifactId folder:
maven.groupId: org.overlord
maven.hash.sha1: 0e48bd3e6279b419c8d111763bfa88143fff9aff
maven.artifactId: sramp
maven.type: xml
maven.hash.md5: 241a18e0cceb8dfc0ca01640dffc5db5
maven.version: maven-facade-test-api
These properties are incorrect (artifactId, groupId, and version are all
wrong).
3) I don't see an option to disable/enable SNAPSHOT support in the
facade. I think we need this option for this release and I think it
should default to "disabled". In other words, let's turn off SNAPSHOT
support by default. It should be controlled via a property in
sramp.properties.
was:
ome issues I found in no particular order:
1) the *.pom file is added with an artifact type of "Document" - it
should be "MavenPom"
2) when uploading maven-metadata.xml the GAV properties are incorrect
for the one in the parent folder (at least). For example, here is the
s-ramp meta-data for maven-metadata.xml in the artifactId folder:
maven.groupId: org.overlord
maven.hash.sha1: 0e48bd3e6279b419c8d111763bfa88143fff9aff
maven.artifactId: sramp
maven.type: xml
maven.hash.md5: 241a18e0cceb8dfc0ca01640dffc5db5
maven.version: maven-facade-test-api
These properties are incorrect (artifactId, groupId, and version are all
wrong).
3) I don't see an option to disable/enable SNAPSHOT support in the
facade. I think we need this option for this release and I think it
should default to "disabled". In other words, let's turn off SNAPSHOT
support by default. It should be controlled via a property in
sramp.properties.
> Errors maven repository facade
> ------------------------------
>
> Key: SRAMP-482
> URL: https://issues.jboss.org/browse/SRAMP-482
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: David virgil naranjo
> Assignee: David virgil naranjo
>
> 1) the *.pom file is added with an artifact type of "Document" - it
> should be "MavenPom"
> 2) when uploading maven-metadata.xml the GAV properties are incorrect
> for the one in the parent folder (at least). For example, here is the
> s-ramp meta-data for maven-metadata.xml in the artifactId folder:
> maven.groupId: org.overlord
> maven.hash.sha1: 0e48bd3e6279b419c8d111763bfa88143fff9aff
> maven.artifactId: sramp
> maven.type: xml
> maven.hash.md5: 241a18e0cceb8dfc0ca01640dffc5db5
> maven.version: maven-facade-test-api
> These properties are incorrect (artifactId, groupId, and version are all
> wrong).
> 3) I don't see an option to disable/enable SNAPSHOT support in the
> facade. I think we need this option for this release and I think it
> should default to "disabled". In other words, let's turn off SNAPSHOT
> support by default. It should be controlled via a property in
> sramp.properties.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months
[JBoss JIRA] (SRAMP-482) Errors maven repository facade
by David virgil naranjo (JIRA)
David virgil naranjo created SRAMP-482:
------------------------------------------
Summary: Errors maven repository facade
Key: SRAMP-482
URL: https://issues.jboss.org/browse/SRAMP-482
Project: S-RAMP
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: David virgil naranjo
Assignee: David virgil naranjo
ome issues I found in no particular order:
1) the *.pom file is added with an artifact type of "Document" - it
should be "MavenPom"
2) when uploading maven-metadata.xml the GAV properties are incorrect
for the one in the parent folder (at least). For example, here is the
s-ramp meta-data for maven-metadata.xml in the artifactId folder:
maven.groupId: org.overlord
maven.hash.sha1: 0e48bd3e6279b419c8d111763bfa88143fff9aff
maven.artifactId: sramp
maven.type: xml
maven.hash.md5: 241a18e0cceb8dfc0ca01640dffc5db5
maven.version: maven-facade-test-api
These properties are incorrect (artifactId, groupId, and version are all
wrong).
3) I don't see an option to disable/enable SNAPSHOT support in the
facade. I think we need this option for this release and I think it
should default to "disabled". In other words, let's turn off SNAPSHOT
support by default. It should be controlled via a property in
sramp.properties.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months
[JBoss JIRA] (RTGOV-507) Deprecate activity server/store query method as dependent upon store impl
by Gary Brown (JIRA)
Gary Brown created RTGOV-507:
--------------------------------
Summary: Deprecate activity server/store query method as dependent upon store impl
Key: RTGOV-507
URL: https://issues.jboss.org/browse/RTGOV-507
Project: RTGov (Run Time Governance)
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 2.0.0.Final
The query method provides a QuerySpec instance that defined an expression and format - which exposes the store implementation.
Deprecate the query methods on the REST service, ActivityServer API and ActivityStore API, as well as the QuerySpec class.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months
[JBoss JIRA] (RTGOV-491) Performance tests
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-491?page=com.atlassian.jira.plugin.... ]
Gary Brown updated RTGOV-491:
-----------------------------
Fix Version/s: 2.1.0.Final
(was: 2.0.0.Final)
> Performance tests
> -----------------
>
> Key: RTGOV-491
> URL: https://issues.jboss.org/browse/RTGOV-491
> Project: RTGov (Run Time Governance)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 2.1.0.Final
>
>
> Currently old performance tests reside in release folder, which has almost completely been removed due to restructure in RTGOV-490.
> Need to decide whether still required/useful, and if so relocate. If no required, then should be removed.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months
[JBoss JIRA] (RTGOV-491) Performance tests
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-491?page=com.atlassian.jira.plugin.... ]
Gary Brown commented on RTGOV-491:
----------------------------------
Moved to more appropriate location under /tests but still not included in the build.
> Performance tests
> -----------------
>
> Key: RTGOV-491
> URL: https://issues.jboss.org/browse/RTGOV-491
> Project: RTGov (Run Time Governance)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 2.0.0.Final
>
>
> Currently old performance tests reside in release folder, which has almost completely been removed due to restructure in RTGOV-490.
> Need to decide whether still required/useful, and if so relocate. If no required, then should be removed.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months