Hi,
you don't need to use the maven-ejb3-plugin. It was developed because a
draft version of the EJB3 specification contained a new .ejb3 packaging
type. This new type was dropped for the final specification and the
plugin never maid it out of the sandbox and was never released. Just use
the
Yes that struck to me later :). its the install goal that makes ur jar fall
in the .m2/repository/ :)
thanks
On Sun, Jun 22, 2008 at 6:04 AM, Wayne Fay [EMAIL PROTECTED] wrote:
You should not be creating projects in the ~/.m2/repository directory.
Rather, Maven2 uses this directory for
Hi,
using Maven 2.0.9 instead of 2.0.8 same problem. I also deleted the
Plugin in my local repo.
What makes me really confusing is that nowhere stand clear and readable
which version of that plugin
works for maven 1 or 2 :/ For example on top of the Plugin Site ?
Using MvnRepoo Exlorer :
So,
i could isolate the Problem. Version 1.9 do not have a pom.xml in Repo.
This must be a bug in my eyes!!!
1.0-SNAPSHOT works, problem was that in my reporting section stand a 1.9
dependency of the dashboard plugin.
best regards,
Jens
Hi,
using Maven 2.0.9 instead of 2.0.8 same
Hello,
i tried the Archetype Plugin to generate a stub for a Projekt Website.
I missunderstood something as the plugin outputs:
[WARNING] No archetype repository found. Falling back to central
repository (htt
p://repo1.maven.org/maven2).
[WARNING] Use -DarchetypeRepository=your repository if
I figured out that maven assembly plugin was the culprit even when
single goal (instead of attached) is bound to package phase.
I tried maven assembly 2.1 plugin with maven 2.0.8 and even tried
assembly plugin 2.2-beta-2 with maven 2.0.9 but i still got the same errors.
I have many projects that
Hi Jens,
Have you tried the 'mvn archetype:generate' command line (w/o any
other argument)?
maybe the archetype you want to use is in the default list.
You have indicated archetypeGroupId in yours. That property is used
to defined the archetype's groupId, not the
future project's groupId.
Or
Hi,
I have a requirement to specify a dependency in my pom whilst excluding
all of it's associated dependencies. The exclusion tag enables me to
specify dependencies I do not need, but only one at a time! How do I do
a global exclusion of a dependency?
--
Regards
Andrew
On Sun, 22 Jun 2008 06:02:48 am Jason van Zyl wrote:
Use the maven-dependency-plugin, it can retrieve artifacts and place
them so that you can subsequently process them. I suggest staying away
from the artifact resolver directly.
Why is that? Surely the dependency plugin can't be appropriate
On 22-Jun-08, at 5:50 PM, Eric Rose wrote:
On Sun, 22 Jun 2008 06:02:48 am Jason van Zyl wrote:
Use the maven-dependency-plugin, it can retrieve artifacts and place
them so that you can subsequently process them. I suggest staying
away
from the artifact resolver directly.
Why is that?
There are actively development works at IzPack to allow IzPack's
custom panels to be pulled in via izpack-maven-plugin, please join
your work to make this happen.
the plugin site is at http://izpack.codehaus.org/izpack-maven-plugin
-D
On Sun, Jun 22, 2008 at 5:50 PM, Eric Rose [EMAIL
also once IZPACK-78 enhancement completes, we should be able to use
just maven-dependency-plugin to pull in all custom panels and get
bundled with the installer by izpack-standalone-compiler
-D
On Sun, Jun 22, 2008 at 10:19 PM, Dan Tran [EMAIL PROTECTED] wrote:
There are actively development
On Mon, 23 Jun 2008 01:58:23 pm Jason van Zyl wrote:
On 22-Jun-08, at 5:50 PM, Eric Rose wrote:
On Sun, 22 Jun 2008 06:02:48 am Jason van Zyl wrote:
Use the maven-dependency-plugin, it can retrieve artifacts and place
them so that you can subsequently process them. I suggest staying
away
13 matches
Mail list logo
