[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [m2e-users] import project from git workflow
|
great! thank you Jason
I tried yesterday at home with Kepler (where i don't have the maven to git
connector installed) by going to "install new software" and entering the
url you posted but it didn't find anything in the update site. So i tried
to install the old version, the one currently in the m2e catalog but it
could not install due to a missing dependency (i *think* it was egit core
1.0.0 to 3.0.0 even though i do have (and use) egit) This was with a new,
clean eclipse so it looks like the egit connector is not available at all
for Kepler right now
I will try at work where I still have Juno and i do have the old version of
the connector (0.14.0.201207041402) installed
Thank you,
Alejandro Endo | Software Designer/Concepteur de logiciels
From: Jason van Zyl <jason@xxxxxxxx>
To: Maven Integration for Eclipse users mailing list
<m2e-users@xxxxxxxxxxx>,
Date: 2013-06-28 00:51
Subject: Re: [m2e-users] import project from git workflow
Sent by: m2e-users-bounces@xxxxxxxxxxx
On Jun 27, 2013, at 4:44 PM, Alejandro.Endo@xxxxxxxxxxx wrote:
1) When you did that, did the connector clone the github repo
locally? i
imagine it did, right?
Yes.
But my main question is
2) Is that project you imported, linked to your local clone repo?
i.e. can
you commit? if you right click/Team, does it show you only the Share
Project item or you can do all the operations related to a repo?
http://screencast.com/t/n3JlXoYular
In Kepler the Git integration has auto-sharing without having to do
anything programmatically. So in my example Git repos Import in one
operation and Git operations are available.
Thank you for your help
Alejandro Endo | Software Designer/Concepteur de logiciels
From: Jason van Zyl <jason@xxxxxxxx>
To: Maven Integration for Eclipse users mailing list
<m2e-users@xxxxxxxxxxx>,
Date: 2013-06-27 16:06
Subject: Re: [m2e-users] import project from git workflow
Sent by: m2e-users-bounces@xxxxxxxxxxx
Just so that we're talking about the same thing, this is the flow I
am
accustom to:
http://screencast.com/t/EYRaNnP9hGQA
What you want? If not can you explain what you would like to be
different.
I do not have the clone and then import. It's all done in one step.
On Jun 27, 2013, at 3:38 PM, Alejandro.Endo@xxxxxxxxxxx wrote:
Jason, I already have
Maven SCM Handler for EGit 0.14.0.201207041402
org.sonatype.m2e.egit.feature.feature.group Sonatype, Inc.
installed. Everything I described still happened with it (i.e
not
being
able to have a working project in less than 3 steps vs 1 for
cvs/svn)
the version you mention is newer though, but has this particular
issue I
mentioned been fixed since? I can't test this until ~ Monday
Alejandro Endo | Software Designer/Concepteur de logiciels
From: Jason van Zyl <jason@xxxxxxxx>
To: Maven Integration for Eclipse users mailing list
<m2e-users@xxxxxxxxxxx>,
Date: 2013-06-27 15:03
Subject: Re: [m2e-users] import project from git workflow
Sent by: m2e-users-bounces@xxxxxxxxxxx
Use the m2eclipse-egit connector if you want to import a Maven
project from
a Git repository:
install new software using this URL:
http://repository.tesla.io:8081/nexus/content/sites/m2e.extras/m2eclipse-egit/0.14.0/N/0.14.0.201305250025/
On Jun 27, 2013, at 1:14 PM, Alejandro.Endo@xxxxxxxxxxx wrote:
I am not sure whether this is an m2e issue or another
component's so
let me
know if I need to ask somewhere else
I am trying to import a github repo into eclipse. Ideally i
would
like to
do everything in a single wizard which 1) clones the remote
repo
locally,
2) generates the eclipse metadata 3) imports the project
and
leaves
it
ready to commit. This is exactly the current workflow with
SVN
and
CVS
using "Checkout Maven project from SCM": in one wizard you
end
up
with a
compilable/runnable/commitable project in your workspace
Given that git is distributed, I think it's acceptable (not
ideal) to
have
two steps (wizards), one where you only clone the repo, and
another
where
you maven-import the projects in it. However even this
doesn't
currently
work. From the git repositories view (or perspective) I can
right
click on
the local clone and select "Import maven project". This
scans my
maven
structure and lets me select which projects to import. This
imports
the
project quasi-correctly: i can compile and run, however, i
cannot
commit.
My eclipse project is not linked to the local repo even
though i
started
the whole import by right clicking on it. Is this a bug? if
I
import
from a
repo i obviously want to commit to that same repo. Am I
doing it
wrong? is
it m2e the one that handles these imports from a git repo?
i know i can do "team/share project" but my point is that
the
fact
you
need to do this looks like a bug to me.
What do you guys think? if someone agrees I will open a
ticket
for it
if
there's not one already
Alejandro Endo | Software Designer/Concepteur de logiciels
DISCLAIMER:
Privileged and/or Confidential information may be contained
in
this
message. If you are not the addressee of this message, you
may
not
copy, use or deliver this message to anyone. In such event,
you
should destroy the message and kindly notify the sender by
reply
e-mail. It is understood that opinions or conclusions that
do
not
relate to the official business of the company are neither
given
nor endorsed by the company.
Thank You.
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
The modern conservative is engaged in one of man's oldest
exercises
in
moral philosophy; that is,
the search for a superior moral justification for selfishness.
-- John Kenneth Galbraith
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
DISCLAIMER:
Privileged and/or Confidential information may be contained in
this
message. If you are not the addressee of this message, you may
not
copy, use or deliver this message to anyone. In such event, you
should destroy the message and kindly notify the sender by reply
e-mail. It is understood that opinions or conclusions that do
not
relate to the official business of the company are neither given
nor endorsed by the company.
Thank You.
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
We all have problems. How we deal with them is a measure of our
worth.
-- Unknown
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
DISCLAIMER:
Privileged and/or Confidential information may be contained in this
message. If you are not the addressee of this message, you may not
copy, use or deliver this message to anyone. In such event, you
should destroy the message and kindly notify the sender by reply
e-mail. It is understood that opinions or conclusions that do not
relate to the official business of the company are neither given
nor endorsed by the company.
Thank You.
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
We all have problems. How we deal with them is a measure of our worth.
-- Unknown
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
DISCLAIMER:
Privileged and/or Confidential information may be contained in this
message. If you are not the addressee of this message, you may not
copy, use or deliver this message to anyone. In such event, you
should destroy the message and kindly notify the sender by reply
e-mail. It is understood that opinions or conclusions that do not
relate to the official business of the company are neither given
nor endorsed by the company.
Thank You.