[JBoss JIRA] (JBDS-2860) Missing "build-5" artifact
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-2860?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on JBDS-2860:
-----------------------------------
Log of today's discussion with [~rafabene], [~pmuir] :
{quote}
(15:38:27) ***rbenevides looking
(15:40:34) rbenevides: mmalina fbricon It seems that the wrong archetype was released. we shouldn't depend on *-build-* dependencies
(15:41:02) rbenevides: mmalina fbricon we should depend only on -redhat-* dependencies
(15:41:22) fbricon: rbenevides: is there a proper release already?
(15:41:55) rbenevides: fbricon I don't think so. This archetype was staged and WFK team said it's ok to release it. There wasn't any other release after
(15:46:53) mmalina: rbenevides: so will you be able to fix that? perhaps create a new release? do you want me to create a JIRA for you?
(15:47:19) rbenevides: mmalina Please, create a Jira on WFK so they can improve the QE tests
(15:47:50) rbenevides: mmalina https://issues.jboss.org/browse/WFK2
(15:48:30) fbricon: mmalina: I can reproduce the warning issue
(15:48:56) mmalina: fbricon: cool
(15:50:30) fbricon: mmalina: warnings are reset in memory once the settings are changed, but the visual warning component is not reset :/
(15:51:33) fbricon: mmalina: mmm actually it seems more subtle than that. need to debug
(15:51:39) mmalina: fbricon: ok :)
(15:56:50) mmalina: rbenevides: where can I find the version of the archetype? to include in the jira
(15:57:12) rbenevides: mmalina https://github.com/jboss-developer/jboss-wfk-archetypes/releases/tag/2.4....
(15:58:14) mmalina: rbenevides: oh, ok, so Affects version: 2.4.0.GA should be enough
(15:58:42) rbenevides: mmalina It's strange because I don't see the -build-* on the sources
(15:58:52) rbenevides: fbricon ^^^
(15:58:54) rbenevides: https://github.com/jboss-developer/jboss-wfk-archetypes/blob/2.4.0.Final/...
(15:59:26) fbricon: rbenevides: on the javaee-web archetype
(15:59:41) fbricon: *html5
(15:59:51) rbenevides: fbricon mmalina hummmm. Sorry! So let me start again
(16:00:02) rbenevides: mmalina hang on
(16:00:29) mmalina: rbenevides: ok, so no jira for WFK2 then? I'm on hold... :)
(16:01:11) rbenevides: mmalina exactly. I misunderstood completely because the only "new" archetype is html5.
(16:01:34) rbenevides: mmalina that other archetypes are staging for eap 6.2
(16:02:24) rbenevides: mmalina so while the maven.repository.redhat.com is not on nexus, we're place the depedencies on jboss-developer.github.io/temp-maven-repo/
(16:02:38) rbenevides: mmalina it should be temporary as the name is said
(16:02:46) rbenevides: mmalina sorry for the confusion
(16:02:48) mmalina: rbenevides: ok, so stacks.yaml refers to staging archetype to work with eap 6.2?
(16:03:13) mmalina: rbenevides: when do you think this will be resolved?
(16:03:14) rbenevides: mmalina yes. maybe we should comment it out cc fbricon
(16:04:10) rbenevides: mmalina the archetypes should be released on 6.2 relase. I send an email to pmuir friday. I'll talk again with him today about it
(16:04:13) rbenevides: sent
(16:04:30) mmalina: rbenevides: a) if you comment this out, what would be the consequence? would the current archetype work with eap 6.2?
(16:04:48) rbenevides: mmalina I don't think so
(16:04:53) mmalina: rbenevides: b) shouldn't this staged archetype be only used for eap 6.2 and not 6.1.1?
(16:05:08) mmalina: rbenevides: because I reproduced this also for eap 6.1.1
(16:05:17) rbenevides: mmalina I need to check
(16:05:22) mmalina: rbenevides: on friday, stacks.yaml still had no eap 6.2 definition. not sure now
(16:05:42) rbenevides: mmalina it was commented
(16:07:00) mmalina: rbenevides: I can see it now. any reason why it is commented? and to be clear, if eap 6.2 is commented, then eap 6.2 automatically uses the eap 6.1 definition? I'm not sure how it works
(16:07:55) rbenevides: mmalina I was waiting to 6.2 to be released. I need to work on it.
(16:18:44) rbenevides: hey pmuir ! did you have time to look about archetypes for eap 6.2 ?
(16:26:08) pmuir: rbenevides: what am i supposed to be looking at there?
(16:27:24) mmalina: rbenevides: oh, ok. so in theory you should be able to leave the eap 6.1 archetypes as they were and play with the eap 6.2 definitions, no?
(16:28:09) mmalina: rbenevides: right now we are in the final stage of JBDS 7.1 testing and we need to determine if EAP 6.2 works properly with the examples in JBoss Central
(16:28:45) rbenevides: pmuir I think that we should discuss with eap team about the release of those archetypes
(16:29:11) rbenevides: pmuir based on your plan, they should release it and place on maven.repository.redhat.com
(16:29:57) rbenevides: mmalina in teory yes
(16:32:11) pmuir: rbenevides: well yes,but can you make sure it is all ok for 6.2 with pgier directly>
(16:32:14) pmuir: ?
(16:32:22) pmuir: as that doc isn't in force yet
(16:33:17) rbenevides: pmuir ok. I'll look with him
{quote}
Basically, new archetypes must be released and stacks.yaml must be updated.
In the mean time, we can decide to hide these *temporary* archetypes from Central. Your call Burr.
> Missing "build-5" artifact
> --------------------------
>
> Key: JBDS-2860
> URL: https://issues.jboss.org/browse/JBDS-2860
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Burr Sutter
> Assignee: Fred Bricon
>
> When using the Java EE Web Project from JBoss Central for JBDS 7.1.0.CR2 (GA-v20131208-0703-B592), this error is shown:
> {quote}
> This project has a dependency on org.jboss.bom.eap:jboss-javaee-6.0-with-tools:pom:6.2.0-build-5, which cannot be found.
> {quote}
> !http://content.screencast.com/users/BurrSutter/folders/Jing/media/553653d6-7047-4cfa-8be9-b594ead3f16d/00000745.png!
> http://www.screencast.com/t/vDbKBmuXvty8
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (TOOLSDOC-438) Document combined universal installer to include EAP 6.2
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-438?page=com.atlassian.jira.plug... ]
Michelle Murray commented on TOOLSDOC-438:
------------------------------------------
PR merged with master and 4.1.x: https://github.com/jbosstools/jbosstools-documentation/pull/230
> Document combined universal installer to include EAP 6.2
> --------------------------------------------------------
>
> Key: TOOLSDOC-438
> URL: https://issues.jboss.org/browse/TOOLSDOC-438
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Installation Guide, Release Notes
> Affects Versions: 4.1.1
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.1
>
>
> As per JBDS-2856, combined universal installer EAP version is being bumped from 6.1.1 to 6.2.0.
> Need to:
> * Update item in Release Notes document
> * Change info on Customer Portal supported configs page
> _In event that combined universal installer is pulled, need to:_
> * Remove mention of bundled installer from Release Notes document
> * Change info on Customer Portal supported configs page
> * Identify and remove selected text from Installation Guide sections: 3.1 Install Options, 3.2 Install JBoss Developer Studio
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (TOOLSDOC-438) Document combined universal installer to include EAP 6.2
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-438?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-438:
-------------------------------------
Component/s: (was: Installation Guide)
> Document combined universal installer to include EAP 6.2
> --------------------------------------------------------
>
> Key: TOOLSDOC-438
> URL: https://issues.jboss.org/browse/TOOLSDOC-438
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Release Notes
> Affects Versions: 4.1.1
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.1
>
>
> As per JBDS-2856, combined universal installer EAP version is being bumped from 6.1.1 to 6.2.0.
> Need to:
> * Update item in Release Notes document
> * Change info on Customer Portal supported configs page
> _In event that combined universal installer is pulled, need to:_
> * Remove mention of bundled installer from Release Notes document
> * Change info on Customer Portal supported configs page
> * Identify and remove selected text from Installation Guide sections: 3.1 Install Options, 3.2 Install JBoss Developer Studio
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (TOOLSDOC-438) Document combined universal installer to include EAP 6.2
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-438?page=com.atlassian.jira.plug... ]
Michelle Murray resolved TOOLSDOC-438.
--------------------------------------
Resolution: Done
> Document combined universal installer to include EAP 6.2
> --------------------------------------------------------
>
> Key: TOOLSDOC-438
> URL: https://issues.jboss.org/browse/TOOLSDOC-438
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Release Notes
> Affects Versions: 4.1.1
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.1
>
>
> As per JBDS-2856, combined universal installer EAP version is being bumped from 6.1.1 to 6.2.0.
> Need to:
> * Update item in Release Notes document
> * Change info on Customer Portal supported configs page
> _In event that combined universal installer is pulled, need to:_
> * Remove mention of bundled installer from Release Notes document
> * Change info on Customer Portal supported configs page
> * Identify and remove selected text from Installation Guide sections: 3.1 Install Options, 3.2 Install JBoss Developer Studio
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBDS-2748) Fix bugs in 7.0 documentation
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2748?page=com.atlassian.jira.plugin.... ]
Michelle Murray commented on JBDS-2748:
---------------------------------------
Identified bugs fixed.
QE review of docs ahead of GA - JBQA-8549.
> Fix bugs in 7.0 documentation
> -----------------------------
>
> Key: JBDS-2748
> URL: https://issues.jboss.org/browse/JBDS-2748
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: documentation, requirements
> Affects Versions: 7.0.0.GA
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 7.1.0.GA
>
>
> We should include essential but trivial fixes for the bugs in docs that have been found by docs/QE/users.
> All those should be linked to this jira.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBDS-2749) Update screen captures in docs that explicitly reference JBDS 7.0
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2749?page=com.atlassian.jira.plugin.... ]
Michelle Murray commented on JBDS-2749:
---------------------------------------
Final image included. Marking jira as done.
> Update screen captures in docs that explicitly reference JBDS 7.0
> -----------------------------------------------------------------
>
> Key: JBDS-2749
> URL: https://issues.jboss.org/browse/JBDS-2749
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: documentation, requirements
> Affects Versions: 7.0.0.GA
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 7.1.0.GA
>
>
> Screen captures that will need updating for 7.1 docs
> *Installation Guide*
> * Figure 3.1. JBoss Developer Studio Downloads Listed on the Customer Portal
> * Figure 3.2. Installation Step 3: Select Target Folder
> * Figure 3.3. Installation Step 4: Select Java VM
> * Figure 3.5. Installation Step 7: Installation Progress in Finished State
> * Figure 3.6. Install JBoss Developer Studio BYOE via Eclipse Marketplace
> * Figure 3.7. Confirm Selected Features Window
> * Figure 3.10. Work from an Online Website
> * Figure 3.11. work from a Local Copy of the Update .zip File
> * Figure 3.12. Available Software Window Listing JBoss Developer Studio 7.0 - Bring Your Own Eclipse
> * Figure 6.2. Uninstall JBoss Developer Studio via Eclipse Marketplace
> * Figure 6.3. Confirm Selected Features Window
> *Migration Guide*
> * Figure 3.1. jbdevstudio.ini File Open in a Text Editor
> *Getting Started Guide* (all Fig. shared with Installation Guide)
> * Figure 3.1. JBoss Developer Studio Downloads Listed on the Customer Portal
> * Figure 3.2. Installation Step 3: Select Target Folder
> * Figure 3.3. Installation Step 4: Select Java VM
> * Figure 3.5. Installation Step 7: Installation Progress in Finished State
> *User Guide*
> * Figure 2.4. JBoss Buzz
> * Figure 2.22. Set Cheat Sheet Behavior in Project Examples Pane of Preferences Window
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months