How to make release:prepare ask for password?

2012-09-21 Thread Magne Nordtveit
How can I make the release-plugin ask for a password when it needs it, rather 
than having to either a) provide it as a property when building, or b) putting 
it in a settings.xml file or equivalent. I don't like the fact that I have to 
have the password stored in a batch history file somewhere, or in a 
settings.xml file everybody knows where is...

Thanks,
--
Magne Nordtveit
Senior Systems Engineer

Mobile: +47 957 20 187

Offshore Simulator Centre AS
Visiting address: Borgundvegen 340, N-6009, Aalesund, Norway
Postal address:   Borgundvegen 340, N-6009, Aalesund, Norway
www.offsim.nohttp://www.offsim.no/



RE: How to make release:prepare ask for password?

2012-09-21 Thread Magne Nordtveit
That doesn't really answer my question though - that's just a replacement of a 
plain text password by an encrypted one. The value of that isn't really high 
when it requires the master password to be stored in a different file IMHO, but 
that's a different discussion all together. I want to be asked for password 
when one is required - that way NO passwords are stored longer than they have 
to.

Magne

-Original Message-
From: Aliaksei Lahachou [mailto:aliaksei.lahac...@gmail.com] 
Sent: Friday, 21 September, 2012 11:58
To: Maven Users List
Subject: Re: How to make release:prepare ask for password?

Hi,

you can encrypt passwords in settings.xml:
http://maven.apache.org/guides/mini/guide-encryption.html.


Regards,
htfv (Aliaksei Lahachou)


On Fri, Sep 21, 2012 at 11:52 AM, Magne Nordtveit m...@offsim.no wrote:

 How can I make the release-plugin ask for a password when it needs it, 
 rather than having to either a) provide it as a property when 
 building, or
 b) putting it in a settings.xml file or equivalent. I don't like the 
 fact that I have to have the password stored in a batch history file 
 somewhere, or in a settings.xml file everybody knows where is...

 Thanks,
 --
 Magne Nordtveit
 Senior Systems Engineer

 Mobile: +47 957 20 187

 Offshore Simulator Centre AS
 Visiting address: Borgundvegen 340, N-6009, Aalesund, Norway
 Postal address:   Borgundvegen 340, N-6009, Aalesund, Norway
 www.offsim.nohttp://www.offsim.no/



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



RE: How to make release:prepare ask for password?

2012-09-21 Thread Magne Nordtveit
That puts us back to having the password stored in some bash history file, in 
plain text... Looks like I might have to put in for a feature request. Just 
have to figure out where to put it :-P

Magne

-Original Message-
From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf Of 
Anders Hammar
Sent: Friday, 21 September, 2012 12:58
To: Maven Users List
Subject: Re: How to make release:prepare ask for password?

Don't think you can have it ask for the password, but you can provide it as a 
Java (system) property on command-line.
mvn release:prepare -Dpassword=blabla

/Anders

On Fri, Sep 21, 2012 at 11:52 AM, Magne Nordtveit m...@offsim.no wrote:
 How can I make the release-plugin ask for a password when it needs it, rather 
 than having to either a) provide it as a property when building, or b) 
 putting it in a settings.xml file or equivalent. I don't like the fact that I 
 have to have the password stored in a batch history file somewhere, or in a 
 settings.xml file everybody knows where is...

 Thanks,
 --
 Magne Nordtveit
 Senior Systems Engineer

 Mobile: +47 957 20 187

 Offshore Simulator Centre AS
 Visiting address: Borgundvegen 340, N-6009, Aalesund, Norway
 Postal address:   Borgundvegen 340, N-6009, Aalesund, Norway
 www.offsim.nohttp://www.offsim.no/


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: How to know programatically the SNAPSHOT version

2008-10-02 Thread Magne Nordtveit
On Wednesday 24 September 2008 18:42:27 mateamargo wrote:
 I have setted the version to 1.0-SNAPSHOT, but I need to know what's the
 current value. Is there a way to know that using any Maven API? or maybe
 generating a file after compiling?

 Thanks.

