Hi,
The repo you are using is not browsable but if you try to get some file that
actually exists it should work. Eg.
https://maven-central-eu.storage-download.googleapis.com/repos/central/data/abbot/abbot/1.4.0/abbot-1.4.0.pom
br,
Samuli
> -Original Message-
> From: Anton Alipov
>
You could try including true in the
fileSet to see if the pattern actually matches anything. Running with mvn -X
might also give some insight of what is actually happening during assembly.
br,
Samuli
From: Arnold Morein
Sent: 18. joulukuutata 2018 23:58
To: Maven Users List
Subject: Re: How
Hi,
You can specify Maven assembly plugin to include provided scoped artifacts as
described here: https://stackoverflow.com/a/14616643/7773647. There is also a
sample of changing the scope using properties but seems more hacky to me.
br,
Samuli
From: Arnold Morein
Sent: 18. joulukuutata 2018
Hi,
"
I have edited my ~/.bash_profile and added /usr/local/apache-maven-3.5.3/bin
"
Might be a typo but there is one 'bin' missing from that path. Should probably
be /usr/local/bin/apache-maven-3.5.3/bin
br,
Samuli
> -Original Message-
> From: Romanos Sklavenitis Pistofidis
(`maven` distribution is around 9MB)
>
> Once again thank your for quickly responding :)
>
> On Fri, Nov 10, 2017 at 12:07 PM, Samuli Saarinen <
> samuli.saari...@remion.com> wrote:
>
> > Hi,
> >
> > Could you use maven wrapper [1]? It obviously needs
Hi,
Could you use maven wrapper [1]? It obviously needs to download Maven from the
interwebs when performing the build though.
[1] https://github.com/takari/maven-wrapper
br,
Samuli
> -Original Message-
> From: Kasun Siyambalapitiya [mailto:kasu...@wso2.com]
> Sent: 10. marraskuutata
Hi,
You could import the dependencies in dependencyManagement as described in [1]
and only declare needed dependencies in the project.
Cheers
Samuli
[1]
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Importing_Dependencies
-Original Message-
-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Remion Oy Etävalvontajärjestelmät liiketoiminnan
Samuli Saarinen tehostamiseen
gsm +358 (0)50 3560075
fax +358 (0)3 2125064 www.remion.com
.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Remion Oy Etävalvontajärjestelmät liiketoiminnan
Samuli Saarinen tehostamiseen
gsm +358 (0)50 3560075
...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Remion Oy Etävalvontajärjestelmät liiketoiminnan
Samuli Saarinen tehostamiseen
gsm +358 (0)50 3560075
fax +358 (0)3 2125064 www.remion.com
Hi,
I used the following code in a plugin. Got it from
hibernate3-maven-plugin if I remember correctly.
*/
* @parameter expression=${project}
* @required
* @readonly
*/
protected MavenProject project;
protected boolean isJavaProject() {
ArtifactHandler artifactHandler =
Rice Yeh wrote:
Hi,
I have a web project with some files under webapp/META-INF, like tomcat's
context.xml. I find they are not included in the result war file. I cannot
find any configuration parameter in war:war plugin.
Hello,
Is this what you are looking for?
Markus Jostock wrote:
Hi
My project structure is like this
parent-- type pom
+-- module1 -- type jar
+-- module2 -- type jar, depends on module 1
When running mvn in the parent directory everything works fine.
But when running mvn in the module2, which depends on
Markus Jostock wrote:
So it's the reactor which is a kind of execution entity? I thought it
would be possible for the reactor via the parent/child relationship to
find the parent pom and therein the modulemodule1/module ...
Cheers
Markus
Samuli Saarinen wrote :
parent-- type pom
Ok, I found the issue http://jira.codehaus.org/browse/MRELEASE-295
Brett Porter wrote:
That sounds like a bug. It is generally uncommon to use the release
plugin to simultaneously release projects of different versions, but
it should work.
- Brett
2008/10/7 Samuli Saarinen [EMAIL PROTECTED
Hello,
I'm using maven 2.0.9 with a multi-module project and try to make a
release using maven-release-plugin. My project structure is following:
parent
- child1
- child2
parent pom.xml:
project
...
version1.0.2-SNAPSHOT/version
modules
modulechild1/module
16 matches
Mail list logo