[jbosstools-issues] [JBoss JIRA] (JBDS-2860) Missing "build-5" artifact

Mon Dec 9 19:45:06 EST 2013

    [ https://issues.jboss.org/browse/JBDS-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929661#comment-12929661 ] 

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.0.Final
(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/jboss-html5-mobile-archetype/src/main/resources/archetype-resources/pom.xml
(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