[JBoss JIRA] (JBIDE-19497) Use Jetty 9 in TP
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19497?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-19497:
-------------------------------------
Ok, I'd rather prefer to use 9.2.5 then, cause I do need single version of jetty bundles.
< But even if we move to 9.2.5 now, there are chances that other projects move up before Mars.
Oh, I see. but I guess there is no other way but catch up if this happens. Or alternatively we could ship whole pack of jetty 9.2.10 by our own and not depend on Eclipse Mars stuff. However, it means that there will be duplicates of jetty bundles in the TP (e.g org.eclipse.jetty.util_9.2.5 + org.eclipse.jetty.util_9.2.10), which is not good, right?
> Use Jetty 9 in TP
> -----------------
>
> Key: JBIDE-19497
> URL: https://issues.jboss.org/browse/JBIDE-19497
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.3.0.Alpha2
> Reporter: Mickael Istria
>
> *Reason:* It seems like we are ready to move away from Jetty 8 and to use Jetty 9 in CordovaSim & LiveReload. We should update TP to include all Jetty 9 bundles
> *Project page/sources:* https://www.eclipse.org/jetty/
> *Version:* 9.2.10.v20150310
> *License and owner:* Eclipse.org
> *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.2.9.v20150224
> *JBoss mirror:* TODO
> *Include Sources:* Yes
> *Affected projects:* Livereload, Cordovasim
> *Include in JBDS:* Yes
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> {code}
> TODO: suggested diff on the .target files/p2diff
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3285) Git: Easy Import
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ]
Mickael Istria updated JBDS-3285:
---------------------------------
Description:
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
was:
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):
{quote}
Easymport framework has been contributed to e4 (Platform Incubator): in http://git.eclipse.org/c/e4/org.eclipse.e4.ui.git/tree/bundles , see all org.eclipse.e4.ui.importer* . You can install it in your IDE from http://download.eclipse.org/e4/snapshots/org.eclipse.e4.ui . The entry-points are either the new menu "File > Import projects from folder..." or from legacy import wizard under "General > Local folder(s) as project into workspace".
We have working extensions that allow to import Java EE & Maven: https://github.com/jbosstools/jbosstools-playground/tree/master/plugins (install from http://download.jboss.org/jbosstools/builds/staging/jbosstools-playground... ) , that we plan to contribute upstream when projects such as m2e and WTP when the framework seems mature enough.
There is not yet an easy link from the EGit wizard to the Easymport one, nor an easy link from SVN wizard to Easymport.
There is almost no chance that this can be included in Eclipse IDE for Mars release in June. But we could already think about including it in next JBoss Tools and JBoss Developer Studio milestones, so that we'd get more feedback. At this point, feedback from users and adopters is the key point.
I invite you to give it a try, and to report issues here.
{quote}
> 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: requirements, upstream
> Affects Versions: 8.0.0.GA
> Reporter: Burr Sutter
> Assignee: Mickael Istria
> Labels: usability
> Fix For: 9.0.0.Alpha2
>
>
> 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)
11 years