[jbosstools-issues] [JBoss JIRA] (JBIDE-12218) Git-versioned projects not building when deployed on OpenShift

Andre Dietisheim (JIRA) jira-events at lists.jboss.org
Wed Aug 22 09:10:16 EDT 2012


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

Andre Dietisheim edited comment on JBIDE-12218 at 8/22/12 9:09 AM:
-------------------------------------------------------------------

There is a slight error though:

The import does not recognize that the individual projects are shared within a git repo in the parent folder. The importer then creates a new git repo in the project-folder (you then end up having a new, additional git-repo nested in the project folder).

*EGitUtils.isSharedWithGit(IProject)* is actually only testing for the Eclipse team provider to be connected with the given project:
{code}
RepositoryProvider provider = RepositoryProvider.getProvider(project);
return provider != null
	&& EGIT_TEAM_PROVIDER_ID.equals(provider.getID());

{code}

                
      was (Author: adietish):
    There is a slight error though:

The import does not recognized that the individual projects are shared within a git repo in the parent folder. The importer then creates a new git repo in the project-folder (you then end up having a new git-repo nested in the project folder).

*EGitUtils.isSharedWithGit(IProject)* is actually only testing for the Eclipse team provider to be connected with the given project:
{code}
RepositoryProvider provider = RepositoryProvider.getProvider(project);
return provider != null
	&& EGIT_TEAM_PROVIDER_ID.equals(provider.getID());

{code}

                  
> Git-versioned projects not building when deployed on OpenShift
> --------------------------------------------------------------
>
>                 Key: JBIDE-12218
>                 URL: https://issues.jboss.org/browse/JBIDE-12218
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 3.3.0.CR1
>            Reporter: Stefan Bunciak
>            Assignee: Andre Dietisheim
>            Priority: Blocker
>             Fix For: 3.3.2, 3.4.0.M1
>
>         Attachments: deployed-helloworld.png, push-force.png
>
>
> After trying to *Commit & Push* i get: master: master [rejected - non-fast-forward]
> {code}
> Repository ssh://500881bf89dc482298bebb43ea15fbdf@html-rhtestdomain.rhcloud.com/~/git/html.git/
> {code}
> After *publishing* via server adapter (no Maven build triggered):
> {code}
> Repository ssh://500881bf89dc482298bebb43ea15fbdf@html-rhtestdomain.rhcloud.com/~/git/html.git/
> Stopping application...
> Done
> ~/git/html.git ~/git/html.git
> ~/git/html.git
> Emptying tmp dir: /var/lib/stickshift/500881bf89dc482298bebb43ea15fbdf/html/jbossas-7/standalone/tmp/auth
> Emptying tmp dir: /var/lib/stickshift/500881bf89dc482298bebb43ea15fbdf/html/jbossas-7/standalone/tmp/vfs
> Emptying tmp dir: /var/lib/stickshift/500881bf89dc482298bebb43ea15fbdf/html/jbossas-7/standalone/tmp/work
> Starting application...
> Done
> {code}
> Output of the server.log (used the *Tail files* option from OpenShift Explorer):
> {code}
> 2012/06/19 09:41:23,904 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014777:   Services which failed to start:      service jboss.server.deployment.scanner.default: org.jboss.msc.service.StartException in service jboss.server.deployment.scanner.default: java.lang.IllegalArgumentException: JBAS015053: /var/lib/stickshift/500881bf89dc482298bebb43ea15fbdf/html/jbossas-7/standalone/deployments does not exist
> 2012/06/19 09:41:23,983 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss AS 7.1.0.Final "Thunder" started (with errors) in 32395ms - Started 168 of 283 services (1 services failed or missing dependencies, 111 services are passive or on-demand)
> {code}
> But git project (jboss-kithensink) from [git://github.com/openshift/kitchensink-example.git] works fine. What's the difference? Probably their repo layout.

--
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

        


More information about the jbosstools-issues mailing list