Cc: Subversion Mailing List
> Betreff: Maven, Subversion and Eclipse issue
>
>
> Team
>
> I've an issue with the m2 plugin using maven in conjunction with
> subversion.
> Since this crosses three platforms I thought I would try both the
> subversion and maven list
iling List
Sent: Mon, May 9, 2011 12:54:01 PM
Subject: Re: Maven, Subversion and Eclipse issue
I did not catch that until you told me about it. I will experiment with that
today. Thank you!
--Refr inn gra
"Wars are to be won with swords and spears,
not with rice and salt.&quo
Mon, May 9, 2011 12:22:15 PM
Subject: Re: Maven, Subversion and Eclipse issue
You can do it in Eclipse from the Team menu.
On 09/05/2011 11:07 AM, Refr Bruhl wrote:
> So that is manual svn command outside of eclipse?
>
> I'll give it a shot. Thank you!
>
> --Refr inn gra
- Original Message
From: Brian Smith
To: Maven Users List
Cc: Subversion Mailing List
Sent: Mon, May 9, 2011 9:56:14 AM
Subject: Re: Maven, Subversion and Eclipse issue
We set the following on each module's trunk:
$ svn ps svn:ignore core "
target
.project
.classpath
.setting
2011 10:05:48 AM
Subject: Re: Maven, Subversion and Eclipse issue
The SVN ignore file does that trick, right?
on, May 9, 2011 at 12:03 PM, Refr Bruhl wrote:
>
> The subversion plugin doesn't really give that as an option unless every
> time
> you commit you uncheck the target dir
ad an option to exclude directories at set up time.
>
>
>
> --Refr inn gra
>
>
> "Wars are to be won with swords and spears,
> not with rice and salt." -- Uesugi Kenshin
>
>
>
> - Original Message
> From: Alex Lopez
> To: users@maven.apac
ling List
Sent: Mon, May 9, 2011 9:56:14 AM
Subject: Re: Maven, Subversion and Eclipse issue
We set the following on each module's trunk:
$ svn ps svn:ignore core "
target
.project
.classpath
.settings"
On 9 May 2011 15:42, Refr Bruhl wrote:
>
> Team
>
> I
not with rice and salt." -- Uesugi Kenshin
- Original Message
From: Alex Lopez
To: users@maven.apache.org
Sent: Mon, May 9, 2011 9:50:36 AM
Subject: Re: Maven, Subversion and Eclipse issue
never a good idea to commit the target dir IMO...
Em 09-05-2011 15:42, Refr Bruhl esc
We set the following on each module's trunk:
$ svn ps svn:ignore core "
target
.project
.classpath
.settings"
On 9 May 2011 15:42, Refr Bruhl wrote:
>
> Team
>
> I've an issue with the m2 plugin using maven in conjunction with
> subversion.
> Since this crosses three platforms I thought I wo
Definitely.
On Mon, May 9, 2011 at 11:50 AM, Alex Lopez wrote:
> never a good idea to commit the target dir IMO...
>
> Em 09-05-2011 15:42, Refr Bruhl escreveu:
>
>>
>> Team
>>
>> I've an issue with the m2 plugin using maven in conjunction with
>> subversion.
>> Since this crosses three platform
never a good idea to commit the target dir IMO...
Em 09-05-2011 15:42, Refr Bruhl escreveu:
Team
I've an issue with the m2 plugin using maven in conjunction with subversion.
Since this crosses three platforms I thought I would try both the subversion and
maven list to see if anyone has run acr
Team
I've an issue with the m2 plugin using maven in conjunction with subversion.
Since this crosses three platforms I thought I would try both the subversion
and
maven list to see if anyone has run across a similar issue and what the
solution
was.
When maven dependency is enabled for an ec
Then you don't use svn+ssh.
On Sun, Mar 13, 2011 at 1:50 PM, anjana wrote:
> but sir i will have to use file:/// such type of url because my repository is
> local type
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/maven-subversion-issue-tp3555
but sir i will have to use file:/// such type of url because my repository is
local type
--
View this message in context:
http://maven.40175.n5.nabble.com/maven-subversion-issue-tp3555224p363.html
Sent from the Maven - Users mailing list archive at Nabble.com
Hi,
scm:svn:svn+ssh://file:///E:/my-app-repos/trunk
Why are you using file:///... access in relationship with svn+ssh ?
Have you tried to access the repository from command line with this URL ?
Just try an svn list svn+ssh://file:///E:/my-app-repos/trunk which i
assume will fail ...
svn lis
then when i m trying to mvn release:prepare command i m getting error as
fail to execute goal org.apache.maven.plugins
and further more
--
View this message in context:
http://maven.40175.n5.nabble.com/maven-subversion-issue-tp3555224p3555224.html
Sent from the Maven - Users mailing list
then when i m trying to mvn release:prepare command i m getting error as
fail to execute goal org.apache.maven.plugins
and further more
--
View this message in context:
http://maven.40175.n5.nabble.com/maven-subversion-tp3424560p3424560.html
Sent from the Maven - Users mailing list archive at
his problem
>
>
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/maven-subversion-tp3415264p3415264.html
> Sent from the Maven - Issues mailing list archive at Nabble.com.
>
-
To unsu
Thanks. This seems like the right answer.
John Coleman wrote:
Sorry, that wasn't clear from your original post. Branches, tags, and
trunk do not belong in a Maven directory structure, rather the Maven
directory structure belongs in the branches/tags/trunk:
/root
/project
/trunk
Sorry, that wasn't clear from your original post. Branches, tags, and
trunk do not belong in a Maven directory structure, rather the Maven
directory structure belongs in the branches/tags/trunk:
/root
/project
/trunk
/src
/test
/module0
/src
/test
Umm, no.
This question has nothing to do with repositories. It has to do with the
directory structure on the development machines.
John Coleman wrote:
Seems like you have a fundamental misunderstanding of what Maven is
for. Maven is a build tool, similar to Ant. The structure that Maven
Seems like you have a fundamental misunderstanding of what Maven is
for. Maven is a build tool, similar to Ant. The structure that Maven
"wants" is a conventional way to setup your project so that Maven can
build it with minimal fuss.
A Maven repo and a Subversion repo are two different t
Hi Chris I'm doing the Maven plugin for Globus right now to build and
create the GARs.. ;) that's perfect!!
I probably can be of assistance...I have a meeting in 2 mins I'll write
a little more later..
Chris wrote:
I'm migrating a number of projects and modules to Maven. I'm confused
on how
I'm migrating a number of projects and modules to Maven. I'm confused on
how the directories should be set up.
Maven wants this:
/projectname
/module0
/src
/module1
/src
Subversion wants this:
/root
/projectname
/branches
get" and "bin" not
to commit them, and you add the svn:ignore property on it.
--
Régis
--
View this message in context:
http://www.nabble.com/Maven-Subversion-Eclipse-Subclipse-Configuration-tf4757978s177.html#a13623976
Sent from the Maven - Users mailing list archive at N
I agree with you, Vanja. And if the developers on the project are
definitely using Eclipse, you can create a "Maven Builder" for Eclipse
that hooks into the Eclipse build lifecycle. See the
additionalBuildCommands tag here:
http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html.
This is straying off topic into Subversion but dare I mention it?... If
you are developing on Windows there is an excellent open source
graphical client for Subversion called TortoiseSVN for checking things
in and out of subversion and managing the SVN repo. You can get it at
http://tortoisesvn.t
Check config file for the subversion. There you can find global-ignores
option, where you can set filtering for target and other non-maven files
(like IDE specific files).
I am following the procedure:
1) Create Maven project structure
2) Import to the Subversion (with mentioned global-ignores)
3
Were configuring our first Maven project and wondering if we have the
right approach.
Were using Maven2, Subversion accessible via WebDAV, Eclipse with both
Subclipse and Maven2Eclipse plugin.
We created a new Maven2 project in Eclipse.
We have an existing project structure that we want to conver
29 matches
Mail list logo
