On 11 Mar 2013, at 21:28, Thomas Koch wrote:
> Stuart McCulloch:
>> Perhaps you could post a link to your re-packaging build so people can
>> recreate the issue? There's not enough information here to debug the
>> problem remotely.
>
> http://anonscm.debian.org/gitweb/?p=pkg-java/maven-plugin-
>
Stuart McCulloch:
> Perhaps you could post a link to your re-packaging build so people can
> recreate the issue? There's not enough information here to debug the
> problem remotely.
http://anonscm.debian.org/gitweb/?p=pkg-java/maven-plugin-
tools.git;a=tree;hb=refs/heads/update_to_3.2
The build w
They dont seem to be published on the site. I'll see if I can add it
to the site and
get it out there; but it might be a few days. Use the source code in
the mean time.
Kristian
2013/3/11 Grzegorz Słowikowski :
> Hi
>
> I'm looking for surefire-api javadocs url.
> Found http://maven.apache.org/s
The Maven team is pleased to announce the release of the Maven
Surefire Plugin, version 2.14
Please note the introduction of the "forkCount" parameter and check
the docs for this; a few of the settings relating to parallel forks
have changed slightly:
http://maven.apache.org/surefire/maven-surefi
Anyone? :-)
Best regards,
Eric
Hi
I know a lot has been written about skinny WARs and the problems they represent.
The strategy that we're using is:
- Set dependencies in the web module to scope 'provided', except dependencies
that are web-specific (PrimeFaces, ..
Hi
I'm looking for surefire-api javadocs url.
Found http://maven.apache.org/surefire/surefire-api/apidocs/index.html
(referenced from http://maven.apache.org/surefire/surefire-api/index.html)
but it's not valid.
Where is the valid one (for latest 2.14 version)?
Thank you in advance.
Grzegorz Sl
On 8 Mar 2013, at 16:54, Thomas Koch wrote:
> Thomas Koch:
>> [DEBUG] Using 0 mojo extractors.
>
> I could track down the problem. The field "mojoDescriptorExtractors" in the
> DefaultMojoScanner class is not filed by plexus with the available extractors
> although they should be available on
+1.
If you speak about mvn deploy, using settings.xml is the way to go.
Have a look here: http://maven.apache.org/guides/mini/guide-encryption.html
Cheers
Le 11 mars 2013 02:39, "Doug Douglass" a écrit :
> On Sun, Mar 10, 2013 at 6:24 PM, Martin Gainty
> wrote:
> >
> > > From: guido.martin.lar
Hi,
That is true that Maven 3 will now deploy timestamped snapshots
irrespective of the pom settings.
Note that if you use a repo manager, like you say you do, this should not
be an issue. I suppose there's a configurable system like in nexus to clean
old snapshots?
About updateAlways, I never use
