Hi,
Its regarding identifiyng the plugin name.
We are using Maven in my project. i have small doubt.
I need to identify the "aspectj-maven-plugin" if we are using in our project.
if it is found then we need to project nature according to that.
Can you please let me know where i can
+1
-Deng
Arnaud HERITIER wrote:
+1
Arnaud
On 19/05/07, Vincent Siveton <[EMAIL PROTECTED]> wrote:
Thanks Carlos!
Here is the staging site:
http://people.apache.org/~vsiveton/maven-ant-plugin/
Here is my +1
Cheers,
Vincent
2007/5/18, Carlos Sanchez <[EMAIL PROTECTED]>:
> install plugin h
+1 also
arnaud
On 21/05/07, Brett Porter <[EMAIL PROTECTED]> wrote:
+1, looks right to me.
Some of the directories probably aren't necessary in a future release
(meeper, design, etc), but works for this one.
- Brett
On 19/05/2007, at 10:15 AM, Wendy Smoak wrote:
> I'd like to release a bui
+1
Arnaud
On 19/05/07, Vincent Siveton <[EMAIL PROTECTED]> wrote:
Thanks Carlos!
Here is the staging site:
http://people.apache.org/~vsiveton/maven-ant-plugin/
Here is my +1
Cheers,
Vincent
2007/5/18, Carlos Sanchez <[EMAIL PROTECTED]>:
> install plugin has been released, so vote starts ag
Why is that needed? Will it still work on Windows?
On 22/05/2007, at 12:56 AM, [EMAIL PROTECTED] wrote:
Author: evenisse
Date: Mon May 21 07:55:57 2007
New Revision: 540158
URL: http://svn.apache.org/viewvc?view=rev&rev=540158
Log:
Fix eol
Modified:
maven/release/trunk/maven-release-manag
Using the manual resolution would only work if an earlier step in the
release:prepare process had definitely built all the dependencies.
However, there is an alternative: you can combine the reactor
projects (which you should have), with the artifacts returned from
manual resolution (and us
It seems more that you'd need to change the code that is relying on
the isSnapshot result from the wrong directory?
On 21/05/2007, at 10:32 PM, Mark Hobson wrote:
Hi there,
I'm wondering what the best approach is to fix MNG-2994 [1]. The
problem appears to be that the RepositoryMetadata imp
"But more importantly, it helps identify your dependency jars as
described in the proposal. In my experience this is a large percentage
of the conversion work for most projects."
I completely agree. This piece alone would be very handy.
--
Addendum,
During my holydays, i coded points 1, 2, 3, 4
I just committed today.
Raphaël
2007/5/14, Raphaël Piéroni <[EMAIL PROTECTED]>:
Hi,
Based on a previous email in which i said i saw the current revision
(r4054) of
archetypeng as the first alpha.
I have schedules the above features in:
-
Hi,
So the long answer
2007/5/21, Brett Porter <[EMAIL PROTECTED]>:
This is mostly for Raphaël, but also anyone else interested in
Archetype dev.
So, as I understand it:
- maven-archetype-1.0.x branch is no longer needed (this was for the
alpha series releases before the re-arrangement / refa
On 01/02/07, Brett Porter <[EMAIL PROTECTED]> wrote:
Edwin - can we double check the requirement here. I recently removed
this to prevent the problem of it failing if you haven't installed
the project first.
I was planning to reintroduce @requiresDependencyResolution test on
release:prepare to
ARCHETYPE-38 is not in archetypeng for what I could see
And it doesn't build for me on windows, attached is the log
Tests in error:
testGenerateArchetypeCompleteWithoutParent(org.codehaus.mojo.archetypeng.generator.DefaultArchetypeGeneratorTest)
testGenerateArchetypeSite(org.codehaus.mojo.arch
I'd like to get a discussion going on how to tackle the documentation
present on the site.
:: Javadoc distribution and role ::
I'm a firm believer that the javadoc for a project should be versioned
and always available, even for back versions.
If we use http://jakarta.apache.org/commons/collec
>>> I'm looking for others that are interested in working with or using
>>> this - thoughts?
I would be interested using the dependency discovery from md5 feature
(currently have a need for this.)
-
To unsubscribe, e-mail: [
+1
Arnaud
On 20/05/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
+1
Stéphane
On 5/18/07, Lukas Theussl <[EMAIL PROTECTED]> wrote:
> We discovered two rather severe issues in plugins bundled in
> Maven-1.1-RC1 which are fixed and I would like to include the updated
> plugins in 1.1-final (to
Hi there,
I'm wondering what the best approach is to fix MNG-2994 [1]. The
problem appears to be that the RepositoryMetadata implementation for
an artifact directory itself returns false for isSnapshot. The code
states that this is done since version information is below this
metadata, which is
On 5/21/07, Vincent Siveton <[EMAIL PROTECTED]> wrote:
Hi,
Since plexus-utils:1.4.2 is out, bump to it instead of snapshot.
Ok.
Can I convince someone to create versions in the PLXUTILS components :)
I didn't know it was cut.
--
Brett Porter a écrit :
On 21/05/2007, at 5:33 PM, Jason Dillon wrote:
Sounds helpful... though I'm kinda wondering what it would produce for
trivial and non-trivial ant and m1 projects. I'm not really sure how
such a tool could really figure out the right way to implement the m2
build...
On 21/05/2007, at 5:33 PM, Jason Dillon wrote:
Sounds helpful... though I'm kinda wondering what it would produce
for trivial and non-trivial ant and m1 projects. I'm not really
sure how such a tool could really figure out the right way to
implement the m2 build...
Well, it's definitely
Like Jason, I think it would be very helpful, but I would like to see the
extent that it can convert an ant script to a maven 2 project. I've written
and seen some very hairy ant scripts and I wonder how much this would
correctly pull from them.
Converting maven 1 projects to maven 2 is definite
Sounds helpful... though I'm kinda wondering what it would produce
for trivial and non-trivial ant and m1 projects. I'm not really sure
how such a tool could really figure out the right way to implement
the m2 build...
--jason
On May 21, 2007, at 12:15 AM, Brett Porter wrote:
Hi all,
Hi all,
DevZuz have developed some tools for build conversion as part of the
Maestro project and for internal use. If it is desired, we would now
like to donate that to the Maven project for others to enhance and re-
use. It would find a place both as an independent toolkit, and as an
Arch
On 21/05/2007, at 4:56 PM, Raphaël Piéroni wrote:
Quick answer, will answer in depth after work.
Cool, np.
I didn't fork from a revision, but rewrite from scratch.
So, are there changes on trunk that we should be reviewing to make
sure they also found their way into NG? Surely some of
23 matches
Mail list logo
