maven-dependency-tree offers a really simple API: that's its objective.
The drawback is that it is not very flexible
The value is that it hides Maven 2, Maven 3.0.x and Maven 3.1.x+
implementations, which are completely different (initial Maven 2 is made of
listeners, Maven 3 uses Aether and
Herve,
I didn't think I was asking for any extra flexibility out of
dependency-tree that it didn't already give. Are you saying that it doesn't
support resolution of projects in the current reactor?
William
On Thu, Mar 20, 2014 at 5:16 PM, Hervé BOUTEMY herve.bout...@free.frwrote:
I don't really know: that's a precise feature that I didn't sudy
dependency-tree is used in Maven plugins in contexts where components are
already installed: so there is not much difference between reactor resolution
and local repository resolution
you're probably right: if reactor resolution
Using the EAR plugin, if I specify the context root in the EAR's pom it
works. But if I specify the contextRoot in a profile (in its parent pom), it
sets the contextRoot by default (articleId).
Am I doing something wrong?
This is a piece of code for the EAR's pom:
plugins
Hi,
poroto20 wrote:
Using the EAR plugin, if I specify the context root in the EAR's pom it
works. But if I specify the contextRoot in a profile (in its parent pom),
it sets the contextRoot by default (articleId).
Am I doing something wrong?
And what do you do to activate the profile?
The par packaging is not working. It is dependent on the
org.apache.maven.plugins:maven-par-plugin, but this plugin does not exist.
Is it deprecated?
I am using the latest maven 3.2.1.
How should I make the par package these days? I know this thing is
relatively simple: just a collection of jars
I am running:
mvn clean install -P jboss6
I think tt is using the correct profile because it is adding the web module
to application.xml, only that it is using the wrong contextRoot
--
View this message in context:
It was my mistake. I wanted to exclude a web module by using a profile and it
did not work. But I could fix it using combine.children=append. So I
basically I added an extra web module in my profile using:
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
I got a working setup for the release profile in the android maven plugin code.
Check it out
https://github.com/jayway/maven-android-plugin
Benson Margulies wrote on 19.03.2014 19:20:
Best ask them. This is a product of github, not the Apache Maven Project.
On Wed, Mar 19, 2014 at 7:32
I copied what you had in your pom.xml, but I still get the same error.
[ERROR] Failed to execute goal
com.github.github:site-maven-plugin:0.9:site (default) on project
java-file-utilities: Error creating blob: Not Found (404) - [Help 1]
What does your settings.xml look like?
Mine is:
So is there an equivalent to altReleaseDeploymentRepository and
altSnapshotDeploymentRepository for the Site Deployment information
also? Since all three are in the Distribution Management directive, I
was hoping I could define this last one in the settings.xml also.
Robert Kuropkat
On
I am looking for some way to force my integration tests before a
release, without explicitly using a profile.
For example,
plugin
artifactIdmaven-release-plugin/artifactId
configuration
preparationGoalsclean verify site/preparationGoals
/configuration
On 21 March 2014 06:02, Eric Kolotyluk eric.koloty...@gmail.com wrote:
I am looking for some way to force my integration tests before a release,
without explicitly using a profile.
[del]
Is there some way I can trigger the integration tests when doing a release
mvn release:prepare
Hello Robert,
reading the information at
https://maven.apache.org/plugins/maven-site-plugin/deploy-mojo.html I
do not think there is an easy way to do this and probably never will
be.
1) AFAIK there is no (central) server available which hosts sites by default.
2) As stated on above page, there
Hi,
Out of curiosity, what's a par packaging? The only links I found on the Web
talks about perl, are they perl archive or so?
Just had a quick at https://maven.apache.org/plugins/ and didn't find
anything related to par. I've personnally never heard of it. Can you
provide us with more details?
Eric,
when you use the maven-release-plugin a property performRelease is set
during release:perform.
So define in the pluginManagement section a definition for the
maven-failsafe-plugin in your build section:
build
pluginManagement
plugins
plugin
Yep, that is one of the many pages I had looked at also. I was also
considering the stage-deploy target as I think that actually does have a
property for URL, but was not sure what other side affects it would have
since it might be deemed a mis-use of that feature. I need to
understand it
Google has more information on the par plugin if you look there. From
what I can see, the Apache Maven dev team has nothing to do with this
plugin.
Instead I think you should look at the Codehaus Mojo project, specifically:
http://mojo.codehaus.org/jboss-packaging-maven-plugin/par-mojo.html
I
18 matches
Mail list logo
