[JBoss JIRA] (JBTIS-1042) Fix marketplace categories for devstudio integration stack
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1042?page=com.atlassian.jira.plugin... ]
Paul Leacu resolved JBTIS-1042.
-------------------------------
Resolution: Done
Finalized the Eclipse MarketPlace IS categories to:
Business Intelligence, Reporting and Charting
Database Development
SOA Development
Tools
Web Services
> Fix marketplace categories for devstudio integration stack
> ----------------------------------------------------------
>
> Key: JBTIS-1042
> URL: https://issues.jboss.org/browse/JBTIS-1042
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 10.0.0.GA
> Reporter: Nick Boldt
> Assignee: Paul Leacu
> Fix For: 10.1.0.GA
>
>
> After a recent change to the Eclipse Marketplace, we can only select up to 5 categories. This affects how we're discovered when someone searches for Marketplace listings.
> Here's what we currently use for JBoss Tools and devstudio:
> {code}Application Server
> Database Development
> Linux Tools
> Mobile and Device Development
> Web, XML, Java EE and OSGi Enterprise Development
> {code}
> And for Devstudio IS:
> {code}
> Database Development
> IDE
> SOA Development
> Tools{code}
> For Integration Stack, we could drop "IDE" and "Tools" and use instead:
> {code}
> Business Intelligence, Reporting and Charting
> Database Development
> Database Persistence
> SOA Development
> Web Services{code}
> What do you think?
> Here's the current full list of categories from which to choose:
> {code}Application Development Frameworks
> Application Management
> Application Server
> BIRT
> Build and Deploy
> Business Intelligence, Reporting and Charting
> Code Management
> Collaboration
> Database
> Database Development
> Database Persistence
> Documentation
> Eclipse Kura
> Eclipse SmartHome
> EclipseRT Target Platform Components
> Editor
> Entertainment
> General Purpose Tools
> Graphics
> IDE
> Internet of Things (IoT)
> J2EE Development Platform
> J2ME
> Languages
> Linux Tools
> Logging
> Mobile and Device Development
> Modeling
> Modeling Tools
> Mylyn Connectors
> Network
> Other
> Process
> Profiling
> Programming Languages
> Reporting
> Rich Client Applications
> SCM
> Search
> SOA Development
> Source Code Analyzer
> Systems Development
> Team Development
> Testing
> Tools
> UI
> UML
> Web
> Web Services
> Web, XML, Java EE and OSGi Enterprise Development
> XML{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBDS-3866) vagrant up failed due to rsync error, eclipse tooling confused about state of cdk server
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-3866?page=com.atlassian.jira.plugin.... ]
Jeff MAURY updated JBDS-3866:
-----------------------------
Fix Version/s: 10.4.0.AM1
(was: 10.3.0.AM2)
> vagrant up failed due to rsync error, eclipse tooling confused about state of cdk server
> ----------------------------------------------------------------------------------------
>
> Key: JBDS-3866
> URL: https://issues.jboss.org/browse/JBDS-3866
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 9.1.0.Beta1
> Environment: Windows 7/64 bit.
> (previous installs of CDK and dependencies)
> Reporter: Robert Terzi
> Assignee: Rob Stryker
> Fix For: 10.4.0.AM1
>
>
> vagrant up through the CDK server tooling failed because of an rsync problem. The tooling lost track of the state of the vagrant box. The vagrant box couldn't be stopped from inside of Eclipse.
> The vagrant up failed because of an error with rsync. Something was confused about the user's home directory. It was trying to write to /home/username/.ssh, however, $HOME isn't /home/username, it's /cygdrive/c/Users/username, so /home/username/ doesn't exist.
> The CDK server was shown as 'Started, Sychronized'.
> The error message appeared in the server console tab. However the stop button wouldn't work. Provisioning had never finished so the OpenShift connection wasn't working either.
> Synchronized seems misleading here, since no files had been sync'd yet.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBDS-2355) JEE web project example generates warnings
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-2355?page=com.atlassian.jira.plugin.... ]
Jeff MAURY updated JBDS-2355:
-----------------------------
Fix Version/s: 10.4.0.AM1
(was: 10.3.0.AM2)
> JEE web project example generates warnings
> ------------------------------------------
>
> Key: JBDS-2355
> URL: https://issues.jboss.org/browse/JBDS-2355
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central
> Affects Versions: 6.0.0.Alpha2
> Environment: Version: 6.0.0.Alpha2
> Build id: Alpha2-v20121004-2330-B40
> Build date: 20121004-2330
> Reporter: Len DiMaggio
> Assignee: Fred Bricon
> Labels: examplewarnings
> Fix For: 10.4.0.AM1
>
>
> The JEE web project example generates these warnings:
> The import java.util.logging.Logger is never used
> MemberController.java
> /jboss-javaee6-webapp/src/main/java/org/jboss/tools/examples/controller
> line 3
> No connection specified for project. No database-specific validation will be performed.
> jboss-javaee6-webapp
> Unnecessary @SuppressWarnings("unused") Resources.java
> /jboss-javaee6-webapp/src/main/java/org/jboss/tools/examples/util
> line 26
> The import javax.persistence.EntityManager is never used
> MemberController.java
> /jboss-javaee6-webapp/src/main/java/org/jboss/tools/examples/controller
> line 14
> The import javax.enterprise.event.Event is never used
> MemberController.java
> /jboss-javaee6-webapp/src/main/java/org/jboss/tools/examples/controller
> line 7
> The import javax.ejb.Stateful is never used
> MemberController.java
> /jboss-javaee6-webapp/src/main/java/org/jboss/tools/examples/controller
> line 6
> The import org.jboss.tools.examples.controller.MemberController is never used
> MemberRegistrationTest.java
> /jboss-javaee6-webapp/src/test/java/org/jboss/tools/examples/test
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month