What you can do, is to perform resource filtering on a text file you package 
into the jar, and then read this when querrying for the version. This is what 
we do for a number of our software, and it works like a charm. (Check [1] if 
you are unsure about what i mean)

If you want to include buildnumber, i think there is a build number generating 
maven plugin you can use. I think i have seen something like that earlier.

Magne

[1] - http://maven.apache.org/plugins/maven-resources-plugin/
-- 
Magne Nordtveit [EMAIL PROTECTED]
Systems Engineer
Offshore Simulator Centre AS
http://www.offsimcentre.no


signature.asc
Description: This is a digitally signed message part.


Re: AW: Updating pom versions without using release plugin

2008-09-18 Thread Magne Nordtveit
What you CAN do, is perform a release:branch and then just delete the branch. 
Abit messy, but saves you the time of manually doing it. If you have multiple 
sub projects, that can save you loads of time.

But your wish has my vote ;-)

Magne
-- 
Magne Nordtveit [EMAIL PROTECTED]
Systems Engineer
Offshore Simulator Centre AS
http://www.offsimcentre.no


signature.asc
Description: This is a digitally signed message part.


Re: mvn exec:java is giving error

2008-07-29 Thread Magne Nordtveit
On Tuesday 29 July 2008 02:24:10 Abhishek Sanoujam wrote:
---8---
 $ mvn exec:java -Dexec.mainClass=simpleproject.App
---8---
 plugin 'org.apache.maven.plugins:maven-exec-plugin' does not

Maven looks for org.apache.maven.plugins: if you don't specify a groupid for 
the plugin you want to execute.

---8---
 $ mvn org.codehaus.mojo:exec-maven-plugin:1.1:java
 -Dexec.mainClass=simpleproject.App

 The above works.
---8---

You need to add a plugin group to your settings.xml file. Go to your 
~/.m2/settings.xml and add the following there:

pluginGroups
pluginGrouporg.codehaus.mojo/pluginGroup
/pluginGroups

This tells Maven to look at org.codehaus.mojo: for plugins aswell.

Regards,
Magne

-- 
Magne Nordtveit [EMAIL PROTECTED]
Systems Engineer
Offshore Simulator Centre AS
http://www.offsimcentre.no


signature.asc
Description: This is a digitally signed message part.


Re: [m2] What triggers attempt to download from: http://cvs.apache.org/maven-snapshot-repository ?

2008-07-29 Thread Magne Nordtveit
On Wednesday 30 July 2008 04:50:50 Dan Rollo wrote:
 Hi Martin,

 Thanks for the reply, but I don't understand what you mean by comment
 it out? Where exactly would I comment it out?

 I don't have any settings.xml, nor any reference to that repo in my
 pom.xml. If the repo is referenced in one of the master poms,
 how/where can I comment that out?

 Dan
8---

You have it in your local repository ~/.m2/repository if you want to change 
it. A better way of doing it is to add a mirror/ block in your settings.xml 
file as Wendy suggested.

Magne
-- 
Magne Nordtveit [EMAIL PROTECTED]
Systems Engineer
Offshore Simulator Centre AS
http://www.offsimcentre.no


signature.asc
Description: This is a digitally signed message part.


Re: jar:jar with classifier runs twice.

2008-07-29 Thread Magne Nordtveit
On Tuesday 29 July 2008 15:00:12 [EMAIL PROTECTED] wrote:
 [...]
 build
plugins
  plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
executions
  execution
configuration
  classifier${environment.suffix}/classifier
/configuration
goals
  goaljar/goal
/goals
  /execution
/executions
  /plugin
/plugins
 /build

 profiles
profile
  idlive/id
  properties
environment.suffixliveConfig/environment.suffix
  /properties
/profile
profile
  idtest/id
  properties
environment.suffixtestConfig/environment.suffix
  /properties
/profile
 /profiles
 [...]


Try to pull it out of the execution

[...]
build
   plugins
 plugin
   groupIdorg.apache.maven.plugins/groupId
   artifactIdmaven-jar-plugin/artifactId
   configuration
 classifier${environment.suffix}/classifier
   /configuration
   goals
 goaljar/goal
   /goals
 /plugin
   /plugins
