I found the bug in the modello plugin that was breaking /any/ build
using modello in multi-modules; and I'm fairly sure the same kind of
issue will be found elsewhere:
Quite simply the mojo's use plexus components that are singletons but
the mojos themselves contain per-request mutable state
Do we have any top-level jira for thread-safety and // build issues ?
I myself got failures in // build with AspectJ plugin
2010/4/12 Kristian Rosenvold kristian.rosenv...@gmail.com
I found the bug in the modello plugin that was breaking /any/ build using
modello in multi-modules; and I'm
I figured I'd make individual issues on the plugins and commit the
fixes, the plugin issues I've found so far are
reasonably small and I do not see the need for a high-level issue. (As
long as it's trivial stuff I'll just
make these commits without further ado).
We might need some kind of way
Hi,
I am now using Maven as my new project's build process tool.
My company is using an issue tracker application which is not support by
maven-changes-plugin.
But I really want to use maven-changes-plugin to generate issue list.
Could any people familiar with maven-change-plugin give me some
+1
Emmanuel
On Sat, Apr 10, 2010 at 1:40 PM, Jason van Zyl ja...@sonatype.com wrote:
Hi,
This was simply to bump the default source/target to 1.5. I don't want
3.0-beta-1 released requiring people to set these as they should be defaults
now.
Staging repo:
All,
I have a multi module project where I have only two modules. Every thing
works fine like build, install, etc. However I have problem while
deploying the artifact into my snapshot repository. I'm hosting
artifactory as my organization repository and every thing is perfect
from the
Would it make more sense to reject running // build or fallback to
sequential execution (with a warning) if any of the mojos bound to
lifecycle is NOT marked as thread safe? Personally, I'd hate to have
intermittent build failures.
--
Regards,
Igor
Kristian Rosenvold wrote:
I found the bug in
On 4/12/10 9:29 AM, M Muthukumaran wrote:
All,
I have a multi module project where I have only two modules. Every thing
works fine like build, install, etc. However I have problem while
deploying the artifact into my snapshot repository. I'm hosting
artifactory as my organization
+1
This will save me quite a bit of time and frustration in the future...
On 4/10/10 7:40 AM, Jason van Zyl wrote:
Hi,
This was simply to bump the default source/target to 1.5. I don't want
3.0-beta-1 released requiring people to set these as they should be defaults
now.
Staging repo:
Non-binding +1
Many, many trees will be saved from this simple change.
Tim
On Mon, Apr 12, 2010 at 9:46 AM, John Casey jdca...@commonjava.org wrote:
+1
This will save me quite a bit of time and frustration in the future...
On 4/10/10 7:40 AM, Jason van Zyl wrote:
Hi,
This was simply to
Hi John,
Author: jdcasey
Date: Mon Apr 12 19:44:10 2010
New Revision: 933380
URL: http://svn.apache.org/viewvc?rev=933380view=rev
Log:
[MJAVADOC-280] Fixing IT from previous work, adding support for
javadoc-resource bundles that allow non-source javadoc configs and resources to
be aggregated
Yup was thinking about that too. I'll have to go revamp the @since
versions, but I think it's definitely a good idea.
-john
On 4/12/10 3:52 PM, Benjamin Bentmann wrote:
Hi John,
Author: jdcasey
Date: Mon Apr 12 19:44:10 2010
New Revision: 933380
URL:
Is there any info on how to get report generation to work using m3?
(when I generate a site using 3.0-alpha-7 none of the reports get
generated - either then *standard* reports from
maven-project-info-reports-plugin or anything defined in the
reporting section)
Thanks
Niall
13 matches
Mail list logo
