[JBoss JIRA] (RTGOV-432) RTGov samples not building due to maven parent dependencies
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-432?page=com.atlassian.jira.plugin.... ]
Gary Brown resolved RTGOV-432.
------------------------------
Resolution: Done
> RTGov samples not building due to maven parent dependencies
> ------------------------------------------------------------
>
> Key: RTGOV-432
> URL: https://issues.jboss.org/browse/RTGOV-432
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Affects Versions: 2.0.0.Final
> Reporter: ivan mckinley
> Assignee: Gary Brown
> Priority: Minor
>
> Building the sla quickstart under jbossas results in the following error message
> mvn jboss-as:deploy
> [INFO] Scanning for projects...
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR] The project org.overlord.rtgov.samples.jbossas:sla:2.0.0-SNAPSHOT (/Users/imckinle/jboss/Overlord/rtgov/samples/jbossas/sla/pom.xml) has 1 error
> [ERROR] Non-resolvable parent POM for org.overlord.rtgov.samples.jbossas:parent:2.0.0-SNAPSHOT: Could not find artifact org.jboss.integration-platform:jboss-integration-platform-parent:pom:6.0.0-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ org.overlord.rtgov.samples.jbossas:parent:2.0.0-SNAPSHOT, /Users/imckinle/jboss/Overlord/rtgov/samples/jbossas/pom.xml, line 15, 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
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (RTGOV-432) RTGov samples not building due to maven parent dependencies
by ivan mckinley (JIRA)
ivan mckinley created RTGOV-432:
-----------------------------------
Summary: RTGov samples not building due to maven parent dependencies
Key: RTGOV-432
URL: https://issues.jboss.org/browse/RTGOV-432
Project: RTGov (Run Time Governance)
Issue Type: Bug
Affects Versions: 2.0.0.Final
Reporter: ivan mckinley
Assignee: Gary Brown
Priority: Minor
Building the sla quickstart under jbossas results in the following error message
mvn jboss-as:deploy
[INFO] Scanning for projects...
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project org.overlord.rtgov.samples.jbossas:sla:2.0.0-SNAPSHOT (/Users/imckinle/jboss/Overlord/rtgov/samples/jbossas/sla/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM for org.overlord.rtgov.samples.jbossas:parent:2.0.0-SNAPSHOT: Could not find artifact org.jboss.integration-platform:jboss-integration-platform-parent:pom:6.0.0-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ org.overlord.rtgov.samples.jbossas:parent:2.0.0-SNAPSHOT, /Users/imckinle/jboss/Overlord/rtgov/samples/jbossas/pom.xml, line 15, 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
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (RTGOV-409) Focus service dependency graph on a particular service type
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-409?page=com.atlassian.jira.plugin.... ]
Gary Brown resolved RTGOV-409.
------------------------------
Resolution: Done
> Focus service dependency graph on a particular service type
> -----------------------------------------------------------
>
> Key: RTGOV-409
> URL: https://issues.jboss.org/browse/RTGOV-409
> Project: RTGov (Run Time Governance)
> Issue Type: Feature Request
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 2.0.0.Final
>
> Original Estimate: 3 days
> Remaining Estimate: 3 days
>
> Enable the service dependency graph to be focused on a particular service type. This should result in the generated graph only including service nodes that either directly call the focused service type, or that the service type directly calls.
> Indirect calling/called service nodes may be included at a later date.
> The focused service type should also be highlighted in some way.
> Due to the multiple inbound and outbound links from the focused service type, a different layout approach would be required.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (SRAMP-395) S-RAMP allows artifacts to be created with invalid characters in the Artifact Type
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-395?page=com.atlassian.jira.plugin.... ]
Eric Wittmann commented on SRAMP-395:
-------------------------------------
I added an isValid() method in the artifact type which gets called whenever an extended artifact type is being created. If the valid test fails then the artifact type cannot be created. This is very low level and should prevent this problem no matter where it comes from (UI, CLI, API, any other I).
> S-RAMP allows artifacts to be created with invalid characters in the Artifact Type
> ----------------------------------------------------------------------------------
>
> Key: SRAMP-395
> URL: https://issues.jboss.org/browse/SRAMP-395
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 0.4.0 - Tomcat Support
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Fix For: 0.5.0 - API Management
>
>
> There are two ways (I believe) that users can mistakenly create artifacts with an invalid artifact type. The first is via the CLI:
> {code}
> s-ramp:upload /path/to/file.ext "Invalid Type"
> s-ramp:create "Invalid Type" "Valid Artifact Name" "Description goes here."
> {code}
> The other is via the s-ramp UI's Import Artifact dialog. This dialog allows the user to type in any Artifact Type they want, which is an opportunity to mess it up.
> We need to make sure we have appropriate validation of any custom Artifact Type provided by the user on the server (probably in the REST layer).
> For bonus points we can add validation to the UI and CLI to prevent the request from even being made to the server unless it's valid.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (SRAMP-395) S-RAMP allows artifacts to be created with invalid characters in the Artifact Type
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-395?page=com.atlassian.jira.plugin.... ]
Eric Wittmann resolved SRAMP-395.
---------------------------------
Resolution: Done
> S-RAMP allows artifacts to be created with invalid characters in the Artifact Type
> ----------------------------------------------------------------------------------
>
> Key: SRAMP-395
> URL: https://issues.jboss.org/browse/SRAMP-395
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 0.4.0 - Tomcat Support
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Fix For: 0.5.0 - API Management
>
>
> There are two ways (I believe) that users can mistakenly create artifacts with an invalid artifact type. The first is via the CLI:
> {code}
> s-ramp:upload /path/to/file.ext "Invalid Type"
> s-ramp:create "Invalid Type" "Valid Artifact Name" "Description goes here."
> {code}
> The other is via the s-ramp UI's Import Artifact dialog. This dialog allows the user to type in any Artifact Type they want, which is an opportunity to mess it up.
> We need to make sure we have appropriate validation of any custom Artifact Type provided by the user on the server (probably in the REST layer).
> For bonus points we can add validation to the UI and CLI to prevent the request from even being made to the server unless it's valid.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months