Release Plugin does not use Parent POM?

2008-10-29 Thread von Janowsky, Simon
  Hi all,
when executing the release plugin 2.0-beta-7, will the profiles
i have in my parent pom for that pom executed also?


__
After I execute

'mvn release:prepare -Pbuild-rel -Dusername= -Dpassword=
-DignoreSnapshots=true'

and

'mvn release:perform -Dgoals=deploy -Pbuild-rel'

I get the following error:

[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] Failed to configure plugin parameters for:
org.apache.maven.plugins:maven-deploy-plugin:2.3

check that the following section of the pom.xml is present and correct:

distributionManagement
  !-- use the following if you're not using a snapshot version. --
  repository
idrepo/id
nameRepository Name/name
urlscp://host/path/to/repo/url
  /repository
  !-- use the following if you ARE using a snapshot version. --
  snapshotRepository
idrepo/id
nameRepository Name/name
urlscp://host/path/to/repo/url
  /snapshotRepository
/distributionManagement

Cause: Class 'org.apache.maven.artifact.repository.ArtifactRepository'
cannot be instantiated


Now what concerns me is the following output during the prepare and the
perform goal:

   [INFO] Executing: mvn clean verify --no-plugin-updates -P
build-dev,build-dev
   [INFO] Executing: mvn deploy --no-plugin-updates -P build-dev,build-dev
-DperformRelease=true -f pom.xml

and this line in release.properties:

   exec.additionalArguments=-P build-dev,build-dev


build-dev is a profile in my settings.xml
__


Why isn't the build-rel profile added to the POM?

When I add the profile build-rel manually into the child POM,
although present in the parent POM, the deploy works fine.



Hope someone can help me with this,
Simon.




smime.p7s
Description: S/MIME cryptographic signature


AW: Release Plugin does not use Parent POM?

2008-10-29 Thread von Janowsky, Simon
-Darguments=-Pbuild-rel worked great.

Thanks a lot :-)
Simon. 


