I've started my second attempt to generify the API, using call hierarchy to
check how collections are used in code.
I still don't know how to handle this buildFromRepository method :
Considering the current remote-resource-plugin releases will wail with a
ClassCastException I'd like to remove the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
thanks for your answer...
absolutely everybody having large maven projects is
annoyed by maintaining the versions in all the poms.
Are you using the release plugin?
Nope! I tried it and came to the point that is no good for me.
Are you using the release plugin?
Nope! I tried it and came to the point that is no good for me.
I also had a discussion with the developers long time ago
and filed some feature request. Anyhow I still think this
is the wrong approach for me.
Can you give more details about what doesn't
On May 9, 2009, at 7:42 PM, Brian Fox wrote:
On Sat, May 9, 2009 at 5:44 PM, Joerg Hohwiller jo...@j-
hohwiller.dewrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
absolutely everybody having large maven projects is
annoyed by maintaining the versions in all the poms.
Are
On Sun, May 10, 2009 at 3:09 PM, Joerg Hohwiller jo...@j-hohwiller.dewrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You can use dependency management or properties to deal with omitting
the
dependencies. I personally never assume what will be contained in a
reactor
and
On 9-May-09, at 10:49 PM, Brett Porter wrote:
Hi,
Can someone clear up what the current state of trunk, particularly
in regard to the MNG-2766 branch where all the work is happening at
the moment? Is everything from trunk in there now, or are there two
streams of dev? I thought I had
On 10-May-09, at 8:05 AM, nicolas de loof wrote:
I've started my second attempt to generify the API, using call
hierarchy to
check how collections are used in code.
Nicolas this is not the way to learn the code and help.
Pick a particular problem and learn a part of the code base.
I just was not aware John was creating a RC when I committed into core. My
current issue with core is that from a plugin developer point of view it is
really hard to use as too many untyped List are used, and there is no
Javadoc to explain what is expected. buildFromRepository() is typically one
I agree that this (lack of generics) can be a problem, but concur that it's
not the most pressing thing, particularly with 3.x looming ahead. Fixing
bugs in 2.x would serve the users far more and once 3.x stabilizes, then we
can add generics if they aren't there yet.
On Sun, May 10, 2009 at 3:48
It's time to start looking at the problems with the current 2.x resolution
scheme as it specifically relates to repository declaration and discovery.
I've created the start of a document at [1]. This should be the place to
gather feedback and use cases that will help drive towards a more complete
10 matches
Mail list logo
