Why isn't the war the primary artifact?
I would suggest you structure this as two modules; the first creates the war
that includes the applet and the other one is the larger war.
/Anders
On Tue, Jan 11, 2011 at 21:22, Mike Calmus wrote:
> I am trying to create a non-primary war that includes a
I am trying to create a non-primary war that includes an applet jar and its
dependencies. This war is then merged into a larger war.
When I try to do this, though I get an error from the Maven Install plugin
indicating no primary artificat was created. The error returend is somewhat
different dep
Hi
I am really looking to get this issue resolved but am unable to do so. I
have a local Apache Jetty web server installed in my local machine and I was
wondering as to how to use the Maven site plugin to push the reports to my
web server? Any help would be really appreciated.
Thanks.
--
View t
Try Codehaus Cargo, it should support your use case. If you need help, ask
on the cargo user list.
/Anders
On Tue, Jan 11, 2011 at 21:56, Ryan Connolly wrote:
> Hi:
> Does anyone happen to know whether it is possible to configure
> tomcat:run to deploy a defined war dependency as well as r
It looks like you have a pom project, but have declared to use the project's
artifact. A pom project only have the pom artifact, so that might be the
reason of the error message. Try declaring useProjectArtifact as false.
/Anders
On Tue, Jan 11, 2011 at 22:43, jaybytez wrote:
>
> Thanks...I wen
Hi,
I have a doubt regarding distributing configuration files which needs to be
deployed in application server. But these files needs to be separated from the
web achieve. I am publishing the web archive and other artifacts to remote
repository, from where I am picking up and deploying them to
Patchs are always welcome :-)
2011/1/11 Ryan Connolly :
> Thanks for the reply, Olivier. I'll give your suggestion a try. Would it
> be worth my time trying to create a patch for this feature or would rather
> just a feature request in JIRA?
>
> Thanks again.
> -Ryan
> On Jan 11, 2011 5:09 PM, "
Thanks for the reply, Olivier. I'll give your suggestion a try. Would it
be worth my time trying to create a patch for this feature or would rather
just a feature request in JIRA?
Thanks again.
-Ryan
On Jan 11, 2011 5:09 PM, "Olivier Lamy" wrote:
> Hello,
> It's not supported currently (btw it'
Hello,
It's not supported currently (btw it's a good idea).
You can use copy goal [1] from dependency plugin to get your artifact
and use deploy-only mojo from t-m-p
[1]
http://maven.apache.org/plugins/maven-dependency-plugin/examples/copying-artifacts.html
2011/1/11 Ryan Connolly :
> Hi:
>
Thanks...I went through the example and created a bin.xml that represented
the jar-with-dependencies example.
http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/plugins/mave
Hi:
Does anyone happen to know whether it is possible to configure
tomcat:run to deploy a defined war dependency as well as run the current
project as a dynamic web app in the embedded container? I've tried setting
the true
configuration option and have declared a war dependency in the tomca
If you are building an web application (war or ear) then I would take a look
at the maven-war-plugin and maven-ear-plugin. Here's an example:
maven-war-plugin
On 11/01/2011 9:28 AM, Justin Edelson wrote:
Are you going to hire Ron Wheeler to do sales?
(Sorry Ron, couldn't resist)
I don't mind. I really appreciate the product and how much better it has
made our lives since we moved to Eclipse/STS with the Maven integration
supplied by Sonatype.
I rea
On 11/01/2011 4:33 AM, Anders Hammar wrote:
Your aggregating pom is just a kind of helper project which holds all
modules you want to build. Normally, it shouldn't include any dependencies
(unless you make it a parent pom as well). In any case, it should most
definitely not have a dependency to a
If he wants to use Guice instead of Spring, sure :-)
On Jan 11, 2011, at 9:28 AM, Justin Edelson wrote:
> Are you going to hire Ron Wheeler to do sales?
>
> (Sorry Ron, couldn't resist)
>
> On Jan 11, 2011, at 8:58 AM, Jason van Zyl wrote:
>
>> For those of you interested in Maven integration
Are you going to hire Ron Wheeler to do sales?
(Sorry Ron, couldn't resist)
On Jan 11, 2011, at 8:58 AM, Jason van Zyl wrote:
> For those of you interested in Maven integration in Eclipse:
>
> http://www.sonatype.com/people/2011/01/maven-ide-the-year-of-maven-eclipse-2/
>
> Thanks,
>
> Jason
2011/1/11 Jason van Zyl :
> For those of you interested in Maven integration in Eclipse:
>
> http://www.sonatype.com/people/2011/01/maven-ide-the-year-of-maven-eclipse-2/
Wow, I think you read my mind, I always wanted a nicer integration
between Eclipse, Maven, GWT and Android.
What a great team y
For those of you interested in Maven integration in Eclipse:
http://www.sonatype.com/people/2011/01/maven-ide-the-year-of-maven-eclipse-2/
Thanks,
Jason
--
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
---
It's not a Maven core issue then, I understand.
I think I just simply open Jira items for (some of) the plugins, that
run into this problem. But I think this will also require some work on
the Site plugin (3.x), as the Site plugin now should provide a way to access
that list of configured repor
Anders Hammar wrote:
To me it seems as
project.getReportPlugins()
don't cope with the new syntax for declaring report plugins (i.e. declared
in the configuration of the site plugin). I would start by filing a jira on
Maven core.
This is "Won't fix" as far as Maven core is concerned. This met
thanx.
I understand it now.
regards
Leon
On Tue, Jan 11, 2011 at 10:33 AM, Anders Hammar wrote:
> Your aggregating pom is just a kind of helper project which holds all
> modules you want to build. Normally, it shouldn't include any dependencies
> (unless you make it a parent pom as well). In any
Your aggregating pom is just a kind of helper project which holds all
modules you want to build. Normally, it shouldn't include any dependencies
(unless you make it a parent pom as well). In any case, it should most
definitely not have a dependency to any of the artifacts it's building.
If you wan
Yes, the assembly plugin is they way to do this. Declare the packaging as
"pom".
There are several examples at the plugin's homepage, or google for some live
ones.
/Anders
On Tue, Jan 11, 2011 at 02:11, jaybytez wrote:
>
> Is the Maven Assembly Plugin the right way for me to define a pom.xml and
To me it seems as
project.getReportPlugins()
don't cope with the new syntax for declaring report plugins (i.e. declared
in the configuration of the site plugin). I would start by filing a jira on
Maven core. I'm sure Benjamin will move it if he doesn't agree with this
being a core issue.
Please
24 matches
Mail list logo
