To solve this, it seems I need to publish a SNAPSHOT. When I try this:
mvn clean deploy -Prelease
It fails with:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.3:single (default) on
project commons-vfs2: Error reading assemblies: No assembl
y descriptors found. -
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-vfs2-sandbox has an issue affecting its community integration.
Thi
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-proxy-test has an issue affecting its community integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-graph has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-digester3 has an issue affecting its community integration.
This i
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-exec-test has an issue affecting its community integration.
This i
Perhaps classscan? :)
On Sat, May 19, 2012 at 5:38 PM, Christian Grobmeier
wrote:
> On May 19, 2012 10:13 PM, "Gary Gregory" wrote:
>>
>> A one component test drive seems reasonable.
>
> +1
> Not everybody is fluent with git. One component gives us the chance to
> document some best practices.
On May 19, 2012 10:13 PM, "Gary Gregory" wrote:
>
> A one component test drive seems reasonable.
+1
Not everybody is fluent with git. One component gives us the chance to
document some best practices.
Maybe it would be good to start with a sandbox comp. But i am afraid those
are not active enoug
A one component test drive seems reasonable.
Gary
On May 19, 2012, at 4:08, Luc Maisonobe wrote:
> Le 16/05/2012 15:41, Jochen Wiedmann a écrit :
>> Well, with our multitude of projects, it might make sense to ask for
>> one or two of them
>> being migrated, so that we gather the experience. (I
+1 on trying it out on a single component.
-Adrian
On 5/19/2012 9:08 AM, Luc Maisonobe wrote:
Le 16/05/2012 15:41, Jochen Wiedmann a écrit :
Well, with our multitude of projects, it might make sense to ask for
one or two of them
being migrated, so that we gather the experience. (I've got none
Le 16/05/2012 15:41, Jochen Wiedmann a écrit :
> Well, with our multitude of projects, it might make sense to ask for
> one or two of them
> being migrated, so that we gather the experience. (I've got none so
> far.) Would anyone
> volunteer for the job of being involved?
I was wondering if we sho
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-jmx has an issue affecting its community integration.
T
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-scxml-test has an issue affecting its community integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-id has an issue affecting its community integration.
This issue af
14 matches
Mail list logo