/build

I havn't tested it, but it should do the trick.

Magne
-- 
Magne Nordtveit [EMAIL PROTECTED]
Systems Engineer
Offshore Simulator Centre AS
http://www.offsimcentre.no

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



Continuum and Archiva mail address.

2008-07-22 Thread Magne Nordtveit
Hi!

I have  just set up Archiva and Continuum on the same Tomcat server, and its 
working beautifully (After setting the users-db to different directories... 
Doh!).

Only one thing remaining now, to make Archiva's mailing address be 
[EMAIL PROTECTED] and give it a name i.e Archiva Repository Manager, and the 
same with Continuum.

But I can't find out how to configure the sender...

-- 
Magne Nordtveit [EMAIL PROTECTED]
Systems Engineer
Offshore Simulator Centre AS
http://www.offsimcentre.no

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



Continuum + Tomcat: Not using settings.xml?

2008-07-22 Thread Magne Nordtveit
I have set up continuum in tomcat. It seems to be working good, but when i add 
a project with dependencies to internal jar files, continuum doesn't resolve 
the repositories specified in the maven/conf/settings.xml file...

I get a Missing artifact trying to build the POM. Check that its parent POM 
is available or add it first in Continuum. error message, and no usefull 
output from the logs either...

Hope somebody recognises my mistake :-)

Regards,
Magne
-- 
Magne Nordtveit [EMAIL PROTECTED]
Systems Engineer
Offshore Simulator Centre AS
http://www.offsimcentre.no

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



Re: prevent javadoc during release

2008-07-15 Thread Magne Nordtveit
On Mon, 2008-07-14 at 16:38 -0400, Kallin Nagelberg wrote:
 Is there a way to prevent javadoc from occuring during release? I would also
 like to prevent production of source JAR. Any ideas?

When releasing, try setting the useReleaseProfile property to false,
mvn release:perform -DuseReleaseProfile=false

This will disable the attachment of javadoc and sources.

Regards,
Magne 
-- 
Magne Nordtveit [EMAIL PROTECTED]
Systems Engineer
Offshore Simulator Centre AS
http://www.offsimcentre.no

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



Re: Odd warning in assembly plugin

2008-07-01 Thread Magne Nordtveit
On Mon, 2008-06-30 at 18:27 -0500, Kathryn Huxtable wrote:
 Correct. I have several Internet2 projects which are not currently in  
 any repository except my local one. They, in turn, have dependencies.
 
 Of these, only the Grouper project gives me the warning.
 
 -K, who will go over the Grouper and Signet poms with a fine-toothed  
 comb to see what, if any, differences there are.
I too get this warning, but only on projects that arn't originally Maven
projects. (Ant build which is deployed with a deploy:deploy-file
execution).
-- 
Magne Nordtveit [EMAIL PROTECTED]
Systems Engineer
Offshore Simulator Centre AS
http://www.offsimcentre.no

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



Re: How to generate POM for existed dependency?

2008-06-03 Thread Magne Nordtveit
On Tue, 2008-06-03 at 01:11 -0700, youhaodeyi wrote:
 I have downloaded some dependencies from remote repository into local
 repository. But some of them don't have pom file. How can I generate pom
 file for dependencies in local repository?

When you install it to your local repository, specify
-DgeneratePom=true. If the artifact is automatically downloaded to your
repository from another source (i.e. central) consider creating a
thirdparty repo inhouse and deploy it to that (the -DgeneratePom=true
should work for the deploy plugin aswell).
-- 
Magne Nordtveit [EMAIL PROTECTED]
Systems Engineer
Offshore Simulator Centre AS
http://www.offsimcentre.no/

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



Re: How to generate POM for existed dependency?

2008-06-03 Thread Magne Nordtveit
On Tue, 2008-06-03 at 01:42 -0700, youhaodeyi wrote:
 What do you mean by inhouse? Could you give more information on this?
 
What I mean is creating a company/private repository that you can deploy
own or thirdparty artifacts to.

