[ https://issues.jboss.org/browse/JDF-151?page=com.atlassian.jira.plugin.sy... ] Brian Leathem updated JDF-151: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jboss-jdf/jdf-stack/pull/3 -- 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

[ https://issues.jboss.org/browse/JDF-151?page=com.atlassian.jira.plugin.sy... ] Rafael Benevides commented on JDF-151: -------------------------------------- [~bleathem] Please, take a look at my comments and please updated your PR: https://github.com/jboss-jdf/jdf-stack/pull/3#issuecomment-10444722 -- 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

[ https://issues.jboss.org/browse/JDF-151?page=com.atlassian.jira.plugin.sy... ] Rafael Benevides commented on JDF-151: -------------------------------------- [~bleathem] Hi Brian, The tests said that: Can't resolve Archetype [org.richfaces.archetypes:richfaces-archetype-kitchensink:4.2.3.Final-1] I looked at https://repository.jboss.org/nexus/content/groups/public/org/richfaces/ar... and I didn't see this version: 4.2.3.Final-1 that you added in this commit: https://github.com/bleathem/jdf-stack/commit/6b222608338c121a8d0b3fc33f0a... Could you check the release of this version ? Thanks. -- 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

[ https://issues.jboss.org/browse/JDF-151?page=com.atlassian.jira.plugin.sy... ] Rafael Benevides edited comment on JDF-151 at 11/27/12 1:26 PM: ---------------------------------------------------------------- [~bleathem] Brian, This BOM (org.jboss.spec:jboss-javaee-6.0:pom:3.0.0.Final-redhat-1) is available at the EAP6 maven repository. I'm not sure with we should merge the PR before the staging is finished since this can break anything. Shouldn't we wait the RF KS archetype to be released ? Most of stacks tools can use an alternate stacks repo. So you can use this feature to test your changes like [~fbricon] commented on JBIDE-13059: The archetype can be tested in Central by starting eclipse/jbds using the system property : -Dorg.jboss.examples.stacks.url=https://raw.github.com/bleathem/jdf-stack/a4d996b89e5a311759c2f8c9445cfc75a70cc49f/stacks.yaml was (Author: rafabene): [~bleathem] Brian, This BOM is available at the EAP6 maven repository. I'm not sure with we should merge the PR before the staging is finished since this can break anything. Shouldn't we wait the RF KS archetype to be released ? Most of stacks tools can use an alternate stacks repo. So you can use this feature to test your changes like [~fbricon] commented on JBIDE-13059: The archetype can be tested in Central by starting eclipse/jbds using the system property : -Dorg.jboss.examples.stacks.url=https://raw.github.com/bleathem/jdf-stack/a4d996b89e5a311759c2f8c9445cfc75a70cc49f/stacks.yaml -- 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