[JBoss JIRA] (JBDS-3279) Screencasts: Maven
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-3279?page=com.atlassian.jira.plugin.... ]
Jeff MAURY updated JBDS-3279:
-----------------------------
Fix Version/s: LATER
(was: 10.x)
> Screencasts: Maven
> ------------------
>
> Key: JBDS-3279
> URL: https://issues.jboss.org/browse/JBDS-3279
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: documentation, maven, requirements
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Priority: Minor
> Fix For: LATER
>
>
> As a Java EE developer, new to using Eclipse + Maven, I need short, sub-6 minute screencasts of individual key Maven focused use cases, so that I can better understand how Maven is integrated into the Eclipse + Java EE development workflow.
> Use cases include:
> - creation of a new project and its pom.xml, with the pom.xml editor
> - dependencies adds/removes
> - Import maven projects - from a SVN or Git repo
> - multi-module maven projects
> - run on server
> - package vs install
> - update - the magic "update project" that helps get Eclipse and Maven back into agreement
> - adjust profiles - address the Arquillian profile
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-18678) Make dependencies to org.jboss.tools.usage optional
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18678?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-18678:
-------------------------------
Fix Version/s: 4.5.0.AM1
(was: 4.4.x)
> Make dependencies to org.jboss.tools.usage optional
> ---------------------------------------------------
>
> Key: JBIDE-18678
> URL: https://issues.jboss.org/browse/JBIDE-18678
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: browsersim, usage
> Affects Versions: 4.2.0.CR1
> Reporter: Kaloyan Raev
> Assignee: Jeff MAURY
> Fix For: 4.5.0.AM1
>
>
> I am interested in adopting the CordovaSim feature in our product. However, most of the browsersim bundles have a strong dependency to org.jboss.tools.usage bundle, which force a Usage Reporting popup on startup. I want to avoid this and have the org.jboss.tools.usage excluded from my build.
> Is it possible to make the dependencies to org.jboss.tools.usage optional?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-18565) Default generated entity is invalid
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18565?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-18565:
-------------------------------
Fix Version/s: 4.5.0.AM1
(was: 4.3.x)
> Default generated entity is invalid
> -----------------------------------
>
> Key: JBIDE-18565
> URL: https://issues.jboss.org/browse/JBIDE-18565
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: hibernate, upstream
> Reporter: Arun Gupta
> Assignee: Koen Aers
> Fix For: 4.5.0.AM1
>
>
> Code for a default generated JPA entity looks like:
> package org.svcc;
> import java.io.Serializable;
> import javax.persistence.*;
> /**
> * Entity implementation class for Entity: Student
> *
> */
> @Entity
> public class Student implements Serializable {
>
> private static final long serialVersionUID = 1L;
> public Student() {
> super();
> }
>
> }
> This is an invalid entity because each JPA entity must have a primary key.
> For a simpler OOTB experience, generate a default primary key.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-18565) Default generated entity is invalid
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18565?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-18565:
----------------------------------
Assignee: Koen Aers
> Default generated entity is invalid
> -----------------------------------
>
> Key: JBIDE-18565
> URL: https://issues.jboss.org/browse/JBIDE-18565
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: hibernate, upstream
> Reporter: Arun Gupta
> Assignee: Koen Aers
> Fix For: 4.5.0.AM1
>
>
> Code for a default generated JPA entity looks like:
> package org.svcc;
> import java.io.Serializable;
> import javax.persistence.*;
> /**
> * Entity implementation class for Entity: Student
> *
> */
> @Entity
> public class Student implements Serializable {
>
> private static final long serialVersionUID = 1L;
> public Student() {
> super();
> }
>
> }
> This is an invalid entity because each JPA entity must have a primary key.
> For a simpler OOTB experience, generate a default primary key.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-18534) [WATCHER] OpenShift wizard: Length of combo boxes selection space is reduced
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18534?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-18534:
-------------------------------
Fix Version/s: 4.5.0.AM1
(was: 4.4.x)
> [WATCHER] OpenShift wizard: Length of combo boxes selection space is reduced
> ----------------------------------------------------------------------------
>
> Key: JBIDE-18534
> URL: https://issues.jboss.org/browse/JBIDE-18534
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.2.0.CR2
> Reporter: Marián Labuda
> Priority: Minor
> Labels: application_wizard
> Fix For: 4.5.0.AM1
>
> Attachments: ccombo.png, combo.png, gimp-combo1.png, gimp-combo2.png, glade-combo.png, non-readonly-combo.png
>
>
> Selection of combo boxes in New application wizard has reduced area of selection. Size is reduced to the size of the longest selection. It should cover whole length of combo box.
> !combo.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-18525) Investigate how to do module deployment ordering properly with management api
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18525?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-18525:
-------------------------------
Fix Version/s: 4.5.0.AM1
(was: 4.4.x)
> Investigate how to do module deployment ordering properly with management api
> -----------------------------------------------------------------------------
>
> Key: JBIDE-18525
> URL: https://issues.jboss.org/browse/JBIDE-18525
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.2.0.CR2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.0.AM1
>
>
> This is a followup of JBIDE-18373 which was originally about deployment via management api not handling "mark as deployable" files properly. This was fixed, but there's still a problem of ordering. The use case here was a seam project deployed to EAP 6.3. There are three parts:
> 1. Seam project war
> 2. database driver jar
> 3. datasource xml
> When you click "Add and Remove..." on the server in server view, it will sometimes be deployed in the wrong order and fail to deploy.
> Specifically, when you click "Add All" in the dialog, it will not work, whereas if you click "Add" for each of the three resources, it will deploy alright.
> As Rob pointed out, it can get really tricky to guess the right ordering.
> See JBIDE-18373 for more details.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months