[jbosstools-issues] [JBoss JIRA] (JBDS-3285) Easy Import of non-eclipse projects
[
https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin....
]
Mickael Istria commented on JBDS-3285:
--------------------------------------
What's the difference between hide and fix?
Explanation is that the classes/ folder contains META-INF/MANIFEST.MF (which is currently
detected as a PDE plugin - that's something to improve, but that's another topic),
so the PDE detector applies.
However, when you have the Maven detector, it first detects your project as a Maven
project, and it also computes a list of directories to exclude from analysis. In the case
of Maven, it's the target/ folder. So the import framework just know that it
doesn't have to get into the target/ folder in that case, and does try to import its
content.
Easy Import of non-eclipse projects
-----------------------------------
Key: JBDS-3285
URL: https://issues.jboss.org/browse/JBDS-3285
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: requirements, upstream
Affects Versions: 8.0.0.GA
Reporter: Burr Sutter
Assignee: Mickael Istria
Labels: usability
Fix For: 9.0.0.Alpha2
Attachments: import-me.zip
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.
Progress/Status (updated progressively): https://wiki.eclipse.org/E4/UI/Smart_Import
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)