Take a look at http://archiva.apache.org/ that might help you with that
part.

-- 
Magne Nordtveit [EMAIL PROTECTED]
Systems Engineer
Offshore Simulator Centre AS
http://www.offsimcentre.no/

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



Re: How to generate POM for existed dependency?

2008-06-03 Thread Magne Nordtveit


[EMAIL PROTECTED] wrote:
 
 I'm not sure why you'd bother doing this though. As far as I know the
 only effect would be to shut up warnings about trying to fetch pom.
 
 What dependencies (groupId, artifactId, version) don't have poms?
 

The times you have to download a jar from a third party project that 
ISN'T uploaded onto the maven central server. Then you would need 
to install it.

We do this with our third party APIs, the pom is used to add some 
additional information such as license and where it was downloaded 
from.

As a sidenote, I noticed when testing with the 2.1-SNAPSHOT that 
it actually required a pom on the artifacts that it downloads and
uses as dependency. Thats when i had to setup a pom for all our 
third party libraries. I don't know if this is a bug, or if it is actually 
required in the 2.1 release tho.

-- 
Magne Nordtveit [EMAIL PROTECTED]
Systems Engineer
Offshore Simulator Centre AS
http://www.offsimcentre.no/
-- 
View this message in context: 
http://www.nabble.com/How-to-generate-POM-for-existed-dependency--tp17618375p17621340.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]



Naming convention for multimoduled projects?

2008-05-22 Thread Magne Nordtveit
I'm just wondering, how do you name your artifacts in a large
multimoduled project to avoid having two modules with the same
artifact-id?

I am thinking in the lines of project-partofgroupid-descriptivename as
artifact-id. This would make the name of the final jar files (at least
more) unique and easily identified, but it might give some long
file-names...

I guess I'm just asking for suggestions here, or a pointer if it exists
a best-practise on it?

Cheers!
Magne
-- 
Magne Nordtveit [EMAIL PROTECTED]
Systems Engineer
Offshore Simulator Centre AS
http://www.offsimcentre.no/

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



Re: Naming convention for multimoduled projects?

2008-05-22 Thread Magne Nordtveit
On Thu, 2008-05-22 at 15:23 +0200, simon wrote:
 On Thu, 2008-05-22 at 15:02 +0200, Magne Nordtveit wrote:
  I'm just wondering, how do you name your artifacts in a large
  multimoduled project to avoid having two modules with the same
  artifact-id?
  
  I am thinking in the lines of project-partofgroupid-descriptivename as
  artifact-id. This would make the name of the final jar files (at least
  more) unique and easily identified, but it might give some long
  file-names...
  
  I guess I'm just asking for suggestions here, or a pointer if it exists
  a best-practise on it?
 
 Why not just set the groupId to something reasonable.
 
 If your company is acme.com, then the groupId should *start* with
 com.acme, but you can have any arbitrary number of parts after that.
 
 And presumably your modules have structured java package names so that
 the classnames don't collide. So why not model the groupId after the
 package in which the code for each module lives?
 
   com.acme.tractor.engine
   com.acme.tractor.chassis
   com.acme.steamroller
 
 IMO, that is nicer than embedding excessive structure into the
 artifactId.
 
 Regards,
 Simon
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 

Exactly.

But what happens when you have com.acme.tractor:common and
com.acme.steamroller:common if you for some reason need to have both
common-packages (ok, probably a bad example) as a dependency to another
project?

When running, wouldn't the classpath be set too
lib/common-1.0.jar:lib/common-1.0.jar? As far as I know, its only the
artifactId that gets put into the actual jar-file.

That's what i want to avoid before it happens and while our project is
still sub-100 modules.

Magne
-- 
Magne Nordtveit [EMAIL PROTECTED]
Systems Engineer
Offshore Simulator Centre AS
http://www.offsimcentre.no/

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



Re: [SURVEY] How does your team retrieve artifacts?

2008-05-21 Thread Magne Nordtveit
 [X] Our team uses HTTP to retrieve our artifacts

Magne

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