[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-users] 回覆︰ 回覆︰ one parent with 2 children
|
As I said before this isn't related to m2e but the Eclipse SVN team provider that you're using. The server does not need two copies, you simply need to link the Eclipse project to the existing SVN files. I haven't used SVN in years but typically you can right-click the project, select Team > Share then follow the wizard.
On 3 June 2012 22:27, tong123123
<tong123123@xxxxxxxxxxxx> wrote:
yes, I have not added the core and webapp project to svn as the parent project already encloses it. and in the parent project, I can drill down to core and then the subpackage of core, and it is in svn. So do you mean I also need share the webapp and core in svn? if this is the case, then svn server will have 2 copy of core and webapps (one enclose in parent, one self existing after import to m2eclipse)???
if there is some screen layout, it is better to discuss, or is there any web resources about this problem?
But, as Matthew pointed out, only the parent project seems to have been added to source; the core and webapp aren't suffixed with their SVN location in the Package Explorer. And I don't see your pom files in Windows Explorer for some reason. Again, we have a modules block in our parent structure that lists the chid projects. The parent was shared (as a folder with a pom) then the two projects were shared as subfolders
beneath it. Then when we check out the trunk using "Check Out As Maven Project" we get a "root" project in Package Explorer for the parent and another one each for the actual projects. Then if we drill down through the parent, as we rarely do, we do see the hierarchy - which we use mostly for our build process. Sorry not sure what you're missing exactly :(
Craig
On Fri, Jun 1, 2012 at 4:25 AM, tong123123
<tong123123@xxxxxxxxxxxx> wrote:
The problem is in window explorer, the project sturcture is the two child are directly under the parent (as in m2eclipse3.png).
but after imported with m2eclipse, the structure become one parent with two child, and then the two child has its own project itself!! (as in m2eclipse2.png)
I use "team > shared" to put the parent and two child in svn, but the magic created child own project...how to handle it?
For clear, I attach the parent(viewer.project) and the two child(core, webapp) eclipse .poject file also.
Looking at your image the two child projects aren't shared with SVN.
On 29 May 2012 07:17, Igor Fedorenko
<igor@xxxxxxxxxxxxxx> wrote:
The three workspace projects are mapped to the same directory tree on
the filesystem. Use parent project to commit changes to svn, this will
commit changes to module projects too.
--
Regards,
Igor
On 12-05-29 6:08 AM, tong123123 wrote:
as the attached image shown, in m2eclipse, if I have one parent project
and two child projects, when import to m2eclipse, the layout becomes
three project, one is
parent
---------child1
---------child2
the second is
child1
the third is
child2
and if I change child1 in second project, it will synchronize with the
child1 in parent project.
But now I have svn commit parent and two childs project, so the first
parent
---------child1
---------child2
has svn symbol for change and can check check from repository, but the
second and third project cannot!!
how to handle this case?
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
