On 01/18/2010 07:28 PM, eyal edri wrote:
i'm interested in how people do deploy their apps, even if it's not directly
connected to maven.
I create a runnable jar (with all dependencies) or a war (for web
applications). That is deployed to the repository.
That can be downloaded with a one
Ich bin von Mo, 18.01.2010 bis Mo, 25.01.2010 abwesend.
Hinweis: Dies ist eine automatische Antwort auf Ihre Nachricht Re:
install maven project from repository to local fs gesendet am 19.01.2010
11:25:25.
Diese ist die einzige Benachrichtigung, die Sie empfangen werden, während
diese
so you create a 'FAT' jar, as i understand.
this can be very troublesome.
think about a scenario where you need to update one of the dependencies, and
its being used in a lot of application jars. you will need to update all the
applications jars
On Tue, Jan 19, 2010 at 12:25 PM, Johannes
Hi,
I have found that metadata.xml:
Why is the latest version 1.2.1-SNAPSHOT and not 2.0.6-SNAPSHOT?
Any hints? I think I miss something fundamentally,
Thanks,
Johannes
?xml version=1.0 encoding=UTF-8?
metadata
groupIdcom.cedarsoft/groupId
artifactIdopen/artifactId
versioning
The last version deployed is 1.2.1-SNAPSHOT
This is why LATEST and RELEASE are a pile of shite and deprecated.
-Stephen
2010/1/19 Johannes Schneider maili...@cedarsoft.com:
Hi,
I have found that metadata.xml:
Why is the latest version 1.2.1-SNAPSHOT and not 2.0.6-SNAPSHOT?
Any hints? I
On 01/19/2010 11:30 AM, eyal edri wrote:
so you create a 'FAT' jar, as i understand.
Yes. Most of the time.
One project uses another approach where all dependencies are copied to a
lib folder. But this has other disadvantages: It isn't deployed to the
repository:
...
plugin
On 01/19/2010 12:46 PM, Stephen Connolly wrote:
The last version deployed is 1.2.1-SNAPSHOT
And the other versions? How did they end up in the repository? Downloaded?
This is why LATEST and RELEASE are a pile of shite and deprecated.
-Stephen
2010/1/19 Johannes
I also used the copy dependencies option, but again this requires you (the
developer) to run this from the machine that holds the pom file and deploy
it (no sure if it supports remote copy).
there might be another option like wayne suggested:
http://cargo.codehaus.org/
and using the maven2
Another idea came to mind:
what do you think about the following:
1. writing + deploying all the projects to the repository. *(done by
developer).*
2. write a small maven project on production system (an install project) :
that uses GMaven (groovy) plugin, to dynamically create a local pom
Using maven to install in this way is just wrong IMO. You should be able
to install your product without the person installing knowing anything
about maven.
---
Todd Thiessen
-Original Message-
From: eyal edri [mailto:eyal.e...@gmail.com]
Sent: Tuesday, January 19, 2010 9:25 AM
I'm using the properties-maven-plugin to load properties from a file and
trying to use one of these properties in configuring the GWT plugin. GWT has
a run goal, which has executePhase=compile. When I invoke gwt:run, the
value of the property in question is null instead of the value from the
so how do you suggest on doing so?
let's say you're the sys admin and you know the JARs are in the repository.
and you need to install them (with dependencies) on the server.
what do you do?
(btw, we don't use java application server yet, since we only deploy classic
runnalbe java jars (not web
You download the install artifacts to your production server and install
them. Just like how you would install any software today.
For example, how did you install Maven? You downloaded the artifacts,
extracted them and followed the instructions either on the web page or
in the extracted readme
And the other versions? How did they end up in the repository? Downloaded?
No, read what he said again... the LAST version deployed was 1.2.1-SNAPSHOT.
I guess the order was something like:
version2.0.3-SNAPSHOT/version
version2.0.4-SNAPSHOT/version
What is plan for releasing version 2.4.1 of ear plugin? All issues for this
release are resolved.
Version 2.4 was just released in late Oct 2009. Are you having
specific problems related to a Jira issue that has been resolved, or
is this just a general inquiry?
Wayne
Hi,
I have a large project which comprises of many modules and sub-modules and
inheritance structure
root
+--- Module 1
+-- Module 1.1
+--- Module 2
+-- Module 2.1
Now i would like to get the SCM Version with the buildnumber-maven-plugin
which
Can't you create the build number in your final build project?
For example, if your final artifact is a war, you create the build
number only in that war project.
Do you really need a build number in all dependency modules?
---
Todd Thiessen
-Original Message-
From: Karl Heinz
We have a project that has a couple of variations of an ear for the for
web servers such as Webspear, Weblogic etc... To handle this, we use
Maven profiles which only include the web server's required files before
packaging. Is there a way to create these variations with at the same
time,
Hi,
My company is developing a product and we're using Maven as project
management tool. My question is: how can I achieve a final release of the
project? More detailed below.
What I am looking for is to have at the end a structure similar to the one
JBoss uses:
*bin
startup
shutdown
lib
You can use classifiers to keep the artifact names separate, like you
suggested. I.e.
profiles
profile
idjboss/id
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
On Tue, 19 Jan 2010 11:29:54 -0500, David.A.Williams wrote
We have a project that has a couple of variations of an ear for the for
web servers such as Webspear, Weblogic etc... To handle this, we use
Maven profiles which only include the web server's required files before
packaging. Is there
What I am looking for is to have at the end a structure similar to the one
JBoss uses:
So, resuming I want something that is similar to the effect of a 'make
install' in common UNIX environments.
The assembly plugin is probably what you're looking for.
Wayne
Yeah, I've used both approaches, overlays and profiles. We generally use
profiles because they are faster, especially if you don't need to always
create all container variants; if you need them all, always, then overlays
might be just as good. (Right, overlays work with wars not sure about
Hi,
first thanks for your answer...
tthiessen wrote:
Can't you create the build number in your final build project?
For example, if your final artifact is a war, you create the build
number only in that war project.
Do you really need a build number in all dependency modules?
Yes i
Yeah, I've used both approaches, overlays and profiles. We generally use
profiles because they are faster, especially if you don't need to always
I'd probably just create multiple ear artifact projects and include
the Java EE target name in the artifactId eg my-app-weblogic. Then
include your
The svn revision stays the same right? Do you even care about the time
stamp?
---
Todd Thiessen
-Original Message-
From: Karl Heinz Marbaise [mailto:k...@soebes.de]
Sent: Tuesday, January 19, 2010 11:56 AM
To: users@maven.apache.org
Subject: RE: Problem with
On 01/19/2010 04:45 PM, Wayne Fay wrote:
And the other versions? How did they end up in the repository? Downloaded?
No, read what he said again... the LAST version deployed was 1.2.1-SNAPSHOT.
Aaah, okay. Thanks... While I don't think that I have released
1.2.1-SNAPSHOT *after*
Thanks everyone for your answers. I'll look into each method. We are using
Bamboo as a build server and the two issues are that 1, need to ensure that all
version have the same source code revision and 2, we are using that Build
Number plug-in and need to keep the build number the same for
That shouldn't be a problem...we have the same requirements...however we use
TeamCity for CI.
-Dave
On Tue, Jan 19, 2010 at 10:29 AM, david.a.willi...@sungard.com wrote:
Thanks everyone for your answers. I'll look into each method. We are
using Bamboo as a build server and the two issues
Hi,
tthiessen wrote:
The svn revision stays the same right?Yeah the svn revision number does
not change, but which is not my problem...
Do you even care about the timestamp?/quote]
My problem is exactly the timestampcause on the build time of each
module the timestamp is changing
My problem is
exactly the timestampcause on the build time of each
module the timestamp is changing over my tree
I guess I don't really understand what the problem with this is ;-). The
build time each module's artifact IS actually different. If your not
interested in the built
Woult this new module for the assembly be a jar module or a pom only module?
On Mon, Jan 18, 2010 at 9:38 PM, Wayne Fay wayne...@gmail.com wrote:
I think what you are suggesting is rather then have a parent module to
have
another module at the same level as the jar/wars and list them as
I have uploaded a second copy of my project
http://weseewhathappens.com/mvn2.zip
I took your suggestion and create a second module called assembly. And
moved the assembly plugin there. I also added my other jars as dependencies.
At the top level if I run
mvn package, things work fine as
I have done the two approaches on bamboo.. and yes, i believe the cleanest
approach is to use separate projects for each appserver.
On advantage of an overlay is that you can do it with a war (and maybe ear)
that is not part of your build. E.g. I modified JasperServer war and added
more stuff
I have successfully used the assembly plugin to create an executable jar
with dependencies as explained here:
http://www.sonatype.com/people/2009/08/how-to-make-an-executable-jar-in-maven/
The jar plugin has an option that will index the jar to speed up
classloading. I have not been able to
When you execute
mvn gwt:run
you're not executing the maven lifecycle - just that goal of the gwt plugin.
Thus, the plugin bindings you've specified are not executed. Try
mvn install
instead.
/Anders
On Tue, Jan 19, 2010 at 16:00, Ryan Stewart rds6...@gmail.com wrote:
I'm using the
I assume this is because I have no assembly at the top level. Since I am
not installing the jar-a - jar-b in the local repo I can't run assembly on
the sub module as I will get errors regarding missing dependencies.
Why not?? I don't want to is not a valid answer. Maven uses its
repository
Dang, the problem just compounded. Being that this is a multi-module project
there are several EJBs etc... modules that have different files for the web
servers. I would prefer not to have different EJB projects just for the web
server. Is this possible, I didn't see an overlay option for
Hi,
I am using the exec-maven plugin from codehaus,and it seems that there
is problem with the exec:java goal's JAR dependency resolution. Or (since
I'm a new user) I'm doing something wrong. Comments welcome!!
Here is the scenario:
(A) I build an application tool, packaged into a JAR
Because of the comment here. I have never been able to get my project to
build properly if I attach my assembly as a build step.
http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-binary-inclusion-simple.html
I think you have stumbled onto why we use profiles. I was going to say that
what you have will work but you can endup with an explosion in the number of
artifacts. If you have lots of wars/ears/ejbs and they all run in lots of
containers, that can add up to lots of projects and build time.
Dave,
If I understand you right, this is similar to what we are doing now, as well.
For example a excerpt of our project looks like the following:
pom.xml
|_web service_1 module
|_ejb_1 module
|_web service_2 module
|_ejb_2 module
|_war module
|_ear module
I kick of this build with a profile
the web servers. I would prefer not to have different EJB projects just for
the web server. Is this possible, I didn't see an overlay option for the
ejb plugin.
We're done this before (still using modules) by having one ejb project
with the common stuff and then one module each for the
I would prefer to build the entire project from one command line. If I put
the assembly into a sub project that is two steps. I must install all of my
artifacts and then run assembly on another module. While feasible it seems
wrong to me that I can't simply walk up to the top level and build
Regarding profiles/classifiers, we went down this path mostly because the
overlay approach took too long to build. Your building 1 + the number of
containers for everything...just took too long. Plus our devs really only
cared about a single container, i.e. one group uses jboss another uses
overlay approach took too long to build. Your building 1 + the number of
containers for everything...just took too long. Plus our devs really only
cared about a single container, i.e. one group uses jboss another uses
weblogic, etc. So profiles meant they could but just what they want fast.
I am not sure what you are proposing. Wouldn't I still mvn install my
artifacts before running mvn assembly on my assembly project?
Jeff
On Tue, Jan 19, 2010 at 4:34 PM, Wayne Fay wayne...@gmail.com wrote:
I would prefer to build the entire project from one command line. If I
put
the
I am not sure what you are proposing. Wouldn't I still mvn install my
artifacts before running mvn assembly on my assembly project?
Its highly likely that my suggestion of using single is not
appropriate since you don't want to install things.
I'm not a hardcore assembly user. I am ok with
Hi Todd,
My problem is
exactly the timestampcause on the build time of each
module the timestamp is changing over my tree
I guess I don't really understand what the problem with this is ;-). The
build time each module's artifact IS actually different.
Yeah that's what i
If you got all that going already you can just put a parent object on top of
it all that uses the invoker plugin to call you current parent pom with
different profiles for each app server. That can then run on bamboo or
whatever but in development you stay at the parent you have now and just
The Apache Continuum team is pleased to announce the release of Apache
Continuum 1.3.5 (Beta).
Apache Continuum is an enterprise-ready continuous integration server
with features such as automated builds, release management, role-based
security, and integration with popular build tools and
The Apache Archiva team would like to announce the release of Archiva 1.3.
Archiva 1.3 is available for download from the web site and mirrors:
http://archiva.apache.org/download.html
Archiva is an application for managing one or more remote Maven repositories,
including administration,
52 matches
Mail list logo
