Happy to do so...How do I get a login for Jira?
--
Robert Patrick
VP, FMW Architects Team: The A-Team
Oracle Corporation Office: +1.940.725.0011
1148 Triple Crown Court Fax: +1.940.725.0012
Bartonville, TX 76226, USA Mobile: +1.469.556.9450
Please file a JIRA ticket if you think something is wrong/could be improved!
/Anders
On Fri, Sep 20, 2013 at 8:18 AM, Robert Patrick
wrote:
> I figured it out. It appears that in order to get the -Dparam=value to
> work, you *must* specify the @Parameter annotation's "property" element.
> Is
I figured it out. It appears that in order to get the -Dparam=value to work,
you *must* specify the @Parameter annotation's "property" element. Is this
expected behavior?
If so, the javadocs at
http://maven.apache.org/plugin-tools/maven-plugin-annotations/apidocs/org/apache/maven/plugins/a
It appears that the behavior for Maven plugins change depending on whether they
use Javadoc-style annotations or Java annotations. With a plugin that uses
Javadoc annotations, I can execute a plugin goal directly from the command-line
and use -Dparam=value to pass in the configuration parameter
Herve; I added the dependency to the parent pom to the docs.
Jason: In the current project I'm working with, I get the following timings:
mvn -o -T 4 clean install : 53 seconds
mvn -o clean install : 50 seconds
mvn -DskipTests -o -T 4 clean install : 14.1 seconds
mvn -DskipTests -o clean install
Seemingly it does.. a release together with the 3.1.1 release of Maven
would be great.
manfred
> I will if it takes 60 days to create a Git repo.
>
> On Sep 19, 2013, at 4:47 PM, Olivier Lamy wrote:
>
>> Maybe can be release from svn.
>>
>> On 13 September 2013 14:05, Manfred Moser
>> wrote:
>>
I will if it takes 60 days to create a Git repo.
On Sep 19, 2013, at 4:47 PM, Olivier Lamy wrote:
> Maybe can be release from svn.
>
> On 13 September 2013 14:05, Manfred Moser wrote:
>> Hi!
>>
>> With the 3.1.1 release of Maven coming up hopefully soon I would like to
>> move forward with th
Maybe can be release from svn.
On 13 September 2013 14:05, Manfred Moser wrote:
> Hi!
>
> With the 3.1.1 release of Maven coming up hopefully soon I would like to
> move forward with the plugin testing harness using it as well. Jason fixed
> it to work with 3.0 and requested the repo to be moved
ah ok, staging to http://maven.staging.apache.org/
no, this url is for CMS staging only, which does not contain/support component
included sites: see http://maven.staging.apache.org/ref/ for example, which
does not exist. In fact, everything from extpaths.txt isn't published in CMS
staging sit
A button on the CMS page that says "Staging Site" and it produces a standard
URL for a staging site that can be used for all core releases.
On Sep 19, 2013, at 1:19 PM, Hervé BOUTEMY wrote:
> what do you call "a standard staging location"?
> what more automation do you expect?
>
> Le jeudi 19
what do you call "a standard staging location"?
what more automation do you expect?
Le jeudi 19 septembre 2013 11:02:46 Jason van Zyl a écrit :
> Do you think we can make a small addition to have it publish to a standard
> staging location? Is that hard to add to the tool? Would help us reach a
>
Sent from my HTC One™ X, an AT&T 4G LTE smartphone
- Reply message -
From: "Jason van Zyl"
To: "Maven Developers List"
Subject: [VOTE] Release Maven 3.1.1
Date: Thu, Sep 19, 2013 7:30 PM
Are you just manually copying that or is there an option on the CMS to make the
staging site?
O
Sent from my HTC On kme™ X, an AT&T 4G LTE smartphone
- Reply message -
From: "Jason van Zyl"
To: "Maven Developers List"
Subject: [VOTE] Release Maven 3.1.1
Date: Thu, Sep 19, 2013 7:30 PM
Are you just manually copying that or is there an option on the CMS to make the
staging site?
Each circle is a project in a multi-project build (I think we need to clean up
our terminology, I stopped saying multi-module built so I don't have to explain
the difference between a module and project).
Kristian is correct it's the depth from the root project. Everything on level 1
can be bui
I'm making a small tool to validate the distro. I don't want to do this
manually anymore :-)
On Sep 19, 2013, at 7:14 AM, Stephen Connolly
wrote:
> Jason, are you going to cast your vote on this?
>
>
> On 17 September 2013 16:39, Jason van Zyl wrote:
>
>> Hi,
>>
>> Maven Core ITs are good
Do you think we can make a small addition to have it publish to a standard
staging location? Is that hard to add to the tool? Would help us reach a state
of more automation.
I'll follow those steps for the time being.
On Sep 19, 2013, at 10:19 AM, Hervé BOUTEMY wrote:
> it does not use CMS
>
ok, thanks you for the update, I'm starting to see
"Maven calculates this graph based on declared inter-module dependencies for a
multi-module build"
IIUC, dependency graph contains both explicit dependencies (in pom
dependencies section) and implicit dependencies got from parent
this would expl
it does not use CMS
I split the instructions in 2 parts to make things as clear as possible:
1. mvn -Preporting site site:stage
= local HTML generation and staging of multiple modules into one local staging
area
2. mvn scm-publish:publish-scm
publish local staging area to website svn area, which
I suppose each circle is a module
but I don't understand what the levels are, and how modules are dispatched
into levels
Regards,
Hervé
Le jeudi 19 septembre 2013 18:36:49 Kristian Rosenvold a écrit :
> Jason sent me some questions about the parallel build that included a
> real nice figure. Si
Good question ;)
I did a minor update to the wiki, adding something like:
Each node in the graph represents a module in a multi-module build,
the "levels" simply indicate the distance to the first module in the
internal reactor dependency graph.
Kristian
2013/9/19 Hervé BOUTEMY :
> I suppose
Jason sent me some questions about the parallel build that included a
real nice figure. Since I'm a sucker for nice figures (especially
those that others make!), I quickly updated the wiki page with this,
and added some docs to describe his figure.
https://cwiki.apache.org/confluence/display/MAVEN
Jason, are you going to cast your vote on this?
On 17 September 2013 16:39, Jason van Zyl wrote:
> Hi,
>
> Maven Core ITs are good, and the license/notice issue has been resolved so
> I'm rolling 3.1.1 again.
>
> Here is a link to Jira with 6 issues resolved:
>
> https://jira.codehaus.org/secur
Hi,
This is preventing us from running code coverage on our macs...
Can anyone confirm whether this is a bug or whether I am missing something?
cheers,
David
Are you just manually copying that or is there an option on the CMS to make the
staging site?
On Sep 18, 2013, at 10:18 PM, Hervé BOUTEMY wrote:
> I didn't have time to test this release for the moment
>
> but I updated a few days ago Maven core release instructions [1] to stage
> core
> ref
After some experimentation I still couldn't detect any errors showing up,
however, I did remember I noticed some strange anomalies after using
dependency:purge-local-repository the other day - where that goal seems to
delete all the local artifacts, doesn't clean up any of the meta-data files in
25 matches
Mail list logo
