| import projects from SCM: choose base folder? [message #500216] |
Wed, 25 November 2009 12:21  |
 Kristian Rink
Messages: 64
Registered: July 2009 |
Member |
|
|
Folks;
while importing maven2 projects from SCM (SVN actually, in our case), I
usually ended up with my projects being dumped somewhere to
<workspace>/maven.<some-identifier>/...
and generally I don't really care. However, in some cases, in example after
discarding and re-importing a project from SCM, it gets dumped into another
<workspace>/maven.<whatever>/
folder, essentially in some cases messing up the project structure. So, how
to state that I want to have maven2 projects checked out, say, not to some
randomly generated folder but i.e. to <workspace>/maven-artifacts/ instead?
TIA and all the best,
Kristian
|
|
|
|
|
|
| Re: import projects from SCM: choose base folder? [message #502568 is a reply to message #502513] |
Tue, 08 December 2009 20:30  |
Kristian Rink
Messages: 36
Registered: July 2009 |
Member |
|
|
Igor;
sorry, I should have been more careful - indeed the SVN repository is
internally available only. As I am not allowed to open it up:
Igor Fedorenko schrieb:
> I am not able to access the url you provided. Can you provide publicly
> accessible url or describe layout of the project you're trying to import?
Well, it basically comes down to something like this
/
/trunk
|
/tags
|
/stable-20091202-consolidated/
|
/lib-core-api
/lib-core-impl
/pom-parent-basic
/...
So, basically, checking out the "stable-20091202-consolidated" tag ends
up with a handful of maven2 artifacts (pom, jar, war) in this very
folder. Hmmm, hard to describe - what kind of information would help you
any further here? In my case, it would just suffice being capable if,
i.e. checking out a tag or a branch like I did here, m2eclipse would use
the name of the tag/branch (stable-2009..., in this case) rather than
"maven.123124323" as project name in <workspace>.
TIA and all the best,
K.
|
|
|
|
| Re: import projects from SCM: choose base folder? [message #502582 is a reply to message #502571] |
Tue, 08 December 2009 21:29 |
Kristian Rink
Messages: 36
Registered: July 2009 |
Member |
|
|
Igor Fedorenko schrieb:
> This structure does not look like a maven project and checkout as maven
> project won't help you here, unless I am missing something.
Yes, that's eventually the problem: It's not a "maven2" project of
nested projects; at checkout time it basically is a collection of (just
loosely associated) artifacts. The only way "dependency" between these
is enforced is one project used for building them all easily, containing
something like
<modules>
<module>../mod1</module>
<module>../mod2</module>
<module>../mod3</module>
</modules>
which, in my case, fails if I delete and checkout one of mod[1|2|3]
again as by then it will end up in a different folder in <workspace>,
not where the projects checked out before did end up. Agreed, this
project structure eventually could be done smarter, but then again, it's
not totally against maven2 multi-module setup (especially in a "flat"
multiproject layout), and it generally works, IDE tooling support let
aside...
Cheers,
Kristian
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03571 seconds
] 
Search
Help
Register
Login
Home
