Hey,
I am upgrading the EAR plugin according to a nice patch that we've received
(MEAR-102). In order to ease the config, I have changed it a bit so that we
can use nested elements for the JBoss loader repository config.
I end with this in my POM:
build
plugins
plugin
same thing with the latest version btw (1.0-beta-3.0.5).
S.
On Sat, Feb 21, 2009 at 12:47 PM, Stephane Nicoll stephane.nic...@gmail.com
wrote:
Hey,
I am upgrading the EAR plugin according to a nice patch that we've received
(MEAR-102). In order to ease the config, I have changed it a bit so
oh yes, something like Violations Hudson plugin [1] for example would be a
great enhancement, since this would be on a central machine and give history.
Definitely helpful and should not be too complicated to add to existing CI
instances.
I'm not a Hudson expert, nor do I really know this
violations-Hudson-plugin is the way I'd go, it's written by peter
reilly over at ant.apache.org, and while he's a maven hater I can
usually bend his ear when the freestyle support is lacking
Sent from my [rhymes with myPod] ;-)
On 21 Feb 2009, at 12:13, Hervé BOUTEMY herve.bout...@free.fr
+1
Vincent
2009/2/21, Hervé BOUTEMY herve.bout...@free.fr:
oh yes, something like Violations Hudson plugin [1] for example would be a
great enhancement, since this would be on a central machine and give history.
Definitely helpful and should not be too complicated to add to existing CI
Hi,
seems like our fears have come true, Hudson just spit out the first
issue that seems to be caused by the introduction of the parallel
artifact resolution:
[java] java.util.ConcurrentModificationException
[java] at
Benjamin,
I suppose the result makes sense. In essence, Maven is becoming
multi-threaded. What about wrapping the LinkedHashMap instances with
Collections.synchronizedList()? Perhaps it is a natural progression of
Maven's stability: 2.0.9 introduced one LinkedHashMap, 2.0.10
converted them all,
I'll take a look but I'm generally in favor of using Maven to do these things
rather than duplicating the effort over again in Hudson specific config.
-Original Message-
From: Vincent Siveton [mailto:vincent.sive...@gmail.com]
Sent: Saturday, February 21, 2009 8:45 AM
To: Maven
maven still has to run checkstyle. the hudson plugin just captures the
results and trends them too
Sent from my [rhymes with myPod] ;-)
On 21 Feb 2009, at 15:00, Brian E. Fox bri...@reply.infinity.nu
wrote:
I'll take a look but I'm generally in favor of using Maven to do
these things
I just want to add that if the parallel resolution is delegating the
dependency managing to a shared object, it would make more sense to
synchronize the methods.
Paul
On Sat, Feb 21, 2009 at 8:09 AM, Paul Benedict pbened...@apache.org wrote:
Benjamin,
I suppose the result makes sense. In
2009/2/21, Brian E. Fox bri...@reply.infinity.nu:
I'll take a look but I'm generally in favor of using Maven to do these things
rather than duplicating the effort over again in Hudson specific config.
Using Checkstyle over the build or a Hudson plugin will have the same
result, ie notify
For 2.x.x you can't use the new container so we would have to patch
the branched version. Make a test case and I'll look at it.
On 21-Feb-09, at 6:59 AM, Stephane Nicoll wrote:
same thing with the latest version btw (1.0-beta-3.0.5).
S.
On Sat, Feb 21, 2009 at 12:47 PM, Stephane Nicoll
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
jason's recently posted
(http://mail-archives.apache.org/mod_mbox/incubator-general/200902.mbox/%3cea7c752b-2f67-4329-b0c5-35ccff853...@sonatype.com%3e)
a warning about tightening up release verification. i think that this
is generally a good thing. i
[WARNING] Error reading archetype catalog http://repo1.maven.org/maven2
org.apache.maven.archetype.source.ArchetypeDataSourceException: Error
parsing ar
chetype catalog.
at
org.apache.maven.archetype.source.CatalogArchetypeDataSource.readCata
log(CatalogArchetypeDataSource.java:202)
The Maven project has recently moved to a new repository within the
Apache infrastructure. The repository that was previously at:
http://people.apache.org/repo/m2-snapshot-repository is deprecated. All
new snapshots are being deployed to
http://repository.apache.org/snapshots . Note that this is
On 21-Feb-09, at 3:05 PM, Robert Burrell Donkin wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
jason's recently posted
(http://mail-archives.apache.org/mod_mbox/incubator-general/200902.mbox/%3cea7c752b-2f67-4329-b0c5-35ccff853...@sonatype.com%3e
)
a warning about tightening up
Jason van Zyl wrote:
If you create a set of binaries that have checksums and are signed it
doesn't much matter how you produced the release. I mentioned the Ant
tasks or using Maven itself as that's generally a good way to make a
release. We'll probably make something with Mercury to
17 matches
Mail list logo
