[
https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBDS-3285:
-------------------------------------------
" I find it very difficult to clone and import a project correctly into JBDS"
Do you mean *any* kind of project, or a *maven* project ?
if it is already an eclipse project it just works. The issue is if the project is not
something egit knows about it wont know how to import it. This is why we created easymport
that are being contributed to eclipse platform to allow wizards like egit import to detect
and automaically configure/open projects based on their content even for things they might
not know about yet.
"having the appropriate facets configured, if it has a maven pom.xml, correctly
setting the build path, where it is easily deployable to a localhost EAP instance"
can you be a bit more specific what you mean here ? today if your project is a pom.xml and
you get it imported all this should all be there and I believe we cannot really get any
better/closer at this. With JBDS the server is there by default and you can drag it to the
server and it will "just work". What parts are missing here in your opinon ?
what kind of projects are you maybe thinking on that is *not* maven projects ?
Git: Easy Import
----------------
Key: JBDS-3285
URL:
https://issues.jboss.org/browse/JBDS-3285
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: upstream
Affects Versions: 8.0.0.GA
Reporter: Burr Sutter
Labels: requirements, usability
As a Java EE developer, in some cases using Git for the first time (or only familiar with
command line git), I find it very difficult to clone and import a project correctly into
JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly
setting the build path, where it is easily deployable to a localhost EAP instance.
The mission here is to make the Git experience much more user friendly.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)