[JBoss JIRA] (ISPN-10384) Create dedicated maven-plugins repository
by Ryan Emerson (Jira)
Ryan Emerson created ISPN-10384:
-----------------------------------
Summary: Create dedicated maven-plugins repository
Key: ISPN-10384
URL: https://issues.jboss.org/browse/ISPN-10384
Project: Infinispan
Issue Type: Enhancement
Components: Build
Affects Versions: 10.0.0.Beta3
Reporter: Ryan Emerson
Assignee: Ryan Emerson
Fix For: 10.0.0.Beta4
In the main ISPN repo we have a plugins dir that contains our custom maven plugins used throughout our builds. Currently this dir contains the infinispan-defaults-maven-plugin for extracting code defaults to xsd and the protocol-parser-generator-maven-plugin for generating the hotrod parser.
We should create a new repository under the infinispan org, e.g. github.com/infinispan/maven-plugins, to contain all of our maven plugins that do not depend on ISPN code.
The infinispan-defaults-maven-plugin can't be moved as it depends on infinispan-commons.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (ISPN-10354) Remove jboss-marshalling dependency from core
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-10354?page=com.atlassian.jira.plugin... ]
Ryan Emerson updated ISPN-10354:
--------------------------------
Status: Open (was: New)
> Remove jboss-marshalling dependency from core
> ---------------------------------------------
>
> Key: ISPN-10354
> URL: https://issues.jboss.org/browse/ISPN-10354
> Project: Infinispan
> Issue Type: Sub-task
> Components: Core, Marshalling
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
>
> Currently the core module has a hard dependency on jboss-marshalling regardless of what user marshaller is used, therefore we should make the necessary abstractions to remove this. This work compliments ISPN-9263 as it should not be necessary to have a jboss-marshalling jar on the classpath when utilising protostream marshalling. Furthermore, jboss-marshalling is not compatible with Quarkus, therefore this step is required in order for Infinispan embedded to be readily consumed via a Quarkus extension.
> Removing jboss-marshalling will result in Serializable user types no longer being marshallable as default, therefore we should introduce a `infinispan-jboss-marshalling` jar that users can continue to utilise jboss-marshalling if they wish. Furthermore, it should also be possible for users to utilise {{JavaSerializationMarshaller}} as the configured user marshaller.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (ISPN-10354) Remove jboss-marshalling dependency from core
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-10354?page=com.atlassian.jira.plugin... ]
Ryan Emerson updated ISPN-10354:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/7118
> Remove jboss-marshalling dependency from core
> ---------------------------------------------
>
> Key: ISPN-10354
> URL: https://issues.jboss.org/browse/ISPN-10354
> Project: Infinispan
> Issue Type: Sub-task
> Components: Core, Marshalling
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
>
> Currently the core module has a hard dependency on jboss-marshalling regardless of what user marshaller is used, therefore we should make the necessary abstractions to remove this. This work compliments ISPN-9263 as it should not be necessary to have a jboss-marshalling jar on the classpath when utilising protostream marshalling. Furthermore, jboss-marshalling is not compatible with Quarkus, therefore this step is required in order for Infinispan embedded to be readily consumed via a Quarkus extension.
> Removing jboss-marshalling will result in Serializable user types no longer being marshallable as default, therefore we should introduce a `infinispan-jboss-marshalling` jar that users can continue to utilise jboss-marshalling if they wish. Furthermore, it should also be possible for users to utilise {{JavaSerializationMarshaller}} as the configured user marshaller.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (ISPN-10381) Anchor for Security Headings
by Gustavo Fernandes (Jira)
[ https://issues.jboss.org/browse/ISPN-10381?page=com.atlassian.jira.plugin... ]
Gustavo Fernandes updated ISPN-10381:
-------------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Anchor for Security Headings
> ----------------------------
>
> Key: ISPN-10381
> URL: https://issues.jboss.org/browse/ISPN-10381
> Project: Infinispan
> Issue Type: Enhancement
> Components: Documentation-Core
> Affects Versions: 10.0.0.Beta3, 9.4.15.Final
> Reporter: Donald Naro
> Assignee: Donald Naro
> Priority: Major
>
> Two headings with "Security". Only one has an anchor.
> Heading 1 in server_protocols_rest.adoc
> ===== Security
> Heading 2 in security.adoc
> [[security]]
> == Security
> Attempting to select Heading 2 in the generated docs redirects to Heading 1. Solution is to have unique anchors for both headings.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months