I would like to produce a tar with my project artifact and all its dependents
jars jarsigned. Also, I would like to deploy the tar as attachment.
I used assembly plugin and write my own descriptor. However, I don’t know
how to sign all the jars before the tar is created.
I did try create the
Eclipse says:
Embedded Runtime is always used for dependency resolution, but does
not use global settings when it is used to launch Maven.
So i think, there is just no global configuration file for this
runtime, because it doesn't use one.
You have to use the user configuration file or an
On 5 January 2011 08:22, xtonic davidptw...@gmail.com wrote:
I would like to produce a tar with my project artifact and all its
dependents
jars jarsigned. Also, I would like to deploy the tar as attachment.
I used assembly plugin and write my own descriptor. However, I don’t know
how to
OK, will likely soon be included in a plugin coming to a repo close to
you...:-)
/Anders
On Tue, Jan 4, 2011 at 23:21, Brett Porter br...@apache.org wrote:
I believe if you regenerated another settings-security.xml file with the
same master password, while the hash would be different it would
What do you mean when you say that the exclusions don't get excluded when
you build from the root?
The subject mentions the assembly plugin, but I don't see that mentioned in
your structure.
More info, please!
/Anders
On Wed, Jan 5, 2011 at 01:36, Anand HS anan...@gmail.com wrote:
Hi,
I have
Hello;
I was working on a project for our custom needs about dependency management. I
have written a program that traverses the repo1.maven.org and list all the
available artifacts. Unfortunately I'm not able access repo1.maven.org any
more. Our company uses maven in many projects for build
Thank you Anders and Zac.
The project was originally managed by Ant (by other man), and I'm
porting that project to maven now. I don't change module structure yet,
but probably the time to change will come soon.
The manager is standalone data server that manage whole configurations
of the
You do know that there is an index that should be used for these purposes,
yes?
/Anders
On Wed, Jan 5, 2011 at 11:34, Faruk Can Kaya fck...@datasel.com.tr wrote:
Hello;
I was working on a project for our custom needs about dependency
management. I have written a program that traverses the
If you have Nexus installed, you can find any dependency available in
any repository that you configure either by looking at the full list or
by searching for it .
That is the right way to manage dependencies.
It is a really big help in making your management of dependencies much
less painful
File an issue at https://issues.sonatype.org under the Community Support -
Maven Central to get removed from the blacklist.
Rich
On Jan 5, 2011, at 8:05 AM, Ron Wheeler wrote:
If you have Nexus installed, you can find any dependency available in any
repository that you configure either by
Thanks, that's a simple solution that might even work in most of the
situations (perhaps excepting the release plugin, etc).
I also found a more complex way to access the versions of a dependency
using Groovy plugin. For those who are interested:
plugins
plugin
Wendy, thanks for your reply.
Here is the example:
1. Someone need to fix a bug in production.
2. Create a new branch for bug fix based on a label.
3. The newly created branch will contain older pom files with older
version that already released in Nexus (or any Maven based
repository).
4.
Configure your Nexus server to not allow artifacts to get overwritten. You
can't stop the build from happening, but you can stop the artifact from being
deployed.
-Original Message-
From: baz themail [mailto:bazthem...@gmail.com]
Sent: Wednesday, January 05, 2011 12:55 PM
To: Maven
On Wed, Jan 5, 2011 at 12:54 PM, baz themail bazthem...@gmail.com wrote:
1. Someone need to fix a bug in production.
2. Create a new branch for bug fix based on a label.
3. The newly created branch will contain older pom files with older
version that already released in Nexus (or any Maven
And use the Maven Release Plugin to create the branch[1][2] in the
first place. This will change the version numbers back to snapshot.
[1] http://maven.apache.org/plugins/maven-release-plugin/branch-mojo.html
[2] http://maven.apache.org/plugins/maven-release-plugin/examples/branch.html
Hth,
On Wed, Jan 5, 2011 at 9:33 AM, juranta juha.ra...@iki.fi wrote:
Thanks, that's a simple solution that might even work in most of the
situations (perhaps excepting the release plugin, etc).
The release plugin is surprisingly good at dealing with versions
declared in properties, try it, might
-Original Message-
From: Reynald Borer [mailto:reynald.bo...@gmail.com]
You can modify the finalName tag to change the name of artifact. By default
it is defined like the following:
project
build
finalName${artifactId}-${version}/finalName
/build
/project
That only affects what gets
Hi,
Apologize for not providing more details.
Here are more details -
1. The ROOT is a ROOT pom that builds both ModuleA and ModuleB.
2. ModuleA uses assembly plug in to generate a Distribution jar. Here is the
distribution XML that builds this jar -
!--
This is the maven assembly descriptor
Anand HS wrote:
4. Now when I invoke mvn install from the ROOT pom, I see that ModuleA and
ModuleA-distribution.jar get build with no issues. Now when ModuleB is
built, in spite of explicit exclusion of ModuleA's dependencies , those
dependencies do not get excluded.
Could be
Indeed. Sorry I read the topic too quickly to give a wrong answer ;-)
Leon, why do you explicitly need to install the war file in your m2repo with a
custom name? Couldn't you simply use the one you can find in the target/
folder? Or you can always use the maven-resources-plugin to copy the
Hello Reynald,
I posted it in my original post.
The webapp have to be accessed by a specific context-path, e.g.
http://host:port/distributeme/registry/list
The easiest way to achieve it, is to name the war distributeme.war.
In other words, for external users its easier to understand:
Download
Understood. So you want your users to download the WAR directly from either
your m2repo (weird) or from a Maven repository tool like Nexus, right?
In that case, I don't think it's a Maven problem. You should consider deploying
your generated war file to a web server like Apache (through
Hi,
we're aiming at a bugfix release of Maven 3 in the next week and
following tradition we invite interested users in taking the RC for a
test drive in order to detect and fix potential regressions since
version 3.0.1 before the actual release of 3.0.2.
For the duration of the RC testing,
The webapp have to be accessed by a specific context-path, e.g.
http://host:port/distributeme/registry/list
The easiest way to achieve it, is to name the war distributeme.war.
Each app server has its own way of handling this -- context.xml,
weblogic, xml, etc. You could also just include all
Since you say I always want bar to use the latest release of foo
then you might as well release them together.
http://www.sonatype.com/books/mvnex-book/reference/multimodule.html
Or, if you feel it's not appropriate to have them be part of the same
project (for example, if 'foo' changes
I am, for the first time, trying to use a nexus repository. I have read
all the information here:
http://maven.apache.org/guides/mini/guide-encryption.html on password
encryption and to the best of my knowledge, have followed it correctly
and set up my setting.xml, settings-security.xml and
On 01/05/2011 04:36 PM, Steve Cohen wrote:
I am, for the first time, trying to use a nexus repository. I have read
all the information here:
http://maven.apache.org/guides/mini/guide-encryption.html on password
encryption and to the best of my knowledge, have followed it correctly
and set up my
Is it appropriate / best practice to use the maven-resources-plugin to
copy dlls from target\dependency\bin to target\bin so they will be
where I need them for runtime?
Thanks,
Phillip
-
To unsubscribe, e-mail:
Steve Cohen wrote:
Another thing I notice is that
mvn -ep {password}
when run several times in succession generates different encryptions
each time.
This is correct/expected, the encrypted value is also based on a random
salt.
Benjamin
You might want to look at the
maven-dependency-plugin(http://maven.apache.org/plugins/maven-dependency-plugin/).
Nice if you also need the transitive dependencies. Also unpack makes it nice
to work with zip files.
From: Phillip Hellewell [via Maven]
On Wed, Jan 5, 2011 at 4:24 PM, khaido khai...@impinj.com wrote:
You might want to look at the
maven-dependency-plugin(http://maven.apache.org/plugins/maven-dependency-plugin/).
Nice if you also need the transitive dependencies. Also unpack makes it
nice to work with zip files.
Thanks.
On Wed, Jan 5, 2011 at 4:32 PM, Phillip Hellewell ssh...@gmail.com wrote:
My question now is, if I want to define the resources in a separate
stand-alone xml file (actually there will be more than one), rather
than in the pom.xml, what code/class do I use to read an xml file into
a
I figured that that must be the case.
Do you have any idea why this would fail? Could the 3.0.1 vs. 2.2.1
thing be involved or MUST it be that I'm making a mistake I just can't see?
On 01/05/2011 05:04 PM, Benjamin Bentmann wrote:
Steve Cohen wrote:
Another thing I notice is that
mvn
Resources are for things packaged and to be used at runtime - that doesn't
sound like what you want here.
This is typically done with a combination of the dependecy assembly plugin.
You might also be interested in NPanday (http://incubator.apache.org/npanday/)
which provides several .NET
I also want to know how to deploy to auto-deploy of weblogic in exploded
format using maven.
Presently we run 'mvn clean install' which creates ear. We run a batch file
to explode this ear and copy this exploded ear to the autodeploy directory.
If we have java changes, we do 'mvn compile' on
35 matches
Mail list logo
