[JBoss JIRA] (JBDS-4730) [Rebranding] Use "Red Hat CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text
by Bob Davis (Jira)
[ https://issues.jboss.org/browse/JBDS-4730?page=com.atlassian.jira.plugin.... ]
Bob Davis commented on JBDS-4730:
---------------------------------
Please loop me into the design discussions for logos/etc. on the CodeReady brand.
Thanks!
> [Rebranding] Use "Red Hat CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text
> ----------------------------------------------------------------------------------------------------
>
> Key: JBDS-4730
> URL: https://issues.jboss.org/browse/JBDS-4730
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: build, installer
> Affects Versions: 12.9.0.AM3
> Reporter: Nick Boldt
> Assignee: Catherine Robson
> Priority: Blocker
> Fix For: 12.11.0.AM1
>
>
> Branding has requested that we rename devstudio from "Red Hat Developer Studio" to "Red Hat CodeReady Studio".
> As we did recently in JBDS-4706, we'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/
> We'll need this rebrand done for the upcoming December release. All changes need to be done by November 6 so they can be included in the AM1 feature complete release on Nov 13, in support of the docs team, updating screenshots, install instructions, etc.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (JBDS-4741) As of Eclipse 4.10 all 32-bit libraries and plugins are being removed and are not supported anymore
by Nick Boldt (Jira)
[ https://issues.jboss.org/browse/JBDS-4741?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4741:
-----------------------------
Fix Version/s: 12.10.0.AM1
(was: 12.10.0.GA)
> As of Eclipse 4.10 all 32-bit libraries and plugins are being removed and are not supported anymore
> ---------------------------------------------------------------------------------------------------
>
> Key: JBDS-4741
> URL: https://issues.jboss.org/browse/JBDS-4741
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Epic
> Components: build
> Affects Versions: 12.10.0.AM1
> Environment: Windows, linux
> Reporter: Ondrej Dockal
> Priority: Critical
> Fix For: 12.10.0.AM1
>
>
> Eclipse is removing 32 bit arch. support in 4.10 release. In both project depending on eclipse platform (devstudio and jbosstools) we should make adjustments to this new setting and remove dependencies on 32 bit libraries/plugins.
> Also we will need to examine infrastructure and remove jenkins templates, label, images that were used to run any such CI aspects, adjust testing matricies, drop test case, etc. Not mentioning libraries used in script for 32 bit images provisioning and updating documentation.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (JBDS-4741) As of Eclipse 4.10 all 32-bit libraries and plugins are being removed and are not supported anymore
by Nick Boldt (Jira)
[ https://issues.jboss.org/browse/JBDS-4741?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4741:
-----------------------------
Affects Version/s: 12.10.0.AM1
(was: 12.10.0.GA)
> As of Eclipse 4.10 all 32-bit libraries and plugins are being removed and are not supported anymore
> ---------------------------------------------------------------------------------------------------
>
> Key: JBDS-4741
> URL: https://issues.jboss.org/browse/JBDS-4741
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Epic
> Components: build
> Affects Versions: 12.10.0.AM1
> Environment: Windows, linux
> Reporter: Ondrej Dockal
> Priority: Critical
> Fix For: 12.10.0.AM1
>
>
> Eclipse is removing 32 bit arch. support in 4.10 release. In both project depending on eclipse platform (devstudio and jbosstools) we should make adjustments to this new setting and remove dependencies on 32 bit libraries/plugins.
> Also we will need to examine infrastructure and remove jenkins templates, label, images that were used to run any such CI aspects, adjust testing matricies, drop test case, etc. Not mentioning libraries used in script for 32 bit images provisioning and updating documentation.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (JBDS-4745) Drools maven archetype or quickstart using kjar packaging doesn't build
by Mister PM (Jira)
[ https://issues.jboss.org/browse/JBDS-4745?page=com.atlassian.jira.plugin.... ]
Mister PM commented on JBDS-4745:
---------------------------------
Issue open against drools project
https://issues.jboss.org/browse/DROOLS-3370
> Drools maven archetype or quickstart using kjar packaging doesn't build
> -------------------------------------------------------------------------
>
> Key: JBDS-4745
> URL: https://issues.jboss.org/browse/JBDS-4745
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build
> Affects Versions: 12.9.0.GA
> Reporter: Mister PM
> Assignee: Jeff MAURY
> Priority: Minor
> Fix For: 12.x
>
> Attachments: pom.xml, pom.xml
>
>
> Any drools project which needs to use kie-maven-plugin to packing kjar maven project it's falling to build with the following error:
>
> An internal error occurred during: "Updating Maven Project".
> Missing parameter for pluginExecutionFilter. groupId, artifactId, versionRange and goals must be specificed, but found: groupId = 'org.kie'
> artifactId = 'kie-maven-plugin'
> versionRange = '7.13.0.Final'
> goals = '[]'
> You can create a maven project from the catalog archetype kie-drools-archetype, which will come with
> ...
> <packaging>kjar</packaging>
> ...
> ...
> <plugin>
> <groupId>org.kie</groupId>
> <artifactId>kie-maven-plugin</artifactId>
> <version>${drools-version}</version>
> <extensions>true</extensions>
> </plugin>
> I also added this part here in the pom file
> <pluginManagement>
> <plugins>
> <!--This plugin's configuration is used to store Eclipse m2e settings
> only. It has no influence on the Maven build itself. -->
> <plugin>
> <groupId>org.eclipse.m2e</groupId>
> <artifactId>lifecycle-mapping</artifactId>
> <version>1.0.0</version>
> <configuration>
> <lifecycleMappingMetadata>
> <pluginExecutions>
> <pluginExecution>
> <pluginExecutionFilter>
> <groupId>org.kie</groupId>
> <artifactId>kie-maven-plugin</artifactId>
> <versionRange>${drools-version}</versionRange>
> <goals>
> <goal>compile</goal>
> <goal>package</goal>
> <goal>build</goal>
> </goals>
> </pluginExecutionFilter>
> <action>
> <ignore />
> </action>
> </pluginExecution>
> </pluginExecutions>
> </lifecycleMappingMetadata>
> </configuration>
> </plugin>
> </plugins>
> </pluginManagement>
> Which was a workaround in previous drools version.
> However this didn't work either.
> I can build from the command line with or without the pluginManagement and I can build this archetype without issues in other IDE like IntelliJ
>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months