-Ursprüngliche Nachricht-
Von: Wendy Smoak [mailto:[EMAIL PROTECTED] 
Gesendet: Mittwoch, 29. Oktober 2008 15:29
An: Maven Users List
Betreff: Re: Release Plugin does not use Parent POM?

On Wed, Oct 29, 2008 at 6:15 AM, von Janowsky, Simon
[EMAIL PROTECTED] wrote:

 After I execute
...
'mvn release:perform -Dgoals=deploy -Pbuild-rel'
...
 Why isn't the build-rel profile added to the POM?

I think you'll need to use the 'arguments' parameter to pass it through to
the Maven execution.

http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html

Or you could rename your profile 'release' and it will be automatically
activated (unless you say -DuseReleaseProfile=false).

--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




smime.p7s
Description: S/MIME cryptographic signature


maven release plugin, set scm from commandline

2008-10-29 Thread von Janowsky, Simon
  Hi all,
another relase plugin question,
before calling the release:perform goal i have to add a scm element to the
POM
and commit the POM.

scm

connectionscm:svn:svn://subversionserver/repo/project/tags/builds/1.0.0-SN
APSHOT/BUILD-2/connection
/scm

Is there a way to add the scm from the command line without altering the
POM?

Best regards,
Simon.


smime.p7s
Description: S/MIME cryptographic signature


AW: maven release plugin, set scm from commandline

2008-10-29 Thread von Janowsky, Simon
 
Those tags represent automatic builds of the release branch RB-1.0.0.
They are tagged by our CI-System (Hudson). So we don't build the release
from the trunk, but from a stable build that the Hudson tagged.

We can live with adding that scm element, but perhaps that was a way to
omit that.

Thanks a lot for your help,
Simon.

-Ursprüngliche Nachricht-
Von: Wendy Smoak [mailto:[EMAIL PROTECTED] 
Gesendet: Mittwoch, 29. Oktober 2008 17:34
An: Maven Users List
Betreff: Re: maven release plugin, set scm from commandline

On Wed, Oct 29, 2008 at 9:19 AM, von Janowsky, Simon
[EMAIL PROTECTED] wrote:

 another relase plugin question,
 before calling the release:perform goal i have to add a scm element 
 to the POM and commit the POM.

 scm
 connectionscm:svn:svn://subversionserver/repo/project/tags/builds/1.
 0.0-SN
 APSHOT/BUILD-2/connection
 /scm

It's unusual to have a snapshot under a tag.  The release process normally
creates the tag for you, starting from trunk or a branch, and once it's
tagged it doesn't change.

 Is there a way to add the scm from the command line without altering 
 the POM?

Not that I know of... you can set the tagBase, but the scm info is expected
to be in the pom.

Maybe if you describe your use case someone will have a better suggestion?

--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




smime.p7s
Description: S/MIME cryptographic signature


AW: skip tests in a single goal

2008-10-15 Thread von Janowsky, Simon
Hi Martin,
thanks for your answer, that helped a bit, now I have a build section and a
reporting section in my pom with
this configurations (see below), works fine, but the problem really was is
that my cobertura plugin which by default,
executes the tests again...I didn't realize that before...

Anyone knows howto avoid this?
When setting 
configuration
skipTeststrue/skipTests
/configuration
in the build section

or -Dmaven.test.skip=true

ALL tests are skipped, in the deploy goal and the site goal.

Greetings,
Simon.





build
...
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-report-plugin/artifactId
version2.4.3/version
/plugin 
...
/build

AND

reporting
...
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-report-plugin/artifactId
version2.4.3/version
reportSets
reportSet
reports
reportreport-only/report
/reports
/reportSet
/reportSets
/plugin
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdcobertura-maven-plugin/artifactId
version2.2/version
configuration
formats
formatxml/format
formathtml/format
/formats
/configuration
/plugin
...
/reporting



-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Baptiste
MATHUS
Gesendet: Mittwoch, 15. Oktober 2008 13:23
An: Maven Users List
Betreff: Re: skip tests in a single goal

Or maybe configuring the report report-only (corresponding to mvn
surefire-report:report-only) could do the trick. It was specifically
developed to workaround the double execution :
http://maven.apache.org/plugins/maven-surefire-report-plugin/report-only-moj
o.html

Cheers.

2008/10/15 aXXa [EMAIL PROTECTED]


 Have you tried
 $mvn deploy -Dmaven.test.skip=true

 -Martin


 von Janowsky, Simon wrote:
 
Hello,
  on our CI-Server (Hudson) we execute three goals per module: clean, 
  deploy, site.
  Now the tests get executed twice, which is a correct behaviour, but 
  can cost lots of time...
  Is there a way to disable tests for one single goal?
 
  Greetings,
  Simon.
 
 
 

 --
 View this message in context:
 http://www.nabble.com/skip-tests-in-a-single-goal-tp19990895p19991066.
 html Sent from the Maven - Users mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




--
Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un
castor !



smime.p7s
Description: S/MIME cryptographic signature


AW: skip tests in a single goal

2008-10-15 Thread von Janowsky, Simon
Yes, but then all tests in all goals will get skipped


-Ursprüngliche Nachricht-
Von: aXXa [mailto:[EMAIL PROTECTED] 
Gesendet: Mittwoch, 15. Oktober 2008 12:48
An: users@maven.apache.org
Betreff: Re: skip tests in a single goal


Have you tried
$mvn deploy -Dmaven.test.skip=true

-Martin


smime.p7s
Description: S/MIME cryptographic signature


AW: trunk/tags/branches: root vs. project level

2008-10-15 Thread von Janowsky, Simon
  Hi Stefan,
we use one repository per project, and within the project there
are several modules and all of them have a trunk/branches/tags directory.
Our structure is like this:

repository project 1:

   module1/branches
   module1/tags
   module1/trunk/pom.xml

   module2/branches
   module2/tags
   module2/trunk/pom.xml

repository project 2:

   module1/branches
   module1/tags
   module1/trunk/pom.xml

   module2/branches
   module2/tags
   module2/trunk/pom.xml


With kind regards,
Simon von Janowsky



-Ursprüngliche Nachricht-
Von: Stefan Fritz [mailto:[EMAIL PROTECTED] 
Gesendet: Mittwoch, 15. Oktober 2008 10:49
An: Maven Users List
Betreff: trunk/tags/branches: root vs. project level

Hi all,

we are in the process of restructuring a subversion repository and
Mavenize all projects.
The main discussion at the moment is whether to have trunk/tags/branches on
the root level or once per project.

root:
trunk/project1/pom.xml
trunk/project2/pom.xml
branches/branch1/project1/pom.xml

project level
project1/trunk/project1/pom.xml
project1/branches/branch1/project1/pom.xml

root level:
pro:
all branch/patch related projects in one location
easy to navigate
easy to update
cons:
 does mvn release:branch work ?
 mergin can get hard if somebody commits at root level

project level.
pro:
 easy to work with mvn release
 merging should be easy
cons:
 complex for scenarios where you have to deal with multiple
projects at once

Would be curious about your opinions/comments!

Thanks
Stefan


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




smime.p7s
Description: S/MIME cryptographic signature


skip tests in a single goal

2008-10-15 Thread von Janowsky, Simon
  Hello,
on our CI-Server (Hudson) we execute three goals per module: clean, deploy,
site.
Now the tests get executed twice, which is a correct behaviour, but can cost
lots of time...
Is there a way to disable tests for one single goal?

Greetings,
Simon.


smime.p7s
Description: S/MIME cryptographic signature


Problem with Maven, Hudson, Archiva - Builds take very long

2008-08-26 Thread von Janowsky, Simon
Hello, 
I am having a Problem with a CI-System. We use Maven with Hudson and
Archiva. 
The Archiva is configured with two repository groups (both virtualize
several proxy connectors and repositories). 
One is for dependencies, the other for plugins. 
In Hudson the build goal is the following: mvn -Pbuild-int clean deploy site

Now for some reason, some builds always hang a long time (up to 40 Minutes)
after 
the Dependencies Report is generated. Here a excerpt from the maven
output... 
Why is it that the Repository Url is blacklisted? 

__ 
POM 

__ 
profile 
idbuild-int/id 
build 
plugins 
plugin 
groupIdorg.apache.maven.plugins/groupId 
artifactIdmaven-compiler-plugin/artifactId 
configuration 
source1.6/source 
target1.6/target 
encodingISO-8859-1/encoding 
debugfalse/debug 
/configuration 
/plugin 
/plugins 
/build 
repositories 
repository 
!-- Repository Group with all Artifacts -- 
idrepositories.all/id 
nameAll Artifacts Repository Group/name 
url 
dav:http://archiva:8080/archiva/repository/repositories.all 
/url 
/repository 
/repositories 
pluginRepositories 
pluginRepository 
!-- Repository Group with all Plugins -- 
idplugin-repositories.all/id 
nameAll Plugins Repository Group/name 
url 
dav:http://archiva:8080/archiva/repository/plugin-repositories.all 
/url 
/pluginRepository 
/pluginRepositories 
distributionManagement 
!-- snapshots deployed by CI Server -- 
snapshotRepository 
idarchiva.snapshots/id 
namesnapshot repository/name 
url 
dav:http://archiva:8080/archiva/repository/snapshots 
/url 
/snapshotRepository 
/distributionManagement 
/profile 

__ 
Maven OUTPUT, the session: Opened Message go one like forever 

__ 

[INFO] Generating Dependencies report. 
[DEBUG] . 
[DEBUG] . 
[DEBUG] . 
[DEBUG] . 
[DEBUG] . 
[WARNING] The repository url
'dav:http://archiva:8080/archiva/repository/repositories.all' is invalid -
Repository 'repositories.all' will be blacklisted.
http://dist.codehaus.org/ - Session: Opened 
http://dist.codehaus.org/ - Session: Disconnecting 
http://dist.codehaus.org/ - Session: Disconnected
http://people.apache.org/maven-snapshot-repository/ - Session: Opened 
http://people.apache.org/maven-snapshot-repository/ - Session: Disconnecting

http://people.apache.org/maven-snapshot-repository/ - Session: Disconnected
http://repo1.maven.org/maven2 - Session: Opened 
http://repo1.maven.org/maven2 - Session: Disconnecting 
http://repo1.maven.org/maven2 - Session: Disconnected
http://dist.codehaus.org/ - Session: Opened 
http://dist.codehaus.org/ - Session: Disconnecting 
http://dist.codehaus.org/ - Session: Disconnected
http://people.apache.org/maven-snapshot-repository/ - Session: Opened 
http://people.apache.org/maven-snapshot-repository/ - Session: Disconnecting

http://people.apache.org/maven-snapshot-repository/ - Session: Disconnected
http://repo1.maven.org/maven2 - Session: Opened 
http://repo1.maven.org/maven2 - Session: Disconnecting 
http://repo1.maven.org/maven2 - Session: Disconnected
http://dist.codehaus.org/ - Session: Opened 
http://dist.codehaus.org/ - Session: Disconnecting 
http://dist.codehaus.org/ - Session: Disconnected
http://people.apache.org/maven-snapshot-repository/ - Session: Opened 
http://people.apache.org/maven-snapshot-repository/ - Session: Disconnecting

http://people.apache.org/maven-snapshot-repository/ - Session: Disconnected
http://repo1.maven.org/maven2 - Session: Opened 
http://repo1.maven.org/maven2 - Session: Disconnecting 
http://repo1.maven.org/maven2 - Session: Disconnected
http://dist.codehaus.org/ - Session: Opened 
http://dist.codehaus.org/ - Session: Disconnecting 
http://dist.codehaus.org/ - Session: Disconnected 
.. 
. 
.. 

__ 
Help would be really appreciated. Thanks a lot, 
Simon. 



smime.p7s
Description: S/MIME cryptographic signature