+1 on integrating it.
it's non intrusive and does what I would expect by default while
allowing me to override the behaviour for some plugins.
it makes my life easier as a maven user and also as a maven tools
developer (the netbeans ide itegration)
Milos
On Tue, Apr 15, 2008 at 10:48 PM, Hervé BO
There, now the branch and trunk use the same method for bootstrapping.
I added the build to Hudson and seems to be happy:
https://ci.sonatype.org/view/Maven%202.0.x/job/Maven-2.0.x-with-bootstrap/7/console
On 15-Apr-08, at 5:34 PM, Deepak Bhole wrote:
* Brian E. Fox <[EMAIL PROTECTED]> [2008-
* Brian E. Fox <[EMAIL PROTECTED]> [2008-04-15 17:55]:
> Yes. I should add it to the Hudson build to check it. Maybe jason will
> feel like rewriting it to use the ant tasks like he did for trunk
>
Ah okay, good to know.
In the mean time, I have found the issue that causes bootstrap.sh in
2.
Hi everyone,
I'd like to make a small change to the artifact version parsing. We currently
have several released projects that use a non-standard version scheme. So
instead of something like:
1.0.1-beta-1
we have
1.0.1.beta1
This was originally done to conform to the OSGi standard which req
I can look at that, it should be relatively easy.
On 15-Apr-08, at 2:55 PM, Brian E. Fox wrote:
Yes. I should add it to the Hudson build to check it. Maybe jason will
feel like rewriting it to use the ant tasks like he did for trunk
-Original Message-
From: Deepak Bhole [mailto:[EMA
Yes. I should add it to the Hudson build to check it. Maybe jason will
feel like rewriting it to use the ant tasks like he did for trunk
-Original Message-
From: Deepak Bhole [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 15, 2008 5:34 PM
To: Brian E. Fox
Cc: Maven Developers List
Sub
* Brian E. Fox <[EMAIL PROTECTED]> [2008-04-15 17:21]:
> Not many people are using the bootstrap on 2.0.x. Just grab 2.0.8 (or
> 2.0.9) and build it as a normal maven project.
>
>
Thanks, that worked. Are there plans to make bootstrap work again
though? I maintain the Maven package in Fedora, an
Not many people are using the bootstrap on 2.0.x. Just grab 2.0.8 (or
2.0.9) and build it as a normal maven project.
-Original Message-
From: Deepak Bhole [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 15, 2008 5:15 PM
To: dev@maven.apache.org
Subject: Maven 2.0.9 build failure
Hi,
I c
Hi,
I checked out the 2.0.9 tag from here:
http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.9
rm -rf'd ~/.m2, set M2_HOME to $PWD/build/apache-maven-2.0.9, and
ran ./bootstrap.sh. However, the build keeps failing:
--- BEGIN ---
Building project in /tmp/maven2-build/maven2/apach
another try...
the proposal is here:
http://docs.codehaus.org/display/MAVENUSER/POM+Element+for+Source+File+Encoding
I did the work on 2 plugins in a branch:
- jxr: http://svn.apache.org/viewvc?rev=645260&view=rev
- javadoc: http://svn.apache.org/viewvc?rev=645262&view=rev
As you can see, the cha
wow, I'm glad to see a happy user, who finds these tasks as useful as me :))
I only worked on bugfixes to improve their quality to the same level as Maven
core. AFAIK, Brett wrote most parts of them. Thanks Brett :)
Hervé
Le mardi 15 avril 2008, Jason van Zyl a écrit :
> Hervé,
>
> The ant task
Hervé,
The ant tasks are great. I just finished getting the bootstrap in
trunk using them and they radically simplified the build.xml file. I
can now sort of read it again. The transitions was easier then I
thought using a POM. I have setup the 2.1 bootstrap using Hudson and
all appears t
Ok i now see what problems are.
2008/4/15, Raphaël Piéroni <[EMAIL PROTECTED]>:
> 2008/4/15, Brett Porter <[EMAIL PROTECTED]>:
>
> > I found a regression in :generate -
> > 1) the default (15) is no longer present
>
> This is not intended.
This is a side effect of the new version of the interna
On Tue, Apr 15, 2008 at 4:06 AM, Vincent Siveton
<[EMAIL PROTECTED]> wrote:
> Hi Carlos,
>
> 2008/4/14, Carlos Sanchez <[EMAIL PROTECTED]>:
>
> > btw the problem is not just let's make the repo work for maven as
> > there are other consumers out there, ie. Equinox provisioning, that
> > may li
I no longer understand this thread.
Brett, can you please provide the output that cause you the problem,
for me to be sure not to answer something stupid.
The only problem, i can see is when the plugin provides a default
value which is not desirable for the user.
And as the default value mechani
Vincent Siveton wrote:
Hi,
Background:
Trying to mavenize an Eclipse Plugin project, I got error messages
like the following:
Couldn't find a version in [1.0.0-v20070606] to match range [1.0.0,2.0.0)
I put in jira a test project to reproduce this error [1].
Discussions:
After some investigation
>> 2) it no longer prompts for the groupId/etc - it goes straight to using
>> some default settings
>This is partially intended.
>the plugin now provides default for all values and
>should ask for confirmation if everithing is correctly set.
I think this is more confusing. What was the problem
2008/4/15, Brett Porter <[EMAIL PROTECTED]>:
> I found a regression in :generate -
> 1) the default (15) is no longer present
This is not intended.
> 2) it no longer prompts for the groupId/etc - it goes straight to using
> some default settings
This is partially intended.
the plugin now provide
Hi Carlos,
2008/4/14, Carlos Sanchez <[EMAIL PROTECTED]>:
> btw the problem is not just let's make the repo work for maven as
> there are other consumers out there, ie. Equinox provisioning, that
> may like to use the repo as a source and if you change their metadata
> to adjust it to maven it
Hi Micah,
2008/4/14, Micah Hainline <[EMAIL PROTECTED]>:
> Hey Vincent, the qualifiers in the release versions of the Eclipse plugins
> are better off stripped out of the repositories in my opinion. Every release
> version of the Eclipse platform should have the incremental version number
> in
I found a regression in :generate -
1) the default (15) is no longer present
2) it no longer prompts for the groupId/etc - it goes straight to
using some default settings
Is that intended?
I did find a bad license header here: archetype-common/src/test/java/
org/apache/maven/archetype/test/I
21 matches
Mail list logo
