It's up now. The last build with these changes failed though, but it's
when jaring one of the modules. I can't trigger a manual build so I
can't tell if it was a hiccup or what.
/Anders
On Mon, Sep 3, 2012 at 3:13 AM, Jason van Zyl wrote:
> I just committed support for JSR330 components in exten
I just committed support for JSR330 components in extensions and plugins. It's
building fine on my CI machine and the ITs work, and I'm trying on the official
grid but builds.apache.org appears to be down[1]. I'll check in the morning,
but if there are any problems feel free to roll back. I can'
will do
Thanks Wayne!
Martin Gainty
__
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbe
I'm willing to do the branch homework once the dust settles.
On Sun, Sep 2, 2012 at 7:30 PM, Chris Graham wrote:
> +1 for a branch.
>
> Sent from my iPhone
>
> On 03/09/2012, at 6:22 AM, Mark Struberg wrote:
>
>> This opens up another can of worms: how to deal with plugins which cannot be
>> ma
+1 for a branch.
Sent from my iPhone
On 03/09/2012, at 6:22 AM, Mark Struberg wrote:
> This opens up another can of worms: how to deal with plugins which cannot be
> made maven2 compatible anymore but we like to implement a new feature? How
> long do we like to support maven2 at all? Will we
We solved 4 issues:
** Bug
* [MSHADE-103] - maven-shade-plugin does not resolve from
user-defined repositories
* [MSHADE-124] - Need better plan for getting
dependency-reduced-pom.xml out of basedir
* [MSHADE-130] - Mark mojo as threadSafe for parallel builds
** New Feature
* [MSH
Hervé
~/asf/mvn/plugins/maven-shade-plugin/ /opt/apache-maven-3.0.4/bin/mvn
release:prepare -Psigned_release
[INFO] Scanning for projects...
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project
org.apache.maven.plugins:maven-shade-plugin:2.1-SNAPSHOT
(/Users/benson/
OK, please consider this VOTE cancelled and I'll make a new one presently.
On Sun, Sep 2, 2012 at 5:52 PM, Hervé BOUTEMY wrote:
> Le dimanche 2 septembre 2012 17:22:20 Benson Margulies a écrit :
>> Would you prefer if I respun the release?
> yes, I think this would be sufficient
>
> -
Le dimanche 2 septembre 2012 17:22:20 Benson Margulies a écrit :
> Would you prefer if I respun the release?
yes, I think this would be sufficient
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands,
On Sun, Sep 2, 2012 at 5:12 PM, Hervé BOUTEMY wrote:
> Le dimanche 2 septembre 2012 16:17:33 Benson Margulies a écrit :
>> Now we have a different problem.
>>
>> According to [1], the version to require Maven 3 was supposed to be
>> 3.0, leaving 2.0 for a merely incompatible release that still wor
Le dimanche 2 septembre 2012 16:17:33 Benson Margulies a écrit :
> Now we have a different problem.
>
> According to [1], the version to require Maven 3 was supposed to be
> 3.0, leaving 2.0 for a merely incompatible release that still worked
> with Maven 2.2.
>
> Folks, what's the story? Do I ne
On Sun, Sep 2, 2012 at 4:22 PM, Mark Struberg wrote:
> This opens up another can of worms: how to deal with plugins which cannot be
> made maven2 compatible anymore but we like to implement a new feature? How
> long do we like to support maven2 at all? Will we create a branch for those
> plugin
This opens up another can of worms: how to deal with plugins which cannot be
made maven2 compatible anymore but we like to implement a new feature? How long
do we like to support maven2 at all? Will we create a branch for those plugins?
LieGrue,
strub
- Original Message -
> From: Ben
Now we have a different problem.
According to [1], the version to require Maven 3 was supposed to be
3.0, leaving 2.0 for a merely incompatible release that still worked
with Maven 2.2.
Folks, what's the story? Do I need to blow this up and try again as
3.0? Will someone fix what Hervé points to?
Sorry, I'm -0 about this: the plugin requires Maven 3 but uses an "old"
dependency-tree which is not really Maven 3 compatible
I updated the dependency in r1379995
Notice I manually removed extra directories in staging site
Regards,
Hervé
Le vendredi 31 août 2012 18:00:45 Benson Margulies a é
> Devs
> I found jspc-compiler-tomcat6 was missing plugin.xml when testing today here
> is the signature
>
> org.codehaus.mojo.jspc
> jspc-compiler-tomcat6
> 2.0
..
> The jspc-tomcat6 source is missing plugin.xml and needs compile goal
> code in the Impl class..I need someone to review a
16 matches
Mail list logo