Did the MNG-3586 is allready fixed or fix is delayed ?
I got this mail :
-
Jason van Zyl updated MNG-3586:
---
Fix Version/s: (was: 2.1-alpha-1)
2.1-alpha-2
--
Very annoying bug for those of us using m2eclipse 0.9.4 and
Here's some tips for folks trying to debug Maven/Plexus/Plugins in Eclipse.
Using m2e you can actually debug/execute plugin _inside_ Eclipse. That means
the plugin executes from the workspace in-situ. Extremely handy.
I was just looking at this Henri - though I'm not longer able to
compile the provided test project so it's impossible to test.
Can you review the project to help make it reproducible?
Thanks,
Brett
On 04/07/2008, at 5:12 PM, Henri Gomez wrote:
Did the MNG-3586 is allready fixed or fix is
2008/7/4 Brett Porter [EMAIL PROTECTED]:
I was just looking at this Henri - though I'm not longer able to compile the
provided test project so it's impossible to test.
Can you review the project to help make it reproducible?
Done.
Redone the test with m2eclipse 0.9.4 (using embedded)
From
On 04/07/2008, at 3:40 AM, John Casey wrote:
Not to distract from the higher-level discussion, but I'd like to
get into the nuts and bolts of MARTIFACT-25 a bit...in case someone
beats me to it.
We introduced a properties file that tracks resolution attempts for
artifacts that weren't
Are you dropping new files into the local repository or integrating
this as part of the metadata? Do these files only work locally?
Also in the case of 2.1 we should also consider just not allowing the
state where there is no POM. Consider the artifact not complete
without a POM.
On
John - are you looking into this? Need it resolved for MNG-3185
Thanks,
Oleg
Brett Porter wrote:
On 04/07/2008, at 3:40 AM, John Casey wrote:
Not to distract from the higher-level discussion, but I'd like to get
into the nuts and bolts of MARTIFACT-25 a bit...in case someone beats
me to
As part of getting adequate coverage for vetting, I have just asked
Nigel and Justin who watch over the Hudson instance here at Apache to
setup the Maven jobs we require for validation. They are running on
Solaris which will be a good compliment to what we have running at
Contegix.
Hi
Maven 2.0.9 has corrected classpath order, direct dependencies are first
(and suborder is among declared entries). I think that thanks this very
hopefilly improvement (bugfix imho ;)) maven eclipse plugin doesn't have to
sort classpath. Generated .classpath should sorted entries amond order in
Just a couple of comments...
code.apt:
~~ * Using SVN properties like \$Id: \$ = Is it a wanted goal for all
files like java or apt?
I think this is helpful, though maybe optional. I don't really think
it's good for the @version tag in Javadoc though.
* Indentation: Always use 2 space
10 matches
Mail list logo
