Bug 745763 - WFK Maven Repository has a direct depedency on EAP6 Repo, even for EWS
Summary: WFK Maven Repository has a direct depedency on EAP6 Repo, even for EWS
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: JBoss Enterprise WFK Platform 2
Classification: Retired
Component: Maven
Version: 2.0.0.DR2
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: 2.0.0.GA
Assignee: Marek Novotny
QA Contact: Karel Piwko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-13 10:39 UTC by Karel Piwko
Modified: 2012-06-22 10:44 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
The JBoss Enterprise Application Platform Maven repository is a prerequisite to use the JBoss Web Framework Kit Maven repository on <emphasis>JBoss Enterprise Web Server</emphasis> as well as the Enterprise Application Platform.
Clone Of:
Environment:
Last Closed: 2012-06-22 10:44:58 UTC
Type: Feature Request

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Karel Piwko 2011-10-13 10:39:41 UTC 
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:

Always.

Steps to Reproduce:
1. Try to include org.jboss.snowdrop:snowdrop-vfs:jar:2.0.0.CR1-redhat-1 in your project

  
Actual results:

It will fail, following artifact cannon be found: org.jboss:jboss-parent:6-redhat-1. 

Expected results:

On EAP6 you should be able to include EAP6 Maven Repository, however what should you do on EWS?

There will be an EWS zip or something to ensure that jboss-parent:6-redhat-1 can be resolved.


Additional info:


{code:xml}
       <profile>
            <id>jboss-wfk2-repository</id>
            <repositories>
                <repository>
                    <id>jboss-wfk2-repository</id>
                    <name>JBoss WFK2 internal Maven Repository</name>
                    <url>http://download.devel.redhat.com/brewroot/repos/jb-wfk-2-rhel-6-build/latest/maven</url>
                    <layout>default</layout>
                    <releases>
                        <enabled>true</enabled>
                        <updatePolicy>never</updatePolicy>
                    </releases>
                    <snapshots>
                        <enabled>false</enabled>
                        <updatePolicy>never</updatePolicy>
                    </snapshots>
                </repository>
            </repositories>
            <pluginRepositories>
                <pluginRepository>
                    <id>jboss-wfk2-repository</id>
                    <name>JBoss WFK2 internal Maven Repository</name>
                    <url>http://download.devel.redhat.com/brewroot/repos/jb-wfk-2-rhel-6-build/latest/maven</url>
                    <layout>default</layout>
                    <releases>
                        <enabled>true</enabled>
                        <updatePolicy>never</updatePolicy>
                    </releases>
                    <snapshots>
                        <enabled>false</enabled>
                        <updatePolicy>never</updatePolicy>
                    </snapshots>
                </pluginRepository>
            </pluginRepositories>
        </profile>
{code}

is needed as there is no EAP6 zip yet.
Comment 1 Marek Novotny 2011-10-13 10:59:32 UTC 
Almost all jboss.org projects have got as parent project org.jboss:jboss-parent. The version 6-redhat-1 is only productized version.

Nobody supposes that a user wants to use wfk maven repository without eap6 maven repository.
Comment 2 Karel Piwko 2011-10-13 11:24:52 UTC 
You mean EWS1 users will use WFK Maven Repository with EAP6 repository? 

They are actually forced to do so by current state. Do they have access to it? Do we ensure EAP6 repository won't contain dependencies with same G:A not compatible on EWS?
Comment 3 Marek Novotny 2012-01-23 12:38:17 UTC 
What will we do with this issue?

Does it require any special handling? Documentation?
Comment 4 Karel Piwko 2012-02-10 14:43:02 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Users wishing to use a JBoss Web Framework Kit Maven repository to build an application for JBoss Enterprise Web Server have to download JBoss Enterprise Application Platform Maven repository as well. 

JBoss Web Framework Kit Maven repository is not supposed to be used standalone but requires JBoss Enterprise Application Platform Maven repository.
Comment 5 Rebecca Newton 2012-03-08 02:53:58 UTC 
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,3 +1 @@
-Users wishing to use a JBoss Web Framework Kit Maven repository to build an application for JBoss Enterprise Web Server have to download JBoss Enterprise Application Platform Maven repository as well. 
+JBoss Enterprise Application Patform maven repository is a prerequisite to use the JBoss Web Framework Kit maven repository on JBoss Enterprise Web Server.-
-JBoss Web Framework Kit Maven repository is not supposed to be used standalone but requires JBoss Enterprise Application Platform Maven repository.
Comment 6 Karel Piwko 2012-03-08 13:04:16 UTC 
Verified that EAP Maven repository is a prerequisite to use WFK Maven repository.
Comment 8 Rebecca Newton 2012-06-19 05:40:47 UTC 
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-JBoss Enterprise Application Patform maven repository is a prerequisite to use the JBoss Web Framework Kit maven repository on JBoss Enterprise Web Server.+The JBoss Enterprise Application Platform Maven repository is a prerequisite to use the JBoss Web Framework Kit Maven repository on <emphasis>JBoss Enterprise Web Server</emphasis> as well as the Enterprise Application Platform.
Comment 9 Karel Piwko 2012-06-22 10:44:58 UTC 
This is released as a part of WFK 2.0.0.
Note You need to log in before you can comment on or make changes to this bug.