yes, it's time for release: I'll do it
thank you for your great help on this one
regards,
Hervé
Le lundi 28 décembre 2020, 19:14:54 CET abra...@gmail.com a écrit :
> Hi community,
>
>
>
> Are there any plans about release of 3.2.0 version of Maven EAR Plugin?
>
>
>
> It feels like there a
Hi Karl,
> I will take a look within the next two weeks so I can create a new release ...
That would be great. Thank you.
Regards,
Marat Abrarov.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional comman
Hi,
On 29.10.19 17:10, abra...@gmail.com wrote:
Hi community,
Does anybody know plans on release of Maven EAR Plugin (3.0.2+, i.e. next
version)? If there is an open resource where release plan / schedule can be
found then I appreciate if smbd could point it.
First to say. This is an open so
Thank you!
Maciej
2014-05-21 16:32 GMT+02:00 Jason Pyeron :
> > -Original Message-
> > From: Maciek Karas
> > Sent: Wednesday, May 21, 2014 6:47
> >
> > Hi.
> >
> > I found bug or at least missing feature in maven ear plugin.
> > I tried to
> > submit it in JIRA http://jira.codehaus.org/
> -Original Message-
> From: Maciek Karas
> Sent: Wednesday, May 21, 2014 6:47
>
> Hi.
>
> I found bug or at least missing feature in maven ear plugin.
> I tried to
> submit it in JIRA http://jira.codehaus.org/browse/MEAR but I
> don't have account there.
To create an account http:/
Hi,
Yes it's failing with 2.2.1 on MacOS as well. I vaguely remember that some
plexus dependencies could not be upgraded to a certain version with Maven
2.x. I can see that plexus-utils was moved to 3.0 and I am sure there was
some incompatibility issue back then.
I am a bit puzzled by the issue
Hi
Okay, so my initial finding turned out to be wrong. This is actually a
good thing, because OS-dependent bugs are a pain to track down and
shouldn't really exist in our Java eco-system.
The IT fails when run with Maven 2.2.1 and succeeds when run with Maven
3.0.4, consistently on both Ubuntu *a
I'll have a closer look at it in a little while.
On 2012-02-09 06:59, Stephane Nicoll wrote:
> Anyone? Or I'll have to install a VM with ubuntu on it but I guess this
> shouldn't take too long to spot.
>
> If that's a bug in plexus, I can revert the feature and reopen the related
> issue until we
Anyone? Or I'll have to install a VM with ubuntu on it but I guess this
shouldn't take too long to spot.
If that's a bug in plexus, I can revert the feature and reopen the related
issue until we get a fix for it.
S.
On Wed, Feb 8, 2012 at 1:05 AM, Stephane Nicoll
wrote:
> Hi,
>
> I am a bit puz
Hi,
I am a bit puzzled by the issue. I agree it makes the whole work
for MEAR-141 useless on Linux or Ubuntu but I really don't understand why
it's failing for you or Jenkins.
I am actually on MacOS and I can't reproduce the issue. If you can't
reproduce the issue on Windows, it remains a linux s
Hi,
It's available in Jenkins:
https://builds.apache.org/job/maven-plugins-ITs-m2/ws/maven-ear-plugin/target/test-classes/projects/project-077/target/application.xml/*view*/
and the expected one:
https://builds.apache.org/job/maven-plugins-ITs-m2/ws/maven-ear-plugin/target/test-classes/projects/p
Hi,
Can you attach the generated application.xml ?
S.
On Thursday, February 2, 2012, Dennis Lundberg wrote:
> Hi
>
> We have a problem with the current trunk of the EAR Plugin.
>
> The pseudo-IT project-077 fails on our Jenkins Ubuntu slave with the
> following message. On my local Ubuntu it al
Ok, I found.
Thanks Benjamin.
The problem was in my user's settings that the verifier wasn't able to read
(maven is able).
I have to see if I can create a testcase to fix the verifier
It seems I had in a coment a character with an accent (é, è ...)
Arnaud
On Thu, Aug 7, 2008 at 9:01 AM, Arnaud H
Same thing with a fresh checkout.
My env (if you find something strange ...) :
octo-ahe:maven-ear-plugin arnaud$ set
Apple_PubSub_Socket_Render=/tmp/launch-l6EBjN/Render
BASH=/bin/bash
BASH_ARGC=()
BASH_ARGV=()
BASH_LINENO=()
BASH_SOURCE=()
BASH_VERSINFO=([0]="3" [1]="2" [2]="17" [3]="1" [4]="relea
I tried with my current checkout, an update (with the new invoker config)
and with a fresh checkout (directory removed and svn co). All three worked
on my Mac (15.0.4)
Can you try with a fresh checkout maybe?
Thanks,
Stéphane
On Wed, Aug 6, 2008 at 10:27 PM, Arnaud HERITIER <[EMAIL PROTECTED]>wro
ok, thanks for your help.
On Wed, Aug 6, 2008 at 6:09 PM, Stephane Nicoll
<[EMAIL PROTECTED]>wrote:
> Weird. I have leopard as well and it works. They were some problems lately
> and I fixed them. Let me check again later today.
>
> S.
>
> On Wed, Aug 6, 2008 at 6:06 PM, Arnaud HERITIER <[EMAIL
Weird. I have leopard as well and it works. They were some problems lately
and I fixed them. Let me check again later today.
S.
On Wed, Aug 6, 2008 at 6:06 PM, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I'm trying to build the ear plugin on leopard but tests are failing.
> Those
On Dec 15, 2006, at 3:34 AM, Graham Leggett wrote:
On Thu, December 14, 2006 9:05 pm, Stephane Nicoll wrote:
This has been tackled a dozen of times and I am not sure it has
anything to do with the EAR plugin, at least if we follow the
spec. If
I am wrong, please let me know.
The valid way
On 12/15/06, Graham Leggett <[EMAIL PROTECTED]> wrote:
On Thu, December 14, 2006 9:05 pm, Stephane Nicoll wrote:
> This has been tackled a dozen of times and I am not sure it has
> anything to do with the EAR plugin, at least if we follow the spec. If
> I am wrong, please let me know.
>
> The v
On Thu, December 14, 2006 9:05 pm, Stephane Nicoll wrote:
> This has been tackled a dozen of times and I am not sure it has
> anything to do with the EAR plugin, at least if we follow the spec. If
> I am wrong, please let me know.
>
> The valid way to bundle shared components/libs in a EAR is to d
On 12/14/06, David Jencks <[EMAIL PROTECTED]> wrote:
I agree that spec support is the way to go.
the jee5 ear lets you specify a lib directory (default is "lib")
where all the jars inside get added to the classpath. We could work
on jee5 support, that ought to keep everyone happy. Does the
def
On Dec 14, 2006, at 11:05 AM, Stephane Nicoll wrote:
Hi,
This has been tackled a dozen of times and I am not sure it has
anything to do with the EAR plugin, at least if we follow the spec. If
I am wrong, please let me know.
The valid way to bundle shared components/libs in a EAR is to define
Hi,
This has been tackled a dozen of times and I am not sure it has
anything to do with the EAR plugin, at least if we follow the spec. If
I am wrong, please let me know.
The valid way to bundle shared components/libs in a EAR is to define
the Class-Path entry of the manifest in EJB module(s) us
Stephane Nicoll wrote:
Are there any showstoppers preventing its release?
No. I just need to cast a vote and we'll release it.
Here is a non binding +1 for release: +1 :)
I was very confusing to see the docs for the new plugin released and
live before the plugin itself.
Yes, the sites ha
On 12/8/06, Graham Leggett <[EMAIL PROTECTED]> wrote:
Stephane Nicoll wrote:
> No, it's implemented as from 2.3 which is not yet released. You can
> retrieve it on the snapshot repository [1] or you can build the plugin
> from source yourself.
Are there any showstoppers preventing its release?
Stephane Nicoll wrote:
No, it's implemented as from 2.3 which is not yet released. You can
retrieve it on the snapshot repository [1] or you can build the plugin
from source yourself.
Are there any showstoppers preventing its release?
I was very confusing to see the docs for the new plugin re
Hi,
On 12/8/06, Graham Leggett <[EMAIL PROTECTED]> wrote:
Hi all,
According to the docs at
http://maven.apache.org/plugins/maven-ear-plugin/modules.html#harModule,
it is now at long last possible to build ear files containing har files
with maven.
Has the version of the maven-ear-plugin descri
Tim,
I looked a bit further and I think I was wrong. Please file a Jira issue
with your pom (not corrupted this time :-) and the stacktrace you have. I'll
have a look.
Thanks,
Stéphane
On 11/30/05, Tim Kettler <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> currently the maven-ear-plugin doesn't support
On 12/1/05, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
>
> On 12/1/05, Tim Kettler <[EMAIL PROTECTED]> wrote:
> >
> >
> > In my opinion (I'm certainly not an maven source code expert) this is
> > bcause the type 'ejb' is hardcoded in the class EjbModule.java
> > (getType() method).
>
>
> We already
On 12/1/05, Tim Kettler <[EMAIL PROTECTED]> wrote:
>
> Please see the example project at
> http://h6282.serverkompetenz.net/tik/test-prj.tar.gz
> which fails like this:
Your zip is corrupted, I can't open it
[EMAIL PROTECTED]:~/Develop/test-prj$ mvn -e package
> + Error stacktraces are turned o
Please see the example project at
http://h6282.serverkompetenz.net/tik/test-prj.tar.gz
which fails like this:
[EMAIL PROTECTED]:~/Develop/test-prj$ mvn -e package
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Unnamed - test:test-project:p
so what? If you are using the maven ear plugin from svn (we are about to
release 2.1), you just specify your dependency as
ejb3
and use configuration if you need to tune a bit. I am sorry, I
don't see what your problem is.
s/
On 12/1/05, Tim Kettler <[EMAIL PROTECTED]> wrote:
>
> When I delete
When I delete the plugin configuration from the pom the type detection
works as expected and the build succeeds. But nevertheless when
specifying a configuration the type of 'ejb' is hardcoded to EjbModule.java.
What is the correct way to fix this? Is the solution proposed in my
first mail ok.
Indeed.
BTW, you don't need to specify the
test
test-ejb
This section is used only if you need to configure the way the module needs
to be handled by the plugin.
Stéphane
On 11/30/05, John Casey <[EMAIL PROTECTED]> wrote:
>
> is
isn't the type already specified in the dependency listed below?
Stephane Nicoll wrote:
You need to provide a type for each dependencies. We have discussed this
many times on the user list.
Cheers,
Stéphane
On 11/30/05, Tim Kettler <[EMAIL PROTECTED]> wrote:
Thanks for the quick replies. It'
You need to provide a type for each dependencies. We have discussed this
many times on the user list.
Cheers,
Stéphane
On 11/30/05, Tim Kettler <[EMAIL PROTECTED]> wrote:
>
> Thanks for the quick replies. It's for M2.
>
> Ok, I pulled the latest trunks from the following locations:
>
> https://sv
Thanks for the quick replies. It's for M2.
Ok, I pulled the latest trunks from the following locations:
https://svn.apache.org/reos/asf/maven/components/trunk
https://svn.apache.org/reos/asf/maven/plugins/trunk
https://svn.apache.org/reos/asf/maven/sandbox/plugins
I then bootstrapped the maven
If M2: It's fixed in SVN, you need to rebuild M2 ear plugin.
Regards,
Stéphane
On 11/30/05, Tim Kettler <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> currently the maven-ear-plugin doesn't support ejb3 modules because it
> expects artifacts of type *.ejb. For my local use I created a new
> Ejb3Module cl
Hi Tim,
Is it for m1 or m2 ?
arnaud
On 11/30/05, Tim Kettler <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> currently the maven-ear-plugin doesn't support ejb3 modules because it
> expects artifacts of type *.ejb. For my local use I created a new
> Ejb3Module class with the only difference to EjbModule.
On Wed, 2005-01-05 at 11:59, Dion Gillard wrote:
> 3) ony check the artifact/types/artifact-version.type part of the
> overall file name?
Yes, that is the better approach, but a pain to implement. We would need
to take the canonical path from the full path and just the repository
and then "crop"
40 matches
Mail list logo
