On Tue, Jul 5, 2011 at 3:26 PM, Niranjan Rao wrote:
> Hi there,
>
> Subject line is rather long, but I think this is easily possible in
> maven. Because of transitive nature of dependencies, many times we end
> including multiple versions of same artifact/group combo.
>
> Is there any plugin that
On Tue, Jul 5, 2011 at 3:31 PM, Niranjan Rao wrote:
> I see lot of discussion using maven eclipse plugin to import the project
> in eclipse. I am wondering why we need to do this as m2eclipse seems to
> be working perfectly fine and works directly with pom file.
>
> So far, m2eclipse has worked fl
I see lot of discussion using maven eclipse plugin to import the project
in eclipse. I am wondering why we need to do this as m2eclipse seems to
be working perfectly fine and works directly with pom file.
So far, m2eclipse has worked flawlessly for me. Is there a preferred
plugin to use because of
Hi there,
Subject line is rather long, but I think this is easily possible in
maven. Because of transitive nature of dependencies, many times we end
including multiple versions of same artifact/group combo.
Is there any plugin that will dump the information if it sees multiple
versions of same ar
> We are currently using Spring Source Tool Suite 2.7.0.M02 that comes with
> m2eclipse 0.12. When our projects are initially imported into eclipse as
m2eclipse is an independent project and has its own set of lists
(user, dev, etc). Questions such as this should be sent there.
Wayne
---
> On Thu, Jun 30, 2011 at 12:45 AM, Sebastian Goldt wrote:
Sebastian, its been five days and no feedback.
Have you worked out your problem?
Has any of this thread been useful?
It would be nice from an archive perspective if you could comment on
your resolution so others can avoid this problem i
James-
is this the functionality
adding
...
to eclipse plugin.xml
?
http://www.eclipse.org/articles/Article-BuildingProjectFacets/tutorial.html#creating.basic.facets
Martin
__
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confid
Please create an issue for it. ping me back with the issue id and I'll
add it to the Backlog
On 4 July 2011 22:48, Christopher Cudennec wrote:
> Thanks Stephen, that was a quick answer :)
>
> Checking if the tag exists seems to be described by:
> http://jira.codehaus.org/browse/MRELEASE-572 and
>
Thanks Stephen, that was a quick answer :)
Checking if the tag exists seems to be described by:
http://jira.codehaus.org/browse/MRELEASE-572 and
http://jira.codehaus.org/browse/MRELEASE-165. I'd vote for these!
Unfortunately I could not find an issue for checking the release
repository. Do you
Hello maven users
We are currently using Spring Source Tool Suite 2.7.0.M02 that comes
with m2eclipse 0.12. When our projects are initially imported into
eclipse as "Import > Existing Maven Projects", some of the projects get
a java facet and some not. And I really have no clue, why some proje
correct. See MRELEASE-166 and other open issues in the release plugin
On 4 July 2011 22:07, Christopher Cudennec wrote:
> Hi everyone!
>
> I'd like to have some advice for using the Maven release plugin. As far as I
> understand the plugin does not check the SCM or the Maven repository before
> p
Hi everyone!
I'd like to have some advice for using the Maven release plugin. As far
as I understand the plugin does not check the SCM or the Maven
repository before performing a release. It will result in a failure if
either the tag already exists in the SCM or the version has already been
d
There is a well documented 10-step process that 2000 other projects have been
able to follow. The process[1] could probably be improved further, possibly
some IDE integration or a small webapp to help, but I don't think you can
categorize the current process as complicated. The process takes 30
I spotted this post over in the jmockit issues page:
http://code.google.com/p/jmockit/issues/detail?id=172
They seem to feel it's too hard to get artifacts into Maven Central.
Can anyone here comment on this?
Thanks
--
View this message in context:
http://maven.40175.n5.nabble.com/jmockit-in
On Sonar side :
+1 for Git (pretty well tested)
+0 for Mercurial (known open issue with the Sonar SCM Activity plugin :
http://jira.codehaus.org/browse/SONARPLUGINS-1157)
Freddy Mallet
www.SonarSource.org
www.SonarSource.com
---
Yes, but git gets more love ;-)
On 4 July 2011 14:07, Olivier Lamy wrote:
> Mercurial support works fine too :-) (at least for Apache Maven stack : no
> idea for eclipse )
>
> --
> Olivier
> Le 4 juil. 2011 13:52, "Stephen Connolly"
> a écrit :
>> Git
>>
>> On 4 July 2011 12:27, Peter Horlock w
Mercurial support works fine too :-) (at least for Apache Maven stack : no
idea for eclipse )
--
Olivier
Le 4 juil. 2011 13:52, "Stephen Connolly"
a écrit :
> Git
>
> On 4 July 2011 12:27, Peter Horlock wrote:
>> Hi!
>>
>> We are planning to move from SVN to either GIT or Mercurial.
>> What woul
The parent pom cannot be found, probably because it has never been
installed in your local repository. Go to you hello-world-application
directory and run 'mvn install'. (add the -N switch if you only want to
build the parent pom and not the modules).
Also in your parent pom, add a version num
Git
On 4 July 2011 12:27, Peter Horlock wrote:
> Hi!
>
> We are planning to move from SVN to either GIT or Mercurial.
> What would you recommend using?
> Which has the better Maven / Eclipse / Sonar Support?
>
> Thanks,
>
> Peter
>
Hi!
We are planning to move from SVN to either GIT or Mercurial.
What would you recommend using?
Which has the better Maven / Eclipse / Sonar Support?
Thanks,
Peter
The scope 'test' is not transitive. Therefore depending on ju-deps with
the scope test set on the junit dependency will not work in your case.
Guillaume
Le 1/07/2011 21:14, Luc De Graef a écrit :
Hello,
I have a problem with the import-scope& dependency management (Maven 3.0.3).
There are 3
21 matches
Mail list logo
