Hi,
If I use scm tag inside my project like this
scm:svn:https://${svn.username}:${passwo...@server_name/path_to_repository
while in my ~/.m2/settings.xml I have the substitution values set as
properties,
then I release the project with maven-release-plugin,
I get commited in Subversion a
, Kiss Tibor kiss.ti...@gmail.com wrote:
Hi,
If I use scm tag inside my project like this
scm:svn:https://${svn.username}:${passwo...@server_name
/path_to_repository
while in my ~/.m2/settings.xml I have the substitution values set as
properties,
then I release the project with maven
to). As a user I would appreciate
that.
/Anders
On Mon, Dec 6, 2010 at 13:46, Kiss Tibor kiss.ti...@gmail.com wrote:
Yes, that issue.
Pasing -Dusername= .. -Dpassword= .. params into the command line while
calling release plugin will suffice for me.
Thank you!
Tibor
On Mon, Dec 6
Hi,
With similar issues I fought in july.
Unfortunately Eclipse does not have individual classpath for just testing,
therefore if the .classpath file has the test directories on sources, also
WTP will put in .settings/org.eclipse.wst.common.component too. and when the
dependencies are resolved
I would like to find or write a maven plugin which once declared in the
company's parent pom, all the builds descending from that, will print out on
the console some information about the packaged and attached artifacts. Here
are some sample patterns.
For JAR:
HERE_YOU_CAN_FIND:
While upgrading from Maven 2.0.10 to 2.1.0 it seems that I cannot deploy the
most simple artifact to my nexus repo if I am using IBM jdk 1.4.2.
In Maven 2.1.0 running on the following IBM jdk
On Linux I have
java version 1.4.2
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
Hi Oskar!
I use the same scheme as your second scenario and in MY_SYSTEM_GLOBAL
(inherits global) I have
buildpluginManagement section with all the plugins configured for jar,
ejb, war, ear packaging types plus specialities done by was6 plugin and of
course all the stack of checkstyle, pmd,
