[jbosstools-issues] [JBoss JIRA] (JBIDE-11166) Supporting multi-module projects in OpenShift Deployment

[Isaac Rooskov (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-11166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Isaac Rooskov closed JBIDE-11166.
---------------------------------

    Resolution: Done


Reclosing issue now release note status has been set. Thanks for writing up release note text though, this will be very useful when writing the component overview.
                
> Supporting multi-module projects in OpenShift Deployment
> --------------------------------------------------------
>
>                 Key: JBIDE-11166
>                 URL: https://issues.jboss.org/browse/JBIDE-11166
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS/Servers, openshift
>            Reporter: Max Rydahl Andersen
>            Assignee: Rob Stryker
>            Priority: Critical
>              Labels: new_and_noteworthy
>             Fix For: 3.3.0.Beta3
>
>         Attachments: JBIDE-11166.b1.patch, JBIDE-11166.b1.slim.patch, JBIDE-11166.patch
>
>
> POH5 archetype recently got updated and became the first project layout that requires support for multimodule project layouts.
> What they have is the following:
> Aggregator Project "AP" includes two child projects "A" and "B".
> This is the simplest case - but you could also easily have more complex layouts,
> i.e. AP includes another aggregatorproject QAP which nest other child projects.
> But the key point is that the "root" in OpenShift is considered the Aggegator project.
> And this is the kind of layout we would need to support, and I see the following things we need to check/implement to make it happen:
> A) The "magic" project on our OpenShift server adapter should be allowed to be any kind of project as long as it has git enabled on it. 
> B) OpenShift Server Adapter should *not* deploy any child of Aggregator as binary by default 
> C) Import of OpenShift Application should be sure it will actually import a multimodule project.
> D) Import of OpenShift App when using existing App would need to do some validity checks *and* somehow ensure the child projects gets available if they aren't imported (maybe a warning is enough?)
> I belive A and C should be trivially implemented if not already.
> B should be as simple as checking the phyiscal location. i.e. if A is a subdir within AP then dont deploy.  i.e. /Users/max/ap is parent for project A stored in /Users/max/ap/x/y/z/a 
> D is the hard part.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira