[JBoss JIRA] (JBIDE-18438) OpenShift: can complete New App Wizard without selecting gear profile
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18438?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-18438:
------------------------------------------
This is on purpose, this translates to "use whatever default there is for gear profiles"
> OpenShift: can complete New App Wizard without selecting gear profile
> ---------------------------------------------------------------------
>
> Key: JBIDE-18438
> URL: https://issues.jboss.org/browse/JBIDE-18438
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.CR1
> Reporter: Michelle Murray
> Priority: Minor
>
> In New OpenShift Application wizard, on page where select 'Gear Profile' - this field is initially blank and user can leave it blank and still successfully complete the wizard. So it works.
> But I don't think it is a good user experience. User should not be able to move to next page until there is a value in this field. Perhaps this field should have a value to start with instead of being blank based on the users account?
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18295) Errors in project after import WildFly quickstarts
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18295?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-18295:
---------------------------------------
Pr was merged and was pushed to update site.
> Errors in project after import WildFly quickstarts
> --------------------------------------------------
>
> Key: JBIDE-18295
> URL: https://issues.jboss.org/browse/JBIDE-18295
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, upstream
> Affects Versions: 4.2.0.Beta3
> Reporter: Xavier Coulon
> Assignee: Fred Bricon
> Priority: Critical
> Fix For: 4.2.0.CR2
>
>
> After importing all modules from https://github.com/wildfly/quickstart into JBDS 8.0.0.CR1b, a few projects have build errors, such as:
> {code}
> Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-dependency-plugin:2.1:copy (execution: default, phase: process-sources)
> {code}
> or
> {code}
> Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-ejb-plugin:2.3:ejb (execution: default, phase: package)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18295) Errors in project after import WildFly quickstarts
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18295?page=com.atlassian.jira.plugi... ]
Xavier Coulon edited comment on JBIDE-18295 at 9/25/14 10:35 AM:
-----------------------------------------------------------------
PR was merged and was pushed to update site.
was (Author: xcoulon):
Pr was merged and was pushed to update site.
> Errors in project after import WildFly quickstarts
> --------------------------------------------------
>
> Key: JBIDE-18295
> URL: https://issues.jboss.org/browse/JBIDE-18295
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, upstream
> Affects Versions: 4.2.0.Beta3
> Reporter: Xavier Coulon
> Assignee: Fred Bricon
> Priority: Critical
> Fix For: 4.2.0.CR2
>
>
> After importing all modules from https://github.com/wildfly/quickstart into JBDS 8.0.0.CR1b, a few projects have build errors, such as:
> {code}
> Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-dependency-plugin:2.1:copy (execution: default, phase: process-sources)
> {code}
> or
> {code}
> Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-ejb-plugin:2.3:ejb (execution: default, phase: package)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18239) Create new update site zip(s) (rather than target platform zip) for JBT content needed for Central/EA site
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18239?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-18239:
------------------------------------
Yes, but that's hardly the point here. The point is that you are either:
a) asking to include all the JBT stuff that's NOT in JBDS into the JBDS/JBDS TP/Central composite [1]
[1] https://devstudio.redhat.com/updates/8.0-staging/compositeContent.xml
or
b) asking for a new update site to include the stuff that's currently in Central/EA which comes from JBoss Tools and which is currently NOT part of JBDS.
Please stop talking about the semantics of composite sites. Can you focus on the title of this JIRA, which I opened based on YOUR request to have content from JBT split out of the target definitions?
> Create new update site zip(s) (rather than target platform zip) for JBT content needed for Central/EA site
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18239
> URL: https://issues.jboss.org/browse/JBIDE-18239
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, central, discovery, updatesite
> Affects Versions: 4.2.0.CR1
> Reporter: Nick Boldt
> Labels: f2f2014
> Fix For: 4.3.0.Alpha1
>
> Attachments: JBIDE18239-proposed.png
>
>
> In order to simplify the process for getting JBT features into Central (for JBDS) and EA (for both JBT/JBDS), it's been suggested (by [~maxandersen], who doesn't like opening JIRAs :D) that instead of a target platform which needs to be updated every time we spin or respin a build, we could instead just produce an update site containing the handful of IUs (cordovasim, arquillian, etc.).
> We could further extend this idea to include all the things that currently are in BOTH JBT or JBDS and in Central, such as TestNG.
> These would be produced as new zips using the JBT aggregate builder:
> https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregate/
> Need to decide what to call this... "Extras" "JBT-not-in-JBDS" "Shared" ...?
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18435) Validation errors in WildFly quickstarts
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18435?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-18435:
----------------------------------
Description:
when importing Wildfly quickstarts from https://github.com/wildfly/quickstart ({{master}} branch), there are some XML files on which some errors are reported by our tooling:
- {{ejb-multi-server/app-one/ejb/src/main/resources/META-INF/jboss-ejb3.xml}}
- {{ejb-multi-server/app-main/web/src/main/webapp/WEB-INF/faces-config.xml}}
- {{cdi-alternative/src/main/webapp/WEB-INF/beans.xml}}
- {{wsat-simple/src/main/webapp/WEB-INF/classes/context-handlers.xml}}
- {{wsat-simple/src/test/resources/context-handlers.xml}}
- {{wsba-coordinator-completion-simple/src/test/resources/context-handlers.xml}}
- {{wsba-participant-completion-simple/src/test/resources/context-handlers.xml}}
Also, a project had a bad packaging type: jts/application-component-2/pom.xml b/jts/application-component-2/pom.xml ({{jar}} instead of {{ejb}})
was:
when importing Wildfly quickstarts from https://github.com/wildfly/quickstart ({{master}} branch), there are some XML files on which some errors are reported by our tooling:
- {{ejb-multi-server/app-one/ejb/src/main/resources/META-INF/jboss-ejb3.xml}}
- {{ejb-multi-server/app-main/web/src/main/webapp/WEB-INF/faces-config.xml}}
- {{cdi-alternative/src/main/webapp/WEB-INF/beans.xml}}
- {{wsat-simple/src/main/webapp/WEB-INF/classes/context-handlers.xml}}
Also, a project had a bad packaging type: jts/application-component-2/pom.xml b/jts/application-component-2/pom.xml ({{jar}} instead of {{ejb}})
> Validation errors in WildFly quickstarts
> ----------------------------------------
>
> Key: JBIDE-18435
> URL: https://issues.jboss.org/browse/JBIDE-18435
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.2.0.CR1
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.2.0.CR2
>
>
> when importing Wildfly quickstarts from https://github.com/wildfly/quickstart ({{master}} branch), there are some XML files on which some errors are reported by our tooling:
> - {{ejb-multi-server/app-one/ejb/src/main/resources/META-INF/jboss-ejb3.xml}}
> - {{ejb-multi-server/app-main/web/src/main/webapp/WEB-INF/faces-config.xml}}
> - {{cdi-alternative/src/main/webapp/WEB-INF/beans.xml}}
> - {{wsat-simple/src/main/webapp/WEB-INF/classes/context-handlers.xml}}
> - {{wsat-simple/src/test/resources/context-handlers.xml}}
> - {{wsba-coordinator-completion-simple/src/test/resources/context-handlers.xml}}
> - {{wsba-participant-completion-simple/src/test/resources/context-handlers.xml}}
> Also, a project had a bad packaging type: jts/application-component-2/pom.xml b/jts/application-component-2/pom.xml ({{jar}} instead of {{ejb}})
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18239) Create new update site zip(s) (rather than target platform zip) for JBT content needed for Central/EA site
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18239?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18239:
---------------------------------------------
@nickboldt - central is not supposed to composite / anymore. discovery would point to / ...no on its own central site.
So the /central would not be the composite but / would be.
Right or?
> Create new update site zip(s) (rather than target platform zip) for JBT content needed for Central/EA site
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18239
> URL: https://issues.jboss.org/browse/JBIDE-18239
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, central, discovery, updatesite
> Affects Versions: 4.2.0.CR1
> Reporter: Nick Boldt
> Labels: f2f2014
> Fix For: 4.3.0.Alpha1
>
> Attachments: JBIDE18239-proposed.png
>
>
> In order to simplify the process for getting JBT features into Central (for JBDS) and EA (for both JBT/JBDS), it's been suggested (by [~maxandersen], who doesn't like opening JIRAs :D) that instead of a target platform which needs to be updated every time we spin or respin a build, we could instead just produce an update site containing the handful of IUs (cordovasim, arquillian, etc.).
> We could further extend this idea to include all the things that currently are in BOTH JBT or JBDS and in Central, such as TestNG.
> These would be produced as new zips using the JBT aggregate builder:
> https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregate/
> Need to decide what to call this... "Extras" "JBT-not-in-JBDS" "Shared" ...?
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18422) Include latest Tern & AngularJS 0.6.0.20140923161* into jbosstools/jbds TPs AND Early Access too
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18422?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-18422:
-----------------------------------------
It's a change in AngularJS only, so probably the only AngularJS-eclipse is to be updated
> Include latest Tern & AngularJS 0.6.0.20140923161* into jbosstools/jbds TPs AND Early Access too
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18422
> URL: https://issues.jboss.org/browse/JBIDE-18422
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.2.0.CR1
> Reporter: Victor Rubezhny
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: new_and_noteworthy
> Fix For: 4.2.0.CR2
>
> Attachments: myApp3.zip, Tern completion with friend.png
>
>
> In JBIDE-18273, the JBT/JBDS target platforms were updated to include the latest Tern 0.6.0.201409041810-SNAPSHOT, but the version of AngularJS included in the Early Access site remained at 0.5.0.201408281218. Since these traditionally have been updated IN PARALLEL at the same time, it seems we need a new version of AngularJS in the EA site.
> However, since the latest AngularJS is now 0.6.0.201409231617, maybe we want to pull the latest Tern 0.6.0.201409231610 too, instead of the 2014/09/04 version?
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18239) Create new update site zip(s) (rather than target platform zip) for JBT content needed for Central/EA site
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18239?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-18239:
------------------------------------
[~maxandersen] you're right, Central is already a composite. I keep saying Central will composite this content because Central already composites it.
[~mickael_istria] removing o.j.t.* isn't enough because these pieces don't exist in JBDS, only in JBT. Thus to provide them as part of the JBDS Central or EA experience, they have to exist somewhere (else).
Choices include:
a) leave them in the Central and EA target platform update sites (current state)
b) move them to a new update site (proposed via this JIRA and the above PRs) which can be composited into the JBDS Central site*
c) include the entire JBT update site in the JBDS Central site* (bad idea IMHO because we'll expose JBDS users to installing JBT content w/o it coming through the Central or EA UI; however this is simpler in that it doesn't require a new category.xml, but also eats more disk space and duplicates content in the Central composite)
* - The JBDS Central site is a composite containing JBDS TP, JBDS update site, and JBoss Central. If we remove the o.j.t.* content from the JBoss Central target platform & update site, it will no longer be in the composite. Therefore it needs to come from somewhere else.
> Create new update site zip(s) (rather than target platform zip) for JBT content needed for Central/EA site
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18239
> URL: https://issues.jboss.org/browse/JBIDE-18239
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, central, discovery, updatesite
> Affects Versions: 4.2.0.CR1
> Reporter: Nick Boldt
> Labels: f2f2014
> Fix For: 4.3.0.Alpha1
>
> Attachments: JBIDE18239-proposed.png
>
>
> In order to simplify the process for getting JBT features into Central (for JBDS) and EA (for both JBT/JBDS), it's been suggested (by [~maxandersen], who doesn't like opening JIRAs :D) that instead of a target platform which needs to be updated every time we spin or respin a build, we could instead just produce an update site containing the handful of IUs (cordovasim, arquillian, etc.).
> We could further extend this idea to include all the things that currently are in BOTH JBT or JBDS and in Central, such as TestNG.
> These would be produced as new zips using the JBT aggregate builder:
> https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregate/
> Need to decide what to call this... "Extras" "JBT-not-in-JBDS" "Shared" ...?
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18422) Include latest Tern & AngularJS 0.6.0.20140923161* into jbosstools/jbds TPs AND Early Access too
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18422?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-18422:
------------------------------------
So... what I'm hearing is: "there will be a new build of Tern/AngularJS 0.6.0 and the 09/23 version should be replaced with something yet newer".
Is that correct, [~azerr] ?
cc: [~dgolovin] [~mickael_istria] [~vpakan]
> Include latest Tern & AngularJS 0.6.0.20140923161* into jbosstools/jbds TPs AND Early Access too
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18422
> URL: https://issues.jboss.org/browse/JBIDE-18422
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.2.0.CR1
> Reporter: Victor Rubezhny
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: new_and_noteworthy
> Fix For: 4.2.0.CR2
>
> Attachments: myApp3.zip, Tern completion with friend.png
>
>
> In JBIDE-18273, the JBT/JBDS target platforms were updated to include the latest Tern 0.6.0.201409041810-SNAPSHOT, but the version of AngularJS included in the Early Access site remained at 0.5.0.201408281218. Since these traditionally have been updated IN PARALLEL at the same time, it seems we need a new version of AngularJS in the EA site.
> However, since the latest AngularJS is now 0.6.0.201409231617, maybe we want to pull the latest Tern 0.6.0.201409231610 too, instead of the 2014/09/04 version?
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18438) OpenShift: can complete New App Wizard without selecting gear profile
by Michelle Murray (JIRA)
Michelle Murray created JBIDE-18438:
---------------------------------------
Summary: OpenShift: can complete New App Wizard without selecting gear profile
Key: JBIDE-18438
URL: https://issues.jboss.org/browse/JBIDE-18438
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.2.0.CR1
Reporter: Michelle Murray
Priority: Minor
In New OpenShift Application wizard, on page where select 'Gear Profile' - this field is initially blank and user can leave it blank and still successfully complete the wizard. So it works.
But I don't think it is a good user experience. User should not be able to move to next page until there is a value in this field. Perhaps this field should have a value to start with instead of being blank based on the users account?
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months